Hi, Gilles Filippini a écrit , Le 12/03/2012 15:26: > 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.
I was curious and gave a try at enabling several RtMidi backends into the same build. The result is a vmpk executable supporting ALSA, Jack and UDP Midi. For now only one backend is used at runtime, selected with a command line option, but it should be possible to enable every available backends and switch from one to another using the preferences dialog. Do you think upstream would welcome such a patch? Thanks, _g.
signature.asc
Description: OpenPGP digital signature
