| I start my csd with ctcsound. Around 5 seconds running I trigger a call
to setScoreOffsetSeconds(12):
The score pointer goes to 12 seconds, and continues playing as described
in the comment for setScoreOffsetSeconds.
The output shows:
time advanced 152112.000 beats by score request
But when I do the same and trigger a call to setScoreOffsetSeconds(1) -
so going back in time: the pointer goes to 1 second but the sound stops!
Also, this is printed in the output:
end of section 1 sect peak amps: 0.59167 0.03978
SECTION 1:
time advanced 44100.000 beats by score request
1) this is not beats, but the number of samples!
2) why does setScoreOffsetSeconds behave differently when I go forward
or back in time?
3) has this been tested at all? If so, what is the expected result?
4) the following functions from ctcsound add to the confusion:
def setScoreOffsetSeconds(self, time):
"""Csound score events prior to the specified time are not
performed.
Performance begins immediately at the specified time (real-time
events
will continue to be performed as they are received). Can be used by
external software, such as a VST host, to begin score performance
midway through a Csound score, for example to repeat a loop in a
sequencer, or to synchronize other events with the Csound score.
"""
libcsound.csoundSetScoreOffsetSeconds(self.cs, MYFLT(time))
def rewindScore(self):
"""Rewinds a compiled Csound score.
It is rewinded to the time specified with setScoreOffsetSeconds().
"""
libcsound.csoundRewindScore(self.cs)
It looks like rewindScore is needed after setScoreOffsetSeconds, but
when I do that, the section also ends when I advance the time...
Richard
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here |