From: Geoff B. <ge...@la...> - 2011-09-23 00:33:04
|
g'day Tim; I still have to enable the "all" box in every midi track for inputs despite having selected the default in channel "all" option in the midi devices dialogue. Have I missed something (again) ? Please can we get rid of this crap fellas - just go back to the good old days when a midi in device just worked? It offers no good feature and just makes work for the user. There is never a use case where you want to do anything with a midi input device other than have it input data - period :) In 21 years of midi sequencing I have never wanted to do anything else.. (apologies if I have set it up the wrong way or something - but if I have the design is flawed anyway imho) thanks g. |
From: Tim E. R. <ter...@ro...> - 2011-09-23 04:18:26
|
On September 22, 2011 08:36:25 pm Geoff Beasley wrote: > g'day Tim; I still have to enable the "all" box in every midi track for > inputs despite having selected the default in channel "all" option in > the midi devices dialogue. Have I missed something (again) ? Go to MusE Settings -> Midi Ports/ Soft Synth and in the list click on the "Def in ch" column and in the popup list of channels click on "Change all tracks now". This retroactively applies the selected input channels to all existing tracks. Does this not work for you? Tim. > > Please can we get rid of this crap fellas - just go back to the good old > days when a midi in device just worked? It offers no good feature and > just makes work for the user. > > There is never a use case where you want to do anything with a midi > input device other than have it input data - period :) In 21 years of > midi sequencing I have never wanted to do anything else.. > > (apologies if I have set it up the wrong way or something - but if I > have the design is flawed anyway imho) > > thanks > > g. > |
From: Geoff B. <ge...@la...> - 2011-09-23 04:26:27
|
On 09/23/2011 01:48 PM, Tim E. Real wrote: > Go to MusE Settings -> Midi Ports/ Soft Synth and in the list click on > the "Def in ch" column and in the popup list of channels click on > "Change all tracks now". > This retroactively applies the selected input channels to all existing tracks. > Does this not work for you? ah yes, that does work. but it's just too much configuration for such a basic midi requirement. - it should be the default behaviour. you should never have to select a midi input port - they should be just there /_always_/. If you can demonstrate a meaningful use case where such flexability is even remotely useful (i've never seen/had one) I'll shutup; otherwise nplease just make Muse2 deliver all the midi input ports automatically. the way it used to be. It's just too complicated the way it is for no benefit at all. ;) best, g BTW, things are working/looking/sounding great :) - stable too so far |
From: Tim E. R. <ter...@ro...> - 2011-09-23 04:54:28
|
On September 23, 2011 12:29:48 am Geoff Beasley wrote: > On 09/23/2011 01:48 PM, Tim E. Real wrote: > > Go to MusE Settings -> Midi Ports/ Soft Synth and in the list click on > > the "Def in ch" column and in the popup list of channels click on > > "Change all tracks now". > > This retroactively applies the selected input channels to all existing > > tracks. Does this not work for you? > > ah yes, that does work. but it's just too much configuration for such a > basic midi requirement. - it should be the default behaviour. It is. When you create new tracks, those selected default input channels in the "Def in ch" column are applied to the track. Is this not working? So long as you create your devices first before any tracks, everything should be automatically connected. Is this not working? It can't get any simpler. Tim. > you should > never have to select a midi input port - they should be just there > /_always_/. > > If you can demonstrate a meaningful use case where such flexability is > even remotely useful (i've never seen/had one) I'll shutup; otherwise > nplease just make Muse2 deliver all the midi input ports automatically. > the way it used to be. > > It's just too complicated the way it is for no benefit at all. > > ;) > > > best, > > g > > BTW, things are working/looking/sounding great :) - stable too so far |
From: Geoff B. <ge...@la...> - 2011-09-23 05:02:17
|
On 09/23/2011 02:24 PM, Tim E. Real wrote: > It is. When you create new tracks, those selected default input channels > in the "Def in ch" column are applied to the track. > Is this not working? I see - it is working. Still think that this whole scenario should never happen. g. |
From: Florian J. <flo...@we...> - 2011-09-23 13:31:09
|
i have an idea for simplifying this: per default, ALL devices/channels are selected for midi IN on each track. also for imported midi files! as long there's no track marked for "record", (or even then? config option ;) ), midi input is always piped into the currently active track. with "currently active" i mean: if the arranger is the active window, then use currently selected track(s) if some midi editor is the active window, then use the currently active part's parent track. if no part is currently active (can happen in the score editor), use the arranger's currently selected track(s) as above. i do see that power users with multiple keyboard manuals and/or an extra drum set might want to specify own channels for certain tracks, and want full control over which track is used for midi thru and which isn't. this will be still possible but the "normal" user simply wants it work. with my proposed changes, exactly that is possible: start muse, select a track, play a note, done! greetings flo |
From: Geoff B. <ge...@la...> - 2011-09-23 22:10:54
|
this is how it used to be and how it should always be imho go flo! g. On 09/23/2011 11:29 PM, Florian Jung wrote: > i have an idea for simplifying this: > > per default, ALL devices/channels are selected for midi IN on each > track. also for imported midi files! > as long there's no track marked for "record", (or even then? config > option ;) ), midi input is always piped into the currently active track. > with "currently active" i mean: > > if the arranger is the active window, then use currently selected track(s) > if some midi editor is the active window, then use the currently active > part's parent track. if no part is currently active (can happen in the > score editor), use the arranger's currently selected track(s) as above. > > i do see that power users with multiple keyboard manuals and/or an extra > drum set might want to specify own channels for certain tracks, and want > full control over which track is used for midi thru and which isn't. > this will be still possible > > but the "normal" user simply wants it work. with my proposed changes, > exactly that is possible: start muse, select a track, play a note, done! > > greetings > flo > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Geoff K. <gs...@gm...> - 2011-09-23 14:36:47
|
Just my $0.02. This really doesn't bother me, but I can see that it could be simplified possibly for some user cases or users. What about a new button or dialog above the arranger that resets all midi inputs to the default or to ALL inputs? Or selects the input keyboard port/channel for all? I have found it necessary to change inputs in the past so wouldn't want to mess that up much. I like the changes Tim has worked on over the last year and like the flexibility of changing the channels when needed. However, it might be nice to change the input keyboard on all tracks with less clicks. Geoff K. |
From: Geoff B. <ge...@la...> - 2011-09-23 22:15:03
|
On 09/24/2011 12:36 AM, Geoff King wrote: > This really doesn't bother me, but I can see that it could be > simplified possibly for some user cases or users. What about a new > button or dialog above the arranger that resets all midi inputs to the > default or to ALL inputs? Or selects the input keyboard port/channel > for all? i disagree here Geoff (nice name btw :) ) . to me this has been a totally useless configuration and just makes work. truth is we never want to make a midi input dysfunctional. if you can show me a use case where it would be useful i'd like to hear it. let's just go back to all midi inputs active always and i'll shut up :D best g. |
From: Florian J. <flo...@we...> - 2011-09-24 10:32:06
|
Am 24.09.2011 00:18, schrieb Geoff Beasley: > On 09/24/2011 12:36 AM, Geoff King wrote: >> This really doesn't bother me, but I can see that it could be >> simplified possibly for some user cases or users. What about a new >> button or dialog above the arranger that resets all midi inputs to >> the default or to ALL inputs? Or selects the input keyboard >> port/channel for all? > i disagree here Geoff (nice name btw :) ) . to me this has been a > totally useless configuration and just makes work. i don't think it's per se useless. it's however useless for many users. with sane default settings, this saves 80% of all muse users from frustration, because it justs works, and requires the other 20% to do one more click for setting up things properly. i think this is a fair tradeoff > > truth is we never want to make a midi input dysfunctional. if you can > show me a use case where it would be useful i'd like to hear it. let's > just go back to all midi inputs active always and i'll shut up :D making it dysfunctional: no idea but being able to have great flexibility over which input controls which track, and being able to temporarily turn off one track's midi thru: definitely: have a master keyboard with two manuals. the first can control track 1,2,3 (but you only want one at a time), the second 4,5,6. then you need this flexibility. this also allows you to turn off midi thru completely, which is possible, but indeed senseless > > best > > g. > greetings flo |