Quantize in main window?

hi folks. i can't seem to be able to quantize midi notes within the main Reaper arrange window (without having to open the midi piano roll). is this possible? can I just select a midi region and hit the Q button to quantize all notes in that region (without opening piano roll)? thanks!!!

People have been asking for this for years. It's not possible. The next closest thing is to open the inline editor, quantize, then close the inline editor. But, for anyone that uses MIDI regularly, that's still two steps too many...

There's a give an take with engineering decisions like this so you take the good with the bad. The universal track class is good (loved by many) but the flip side of that (no specific midi track classes) is well, no midi track classes, which means no midi fader and pan with the standard fader/pan and generally no standard TCP items for midi like a transpose setting on every TCP where you just type in a value and some other things that are pretty standard on midi track TCP's or inspectors. You can't really stack everything necessary to address midi, instrument and audio tracks onto one TCP without it being really cluttered, without an inspector or similar... especially if most of the standard things can't be optionally hidden. So the alternative is to have to go elsewhere for those things or use keystrokes.

I'm saying that quantize, transpose, midi channel, patch and bank lists and the multiple other midi related things that some people may want to be immediately available and visible in arrange via a mouse (and for feedback and/or current status purposes) require some additional considered thought because there is only one track class to put all of that stuff on and no inspector to share the load. That's all. They can put all of that stuff on the TCP right now along with the things that are there now if they wanted to, but it would be one big cluttered mess.

If I had Justin's ear over a shot of Jack Daniels I would honestly ask why there isn't an *optional* real midi track class aside from the universal track class. I'm not really sure why being able to say that one thing "Only one track class for everything!" is so important to so many people, since it would still be there afterward, the universal track, anyway. This would be more, not less. A midi track with cc fader, pan, meter and all the standard stuff on the TCP. Don't need it? Ignore it.

I really don't think this is an issue of needing separate track types. Surely Reaper can tell if a selected item contains audio or MIDI data. It feels more like a prioritization of development than any engineering roadblock. I think if there were any 'hard-core' MIDI users over at CockosHQ quantizing from the main window would've been possible years ago, if only because the devs would likely be just as frustrated in their own compositions by this 'less-than-eloquent' implementation, as so many others who do rely heavily on MIDI appear to be. ;)

It doesnt have to be a fixed track type; like you say it could just be a "tag" that you can change later. It just has to be tagged or marked or whatever that it's a MIDI track and not just a Universal track. DF

The thinking is that it isn't tagged as "a MIDI track", but as whatever you want. MIDI is just an example name to make you guys happy with it. It stays a universal track, just the visible controls change to those you want to see. Saying "just a universal track" puts the perspective upside down, as the universal track is the whole thing and the track with MIDI controls just a partial excerpt of the whole picture.

What would you want besides Midi and Audio? I think we should stop going round in circles about what it's called -- we can start out with Midi and Audio -- and just get those features onto the TCP by default already :) If we start out with "Audio" and "Midi" that would be good enough, or "Universal" and "Midi". I don't care how they implement it; they could weld a ReaMidiControl in thre and just change the presentation. It's the exposition of the features that I think we all want not worrying about how they do it internally. But yes I think people should be able to change the track type at will and not have it be a "fixed" type. It really just controls UI presentation. I wouldn't say that a "Midi" track just gets "partial" -- a Midi track with an embedded VSTi would still have an audio path, it's just that the Pan/Volume would send Midi by default and rechannelize the data to an "output" channel. And it would expose more features -- not less -- than a normal track such as Patch Name, etc. DF

is it realy that hard to open the midi editor? you could have done it 100 times reading this thread..... this ain't pro tools and I for one dont want it to be... b