Dear list,
I just noticed another kind of bug in writesf~ when handling 'open'
'start' and 'stop' messages manually without care : when an 'open' message is received while writing a sound file (without sending a prior 'stop'), the previous sound file is not closed before the new file is opened. With this kind of behaviour, data are of course recorded on the hard drive, but the size of the 'data' chunck (in case of a 'WAV' file) remains zero, and has to be manually changed in the binary file so that the recorded sound file can be read by another software (and PD itself). Of course, user, patches and abstractions should use the messages in the right order, but closing the current sound file before performing a new 'open' would be a very nice feature.
Best regards,
Emmanuel Rio
OS : Windows XP PD : pd-0.37-0.msw