Bug#491963: Clarification needed

2009-03-29 Thread Adrian Knoth
Hi!

I'm not sure if I understand this correctly, but shouldn't alsa-seq and
jack-whatever be two completely different things?

The alsa MIDI ports should show up under ALSA in qjackctl, whereas
jack-midi is put into MIDI.

So running jackd should not prevent qsynth from accessing alsa-seq MIDI
ports.

If you need to bridge between jack-midi and ALSA-midi, there's a2jmidid:

   http://home.gna.org/a2jmidid/

Can you clarify what's wrong?


TIA

-- 
mail: a...@thur.de  http://adi.thur.de  PGP/GPG: key via keyserver



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#491963: Clarification needed

2009-03-29 Thread David Baron
On Sunday 29 March 2009 14:39:59 Adrian Knoth wrote:
 Hi!

 I'm not sure if I understand this correctly, but shouldn't alsa-seq and
 jack-whatever be two completely different things?

 The alsa MIDI ports should show up under ALSA in qjackctl, whereas
 jack-midi is put into MIDI.

 So running jackd should not prevent qsynth from accessing alsa-seq MIDI
 ports.

 If you need to bridge between jack-midi and ALSA-midi, there's a2jmidid:

http://home.gna.org/a2jmidid/

 Can you clarify what's wrong?

It has been a long while since I played with this. If I remember correctly, 
using the -x option in jackd was problematic. I think I was able to use 
a2jmidid instead but I do not remember. The program worked without jack (but 
without the advantages of jack).



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org