From: Tim E. R. <ter...@ro...> - 2012-06-17 20:07:38
|
On June 17, 2012 8:39:11 PM Robert Jonsson wrote: > Hi Tim, > > <...> > > >> To get it working I started muse with -A, which seems to enable the > >> old functionality. Then my midi device popped up. > > > > Yes I did that. If Jack is running, no ALSA ports are listed. You supply > > the -A switch to force it to happen. > > > > The idea is that if Jack is running and you want to use ALSA devices, > > you should run Jack with the ALSA seq (-Xseq), or maybe even the raw. > > > > Failing that you should run that a2jmidid thingy, right Florian? > > > > I mean, we really shouldn't be listing both ALSA and Jack at the same > > time. We could remove the -A and it will return to previous style. Just with the naming and everything it's confusing to users. And the auto-connect wants to connect all the ports to midi tracks by default (so new users can just get going), so they end up with double-notes because both the ALSA and Jack midi are receiving the same thing (the midi input matrix LEDs are all on). Actually my original plan was to INVERT the meaning of -A. That is, you must supply -A to turn off ALSA support. That's an easy option if you want I can do that. But eh... I dunno, I think you can see why I chose this way. BTW I've used Jack -Xseq since they added it. I have no troubles here. I've never had to use a2jmidid. But one problem is, I think correct me if I'm wrong, if someone has both ALSA and say Firewire devices, Jack can only use one driver at a time. Just checked... Yep, only the Jack ALSA audio driver allows a midi driver to be chosen, with -X. One reason that MusE native self-contained ALSA support is good while Jack runs. Whaddya think? Do you want me to invert the -A meaning? Sorry for the trouble. Simplifications, eh... > > Yeah, that might be true, just as long as we are sure how we document > it and what instructions we should provide. Configuring jack with midi > support needs to become a standard procedure. > > I had some difficulties with the midi configuration dialog too, what I > wanted was it to work out of the box with midi input. > It started to work when I deleted my MusE.cfg though so I'll leave it > as working for now. > > For documentation purposes I would like to know more about the > drop-downs in the midi configuration though. > The In routes and Out routes have drop down menus for each listed > device, what am I configuring when editing these values? Oh, those are simply the routes to and from Jack. In muse_evolution midi ports were made tracks just like everything else. You connected their input and output routes to Jack. So that's what we have here in MusE-2, but instead of being tracks, midi ports have their own dialog. Midi port in and out routes are stored in the song just like all other routes. After I added midi port routes, pleasantly it is what allowed me to solo chain - that is connecting with audio routes. You may have gotten confused by my stringent attempts to preserve everything as much as possible ie opening a Jackified song when Jack isn't running. Even if Jack is not running you can create a Jack midi device but you'll notice there are no routes to connect to/from. Maybe I shouldn't have shown the drop-downs at all when Jack is not running. But it was kinda like: Hm, should I at least show the drop-downs empty to at least show the users there's something to be had there, they just need to make them fill up by starting Jack. Tim. > > Regards, > Robert > |