From: Florian J. <flo...@we...> - 2011-05-30 19:42:07
|
Hi i've noticed that you (actually) cannot set the channel for a drum track. i don't like the idea of this. it happens that i'm using drums on several channels to be able to use multiple patches. i think we should make the channel selectable, and make muse set up that channel as "drum" or "non-drum" automatically. also, there is some inconsequence with being not able to change the channel: if you create a MIDI track, at the side bar you can set it's channel if you change this track to "drum", then the channel-spinbox in the sidebar is NOT grayed out. you can still change the channel (and this takes effect!). as soon as you select another drum entry, the field gets grayed out. either fix this, or (preferably) make the channel selectable. what do you think about this? greetings flo |
From: Robert J. <spa...@gm...> - 2011-05-30 20:35:47
|
Hi Flo 2011/5/30 Florian Jung <flo...@we...>: > Hi > > i've noticed that you (actually) cannot set the channel for a drum > track. i don't like the idea of this. it happens that i'm using drums on > several channels to be able to use multiple patches. i think we should > make the channel selectable, and make muse set up that channel as "drum" > or "non-drum" automatically. > > also, there is some inconsequence with being not able to change the channel: > if you create a MIDI track, at the side bar you can set it's channel > if you change this track to "drum", then the channel-spinbox in the > sidebar is NOT grayed out. you can still change the channel (and this > takes effect!). as soon as you select another drum entry, the field gets > grayed out. > > either fix this, or (preferably) make the channel selectable. > what do you think about this? Hmm, ok. As matter of fact it was very recently I changed it to behave like this. The sidebar not being grayed out was a mistake though. It might be that I was wrong since you say it does have effect, I was quite sure it didn't. The reason that I changed it was actually to remove confusion since I think the intended way to change channels is from inside the drum editor, it can be changed /per/ drum. (Actually a very nice feature :) I will revisit it later, if it does indeed work I'll put it back the way it was, if a user knows how to use the per-drum setting they will (hopefully) understand that the track channel has been overridden. Regards, Robert |
From: Florian J. <flo...@we...> - 2011-05-30 20:47:10
|
Am 30.05.2011 22:35, schrieb Robert Jonsson: > Hi Flo > > 2011/5/30 Florian Jung<flo...@we...>: > >> Hi >> >> i've noticed that you (actually) cannot set the channel for a drum >> track. i don't like the idea of this. it happens that i'm using drums on >> several channels to be able to use multiple patches. i think we should >> make the channel selectable, and make muse set up that channel as "drum" >> or "non-drum" automatically. >> >> also, there is some inconsequence with being not able to change the channel: >> if you create a MIDI track, at the side bar you can set it's channel >> if you change this track to "drum", then the channel-spinbox in the >> sidebar is NOT grayed out. you can still change the channel (and this >> takes effect!). as soon as you select another drum entry, the field gets >> grayed out. >> >> either fix this, or (preferably) make the channel selectable. >> what do you think about this? >> > Hmm, ok. As matter of fact it was very recently I changed it to behave > like this. > The sidebar not being grayed out was a mistake though. > > It might be that I was wrong since you say it does have effect, I was > quite sure it didn't. > The reason that I changed it was actually to remove confusion since I > think the intended way to change channels is from inside the drum > editor, it can be changed /per/ drum. (Actually a very nice feature :) > oh, that's of course also a good concept let me think about this before undoing it again ;) > I will revisit it later, if it does indeed work I'll put it back the > way it was, if a user knows how to use the per-drum setting they will > (hopefully) understand that the track channel has been overridden. > > Regards, > Robert > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > |
From: Florian J. <flo...@we...> - 2011-06-02 17:42:17
|
Am 30.05.2011 22:47, schrieb Florian Jung: > Am 30.05.2011 22:35, schrieb Robert Jonsson: > >> Hi Flo >> >> 2011/5/30 Florian Jung<flo...@we...>: >> >> >>> Hi >>> >>> i've noticed that you (actually) cannot set the channel for a drum >>> track. i don't like the idea of this. it happens that i'm using drums on >>> several channels to be able to use multiple patches. i think we should >>> make the channel selectable, and make muse set up that channel as "drum" >>> or "non-drum" automatically. >>> >>> also, there is some inconsequence with being not able to change the channel: >>> if you create a MIDI track, at the side bar you can set it's channel >>> if you change this track to "drum", then the channel-spinbox in the >>> sidebar is NOT grayed out. you can still change the channel (and this >>> takes effect!). as soon as you select another drum entry, the field gets >>> grayed out. >>> >>> either fix this, or (preferably) make the channel selectable. >>> what do you think about this? >>> >>> >> Hmm, ok. As matter of fact it was very recently I changed it to behave >> like this. >> The sidebar not being grayed out was a mistake though. >> >> It might be that I was wrong since you say it does have effect, I was >> quite sure it didn't. >> The reason that I changed it was actually to remove confusion since I >> think the intended way to change channels is from inside the drum >> editor, it can be changed /per/ drum. (Actually a very nice feature :) >> >> > oh, that's of course also a good concept > let me think about this before undoing it again ;) > i think this is a good concept which should be kept, but still must be improved: first, it must allow me to set the patch/bank on each channel used for drums; that's the whole point of using two channels: my keyboard has different patches i'd like to mix; but that's only possible with multiple channels second, it must set the used channels to "drum"; i don't know how this exactly works, but i know this is possible; then, it probably is a good idea to warn if a MIDI track wants to use a part used as drum-part, or vice versa, if you want to put a drum onto a channel which is already used in some MIDI track. what do you think about this? greetings flo > >> I will revisit it later, if it does indeed work I'll put it back the >> way it was, if a user knows how to use the per-drum setting they will >> (hopefully) understand that the track channel has been overridden. >> >> Regards, >> Robert >> >> ------------------------------------------------------------------------------ >> vRanger cuts backup time in half-while increasing security. >> With the market-leading solution for virtual backup and recovery, >> you get blazing-fast, flexible, and affordable data protection. >> Download your free trial now. >> http://p.sf.net/sfu/quest-d2dcopy1 >> _______________________________________________ >> Lmuse-developer mailing list >> Lmu...@li... >> https://lists.sourceforge.net/lists/listinfo/lmuse-developer >> >> >> > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > |
From: Robert J. <spa...@gm...> - 2011-06-03 09:23:23
|
Hi Flo, 2011/6/2 Florian Jung <flo...@we...>: >> oh, that's of course also a good concept >> let me think about this before undoing it again ;) >> > i think this is a good concept which should be kept, but still must be > improved: > first, it must allow me to set the patch/bank on each channel used for > drums; that's the whole point of using two channels: my keyboard has > different patches i'd like to mix; but that's only possible with > multiple channels Ah, yes, I think I understand. I mostly use just soft synths and it's not been a problem but I can see that may be helpful. What about adding a [configure] button last on each line for those extra options? > second, it must set the used channels to "drum"; i don't know how this > exactly works, but i know this is possible; > > then, it probably is a good idea to warn if a MIDI track wants to use a > part used as drum-part, or vice versa, if you want to put a drum onto a > channel which is already used in some MIDI track. Maybe, if it's not just in the way. I think there are legitimate, creative uses for reusing parts this way :) Regards, Robert |
From: Florian J. <flo...@we...> - 2011-06-03 16:23:33
|
Am 03.06.2011 11:23, schrieb Robert Jonsson: > Hi Flo, > > 2011/6/2 Florian Jung<flo...@we...>: > >>> oh, that's of course also a good concept >>> let me think about this before undoing it again ;) >>> >> i think this is a good concept which should be kept, but still must be >> improved: >> first, it must allow me to set the patch/bank on each channel used for >> drums; that's the whole point of using two channels: my keyboard has >> different patches i'd like to mix; but that's only possible with >> multiple channels >> i found out how this works: this is an addition of the yamaha XG standard: at this standard, drums are always on bank 127, no matter which channel (http://www.pcrecording.com/mididrums.htm). maybe we should create two buttons for the drum list: one labeled "set to XG", which automatically sets the bank to 127 for each used channel one labeled "set to GM", which automatically removes all stuff set by "set to XG" then, we have to implement some GUI which allows the user to set the channel's patches and banks IN the drum editor! the used channels should be locked for other midi tracks (playing trumpet on a track acquired by drums isn't a good idea ;) ) > What about adding a [configure] button last on each line for those > extra options? > no, a drum-editor-global "configure" button would be better because we cannot set this on a per-drum or muse-global basis, but on a per-"port/channel-combination"-basis i think we should not abuse multiple tracks for this, but offer this natively in the drumeditor greetings flo |
From: Florian J. <flo...@we...> - 2011-08-19 17:41:17
|
*bump* what do you think about this? then we could manage drums on different channels (because you want different patches for example) in ONE track also, muse currently doesn't offer any way to do this, even if i'd use multiple tracks; because you cannot set the bank or the patch on drum tracks such a function would really rock. ideas? proposals? improvements? greetings flo Am 03.06.2011 18:23, schrieb Florian Jung: > Am 03.06.2011 11:23, schrieb Robert Jonsson: > >> Hi Flo, >> >> 2011/6/2 Florian Jung<flo...@we...>: >> >> >>>> oh, that's of course also a good concept >>>> let me think about this before undoing it again ;) >>>> >>>> >>> i think this is a good concept which should be kept, but still must be >>> improved: >>> first, it must allow me to set the patch/bank on each channel used for >>> drums; that's the whole point of using two channels: my keyboard has >>> different patches i'd like to mix; but that's only possible with >>> multiple channels >>> >>> > i found out how this works: this is an addition of the yamaha XG > standard: at this standard, drums are always on bank 127, no matter > which channel (http://www.pcrecording.com/mididrums.htm). > maybe we should create two buttons for the drum list: > one labeled "set to XG", which automatically sets the bank to 127 for > each used channel > one labeled "set to GM", which automatically removes all stuff set by > "set to XG" > > then, we have to implement some GUI which allows the user to set the > channel's patches and banks IN the drum editor! the used channels should > be locked for other midi tracks (playing trumpet on a track acquired by > drums isn't a good idea ;) ) > > >> What about adding a [configure] button last on each line for those >> extra options? >> >> > no, a drum-editor-global "configure" button would be better > because we cannot set this on a per-drum or muse-global basis, but on a > per-"port/channel-combination"-basis > > > i think we should not abuse multiple tracks for this, but offer this > natively in the drumeditor > > greetings > flo > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is safe, > secure and there when you need it. Discover what all the cheering's about. > Get your free trial download today. > http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > |