Re: [Lmuse-user] As promised in MusE-1 SVN now: Unified Jack midi devices

[Tim E. R. <ter...@ro...>]

On October 15, 2010 08:53:27 pm you wrote:
>   > As promised, I have unified the Jack midi devices,
>
> Hi,
>
> A quick test and it seems to work here.  I hooked it up like usual and
> also started "a2jmidid -e", whereas I normally just use  ALSA in
> qjackctl.   For a hardware synth, why would I want to use this this JACK
> method versus the ALSA connection?  Are there any benefits for in and
> out from a hardware synth?
>

If you don't need both input and output you click on the green 
 in/out enable lights, which will only create in or out client Jack midi ports 
 if they are 'ON'. You can observe this in QJackCtl's graph for example.

It was done for a couple of reasons, chiefly to make the devices
 appear and behave like the ALSA ones.
It should help people get going a bit quicker, and as a bonus
 could potentially free up as many as half the number of ports used
 previously (by combining in and out).
It helps end some confusion over midi track output port selection.

If you want, it can be exactly as before, just click on the lights to  
 choose what's an input and what's not. Loading an existing song
 (made before these changes) will show you exactly the same
 midi port set-up as before. 

I actually want to carry it further by having a one-step 'auto-setup'
 button which creates a bunch of devices for you, already connected
 to the existing available Jack ports and ready to go.
Trouble is, with this new system, it is difficult to tell which Jack midi
 input port might be best 'paired' with a particular Jack midi output port, 
 together as one MusE device (especially with Jack-2's default bland 
 'generic' port naming).
Possibly the best we could do would be to auto-setup separate 
 in and out devices for each of the Jack midi in or out ports.

Tim.