> On Monday 15 Mar 2004 4:51 pm, jeffrey milton wrote: > > The only thing I see that has changed is that rosegardensequencer > > has started jack... > > > > /usr/bin/jackd -T -d alsa -d hw:0 -p 2048 Chris Cannam <cannam@xxxxxxxxxxxxxxxxxxxxx> writes: > Am I right in guessing you have a very new version of JACK, say 0.75 > from CVS? If so, then Rosegarden didn't start JACK -- JACK did. > Rosegarden will happily run without JACK if you only want to do MIDI > and score, but it always tries to attach to the JACK server first and > only goes ahead without it if that fails. With a recent version of > libjack, that attempt to attach to JACK actually causes jackd to > start up. > > That's a problem that we hadn't really anticipated (with Rosegarden). > There is no command-line flag to tell it not to use JACK, just > because we'd assumed the JACK attach would only succeed if you were > already running jackd, in which case you'd probably want it. This comes from JACK CVS 0.95.x, not the latest release 0.94.0. JACK will probably evolve to provide better client control over this new feature. For now, setting JACK_NO_START_SERVER in your environment prevents the server from being started automatically. -- joq
