I didn't know that -- thanks for the info. But in some cases, e.g. running in a text editor running Python, a Csound process has to be killed with a signal 9, which probably would cause the header to be rewritten, so -R is still useful in those cases. Regards, Mike On Thu, Jan 15, 2009 at 11:33 AM, Victor Lazzarini wrote: > Btw, these days Csound does close the file and writes the full header after > ctrl-C. > > At 16:05 15/01/2009, you wrote: >> >> It's primarily for insurance - if the program or the whole computer >> crashes (or even if for any reason you have to abort recording with Ctrl-C >> or something), there is a complete file header (i.e. with length >> information) so what remains on disk is a valid wave or aiff file and thus >> "safe" and immediately playable. When the failure is at the 59th minute of >> an hour long recording, such things matter, if only for peace of mind. >> >> Those who know about such things can of course always hack an incomplete >> header afterwards to rescue the recording, and may then elect to forgo the >> belt and braces of -R in order to reduce disk thrashing. Or eschew >> formatted files altogether and record to a "Raw" file. >> >> Richard Dobson >> >> >> Jason Timm wrote: >>> >>> Why would I want to (-R) continually rewrite header while writing >>> soundfile (WAV/AIFF)? >>> J. >> >> >> >> >> Send bugs reports to this list. >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >> csound" > > Victor Lazzarini > Music Technology Laboratory > Music Department > National University of Ireland, Maynooth > > > Send bugs reports to this list. > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" > -- Michael Gogins Irreducible Productions Michael dot Gogins at gmail dot com