|
I can't reproduce this in a simple test file, so it could be user error, but
I'm wondering if anyone else has encountered anything similar.
I'm constructing a piece using #define statements for individual phrases,
and repeating the phrases using b statements. At the end of the first
section, I want to place an s statement and then start over with a time
value of 0 (so as to avoid having large values for subsequent b statements,
and possibly extra editing as a result).
What I'm finding is that there is a short gap before the beginning of the
second section. I've verified that there are no note events "hanging over"
the end of the first section, so the s statement should operate as intended.
This works as desired, metrically:
b 33.5
$BASSTHROB_03
...but this doesn't:
s 33.5
t 0 80
$BASSTHROB_03
In the first case, the end of the preceding phrase is followed by the new
phrase at the expected time. But the second case, there's a perceptible gap
of about half a beat before the phrase defined in the BASSTHROB_03 macro
starts. This is during real-time playback in QuteCsound 0.5; I haven't yet
examined the disk file output.
The gap is the same, whether I advance the score using an a statement in
order to listen starting at beat 26, or whether I start playback at beat 0.
So I know the a statement is not getting into the act.
As I said, I can't reproduce it in a simple test file. Can anyone suggest
what I may be doing wrong? Thanks!
--Jim Aikin |