Hi,
don't ask how/why I decided to handle this now :) (after 5 years), but
nevertheless, read on...
On Fri, 12 Dec 2003, Jan Weil wrote:
> The question remains: If I set the buffering mode explicitly (using
> cs-option) why isn't the status of the chainsetup affected immediately?
Yes, this indeed was a bug. If you explicitly set a buffering mode (e.g.
'cs-option -B:rt'), but did not connect the chainsetup (which would cause
ecasound to calculate the final buffering params), the output of
"cs-status" was essentially stale.
I now fixed this in the development git tree, and the bugfix will be
part of 2.4.7. Thanks for the bugreport! :)
-- links, my public keys, etc at http://eca.cx/kv ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ecasound-list mailing list Ecasound-list@email-addr-hidden https://lists.sourceforge.net/lists/listinfo/ecasound-listReceived on Tue Mar 4 20:15:15 2008
This archive was generated by hypermail 2.1.8 : Tue Mar 04 2008 - 20:15:15 EET