On Mon, 15 Mar 2010 23:18:55 -1000, david <gnome@xxxxxxxxxxxxx> wrote: > Rui Nuno Capela wrote: >> On Mon, 15 Mar 2010 12:43:36 +1100, Leigh Dyer wrote: >>> On Tue, 2010-03-09 at 20:46 +0000, Rui Nuno Capela wrote: >>>> - Comply with jackd >= 0.118.0 which now runs in real-time mode by >>>> default; use of -R is now deprecated from the jackd command line >>>> interface options; use -r to run in non-real-time-scheduling. >>> Hi Rui, >>> >>> Does this mean that this latest QjackCtl should only be used with JACK >>> versions 0.118 and later? Or does it detect the installed JACK version >>> and continue to use the old -R option for older JACKs? >>> >> >> yes, sort of. >> >> for older jack < 0.118.0 the new qjackctl realtime setting may now be >> nothing less than misleading. >> >> if you really need to keep with this old jackd, you're then strongly >> advised to set the server path to "jackd -R", explicitly. do not ever >> turn off the realtime checkbox. it will break jackd command line startup >> as "-r" being an invalid option. >> >> byee > > And what impact does this change to QJackCtl have on those of us who use > jackdmp AKA Jack2? regarding this specific command line change, jackdmp(jack2) >= 1.9.4 is in sync to jackd(jack1) >= 0.118.0, so if you're running an older jackdmp < 1.9.4 you should either upgrade or stuff the "-R" explicitly on the server path, as suggested for jackd < 0.118.0 alas, if you have jackdmp configured with --dbus, nothing of the above applies ;) cheers -- rncbc aka Rui Nuno Capela rncbc@xxxxxxxxx _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user