Well, they should all work the same whether DSP is on or off. THis isn't always true in reality - in particular, tilde objects don't get to find out their sample rate until DSP goes on. There are probably other situations as well. This one about writesf~ is probably a bug in the object, nothing deeper. But writesf~ is delicate enough that I'm afraid to monkey with it for a "patch" release, so will wait until later to try ti fix this.
cheers Miller
On Sun, Dec 21, 2003 at 07:39:03PM -0500, Larry Troxler wrote:
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
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list