How to edit length of MIDI region

[wwzeitler]

(I'm not 100% sure I have the vocabulary right. I understand a 'MIDI Region' to be a lane-tall box in Track View that contains MIDI events. Like a 'clip' in Cubase.)

So I have a MIDI region that starts a full beat before its first MIDI event. How would I trim that box to start at the first MIDI event?

Or more generally, I would expect to be able to select a MIDI Region, place the play head where I'd like to cut it, and do so, except that the scissor tool is disabled.

Thanks!

[stubbsonic]

It's probably best to think of those little rectangles as what DP is considering "likely selections" so you can click and/or drag that way. In actuality, a MIDI region is whatever MIDI you have selected. So you just need to know a few other ways to select a range when DP's lil time-rectangles of MIDI aren't useful (which for me is much of the time-- I've learned to completely ignore them). But now you know they are pretty arbitrary.

But you can also use the crosshairs to drag across the actual notes you want to select. Range selections can be much easier to control in the MIDI Graphic Editor, but if you want do this out in the Tracks Overview (which is fine) you may need to use some combination of horizontal zoom and/or holding down whatever key it is on Windows to temporarily bypass horizontal grid-snapping of your selection lasso.

You'll know you're pressing the right modifier key to bypass the grid when the crosshairs get a little smaller.

[wwzeitler]

What I'm trying to accomplish is to select my region for Bounce to Track. I have one 'MIDI region' (MR) that starts before the first MIDI event. When I try to select my region starting at the true downbeat, it won't select the MR that extends before the downbeat, so I have to start my selection before I have numerous stems to bounce, so the prospect of going in and editing the true start time of each isn't pleasant.

[wwzeitler]

When I select a region in the Sequence pane, my Bounce is unrecognizably hosed.

[stubbsonic]

I never use bounce-to-disk, I do ALL my bounces in realtime, manually, so I can't help you there.

However, it may be helpful to think of two processes. One is making a time-range selection, and the other is making the track selections.

The current time-range selection appears near the top-center of the tracks overview. In this window, you can make the time-range selection by dragging the crosshairs in any track(s) horizontally across the measure blocks of the tracks overview. Alternatively, you can use the I-beam cursor that appears when you hover over a specific part of the time ruler in the Tracks Overview or Sequence Editor Rulers. Dragging across the time-ruler itself makes the selection. Again, holding a modifier key will bypass the grid-snap for greater precision. Zooming horizontally will also help with precision.

Next, to select which tracks are involved; you can just click on track names, or hold down whatever Windows key helps you make multiple selections with subsequent clicks.

Others can advise about the particulars of bounce-to-disk. But you might need a new topic for that. Please read the manual for Bounce-to-disk. I expect you'll find what you need there.

[HCMarkus]

However, it may be helpful to think of two processes. One is making a time-range selection, and the other is making the track selections.

This! You should be able to select the exact time-range you desire in the Tracks Overview.

I find TO very handy for transferring MIDI Data and Audio from track to track. Also, data can be micro-selected in another window (like the SE), then moved within the TO, which can be zoomed out far enough that timing issues will not inadvertently be introduced when the data is moved. I have my editing windows locked to grid as default, disabling the grid with the Command Key for times I want to freely select or move data.

I, too, do real-time mix and stem creation. Busing and stem tracks are in place in my template, so I'm able to record my mix and all stems simultaneously. As such, the real-time approach takes nominally more time than bouncing and I can monitor the mix to verify the integrity of playback as it is created.

[stubbsonic]

I find TO very handy for transferring MIDI Data and Audio from track to track. Also, data can be micro-selected in another window (like the SE), then moved within the TO, which can be zoomed out far enough that timing issues will not inadvertently be introduced when the data is moved.

THIS! I'll just note that it is easy to accidentally deselect a region when switching from the MIDI graphic editor to the Tracks Overview (TO) so for me, I'm careful to click on the window's header when I bring the TO to the front.

And I should have also mentioned that I use the modifier key (COMMAND on Mac) to temporarily turn of the grid-snap for selection, but I release it when I drag-- to avoid inadvertently moving data horizontally when I don't mean to.

I, too, do real-time mix and stem creation. Busing and stem tracks are in place in my template, so I'm able to record my mix and all stems simultaneously. As such, the real-time approach takes nominally more time than bouncing and I can monitor the mix to verify the integrity of playback as it is created.

I'm glad to hear I'm not the only one. It certainly is possible for me to not have things bussed properly, so realtime bouncing isn't any more or less idiot-proof than bounce-to-disk; but often enough, I've found that as I monitor the mix as I go, I hear stuff to tweak during those passes. And as the final pass is printed I will have that old-school "that-was-the-one" sensation.

[HCMarkus]

I'll just note that it is easy to accidentally deselect a region when switching from the MIDI graphic editor to the Tracks Overview (TO) so for me, I'm careful to click on the window's header when I bring the TO to the front.

When performing operations like this, I'll have SE and TO both open within the Consolidated Window, so once data is selected in SE, all I have to do is click on it in the TO and drag.