Mehdi Dogguy a écrit , Le 12/03/2012 15:10: > On 11/03/12 17:20, Gilles Filippini wrote: >> >> When wmpk is build with RTMIDI_DRIVER=JACK there is no way to >> connect the midi output to timidity. Building with RTMIDI_DRIVER=ALSA >> solves the problem. >> > > I changed debian/rules so that vmpk is built with RTMIDI_DRIVER=JACK by > default. This happened because of a user request [1]. Now, if I change > the RTMIDI_DRIVER back to its default, it won't make things better > because of #629300. How do you suggest to fix this situation? Build vmpk > twice? > > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629300
Yep, I saw this request already. But it doesn't provide actual info stating why the jack backend should be the default. The fact is that building with RTMIDI_DRIVER=JACK doesn't seem to support timidity, while ALSA is supported by jack. Anyway, the best way to fix it should be to enable both backends at runtime (=> upstream). In the meantime, I'd appreciate a step back to the ALSA backend. Thanks, _g.
signature.asc
Description: OpenPGP digital signature
