RE: [ecasound] Bug with multiple loop devices

From: Stuart Allie <Stuart.Allie@email-addr-hidden>
Date: Thu Apr 27 2006 - 01:28:06 EEST

> First I loaded my chain setup (below), then applied some
> effects via IAM through Brad Bowmen's Audio::Ecasound module,
> issued a 'start', then sent various positional commands while
> the transport was running. The transport didn't respond to
> these commands.
> I then used 'cs-save-as' to record the engine's state. To
> my surprise, this Ecasound-generated chain setup was
> invalid, and turns out to differ from the original.

This is a bug (at least in the last version of the code I have.) By
coincidence I noticed this only yesterday - I've been away from
recording for a few months. I have a patch at home that I'll send to the
list tomorrow. The bug causes any chainsetup with loop devices to
incorrectly print inputs as outputs.

I've also got a patch to fix the issue where ladspa plugins are saved
using their id number rather than their name. Unless that's already been
fixed... I really must get the latest code :)

> (To the question 'why have a second loopback device at all?'
> my answer is that multiple devices may want the mixed
> output, for example monitoring the mixed signal while
> writing the mixdown output to disk.)

That's what I use them for too. Very useful :)

I'll post the patch tomorrow.



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Ecasound-list mailing list
Received on Thu Apr 27 12:15:06 2006

This archive was generated by hypermail 2.1.8 : Thu Apr 27 2006 - 12:15:06 EEST