27 Jan
2010
27 Jan
'10
3 p.m.
Le 27 janv. 2010 à 19:41, torbenh a écrit :
On Tue, Jan 26, 2010 at 12:38:53PM +0000, Chris Cannam
wrote:
JACK2 code base can be instrumented (using the "--profile Build with engine
profiling" option ) to give more precise understanding of the source of possible
Xruns.
See : http://www.grame.fr/Ressources/pub/JACK2_lac2009.pdf
We cannot fix possible issues if they are not reported with some precise infos on what
happens.
Stéphane
On Sun, Jan 24, 2010 at 9:05 PM, torbenh
<torbenh(a)gmx.de> wrote:
i am not sure, but there a several users which report xruns with jack2,
where jack1 still works.
though i am not sure if they tested jack 1.9.4 which seem ok in sync mode
at least. since i dont want to let jack1 codebase die in a
feature freeze,
i added some features.
- smp aware
- clickless connections
Is there any reason why a user would prefer this over jack2?