From: <son...@ii...> - 2012-04-20 11:55:56
|
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 |
From: Allan K. <son...@ii...> - 2012-04-20 13:32:03
|
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 > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ Lmuse-developer mailing list Lmu...@li... https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Robert J. <spa...@gm...> - 2012-04-20 14:01:01
|
Hi Allan, long time no hear! Seems we have a bit of conflicting requirements here, it's setup to provide input by default as that is what most users would expect. You are correct in that making a new default.med is a very good solution for your needs. As for the dialog closing, hold ctrl while using the dialog, then it stays open. We should find a way of making this more apparent. Isn't there a button for turning on/off all channels in the dialog too? I may recall wrong. Will have another look tonight. Regards, Robert Den 20 april 2012 15:31 skrev Allan Klinbail <son...@ii...>: > 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 >> >> ------------------------------------------------------------------------------ >> For Developers, A Lot Can Happen In A Second. >> Boundary is the first to Know...and Tell You. >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >> http://p.sf.net/sfu/Boundary-d2dvs2 >> _______________________________________________ Lmuse-developer mailing list Lmu...@li... https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Robert J. <spa...@gm...> - 2012-04-20 16:38:49
|
Hello again, a quick test suggests that clicking the up/down arrow to the left of the channel lights is what you want. It will turn them all on/off. Regards, Robert Den 20 april 2012 16:00 skrev Robert Jonsson <spa...@gm...>: > Hi Allan, long time no hear! > > Seems we have a bit of conflicting requirements here, it's setup to > provide input by default as that is what most users would expect. > You are correct in that making a new default.med is a very good > solution for your needs. > > As for the dialog closing, hold ctrl while using the dialog, then it > stays open. We should find a way of making this more apparent. > Isn't there a button for turning on/off all channels in the dialog > too? I may recall wrong. > Will have another look tonight. > > Regards, > Robert > > Den 20 april 2012 15:31 skrev Allan Klinbail <son...@ii...>: >> 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 >>> >>> ------------------------------------------------------------------------------ >>> For Developers, A Lot Can Happen In A Second. >>> Boundary is the first to Know...and Tell You. >>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >>> http://p.sf.net/sfu/Boundary-d2dvs2 >>> _______________________________________________ Lmuse-developer mailing list Lmu...@li... https://lists.sourceforge.net/lists/listinfo/lmuse-developer >> >> >> >> ------------------------------------------------------------------------------ >> For Developers, A Lot Can Happen In A Second. >> Boundary is the first to Know...and Tell You. >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >> http://p.sf.net/sfu/Boundary-d2dvs2 >> _______________________________________________ >> Lmuse-developer mailing list >> Lmu...@li... >> https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Robert J. <spa...@gm...> - 2012-04-20 22:04:50
|
Hello again, again. I just realized that you wrote trunk. I am not sure about the state of trunk. The best MusE is currently in branches/release_2_0 so please compile that instead. When 2.0 is released the fixes from there will be merged back into trunk. Also, do let us know if there are things we can improve with the problem at hand. Regards, Robert Den 20 april 2012 18:38 skrev Robert Jonsson <spa...@gm...>: > Hello again, > > a quick test suggests that clicking the up/down arrow to the left of > the channel lights is what you want. It will turn them all on/off. > > Regards, > Robert > > > Den 20 april 2012 16:00 skrev Robert Jonsson <spa...@gm...>: >> Hi Allan, long time no hear! >> >> Seems we have a bit of conflicting requirements here, it's setup to >> provide input by default as that is what most users would expect. >> You are correct in that making a new default.med is a very good >> solution for your needs. >> >> As for the dialog closing, hold ctrl while using the dialog, then it >> stays open. We should find a way of making this more apparent. >> Isn't there a button for turning on/off all channels in the dialog >> too? I may recall wrong. >> Will have another look tonight. >> >> Regards, >> Robert >> >> Den 20 april 2012 15:31 skrev Allan Klinbail <son...@ii...>: >>> 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 >>>> >>>> ------------------------------------------------------------------------------ >>>> For Developers, A Lot Can Happen In A Second. >>>> Boundary is the first to Know...and Tell You. >>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >>>> http://p.sf.net/sfu/Boundary-d2dvs2 >>>> _______________________________________________ Lmuse-developer mailing list Lmu...@li... https://lists.sourceforge.net/lists/listinfo/lmuse-developer >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> For Developers, A Lot Can Happen In A Second. >>> Boundary is the first to Know...and Tell You. >>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >>> http://p.sf.net/sfu/Boundary-d2dvs2 >>> _______________________________________________ >>> Lmuse-developer mailing list >>> Lmu...@li... >>> https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Allan K. <son...@ii...> - 2012-04-23 04:45:30
|
Thanks All Recompiling now and trying all suggestions. I realise my use is non-standard.. most people won't have the amount of MIDI ports I have I'll let you know. Also if there are any other suggestions I'll be sure to let you know. On that note - MIDI sync to external gear looks very tight these days. Regards Allan On Sat, 2012-04-21 at 00:04 +0200, Robert Jonsson wrote: > Hello again, again. > > I just realized that you wrote trunk. > I am not sure about the state of trunk. The best MusE is currently in > branches/release_2_0 so please compile that instead. > When 2.0 is released the fixes from there will be merged back into trunk. > > Also, do let us know if there are things we can improve with the > problem at hand. > > Regards, > Robert > > Den 20 april 2012 18:38 skrev Robert Jonsson <spa...@gm...>: > > Hello again, > > > > a quick test suggests that clicking the up/down arrow to the left of > > the channel lights is what you want. It will turn them all on/off. > > > > Regards, > > Robert > > > > > > Den 20 april 2012 16:00 skrev Robert Jonsson <spa...@gm...>: > >> Hi Allan, long time no hear! > >> > >> Seems we have a bit of conflicting requirements here, it's setup to > >> provide input by default as that is what most users would expect. > >> You are correct in that making a new default.med is a very good > >> solution for your needs. > >> > >> As for the dialog closing, hold ctrl while using the dialog, then it > >> stays open. We should find a way of making this more apparent. > >> Isn't there a button for turning on/off all channels in the dialog > >> too? I may recall wrong. > >> Will have another look tonight. > >> > >> Regards, > >> Robert > >> > >> Den 20 april 2012 15:31 skrev Allan Klinbail <son...@ii...>: > >>> 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 > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> For Developers, A Lot Can Happen In A Second. > >>>> Boundary is the first to Know...and Tell You. > >>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > >>>> http://p.sf.net/sfu/Boundary-d2dvs2 > >>>> _______________________________________________ Lmuse-developer mailing list Lmu...@li... https://lists.sourceforge.net/lists/listinfo/lmuse-developer > >>> > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> For Developers, A Lot Can Happen In A Second. > >>> Boundary is the first to Know...and Tell You. > >>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > >>> http://p.sf.net/sfu/Boundary-d2dvs2 > >>> _______________________________________________ > >>> Lmuse-developer mailing list > >>> Lmu...@li... > >>> https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Tim E. R. <ter...@ro...> - 2012-04-20 23:29:14
|
On April 20, 2012 9:55:42 PM 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 I was afraid this would happen. I've said I'm not a fan of auto-connecting anything because it ends up annoying when working with a large project or many inputs. But in an effort to help new users get up and running quickly, and from requests by other users, this was the best/easiest way I could make it work. Look, I was just thinking: Aside from new users who may in fact appreciate that everything is connected and ready to go, Robert's desire to have small projects auto-connected is outweighed by larger projects and many inputs. Look at it this way, *if* I remove auto-connections: If a project is small, then you won't mind making a couple of connections to make it work. That's just something you have to learn. That's how MusE works. Routing and connections. Whereas, someone with a large project or many inputs like Allan, will have a much more difficult time with auto-connections, so let them do everything by themselves. But it's a delicate balance. Even Allan could appreciate *some* form of auto-connections after a while. Geoff B's in a similar situation but he's part of the reason I added all of this - he requested auto-connections. But I'm quite sure even *he* gets annoyed by auto-connections, in its /current/ form, after a while. I agree in its current form it can be annoying. We've been talking about true 'set and forget' setup screens. We weren't able to do it in time for MusE-2 release. But we're gonna try to aim for this in the next phase. Florian has some ideas about how to do this and I have some too. The idea would be that you setup your midi connections and then forget it. They'll always be there the next time you start MusE. These would be true set-and-forget 'global' connections. Also, I added auto-filling of the Midi Ports list with all available devices at startup, in an effort to help users get running. Having to manually create Jack devices was a pain. But even this I am wary of. After discussing on LAD/Jack I concluded that the way I did it was not a good way. So I must try to change it in the next phase, or else turn it off completely before we release version 2. Allan, do you find that feature helpful or a hindrance? About the menu disappearing: Hold Ctrl down as you are clicking and the menu will stay open. Or, if you would like to have them stay open by default, go to Global Settings and click the option: 'Some popup menus stay open (else hold Ctrl)' Also, in the menu, click the small up/down arrows to set/clear an entire row of input LEDs. At least this matrix menu is far better than the cascading popups we had before, eh? And as Robert says, make sure to use the release_2_0 branch as it is the most current. Gonna sit back and take a look at all of this, if there's anything I can do for release. I look forward to the pending discussion ! Your input matters. All for now. Tim. |
From: Tim E. R. <ter...@ro...> - 2012-04-20 23:46:23
|
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. |
From: Geoff B. <ge...@la...> - 2012-04-21 04:53:41
|
On 04/21/2012 09:28 AM, Tim E. Real wrote: > Geoff B's in a similar situation but he's part of the reason I added > all of this - he requested auto-connections. > But I'm quite sure even*he* gets annoyed by auto-connections, > in its/current/ form, after a while. G'day Allan, boyz.Ontour atm - back next week. to answer you Tim ; for inputs? nope.never. I see this more of a lack of "macro" type control. That is, a way of say creating one of something and then "cloning" or duplicating it some how via a menu or dialogue. Auto connecting inputs is extremely logical. Output routing is another story altogether,and as you know I'm not a great fan of Muse's connection routines; though they have improved greatly recently. Thanks Tim ;) This problem exists in the real world too you know.. the answer?? We need a patchbay.Pure and simple.And it needs to be added to the mixer. see you when I get back folks :) g I'm touring with Captn. Typho again.. |
From: Jeffrey H. <jhu...@ya...> - 2012-04-22 02:15:48
|
Hello All, Is the project still accepting donation's through Paypal via Tim's SourceForge account? I tried to check the Supporters page here: http://sourceforge.net/developer/user_donations.php?user_id=606684 ...to see if any recent donations had been made (a solid indicator that the associated Paypal account is still valid), but I get a "404 Page Not Found" error. It may just be that the page is broken, I've had to send support requests to the SourceForge folks plenty of times for stuff like this. Thanks, Jeff |
From: Tim E. R. <ter...@ro...> - 2012-04-22 04:16:56
|
On April 21, 2012 7:15:41 PM Jeffrey Hubbard wrote: > Hello All, > > Is the project still accepting donation's through Paypal via Tim's > SourceForge account? > > I tried to check the Supporters page here: > > http://sourceforge.net/developer/user_donations.php?user_id=606684 > > ...to see if any recent donations had been made (a solid indicator that > the associated Paypal account is still valid), but I get a "404 Page Not > Found" error. > > It may just be that the page is broken, I've had to send support requests to > the SourceForge folks plenty of times for stuff like this. > > Thanks, > Jeff That address does not work for me either. Maybe you clicked an old link? SF changed recently? http://sourceforge.net/donate/?user_id=606684 Works for me. I just followed the link from our web page. But thanks! Yep still there... Tim. |
From: Jeffrey H. <jhu...@ya...> - 2012-04-22 15:41:16
|
You can find that hyperlink by clicking on any of the "donate $XXX" buttons. That page is linked to here: You may enter a comment (up to 100 characters) for the supporters page: where "supporters page" is a link to here: http://sourceforge.net/developer/user_donations.php?user_id=606684 You can send a support request to the SourceForge folks to get it fixed, they're usually pretty fast about these kinds of things. I just donated $250USD, I'll donate more as your project progresses. Thanks, Jeff ________________________________ From: Tim E. Real <ter...@ro...> To: lmu...@li... Sent: Sunday, April 22, 2012 12:16 AM Subject: Re: [Lmuse-developer] Donations? On April 21, 2012 7:15:41 PM Jeffrey Hubbard wrote: > Hello All, > > Is the project still accepting donation's through Paypal via Tim's > SourceForge account? > > I tried to check the Supporters page here: > > http://sourceforge.net/developer/user_donations.php?user_id=606684 > > ...to see if any recent donations had been made (a solid indicator that > the associated Paypal account is still valid), but I get a "404 Page Not > Found" error. > > It may just be that the page is broken, I've had to send support requests to > the SourceForge folks plenty of times for stuff like this. > > Thanks, > Jeff That address does not work for me either. Maybe you clicked an old link? SF changed recently? http://sourceforge.net/donate/?user_id=606684 Works for me. I just followed the link from our web page. But thanks! Yep still there... Tim. ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Lmuse-developer mailing list Lmu...@li... https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
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. |
From: Robert J. <spa...@gm...> - 2012-04-22 17:43:50
|
Hi Jeff, Den 22 april 2012 18:02 skrev Jeffrey Hubbard <jhu...@ya...>: > Hello Again, > > I've been doing some testing of the latest SVN of the Muse2 release_2_0 > branch, and I've compiled a list of bugs that I've found. > > Tested: Latest SVN of branches/release_2_0 > > Test Setup: > > Ubuntu 11.10 - 64bit > Linux kernel 3.0 > AMD FX-8120 > Radeon HD 5450 discrete GPU using the libre Radeon driver > EMU 0204 USB Soundcard > M-Audio Oxygen 49 keyboard > > Terminology: When referring to the 2-window Ubuntu/Unity workaround the > following mean: > > parent window: The window that opens, but doesn't really have anything in > it. > arrangement window: The 2nd window that contains all of the tracks, > instruments, plugins, etc.. > > Bugs: > > Bug #1. Steps to reproduce: > > Launch Muse2 (for example, from the terminal by typing "muse2") > > Expected behaviour: Only one window should open > > Actual behaviour: the 2 window solution is still there even though I'm not > launching with -u. Launching with > -u yields the same behaviour. Check your configuration in MusE Settings->Global Settings, check that the arranger is set as a MDI-subwindow as I expect that is what you want. I don't normally run Ubuntu/unity but i keep a configuration around for testing, upon launching the recent code I got very similar behaviour to what you describe, but it was fixed with editing the configuration. > Also part of bug #1. Opening a project crashes the arrangement window, > while the parent window stays running. > The trigger seems to be if the project contains any MIDI items, an empty > project can be opened. Nothing > is outputted to stdout. My arranger also disappeared but I'm hoping that what you get is the same as for me, simply that the arranger is not visible. Select View->Arranger view in the menu and it should reappear. > I have attached a project that I cannot open. > > At a few points in time stdout printed this: > > unexpected EOF reading *.med file at level 0, line [arbritary line number], > <event><part><> This may be more of a concern. I know there are places (dragging plugins for instance) when we get similar errors, none that are critical though. When opening the file you sent I don't get any errors. One notable difference between our configurations is that mine is 32-bit. Hopefully that isn't related. > but I'm not sure if it's correlated to the arrangement window crashing. > > > Bug #2. Steps to reproduce: > > Add a DSSI synthesizer to a project(Tested with Ray-V and Nekobee) > > Add a parameter as an automation envelope in the arrangement window. > > Expected behaviour: I should be able to add envelope points > > Actual behaviour: I can't add any points to the automation envelope in the > arrangement window, with any of the mouse tools. I can only edit MIDI CCs > within the MIDI editor. Ah, yes, unintuitive design on our part. To ADD points with the automation tool you need to hold <shift>. Uh, this should be improved somehow, originally I dismissed the idea that it should be allowed to add points directly, maybe that isn't so bad though. > Also regarding automation: The sub-context-menu that allows the user to > pick the color of the envelope > doesn't actually show the colors or text of what the color is, the menu > entry is just empty with a > checkmark next to it if that color is selected. Oh, hmmm, haven't heard that one before. The color is shown here... the sub menu does not have any text, maybe that is the problem. > > Bug #3. Hung notes: > > I believe the attached project for bug #1 contains a MIDI item that > consistently causes a hung note > as the play cursor passes the end of the item. Unfortunately, because of > bug #1, I cannot open the > project to confirm that the attached is in fact the correct one, but I'm > pretty sure it is. I'll give it a peek on another computer, this one doesn't have any audio capabilites... Regards, Robert |
From: Jeffrey H. <jhu...@ya...> - 2012-04-22 21:21:14
|
> Check your configuration in MusE Settings->Global Settings, check that > the arranger is set as a MDI-subwindow as I expect that is what you > want. That moved the arrangement back into the parent window, however, now I only get the menu strip that contains "Edit|Functions|Window Config", and not the one that contains "File|Edit|View|Search|Tools|Documents|Help". This probably has something to do with how Unity handles menu strips, I'll test it with the new version of Ubuntu that is to be released this week, to see if it behaves differently in the newer version of Unity. > My arranger also disappeared but I'm hoping that what you get is the > same as for me, simply that the arranger is not visible. > Select View->Arranger view in the menu and it should reappear. That was it, mine was the same. I also verified that the project I attached in the last email does contain a MIDI item that consistently results in a hung note. > Ah, yes, unintuitive design on our part. To ADD points with the > automation tool you need to hold <shift>. Sorry, I should've mentioned that I tried holding shift, and it still doesn't work. > Uh, this should be improved somehow, originally I dismissed the idea > that it should be allowed to add points directly, maybe that isn't so > bad though. I agree, Muse2 already cleanly separates automation from other components like MIDI items, etc... I don't see the harm in allowing envelope points to be added directly. Thanks, Jeff |
From: Robert J. <spa...@gm...> - 2012-04-22 21:51:37
|
Hi Jeff, Den 22 april 2012 23:21 skrev Jeffrey Hubbard <jhu...@ya...>: > > > Check your configuration in MusE Settings->Global Settings, check that > > the arranger is set as a MDI-subwindow as I expect that is what you > > want. > > That moved the arrangement back into the parent window, however, now > I only get the menu strip that contains "Edit|Functions|Window Config", > and not the one that contains "File|Edit|View|Search|Tools|Documents|Help". > Oh, I didn't really try to use it as my machine with ubuntu isn't really usable for music but I'll try to verify this tomorrow if time permits. > > This probably has something to do with how Unity handles menu strips, > I'll test it with the new version of Ubuntu that is to be released this > week, > to see if it behaves differently in the newer version of Unity. > > > > My arranger also disappeared but I'm hoping that what you get is the > > same as for me, simply that the arranger is not visible. > > Select View->Arranger view in the menu and it should reappear. > > That was it, mine was the same. I also verified that the project I > attached > in the last email does contain a MIDI item that consistently > results in a hung note. > Hmm, that didn't happen for me when I opened the project on another machine (which is musically capable) Not sure what to make of that. I should setup a 64-bit machine finally... > > Ah, yes, unintuitive design on our part. To ADD points with the > > automation tool you need to hold <shift>. > > Sorry, I should've mentioned that I tried holding shift, and it still > doesn't work. > > Hmm. Ok. > > > Uh, this should be improved somehow, originally I dismissed the idea > > that it should be allowed to add points directly, maybe that isn't so > > bad though. > > I agree, Muse2 already cleanly separates automation from other components > like > MIDI items, etc... I don't see the harm in allowing envelope points to be > added > directly. > Yes, you are probably right. Thanks for helping us hunt! /Robert > Thanks, > Jeff > > > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > |
From: Jeffrey H. <jhu...@ya...> - 2012-04-28 14:38:51
|
> >>> Check your configuration in MusE Settings->Global Settings, check that >>> the arranger is set as a MDI-subwindow as I expect that is what you >>> want. > >>> That moved the arrangement back into the parent window, however, now >>> I only get the menu strip that contains "Edit|Functions|Window Config", >>> and not the one that contains "File|Edit|View|Search|Tools|Documents|Help". > >Oh, I didn't really try to use it as my machine with ubuntu isn't really usable for music but I'll try to verify this tomorrow if time permits. This seems to be fixed in the final release of Ubuntu 12.04, I get the expected context menus now. |
From: Jeffrey H. <jhu...@ya...> - 2012-04-22 22:56:04
|
> Sorry, I should've mentioned that I tried holding shift, and it still doesn't work. OK, actually it turns out that I can create points like that, but I have to do something like this: 1. Hold down shift 2. Slowly drag the cursor back-and-forth over the automation envelope until that "crosshair" cursor appears. I would say that it's excessively difficult to get that cursor to appear, although that may be somewhat of a configuration issue, it might be easier on a different Desktop Environment or on a different graphics driver or at lower monitor resolution (I'm running 1920x1080 on a 23" monitor). Maybe drawing those lines a few pixels thicker might help? Another solution might be "automation lanes", where each automation envelope is in it's own track, and the automation lanes for each synth can be expanded/collapsed into the parent synth track with little "+/-" buttons on the synth track. This would allow for automation to be drawn by clicking anywhere within the automation lanes, since the envelopes will no longer be sharing the same track, and Muse won't have to attempt to guess which one you meant to click on. Of course, that's probably a very invasive change, but perhaps something to think about for later. Thanks, Jeff |
From: Tim E. R. <ter...@ro...> - 2012-04-22 23:04:22
|
On April 22, 2012 9:02:18 AM Jeffrey Hubbard wrote: > Hello Again, > > I've been doing some testing of the latest SVN of the Muse2 release_2_0 > branch, and I've compiled a list of bugs that I've found. > > Tested: Latest SVN of branches/release_2_0 > > Test Setup: > > Ubuntu 11.10 - 64bit > Linux kernel 3.0 > > AMD FX-8120 > Radeon HD 5450 discrete GPU using the libre Radeon driver > EMU 0204 USB Soundcard > M-Audio Oxygen 49 keyboard > > > Terminology: When referring to the 2-window Ubuntu/Unity workaround the > following mean: > > parent window: The window that opens, but doesn't really have anything in > it. arrangement window: The 2nd window that contains all of the tracks, > instruments, plugins, etc.. > > Bugs: > > Bug #1. Steps to reproduce: > > Launch Muse2 (for example, from the terminal by typing "muse2") > > Expected behaviour: Only one window should open > > Actual behaviour: the 2 window solution is still there even though I'm not > launching with -u. Launching with -u yields the same behaviour. > > Also part of bug #1. Opening a project crashes the arrangement window, > while the parent window stays running. The trigger seems to be if the > project contains any MIDI items, an empty project can be opened. Nothing > is outputted to stdout. > > I have attached a project that I cannot open. Verified. Somehow you closed the Arranger. Click View -> Arranger View to see it again. > > At a few points in time stdout printed this: > > unexpected EOF reading *.med file at level 0, line [arbritary line number], > <event><part><> > > but I'm not sure if it's correlated to the arrangement window crashing. No. This is likely the benign error that occurs when pasting copied parts. It occurs because we reach the end of our xml pasting code. I've known about that one for years. At the time I looked, looked again and again, and couldn't quite figure out how to get rid of it. But I concluded it was benign. Any takers? > > > > Bug #2. Steps to reproduce: > > Add a DSSI synthesizer to a project(Tested with Ray-V and Nekobee) > > Add a parameter as an automation envelope in the arrangement window. > > Expected behaviour: I should be able to add envelope points > > Actual behaviour: I can't add any points to the automation envelope in the > arrangement window, with any of the mouse tools. I can only edit MIDI CCs > within the MIDI editor. And as you say you held shift. Ha bet I know this one. You must click the line drawing tool in the menu bar so that the cursor will change to a +. And hold shift while drawing. Robert remember when I asked the same thing long ago? He he... > > Also regarding automation: The sub-context-menu that allows the user to > pick the color of the envelope doesn't actually show the colors or text of > what the color is, the menu entry is just empty with a checkmark next to it > if that color is selected. OK this sounds weird. What theme and MusE Qt style (Appearance Settings) are you using? > > > > Bug #3. Hung notes: > > I believe the attached project for bug #1 contains a MIDI item that > consistently causes a hung note as the play cursor passes the end of the > item. Unfortunately, because of bug #1, I cannot open the project to > confirm that the attached is in fact the correct one, but I'm pretty sure > it is. Verified. Hookay now... We've got a double note entry in the fifth part of Track 1, at bar 006.03.288. There are two notes there, one is small at len=36, the other is len=272. Tested OK with our Deicsonze and Calf Organ and my external KB's sounds. Definitely an LMS synth problem, I'd say. When I move the small note out of the way up or down, the stuck note does not occur. Your voice allocation or voice stealing code perhaps? Tim. > > Thanks, > Jeff |
From: Jeffrey H. <jhu...@ya...> - 2012-04-23 00:37:06
|
> Verified. Somehow you closed the Arranger. > Click View -> Arranger View to see it again. Ah, makes sense... I was closing the arrangement window before closing the parent window, I must've saved the project whenever the "project has unsaved changes..." dialog popped up, therefore saving the closed arrangement window to the project state. > And as you say you held shift. Back to the last email I sent, I think it's a combination of running a fairly high display resolution makes the line so thin that it's very difficult to actually get the mouse over the line so that the cursor will appear. I have to make several passes over it very slowly while holding shift to actually get a cursor, which was how I missed it on the first ~10 attempts.. I think making the automation envelope ~4px thick instead of 1px(?) thick would fix the problem. >OK this sounds weird. What theme and MusE Qt style (Appearance Settings) >are you using? I was using the "Keep Qt System Style", but I tried a few others just now, and all the same thing. >We've got a double note entry in the fifth part of Track 1, >at bar 006.03.288. > There are two notes there, one is small at len=36, the other is len=272. > Tested OK with our Deicsonze and Calf Organ and my external KB's sounds. > Definitely an LMS synth problem, I'd say. >When I move the small note out of the way up or down, the stuck >note does not occur. >Your voice allocation or voice stealing code perhaps? Quite possibly... I think that's something I can probably fix then, but I think that might allude to a problem elsewhere, or at least areas that could possibly be improved for these reasons: 1. I recorded that loop on my M-Audio Oxygen 49 keyboard. The keyboard itself or it's driver may have sent the notes like that(obviously I didn't hit the same key twice simultaneously with 2 different releases), or that could've even been a bug on Muse's end(but I would think it's probably the MIDI keyboard or it's driver). Perhaps Muse could introduce some sort of duplicate note filtering into the recording process? I can't imagine a situation where that could ever be a desirable behavior. 2. I couldn't tell that the notes actually overlapped because there was no visual indication. Maybe you could create a visual indictator, or maybe just not allow overlapping notes at all? I think that a good strategy would be that when, for example D#-3 plays, and another D#-3 plays again without a note-off event, that a note-off event should be fired immediately before firing a 2nd note-on event on the same key. It might also be good to track where Muse has sent a plugin a note-on event, and not send a note-off event if a note-on was never sent, although you have to be careful there because any bugs in the code might result in a whole slew of random hung notes. Of course, if 2 note-on events fire simultaneously on the same key (or within a very short time of each other), you probably just want to discard the first note-on and the 2nd note-off. I say the 2nd note-off because it should be apparent that somethings wrong when the same note fires twice at the same time, and it's probably not a good idea to take for granted that a 2nd note-off event will ever actually fire. Thanks, Jeff |
From: Tim E. R. <ter...@ro...> - 2012-04-24 02:48:01
|
On April 22, 2012 5:36:58 PM Jeffrey Hubbard wrote: > >OK this sounds weird. What theme and MusE Qt style (Appearance Settings) > >are you using? > > I was using the "Keep Qt System Style", but I tried a few others just now, > and all the same thing. Saw the snapshot. Weird, man. What the ...? So by the attached terminal you sent (the GTK warnings) I was reminded it's Ubuntu you are running, thus Gnome or Unity? Can you dig around and try to find out what KDE or Qt theme your system is using? Oh - and try this: Please go to Appearance settings and change MusE's Qt theme setting to say, Oxygen (the standard for MusE) or try some others. Can't test here, it's KUbuntu. Help ...? Tim. |
From: Tim E. R. <ter...@ro...> - 2012-04-23 03:10:53
|
On April 22, 2012 5:36:58 PM Jeffrey Hubbard wrote: > > Verified. Somehow you closed the Arranger. > > > > Click View -> Arranger View to see it again. > > Ah, makes sense... I was closing the arrangement window > before closing the parent window, I must've saved the > project whenever the "project has unsaved changes..." dialog > popped up, therefore saving the closed arrangement window > to the project state. > > > And as you say you held shift. > > Back to the last email I sent, I think it's a combination of running a > fairly high display resolution makes the line so thin that it's very > difficult to actually get the mouse over the line so that the cursor will > appear. I have to make several passes over it very slowly while holding > shift to actually get a cursor, which was how I missed it on the first ~10 > attempts.. I think making the automation envelope ~4px thick instead of > 1px(?) thick would fix the problem. Yeah I've noticed that. A bit fussy sometimes. > > >OK this sounds weird. What theme and MusE Qt style (Appearance Settings) > >are you using? > > I was using the "Keep Qt System Style", but I tried a few others just now, > and all the same thing. Possible to get a snapshot of the open menu? > > >We've got a double note entry in the fifth part of Track 1, > >at bar 006.03.288. > > > > There are two notes there, one is small at len=36, the other is len=272. > > Tested OK with our Deicsonze and Calf Organ and my external KB's sounds. > > Definitely an LMS synth problem, I'd say. > > > >When I move the small note out of the way up or down, the stuck > >note does not occur. > >Your voice allocation or voice stealing code perhaps? > > Quite possibly... I think that's something I can probably fix then, but I > think that might allude to a problem elsewhere, or at least areas that > could possibly be improved for these reasons: > > 1. I recorded that loop on my M-Audio Oxygen 49 keyboard. The keyboard > itself or it's driver may have sent the notes like that(obviously I didn't > hit the same key twice simultaneously with 2 different releases), or that > could've even been a bug on Muse's end(but I would think it's probably > the MIDI keyboard or it's driver). It's possible the notes were in fact played at different times but somehow our quantization moved them together slightly. Check the menus there's a quantization dialog I think. > > Perhaps Muse could introduce some sort of duplicate note filtering into the > recording process? I can't imagine a situation where that could ever be a > desirable behavior. Someone added that on one of the menus I think. Remove Overlapping Notes I think. > > 2. I couldn't tell that the notes actually overlapped because there was no > visual indication. Maybe you could create a visual indictator, or maybe > just not allow overlapping notes at all? You're in luck. Look closely, all drawing has transparency. Overlapping parts and notes are see-through, including the black selection colour. You can adjust the transparency in the Appearance Settings -> Colors from 0 completely see-through, to 255 completely opaque. It's set at 190 or something by default. You may need to adjust it. The transparency for part and note /borders/ is fixed at 100% opaque. > > I think that a good strategy would be that when, for example D#-3 plays, and > another D#-3 plays again without a note-off event, that a note-off event > should be fired immediately before firing a 2nd note-on event on the same > key. It might also be good to track where Muse has sent a plugin a note-on > event, and not send a note-off event if a note-on was never sent, although > you have to be careful there because any bugs in the code might result in a > whole slew of random hung notes. > > Of course, if 2 note-on events fire simultaneously on the same key (or > within a very short time of each other), you probably just want to discard > the first note-on and the 2nd note-off. I say the 2nd note-off because it > should be apparent that somethings wrong when the same note fires twice at > the same time, and it's probably not a good idea to take for granted that a > 2nd note-off event will ever actually fire. > Mm, I'd have to say our note-on, note-off, and stuck notes handling is pretty solid now, I'd be surprised if there's still errors like that. Although, my last major work there was only months ago. So it just shows how bugs can pop up. Your file works with other synths, and ext. HW via midi. We have a 'notes to be played' list, and a 'stuck notes' list which is automatically maintained according to note length when the notes are cued up to play. The notes are pretty much guaranteed to be told to turn off when their time runs out or when stop is hit. And it should work when overlapping like this. Cheers. Tim. > > Thanks, > Jeff |
From: Allan K. <son...@ii...> - 2012-04-23 05:52:20
|
Hi Tim, Overall this works well. I can now use MusE again realistically for arrangement Something I noticed with the 'Midi Port' dialog. If you try and set a default out channel on one port, then try to set another one on another port the original disappears... e.g. set port 1 to default out on channel 16 then port 2 on channel 15 the first one disappears. (surely this is actually a bug?) This isn't critical to my usage but a very nice to have once working properly. It also would be nice if in the Global Settings Menu a specific template could be chosen instead of default.med and if the read MIDI port configuration could be stored in here. I can live with the current configuration but again this would be a really nice to have.. > > 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. > |
From: Tim E. R. <ter...@ro...> - 2012-04-23 06:21:32
|
On April 22, 2012 11:10:36 PM Tim E. Real wrote: > On April 22, 2012 5:36:58 PM Jeffrey Hubbard wrote: > > 1. I recorded that loop on my M-Audio Oxygen 49 keyboard. The keyboard > > itself or it's driver may have sent the notes like that(obviously I > > didn't hit the same key twice simultaneously with 2 different > > releases), Right, sorry just read that bit again. OK let's try to decode this file, I want to get to the bottom of this, Geoff had some issues with tiny ghost notes at the bottom of the editors but that was surely different I think. 1) You /played/ these parts on the Oxygen keyboard while MusE was recording? Or you /played/ /back/ the notes on the Oxygen without touching the keyboard, while MusE recorded? Or you /drew/ the notes in MusE? The random note velocities suggest not. The random velocities of the two overlapping notes suggest you really did play them at some point, but when... If you played the notes, I find it odd that all the notes in all the parts start perfectly on a 16 snap boundary. And yet, their lengths are random. You could not have played it that perfectly, could you? This suggests you did some processing after you recorded the notes, or else some kind of accidental quantization of start times occurred. If you played back the notes on the Oxygen then did you use MusE's sync features or just let it run asynchronously? If it exists as a song on the Oxygen - keep it so we can try some more tests. 2) A clue may be found in your folder containing this song. See if there's a .med.backup of the file created when you edit, then save, a song. Rename it as a .med, open it and see what's there. 3) I notice you were looping although it was not at that offending part. This is certainly one way overlaps can occur during recording. Possibly you looped that offending part before? 4) I notice from your file, you are using the ALSA devices to (at least) record from. (The device names told me.) Can you give us a printout of MusE starting? Specifically look for "Not running SCHED_FIFO" stuff, and watch what ALSA timer rate it gives you: ~1024Hz=good ~100Hz=bad. Have you tried using the Jack devices? Although, shouldn't be any problem with the ALSA driver so don't bother if you're busy. Also what Jack audio period size are you using etc. You can turn on debugging messages for us with the -D switch. > > or that could've even been a bug on Muse's end(but I would > > think it's probably the MIDI keyboard or it's driver). > > It's possible the notes were in fact played at different times but > somehow our quantization moved them together slightly. > Check the menus there's a quantization dialog I think. Ah sorry, I think MusE used to quantize while recording but now it just has an editing dialog. Hmm... > > > Perhaps Muse could introduce some sort of duplicate note filtering into > > the recording process? I can't imagine a situation where that could > > ever be a desirable behavior. > > Someone added that on one of the menus I think. > Remove Overlapping Notes I think. > > > 2. I couldn't tell that the notes actually overlapped because there was > > no visual indication. Maybe you could create a visual indictator, or > > maybe just not allow overlapping notes at all? It's an interesting suggestion, I've never considered not allowing any overlapping at all before. (Would it make editing freaky? Like when dragging notes: Auto-combine them? Or bump the others away? Plus Undo headaches?) AFAIK Many synths allow such a condition, they just sound two identical notes, and I guess arbitrarily turn off either one upon the first note-off. But I know what you're saying - MusE should have never put two notes together after it processed your recorded notes after you pressed stop while recording. Yeah, possible that's a bug, but depends on how you answer my conditional questions above, ie was it editing that did it... > ... > The notes are pretty much guaranteed to be told to turn off > when their time runs out or when stop is hit. > And it should work when overlapping like this. Right. Playback OK. But the question was /how/ did the overlapping notes get there in the first place... Tim. |
From: Tim E. R. <ter...@ro...> - 2012-04-23 06:47:17
|
On April 23, 2012 3:52:09 PM Allan Klinbail wrote: > Hi Tim, > > Overall this works well. I can now use MusE again realistically for > arrangement > > Something I noticed with the 'Midi Port' dialog. If you try and set a > default out channel on one port, then try to set another one on another > port the original disappears... > > e.g. set port 1 to default out on channel 16 then port 2 on channel 15 > the first one disappears. (Also I recently allowed /no/ default at all.) > (surely this is actually a bug?) No actually MusE only supports one output device at a time per midi track. This is why you don't see them listed in the 'output routes' menu. I mean, I will put them there eventually, and they will be exclusive, but for now the single output port and channel are conveniently displayed in the track info and track list. There was actually a strong desire from the group to keep it this way so we can see at a glance all of the single output devices and channels. Some day I'd like to add multiple output devices and channels. But how to satisfy the desire to see everything at once. Been thinking of some techniques. Maybe try to embed a small version of my midi routing matrix into the track list column? Expand vertically to see more? Now, for as long as I know MusE always supported multiple input devices and channels, and they used to be displayed right on the track info panel in two edit boxes. But it was not really correct at all (whatever channels you entered in the channel edit box would apply to /all/ selected devices at once.) So that's why I removed them and added this multiple input routes stuff. MusE has a bit of split personality like that. I said before it manages to use dual alternate techniques at the same time in several places. Like midi controller graphs vs audio controller graphs, which we've had long discussions over how to unify them - each technique has merits the other does not. > > This isn't critical to my usage but a very nice to have once working > properly. > > It also would be nice if in the Global Settings Menu a specific template > could be chosen instead of default.med and if the read MIDI port > configuration could be stored in here. Agreed. Enter the file name in the specific start song box for now. We need a browse button there. Thinking yesterday of how to accomplish other template filenames. > > I can live with the current configuration but again this would be a > really nice to have.. > > > > OK read my response to Allan about the menu closing (hold Ctrl). Er, same person, fooled me with the addresses. Tim. |