From: Tim E. R. <ter...@ro...> - 2010-10-15 08:40:13
|
Hello. As promised, I have unified the Jack midi devices, in the midi ports list. Try it out. They can now be both input AND output, just like the ALSA midi devices You click on the green 'in/out' lights to create or destroy a corresponding in or out Jack client port. Note: Are you using Jack-1 together with QJackCtl ? May have found a possible intermittent bug in QJackCtl where it refuses to draw connections, after toggling the green 'in/out' lights on a MusE Jack midi device. Does not happen with Jack-2. Still investigating... ---- Also I realized those Jack midi 'buffer overflow' error messages, which you see during sending of midi controller initial values, may not be caused by insufficient Jack midi buffer size like I thought. It may be at this point no connections to any Jack ports have been made yet, thus there is no 'sink' for the events yet. It is not until later when the user (or our song loading routine) makes the connections from the Jack client port, to other Jack ports. Thinking about this today, may require rethinking of just how and when to send midi initializations over the Jack client port, NOT like we do with the ALSA ports. Checking... Well, have a grrreat day. Tim. |
From: Geoff K. <gs...@gm...> - 2010-10-16 00:50:30
|
> 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? Thanks, Geoff K. |
From: Geoff B. <ge...@la...> - 2010-10-16 01:09:21
|
On 10/16/2010 11:53 AM, Geoff King wrote: > Are there any benefits for in and > out from a hardware synth? use what works and sounds best for your system. muse needed jack midi support as more and more apps begin to require it. i use a combination of both alsa and jack midi and find both very accurate and musical. if your system isn't properly setup for audio production then either midi system may suffer jitter or through-put issues. as with all things Linux, it's up to the end user to establish a quality working environment to get the best out of it. but for me it's 50-50 alsa/jack midi and I'm happy ;) best, g. |
From: Tim E. R. <ter...@ro...> - 2010-10-16 01:30:35
|
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. |
From: Geoff B. <ge...@la...> - 2010-10-16 02:03:33
|
On 10/16/2010 12:29 PM, Tim E. Real wrote: > 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 whao, wait up there partner - aint ya gittin too darn smart there ? make the inputs auto selected and let the user setup the outputs; the way it used to be... trust me that's what (midi) users want ;) seem very flexible too as it is Tim - great work best g. |