> The setup you are posting does not require JACK at all,
> and if you do it using ALSA, Ecasound may respond to
> xruns more comprehensively.

Sorry, the real command line is:

ecasound -c -dd -i Bass.wav -o jack,system -G:jack,eca,recv -z:xruns

> I can speculate that Ecasound will only respond to xruns
> that it generates. Probably Ecasound is not aware of xruns
> occurring elsewhere in the JACK graph.

ardour has the option to stop if an xrun is encountered. I thought that ecasound would work the same way.

Is there a way to know which process in the graph generates an xrun ?

BR,
Laurent


2014-07-31 1:11 GMT+02:00 Joel Roth <joelz@pobox.com>:
éléandar wrote:
> Hello,
>
> i'm using ecasound 2.9.1 and i'm using the following command line:
>
> ecasound -c -i Bass.wav -o jack,system -z:xruns
> > engine-launch
> > t
>
> According to the man page: With ’-z:xruns’, processing will be halted if an
> under/overrun occurs.
>
> It doesn't seem to work on my system setup. The processing continue even if
> several xruns messages appear in qjackctl.

> Do you have any tips to make it work ?

I can speculate that Ecasound will only respond to xruns
that it generates. Probably Ecasound is not aware of xruns
occurring elsewhere in the JACK graph.

The setup you are posting does not require JACK at all,
and if you do it using ALSA, Ecasound may respond to
xruns more comprehensively.

> ecasound -c -i Bass.wav -o alsa,default -z:xruns

regards,

Joel

> BR,
> Laurent
--
Joel Roth



------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Ecasound-list mailing list
Ecasound-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list