From: Tim E. R. <ter...@ro...> - 2011-12-13 22:35:15
|
On December 14, 2011 8:44:43 AM Geoff Beasley wrote: > On 12/14/2011 08:13 AM, Geoff Beasley wrote: > > broken with jack2 Tim .. dummy won't even work. there are no jack midi > > nodes at all and the route entries are empty. alsa seems ok. > > aha! if i create a 'new' jack-midi device it's ok ;) so, existing > jack-midi devices in a session are not being created on load, but new > ones are ok. more testing.... > > g > Hm, yeah I was wondering when you start MusE, do you not actually have any sound devices hooked up and running? I mean, like a sound card or another Jack midi app or something? When you start MusE with Jack running I guarantee you it will now pick up /anything/ that exists and slap it on up into the midi ports list! Well, I haven't tried across a network yet but... For example here my sound card is listed first, then my MidiSport USB... All in the midi ports list. So I figured you must be staring Muse, /then/ staring some other app or hardware. It won't auto-fill in that case - only on startup. Yeah I know - don't say it ! I'm looking at complete auto-filling all the time even while running, upon discovery of new Jack and ALSA devices. So the midi ports would basically always reflect what's 'out there', plus what you added. Unfortunately there's a 'gotcha' here in that it might cause infinite recursive auto-filling if say, two instances of MusE were started, or MusE plus another app which did this same kind of auto-filling thingy. Both would be constantly attempting to look at each others' ports. I believe. Oh well, keep thinking I guess... Tim. |