** Summary changed: - terminal required: idjc forces users to use the terminal because jackd needs to be run + jack needs default configuration so it automatically launches
** Description changed: - Binary package hint: idjc - Steps to reproduce: - - install idjc - - run idjc - - select default profile (so just press ok) - - get a message: + Problem: + IDJC uses jack. IDJC uses the 'new' behavior of jack to automatically launch itself. + However with an /etc/jackdrc file it will try to launch itself using 'jackstart' instead of 'jackd'. Jackstart however only works with 2.4.X kernels .. we need to use jackd for the 2.6.X kernels .. - The JACK sound server needs to be running in order to run IDJC. - In order to manually start it try something like: + Solution: + Jack-audio-connection-kit should come with default configuration file - $ jackd -d alsa -r 44100 -p 2048 + ---example configuration file---- + /usr/bin/jackd -d alsa -r 44100 + ---end of example configuration file--- - - Why doesn't it run it? If it knows its not running and it needs to be running? - - Maybe I'm missing something here. But instead of showing the message it should just launch jackd.. - Forcing users to use the terminal is not the way forward. + It should be called /etc/jackdrc and it should be part of the jack- + audio-connection-kit package. - Suggested fix: - - run jackd when it is not running at launch time - - if we automatically started jackd, we kill it at when idjc closes + Will the maintainer please update the package? ** Tags removed: usability -- jack needs default configuration so it automatically launches https://launchpad.net/bugs/86697 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
