Hi Tim, \o/ as always, it'll be great to try out but there's no immediate hurry, take your time.
Regards, Robert 2014-05-26 7:41 GMT+02:00 Tim E. Real <[email protected]>: > On May 17, 2014 11:24:46 PM Robert Jonsson wrote: >> 2014-05-17 6:18 GMT+02:00 Tim E. Real <[email protected]>: >> <...> >> >> >> Finally got around to make a test with the release version. >> >> What exactly do you mean by re-create? Re-assigning the device would >> >> be fine, if it was there but it isn't. >> >> >> >> If I do the following: >> >> 1. start jack without midi >> >> 2. start muse, save an empty song (which won't have any midi devices) >> >> 3. restart jack with midi >> >> 4. start muse (now muse has plenty of midi devices from jack) >> >> 5. load the song (now all midi devices have vanished) >> >> >> >> There's this choice to "create jack-devices" but I have no idea how to >> >> use that. >> > >> > That's the one. You create a new Jack midi device, then use the >> > >> > Input Routes and Output Routes drop-downs (in the list) to assign >> > the new Jack midi device to/from actual Jack ports. >> > >> >> I would really have expected all devices to still be visible after >> >> loading the song. >> > >> > No, not after you save a song without Jack midi. >> > The particular Jack midi devices do not exist at the time of saving. >> > Therefore how can it possibly be expected to properly save all the >> > relevant >> > >> > parameters, such as routes to/from actual Jack ports, device name and so >> > on.> >> > Unless, as I mentioned, we somehow save previous configurations >> > >> > and allow back-peddling. >> > >> > Or multiple, selectable configurations, anyone? I mentioned this once. >> > Or at least a warning dialog rather than obscure command-line output >> > >> > when devices (or anything else for that matter) aren't found upon >> > loading. >> > >> > "Warning, devices will be lost upon saving". >> > >> > I mentioned a while ago that I wanted to add a button or something >> > >> > which says "refill the list with Jack midi devices (as if you started >> > with >> > a fresh song)". >> > >> > But that will not restore, and may upset, custom configurations where >> > >> > specific devices were created or moved around the list or routed to >> > specific Jack ports. >> > >> > There is flexibility in the system in how you use the Jack midi devices. >> > For one thing, because it allows the multiple connections to a Jack port, >> > >> > it may support daisy-chaining midi, as someone asked about before. >> > >> > (Our ALSA devices don't support that kind of thing and are >> > >> > 'fixed' to their ALSA routes.) >> > >> > Then, add synth devices along with ALSA + Jack devices, and it gets >> > trickier. >> > >> > I know, the system needs to be better, easier. >> > >> > I know what you're thinking, "why can't we just automatically create >> > >> > devices for the actual available devices, on the fly, and present them to >> > the user when they select the drop down list in the configuration >> > dialog?" >> > >> > It's not that easy. For registering devices on the fly, there was an issue >> > >> > with infinite recursive creations of devices, goes something like this: >> > "we create ports for newly discovered Jack ports, then some other app, >> > >> > like another instance of MusE, sees THESE ports and automatically creates >> > its own ports for these ports. Then THIS instance of MusE sees THOSE >> > ports >> > and creates ports for them. Then the other app does the same. And so on, >> > infinitely." >> > >> > It's because each created port is EXPOSED to the outside world. >> > (And needs to be, really. Other apps NEED to see your ports.) >> > >> > So that was kind of out of the question. >> > >> > However, a button which says "Re-scan devices now..." or something >> > >> > as I mention above, might help. >> > >> > But I just could not find a way around this recursive 'mirroring' of >> > >> > all ports, each time. To avoid that they needed to be specifically >> > created by the user. >> > >> > It is tricky, I did the best I could at the time... >> > Adding Jack midi was fun though. >> > >> > Also, I realized and mentioned once in discussions on LAD, that >> > >> > ultimately the easiest thing is for the user to see the actual >> > Jack ports and ALSA ports in each Midi TrackInfo panel. >> > >> > That is, in each Midi TrackInfo panel, BYPASS the MusE Midi Ports >> > >> > and display the actual currently available Midi Devices right there. >> > >> > The system IIRC more or less supports this, it's just behind the scenes >> > >> > Midi Ports could still be used. >> > >> > It's not as easy as it sounds, but it would be a good thing. >> > I imagined ways to accomplish it and present the devices to the user. >> >> Ah, yes, now I understand where you are coming from technically. >> >> About using the actual jack devices, that sounds like a good idea, >> never presenting MusE's own ports (though they are of course visible >> in jack). >> I understand that might require some rework though, A refresh button >> would ease usage quite a bit too. >> >> Regards, >> Robert > > > Hi. > > Sorry I am very late with the commit. > > Been super busy, but also super busy with MusE but I am almost done. > > Things are mostly working smoothly and as before now. > Should be good enough for actual production again. > With increased speed and some goodies thrown in. > > Will explain in great detail later. > > Thanks for your patience. > > Tim. > > ------------------------------------------------------------------------------ > The best possible search technologies are now affordable for all companies. > Download your FREE open source Enterprise Search Engine today! > Our experts will assist you in its installation for $59/mo, no commitment. > Test it for FREE on our Cloud platform anytime! > http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk > _______________________________________________ > Lmuse-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lmuse-developer ------------------------------------------------------------------------------ The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
