From: Tim E. R. <ter...@ro...> - 2012-04-21 08:52:29
|
On April 20, 2012 7:46:03 PM Tim E. Real wrote: > On April 20, 2012 11:31:50 PM Allan Klinbail wrote: > > Hi All > > > > Just an update before I get flamed. > > > > I have tried the MIDI configuration panel and set up everything as > > default input channel as none.. > > > > I then closed out of Muse and opened a new file, the problem here was > > that the same thing happened again it started with all inputs recording > > all channels from all inputs. > > > > What I would like to do is modify the default.med template or another > > template to setup my preferences.... > > > > that would be awesome thanks. > > BTW the input configuration screen closing out when a check box is > > checked is still very annoying .. bug maybe?? > > > > cheers > > > > Allan > > > > On Fri, 2012-04-20 at 21:55 +1000, son...@ii... wrote: > > > Hi All, > > > > > > It's been a while since I've used MusE but life is settling again > > > and > > > I'm in the studio. > > > > > > I just compiled the latest trunk and I'm a little bit aghast to see > > > what's happened to MIDI input routing... > > > > > > To explain I have 2 8*8 emagic racks.. (AMT 8 and UNitor 8) > > > 2 MIDI keyboards (one sporting 3 virtual ports) > > > a bcf 2000 and an evolution x-session.. > > > > > > I have a large amount of MIDI gear connected to all of this ... > > > This includes external sequencers and drum machines which are often > > > sending spurious information that I only need to record very > > > occasionally... > > > > > > What I want to do is manually assign which ports will be sent to > > > which > > > muse track and then specifically which channel to record in.. > > > > > > It appears by default in the new matrix selection method everything > > > is > > > on..... > > > > > > So I have something like 368 boxes to uncheck .. before I can get > > > to > > > a default position where I can then select exactly what I want > > > recorded from each port.. This is so cumbersome it has made it > > > impossible for me to simply record some keyboard and then send it to > > > the desired synth... > > > > > > Further more even if I try to do this, each time I try to check a > > > box > > > the configuration window closes... No mean to offend but I'm in hell > > > trying to get this to work > > > > > > Is there some way of creating a default everything is off scenario > > > and > > > then I can check in what I like (opt-in instead of opt-out)? > > > > > > cheers > > > > > > Allan > > OK read my response to Allan about the menu closing (hold Ctrl). > > Now, in your case, what you really want is to set up your > midi ports and save the file as a template. > Then each time you want to use it click 'File -> New', > click on User folder and your template should be there. > > Alas, unfortunately, there's a snag: > When loading templates we ignore the midi configuration > stored in the template. This should be fixed. The idea there > was that built-in templates, such as midiGm.med would > have connections that are meaningless on other peoples' > computers. So we ignore them. Unfortunately we threw > the baby out with the bathwater - it ignores user templates' > stored midi config sections. > > Now that I think of it, I will try to fix that. > Theoretically if I remove any connections from midiGM.med > and turn on loading of midi config, it might work. > But I believe it may want to *erase* any existing connections, > which is undesirable for built-in templates. > I'll check. > > Anyway long story short: > Go ahead and store your custom template with midi connections. > But instead of using 'File -> New', use 'File -> Open' and make sure > in the dialog 'Read Midi Port Configuration' is checked, then > navigate to the templates and load. (Click 'User' folder -> templates, > that's where your custom templates are stored). > > HTH Lemme know if any (more) trouble. > Tim. > Sorry for the CCs... Awright, I've come up with what I think is a somewhat kinda sorta reasonable solution for the moment, given the situation: In release_2_0 branch: -Templates: File open dialog: Added 'read Midi Port Configuration' box. - File dialog: Unset 'read Midi Port Configuration' box for Global folder, set for others. - File dialog: Made side bar buttons auto-exclusive. Some fixes, cleanups. So here's how it works: -------------------------- 1) Start MusE. 2) Got to ye olde Midi Port Configuration window and setup all ye devices, routes and desired default connections. Note that this step itself could be annoying if you have a lot of devices but only need a few of them, as I noted, I auto-fill the Midi ports list at startup now. Opinions? Does it help or hinder? Depends, eh... I did plan to add a button 'Fill now' instead of/in addition to automatic. 3) If you would like any tracks stored along with your soon-to-be new Template, create them now, or remove the default Audio Output track if so desired. 4) Save the file as a Template by clicking 'Save' or 'Save As', and make sure 'Project is a Template' is checked in the new Save Dialog. If using the old Save Dialog, be sure to save your new Template in the user template directory, typically ~/.config/MusE/templates. 5) Now whenever you click File->New, if you click on 'User' folder, you will see your template, and by default 'read Midi Port Configuration' will be checked, so MusE will load the Midi Configuration settings. You can of course also save an existing open project as a template, and even re-open a template project. You can also tell MusE to always start with that file in the Global Settings. Although this could be improved - add a browse button and maybe allow easy templates other than default.med You can 'chain' templates by loading one with 'read Midi Port Configuration' set, then loading another without it set. Caveat: Well, um the midi ports are not auto-connected to the second template's tracks for some reason ATM. Kinda known this for a while... --------- A few months ago when we were talking about this config stuff, what I was getting at was that by having a special global configuration settings template we might eliminate these manual steps, and 'just do it' behind the scenes. Also, it is reasonable to consider allowing bypassing of loading Audio Input and Output tracks, just like bypassing the Midi Configuration, since they are both really just analogs of each other - they both are connections to the outside world. Just that here in MusE-2 Midi Ports happen to be hidden away in a Midi Configuration dialog, unlike muse_evolution where Midi Ports were introduced as tracks. Or to put that the opposite way, here in MusE-2 Audio Inputs and Outputs are brought out as tracks rather than hidden away in a dialog... It's late, hope I typed all that in correctly. Whaddya think? Sincerely hope this helps for now. Tim. |