-
how can i get a nest to be a submaster? ie a common file instead of unique
hey again
i find the nesting feature valuable when i have a multi element build or sequence taht i want to work on seperately, and/or not clog up my main timeline with multiple video tracks. I understand that nesting creates a unique iteration such that if i copy the nest into a different part of my timeline or a different timeline it becomes independent (i dont really know why, but i do know this happens) meaning i can double click on one, make changes, and those changes will not appear on the other copies
BUT
what do i do if i Want those changes to appear? ie my nest is actually a submaster of something, so i can make changes to the nest and those changes will appear on all copies?
so far i have been exporting my nest as a native, current QT and re importing, copying the import to all the places i want to use it (and suggesting this to new users as well) but i wonder if i am missing something? like the way i make the nest etc?
i believe that even if i put the nest in my browser as a sequence, it stays independent, And if i make a new timeline and cut it in as a subtimeline, i get the nesting behavior ie each copy is still independent
any help?
thanx
bee eph
-
4 Replies
-
It’s only the copy/paste function that makes a unique iteration of the sequence.
If you nest a sequence there should be a copy in the Browser. If you use that copy from the Browser and edit it into a sequence. Any changes you make in that nest will be reflected in all other copies of the nest (except for the cut & pasted ones).
All the best,
Tom
Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 2 Editing Workshop” Class on Demand “Complete Training for FCP5” and “Final Cut Express Made Easy” DVDs
-
Yep. And unfortunately the copy / paste things changes with each version of FCP, as does some other features like ctrl+v.
Anyway, it used to be that if you copy’d and pasted that it made a new iteration, but if you option+dragged it kept the connection to the one in the browser. Very nice if you can keep up with it. In fact, it might have been the other way ’round. However, last time I checked they broke it and now option drag or copy and paste makes a new iteration. So be careful in future versions. You could end up making changes to what you think is a copy, but isn’t.
-
[Bret Williams] “Anyway, it used to be that if you copy’d and pasted that it made a new iteration, but if you option+dragged it kept the connection to the one in the browser. Very nice if you can keep up with it. In fact, it might have been the other way ’round. However, last time I checked they broke it and now option drag or copy and paste makes a new iteration. So be careful in future versions. You could end up making changes to what you think is a copy, but isn’t. “
Yeah. This is a rather dangerous feature as presently constituted. They should probably eliminate the whole copy/paste exception and add a checkbox to the nesting dialog to decide whether the nest updates in all instances or not. The dialog would then appear upon creation of a nest under all circumstances…would slow some people down a bit, but prevent a lot of confusion.
-
ooooooooooooooh
so does this mean that when i drag my nest out of the destination timeline to the browser (or a bin) it too becomes a seperate iteration? and what happens if i drag my nest from the root browser level, to a bin? is that a seperate iteration?
it seems that fcp makes a lot of distinctions between edit/record (F9 F10 F11) and cut and paste. I think thats where i have been getting slowed down, even after several months. I am used to cut a paste being just another waht to insert/overwrite
oh well…silly me!
thanx tom!
Reply to this Discussion! Login or Sign Up