hmm, it seems that writesf~ only works correctly for me when the "open"
message is sent when DSP is already on.
For example, this works:
; dsp on
( send open message to writesf~)
(send start message to writesf~)
(wait some time)
(send stop message to writesf~)
(wait some time)
; dsp off
.. but this doesn't (starting with dsp off) :
(send open message to writesf~)
; dsp on
(send start message to writesf~)
(wait some time)
(send stop message to writesf~)
(wait some time)
; dsp off
In the second case, a file does get created, but it captures only a portion of
the total recording time.
I Haven't looked through the source yet to trace this, but this raises a
larger issue I think: how do we know which messages on objects work with dsp
off, and which of them require dsp on?
Best Regards
Larry Troxler