FS#40906 - [timidity++] "Couldn't start JACK device (`j')"
Attached to Project:
Arch Linux
Opened by Christian Landel (Titan) - Friday, 20 June 2014, 00:39 GMT
Last edited by David Runge (dvzrv) - Thursday, 03 December 2020, 18:28 GMT
Opened by Christian Landel (Titan) - Friday, 20 June 2014, 00:39 GMT
Last edited by David Runge (dvzrv) - Thursday, 03 December 2020, 18:28 GMT
|
Details
timidity can't use jack devices (using the -Oj flag):
$ timidity -Oj -iA jack_client_new: deprecated TiMidity starting in ALSA server mode Opening sequencer port: 129:0 129:1 129:2 129:3 Couldn't start JACK device (`j') (the last line of output happens when any MIDI device is connected to timidity, e.g. via qjackctl or rosegarden, no sound is produced even though it would with -Os [ALSA output]) Also I had the same result with both jack and jack2. |
This task depends upon
Closed by David Runge (dvzrv)
Thursday, 03 December 2020, 18:28 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with 2.15.0-5
Thursday, 03 December 2020, 18:28 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with 2.15.0-5
jack_client_new(TIMIDITY_JACK_CLIENT_NAME)
to
jack_client_open(TIMIDITY_JACK_CLIENT_NAME, (jack_options_t)0, NULL)
fixes the deprecated message, but not the issue
add
case PM_REQ_PLAY_START:
in jack_a.c, line 511 ("fall-through")
this constant seems to originate from alsaseq_c.c, line 549.
(traced the error message in gdb with "b fputs")
The blog entry http://blog.163.com/jiams_wang/blog/static/3033914920138120746567 uses wrong/other constant names for some reason.
Playing midi files works over jack, the bug only appears when using -iA -Oj (alsa-sequencer).
It seems that as of today upstream has not fixed this: https://sourceforge.net/p/timidity/git/ci/master/tree/timidity/jack_a.c
I'll release a new version of the package soon.