Subject: Re: [ecasound] ecasound syntax
From: Jeremy Hall (email@example.com)
Date: Fri Jul 13 2001 - 21:37:42 EEST
I second this. My conventions want to have different extentions to a file
depending on what stage of processing it is in, but I have to use this
stupid .raw, .wav, etc to get it right. VERY ANNOYING!
In the new year, toby wrote:
> The way I understand it, the output file type
> is specified by the extension of the file name.
> If this is so, then I would propose that there
> are shortcomings to this. I don't happen to
> save my wave files with a .wav extension, and
> so I have to go through gymnastics to get
> ecasound to recognize them:
> ln -s $1 /tmp/$$.wav
> ecasound /tmp/$$.wav
> rm /tmp/$$.wav
> and things like that. Also, it leaves me with
> no opportunity to specify a header on data that
> goes to stdout.
> If my take on the situation is correct, couldn't
> ecasound read the file type from the header, and
> could there not be a flag to specify file type as
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <firstname.lastname@example.org>.
-- To unsubscribe send message 'unsubscribe' in the body of the message to <email@example.com>.
This archive was generated by hypermail 2b28 : Fri Jul 13 2001 - 21:37:55 EEST