Re: [ecasound] -gm not working correctly with loop device

From: Kai Vehmanen <kvlists@email-addr-hidden>
Date: Sat Aug 10 2013 - 21:29:55 EEST


On Sun, 4 Aug 2013, rocco wrote:

> I see you're looking to release 2.9.1. Any chance you can resolve this
> bug so it can be included in 2.9.1? My front end relies on this to work
> properly.
> Seems that when -gm is used to turn a chain 'on' or 'off', it works
> correctly when the audio is sent directly out to jack,system. But when
> the audio is run through a loop device, it turns 'off' correctly, but

ok, I think what the rootcause is.

When a ecasound gate is closed, no samples are passed through. The loop
object will treat this as an end-of-stream condition and no samples are
provide to JACK anymore after this.

Now, while this needs to be fixed, I wonder if you should use -ea:x or
c-muting instead for your frontend instead? Gates are useful when feeding
streams into files (to ensure noting is written to a file when gate is
closed), but when interfacing with JACK this is not as important (ecasound
always needs to provide some data to JACK, even if it's just silence).

With -ea:x instead of -gm:x (-ea:0 to mute, -ea:100 to unmute), you could
mute chains and this would work throgh loop objects already now.
Alternatively you can also use c-muting, which will also work with loop

Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
Ecasound-list mailing list
Received on Sun Aug 11 00:15:02 2013

This archive was generated by hypermail 2.1.8 : Sun Aug 11 2013 - 00:15:02 EEST