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

From: rocco <rocco556@email-addr-hidden>
Date: Fri Aug 16 2013 - 22:52:56 EEST

On Sun, 4 Aug 2013, rocco wrote:
>> 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

On 08/10/2013 11:29 AM, Kai Vehmanen wrote:
> 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
> objects.

Oh good... I was planning on asking you what is the difference between
the various methods of silencing a chain. I will just use c-muting. I
will use -gm in cases when I need to stop writing to a file.


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 Sat Aug 17 08:15:07 2013

This archive was generated by hypermail 2.1.8 : Sat Aug 17 2013 - 08:15:08 EEST