c-mute with argument interrupts engine

Dominic Sacré <[email protected]> Thu, 08 May 2014 01:57:09 +0200
Newsgroups gmane.comp.audio.ecasound.general
Message-ID <[email protected]>
Hi,

When I issue a c-mute command with an argument (on, off or toggle), 
audio processing of all chains is interrupted, and debug output suggests 
that the entire chainsetup is being reinitialized.
Running c-mute with no arguments, on the other hand, works just as 
expected, toggling the muted state of the selected chain without 
affecting anything else. I'm using ecasound 2.9.1.

Is this a bug, or is there any intentional difference between the 
behavior of 'c-mute' and 'c-mute toggle'? Any idea how to fix this, so 
that I can use 'c-mute on' or 'c-mute off' without dropouts on other chains?


Thanks,

Dominic

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ecasound-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecasound-list