jack needs default configuration so it automatically launches
Bug #86697 reported by
Ralf Nieuwenhuijsen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
idjc (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
jack-audio-connection-kit (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
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 ..
Solution:
Jack-audio-
---example configuration file----
/usr/bin/jackd -d alsa -r 44100
---end of example configuration file---
It should be called /etc/jackdrc and it should be part of the jack-audio-
Will the maintainer please update the package?
Changed in idjc: | |
status: | Unconfirmed → Confirmed |
description: | updated |
Changed in jack-audio-connection-kit: | |
importance: | Undecided → Wishlist |
status: | Confirmed → Triaged |
To post a comment you must log in.
Hi,
/usr/bin/idjc contains: SERVER= "1"
-----
# Make JACK sound server start on demand
export JACK_START_
-----
so jackd is automatically launched when needed, and stopped when all clients exit.
However, when running idjc from a terminal, it displays:
-----
[...]
jackstart: md5 checksum for /usr/bin/jackd does not match
[...]
-----
So it seems this issue comes from jackd