View Single Post
Old 07-03-2010, 10:02 AM   #9
Lawrence
Human being with feelings
 
Join Date: Mar 2007
Posts: 21,551
Default

You use a GM patch plugin (I guess) on the track and/or manually put it into a controller lane for the track in the key editor. Obviously, in most sequencers those things are on the midi track class TCP like with Cubase, Acid, etc and are pretty standard and they give visual feedback of status.

Since there is no midi track class there can't really be (yet, without some clever thought on when and how to show them) "context specific" controls for midi like that without it being kind of a mess. Or those things would be all over your audio track TCP's when you're not even using midi.



I think to address this kind of thing Reaper will eventually need some kind of inspector. When it comes to workflow in general, having things on one single flat work surface (imo, as opposed to various dialogs popping up) is always better. An inspector, info line, or other various methods hosts use to get at those kinds of things are just optional expansions of that same single flat work surface.

So you kinda have multiple choices as to how you want the information presented and how you'd prefer to see or edit it.


Last edited by Lawrence; 07-03-2010 at 10:16 AM.
Lawrence is offline   Reply With Quote