A newly discovered flaw in Clippings??????

[toodamnhip]

I have always loved using clippings. It is a way to move files from one chunk to another, one song to another etc.
The following flaw dawned on me before but I guess I didn;t really SEEEEE it until now.

When you bring over MIDI (or audio I would guess), ONLY THE TOP TRACK MAKES IT THOUGH.
So if you have 10 takes of MIDI piano, with takes 1-9 “hidden” in sub takes, and then make a clipping of that MIDI track and then drag that clipping into another chunk, you will NOT get takes 1-9 anymore as sub takes.
You will only get the top track you had active when you made the clipping.
In addition, what might have been take “10” in this scenario, (it was “10” and on top in the original file from whence it came), it will now be re named take “1”in the file you have imported it to.
I think this kind of messes up a really cool DP feature.
To me, it is a BUG.
It really screws me up too because I keep many IMPORTANT sub takes in MIDI and audio files and do take organization in MIDI files such that losing all sub takes and having the top take renamed screws me big time.
Too bad DP, this is a BUG unless someone around here explains to me how this is meant to be or can be avoided.
I guess the workaround is to expand all sub takes before making a clipping. A real pain.

[supersonic]

Did you write to Motu about this?I only use snippets of data here and there in clipping and never a full sequence. I will try that out. Thanks for the tip

[toodamnhip]

Did you write to Motu about this?I only use snippets of data here and there in clipping and never a full sequence. I will try that out. Thanks for the tip

I figure MOTU watches this forum. I see NO reason why they would not.

[doodles]

Not sure that's a bug, per se, it's just not how you want it to work.

The way I see it is clippings is a neat way to copy and paste data from one sequence tot another. (and keep it stored if you use that part, e.g. a drum sequence, etc) a lot. What you're asking it to do is the import data from sequence feature, which, granted, isn't as nice to use, as half the time it loads up all the VI's and clogs up the sequence

It is a brilliant feature, though.

[toodamnhip]

Not sure that's a bug, per se, it's just not how you want it to work.

The way I see it is clippings is a neat way to copy and paste data from one sequence tot another. (and keep it stored if you use that part, e.g. a drum sequence, etc) a lot. What you're asking it to do is the import data from sequence feature, which, granted, isn't as nice to use, as half the time it loads up all the VI's and clogs up the sequence

It is a brilliant feature, though.

It makes little sense to me to grab a particular track and have the fact that I made it a “clipping”, result in DP altering that track, either by altering it’s take #’s name in the new sequence it’s imported into, or removing takes from a track.
Makes no sense at all.

Should DP also be allowed to remove plug ins? , automation, etc?
If you take a track into a clipping, what should come BACK OUT is 100% what went in!

[doodles]

Yeah, but that's what I'm saying. It doesn't alter the "track", as it doesn't see it as a track. It sees it as data. So whatever you grab, whether you want MIDI data, audio data, plug-in data, that's what you drag and drop for clippings. If you want to copy the entire track as is, that's what the load function in the sequence is for. Feel for you that it doesn't work how you want it to though!

[toodamnhip]

Yeah, but that's what I'm saying. It doesn't alter the "track", as it doesn't see it as a track. It sees it as data. So whatever you grab, whether you want MIDI data, audio data, plug-in data, that's what you drag and drop for clippings. If you want to copy the entire track as is, that's what the load function in the sequence is for. Feel for you that it doesn't work how you want it to though!

“Load” still won’t get a track from one chunk into another INTACT.
I usually use clippings within the SAME session file, from chunk A to chunk B.
I also use it from song to song too.
But if Chunk A has a MIDI piano with 10 takes, #10 being on “TOP”, Load doesn;t help.
You still need to copy that piano into a clipping and then drag said clipping into chunk B. and you will LOSE takes 1-9.
Load doesn;t help.
Yes..I know OTHEr ways to successfully get those takes from chunk A to B, but “clippings” should do it right.
All they’d have to do is program clipping to see sub tracks when a track is put into it.

[toodamnhip]

Yeah, but that's what I'm saying. It doesn't alter the "track", as it doesn't see it as a track. It sees it as data. So whatever you grab, whether you want MIDI data, audio data, plug-in data, that's what you drag and drop for clippings. If you want to copy the entire track as is, that's what the load function in the sequence is for. Feel for you that it doesn't work how you want it to though!

“Load” still won’t get a track from one chunk into another INTACT.
I usually use clippings within the SAME session file, from chunk A to chunk B.
I also use it from song to song too.
But if Chunk A has a MIDI piano with 10 takes, #10 being on “TOP”, Load doesn;t help.
You still need to copy that piano into a clipping and then drag said clipping into chunk B. and you will LOSE takes 1-9.
Load doesn;t help.
Yes..I know OTHEr ways to successfully get those takes from chunk A to B, but “clippings” should do it right.
All they’d have to do is program clipping to see sub tracks when a track is put into it.

[MIDI Life Crisis]

Did you write to Motu about this?I only use snippets of data here and there in clipping and never a full sequence. I will try that out. Thanks for the tip

I figure MOTU watches this forum. I see NO reason why they would not.

It takes waaaay less effort to report something to MOTU than post a dozen messages here, and you are assured it will be tested. Assuming MOTU will see and respond because you posted here is no guarantee that's the way things will get fixed. That's your call, but then don't bitch if it doesn't get fixed.

[James Steele]

MOTU doesn't always see things here. As for it being a "bug" I'm not sure. Never occurred to me that it should include all hidden takes.

[stubbsonic]

I could see the logic having a selection of a region in the track as being 1-take deep, and selecting the entire track via track name to include the other takes making some sense.

Perhaps a logical solution would be to provide another way to copy entire tracks between chunks.

[cbergm7210]

Yes, I noticed this the other day grabbing an audio track with 20 takes on it and trying to port it to another sequence via clippings.

[Kurt Cowling]

I think the only way to copy a track from one chunk to another within the same file with all takes intact is to duplicate the source chunk, delete all unwanted tracks in the copy, drag this new chunk from the chunks window into the left pane of the TO window in the destination chunk. You will probably get a warning about conductor track info being duplicated. I normally choose not to bring in. The conductor track data from the dragged chunk.

[Kurt Cowling]

In my experience using "Load" DOES bring in all takes when moving a chunk from one file into another.

[FMiguelez]

For me the BIGGEST flaw of clippings is that they don't preserve folder structure. This is such an obvious missing feature that I hope MOTU will someday allow us to use folders with clippings.
Without this they loose like 80% of their usefulness to me.

ALSO, track folder structure should be preserved when loading chunks. Currently, you can load anything you want but you loose the folders.

To those of us who rely on folders for session management and organization, this is not only important, but vital... It's really no fun recreating these structures...

MOTU?