Subject: Re: [ecasound] chainsetups
From: Roy Cutler (firstname.lastname@example.org)
Date: Fri Mar 23 2001 - 22:41:21 EET
That is terrific. That makes it just so much more powerful. I would think
this should be loudly trumpeted in the docs. You could create large,
remembered mixes with many variations, I should think.
I am having just one problem at this point and that is that these temp files
that are created by cs-edit are read-only. I don't understand why.
On Friday 23 March 2001 11:19, you wrote:
> On Friday 23 March 2001 15:11, you wrote:
> > I have been working with ecasound for about a week (the synchro problem
> > is fixed!) and after a lot of typing and backscrolling on the command
> > line I came across references to chainsetup files (*.ecs). How do these
> > work? Do I write chainsetups in a text editor and then save them as *.ecs
> > files (i.e., mix1.ecs) using the same format as the command line? If that
> > is so, how do I then invoke them?
> > Here is an example of mix1.ecs:
> > ecasound -r -b:2048 \
> > -a:1 -i drums.wav \
> > -a:2 -i guitar1.wav \
> > -a:3 -i leadvocal.wav \
> > -a:4 -i rguitar-dis.wav \
> > -a:5 -i piano.wav \
> > -a:all -o /dev/dsp
> > Invoking this with "ecasound -s:mix1.ecs" sets the buffer and then dumps
> > me out with an error. Just curious what part of this I've got wrong.
> > thanks, Roy
> You only want to include the chainsetup so remove ecasound -r -b:2048 from
> the file mix1.ecs. Then type ecasound -r -b:2048 -s:mix1.ecs
-- Roy Cutler email@example.com -- To unsubscribe send message 'unsubscribe' in the body of the message to <firstname.lastname@example.org>.
This archive was generated by hypermail 2b28 : Sat Mar 24 2001 - 05:42:31 EET