MOTUnation.com

Is there a way to move data around so that all takes are included? For example, I record a track with multiple takes, then decide to omit a section. I'd like to be able to use the Edit>Snip to get rid of the section I don't want, yet still be able to choose from different takes and have data from after the edit be in the right place.

I was thinking I could use the SE, by doing "Show Takes" on all tracks, but that won't work for MIDI tracks...

Not really... Not without a boring and workflow-killing work around...
I wrote complaining about this like a year ago, along with some suggestions on how to fix it.
I would like to think DP10 will address this at some point, since it obviously could use improvement, just like the issue of how to deal with closed folders and its contents with time-related edits.

So what you have to do now is, every time you need to make time-related edits, you must "explode" your takes into tracks, edit away, and then implode them back in the form of takes.

I found about this the hard way, so I had to restore all the moved and out-of-sync takes by hand, one by one. I don't know whether that method is reliable or not.
I suppose DP still remembers the comped takes when you implode them back. I'd check first...

I wonder if maybe including the conductor track should tell DP that you want ALL Data to be affected, or maybe just an option key with the command would do it....

Yeah, this has always really bothered me. I've written to MOTU about it too, but the nature of comp takes, and the data structuring of DP projects makes it difficult. Comp "marks" are sort of a "pinned on" feature that doesn't really fit in with the rest of the project schema. It's not really part of a track's data in the conventional sense, so it's not beholden to the same rules and transformations.

I like your idea of selecting the conductor track as a way of telling DP to include comp data. However, what they REALLY need to do is have an actual "track preferences" window, per track, and have that be a toggle option. So many other useful features like MIDI keyboard splits to per-track input filtering could be done if they just added a track settings window.

As I think about it, if you select a time range for all tracks including the Conductor track in the TO window, it would be a logical for DP to assume you're wanting to affect ALL 'layers' of data.

SMS wrote:As I think about it, if you select a time range for all tracks including the Conductor track in the TO window, it would be a logical for DP to assume you're wanting to affect ALL 'layers' of data.

One would think that but, in trying to help a fellow member a few weeks ago with a similar (perhaps same) issue, I ran a test on a project copy.

I selected every track in the TO window within a defined range, say bar 10 through 20.

All tracks were highlighted within that designated range.

Then I hit the delete key. All info disappeared EXCEPT the Take 2, Take 3, etc. Underlying punch-ins or alternate takes within the SAME Take were deleted.

It appears that only what's "visible' is affected.

Does that help at all?

Buzzy




Sent from my iPad using Tapatalk

Yeah, Buzzy's right (unfortunately). Making a selection on the time ruler doesn't do anything special, other than act like you're selecting all visible tracks, but it's essentially the same as if you just drew a big 2D selection that encompassed all the of the tracks... it doesn't "drill down" into the takes, or anything that you couldn't do with a single mouse drag. Selecting the conductor track doesn't do anything at all, as the conductor track doesn't actually have any physical relationship with the other tracks.

But I think many of us can agree, that this is something sorely missing from DP.

Right. This is how I know it works. Of course, selecting the conductor does allow data there to be edited. For example, select an entire Chorus then do Edit>Trim and it deletes the Chorus and moves the rest of the sequence earlier in one operation, including markers, key sigs, meters, etc. in the Conductor Track if it's selected.

In particular for those types of operations (Snip, Splice, Shift), I think intuitively it should affect all 'layers'.

Maybe that should be true for all the menu-invoked operations, while moving data with the mouse and keyboard could just affect visible data?

Gotta be a logical way to implement this.

SMS wrote:Maybe that should be true for all the menu-invoked operations, while moving data with the mouse and keyboard could just affect visible data?

Bingo, put the option right below "Smart Selections"