| 2007-02-21 13:16:40 |
Ralf Nieuwenhuijsen |
bug |
|
|
added bug |
| 2007-02-21 13:30:26 |
Lionel Le Folgoc |
idjc: status |
Unconfirmed |
Confirmed |
|
| 2007-02-21 13:30:26 |
Lionel Le Folgoc |
idjc: statusexplanation |
|
|
|
| 2007-02-21 15:59:49 |
Lionel Le Folgoc |
idjc: status |
Confirmed |
Needs Info |
|
| 2007-02-21 15:59:49 |
Lionel Le Folgoc |
idjc: statusexplanation |
|
Hi,
/usr/bin/idjc contains:
-----
# Make JACK sound server start on demand
export JACK_START_SERVER="1"
-----
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 |
|
| 2007-02-21 16:00:55 |
Lionel Le Folgoc |
bug |
|
|
assigned to jack-audio-connection-kit (Ubuntu) |
| 2007-02-21 17:17:34 |
Ralf Nieuwenhuijsen |
idjc: status |
Needs Info |
Rejected |
|
| 2007-02-21 17:17:34 |
Ralf Nieuwenhuijsen |
idjc: statusexplanation |
Hi,
/usr/bin/idjc contains:
-----
# Make JACK sound server start on demand
export JACK_START_SERVER="1"
-----
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 |
|
|
| 2007-02-21 17:17:59 |
Ralf Nieuwenhuijsen |
jack-audio-connection-kit: status |
Unconfirmed |
Confirmed |
|
| 2007-02-21 17:17:59 |
Ralf Nieuwenhuijsen |
jack-audio-connection-kit: statusexplanation |
|
|
|
| 2007-02-21 17:24:17 |
Ralf Nieuwenhuijsen |
description |
Binary package hint: idjc
Steps to reproduce:
- install idjc
- run idjc
- select default profile (so just press ok)
- get a message:
The JACK sound server needs to be running in order to run IDJC.
In order to manually start it try something like:
$ jackd -d alsa -r 44100 -p 2048
- 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.
Suggested fix:
- run jackd when it is not running at launch time
- if we automatically started jackd, we kill it at when idjc closes |
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-connection-kit should come with default configuration file
---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-connection-kit package.
Will the maintainer please update the package?
|
|
| 2007-02-21 17:24:17 |
Ralf Nieuwenhuijsen |
title |
terminal required: idjc forces users to use the terminal because jackd needs to be run |
jack needs default configuration so it automatically launches |
|
| 2008-12-27 02:26:17 |
Daniel T Chen |
jack-audio-connection-kit: status |
Confirmed |
Triaged |
|
| 2008-12-27 02:26:17 |
Daniel T Chen |
jack-audio-connection-kit: importance |
Undecided |
Wishlist |
|
