Snapshots & Compound Clips

With the new folder structure and the new 'hard wire' features with the media does the same hard wiring come into play when using Compound Clips?

When you duplicate a Project which has a CC in the new duplicated Project now has a new independent CC clip in which you can place effects on etc and they won't be mirrored. This means a totally independent CC is created but is it hard wired to the CC that it was duplicated so the file size doesn't duplicate?

Here's the best way to look at snapshots vs. duplicate projects:

Snapshots - no matter what you do to your compound/multicam clips, your snapshot is frozen in time unless you dive into it and change it yourself directly (and it won't have any effect on the original project)

Duplicate projects - changes to compound/multicam clips will ripple through all instances of that compound clip in all duplicated projects

Depending on your workflow/what you're trying to do - one may be better than the othere... but now you have real versioning options no matter what you want to do.

Well put Sam!

Thanks for the reply Sam but I understand how they work. The question was do the Compound Clips get duplicated in size OR do they use the 'Hard Wired' approach?

For example in previous versions if you duplicated a CC in an Event your Event size would quickly increase.
In 10.1 if you create a number of Snapshots or Duplicate CC do the CC increase the size of the Library OR do the duplicated and Duplicated using Snapshot CC just reference the original media pretty much like the way 'media' is hard wired between Libraries and Events in 10.1

What do you mean by hard wired? We are talking about software, right?

Honestly, man, I have absolutely no idea, and that's a great question.

My GUESS is that... actually, I don't have a guess. I have no clue. What I do know is I haven't seen many stumbling blocks in terms of growing library size as we did in the first few version of X with event databases and compound clips. I guess the real question is at what point does the size of a library break down? In my tests so far, bringing in 40+ days of feature footage, it hasn't mattered much. I'll know a bit more in the next week or two, though as we get into some deep testing and heavy editing with a large feature.

However, if anyone actually does know... I'd actually love to know the answer to this. Sorry for misunderstanding.

Your media is never in the library, is it? How big is the library getting? How much rendering have you done? Thinking on a feature this can add up to a honking lot of files.

I think I need to clarify my terminology. When I mentioned Hard Wired I meant Hard Links the new way in which FCPX manages media etc in the Events/Library.

So to go back to my original post if you have a Compound Clip that is used over a number of Events or Projects if you change it the changes will reflect system wide across all the Events/Projects that it is in. Because of the new Hard link way in which FCPX works the media doesn't increase the sizes of the Events due to more and more CC being created. I believe previously when you duplicated a CC then your Events size increased?

So to follow on when you use the new duplicate project feature (which has a CC in) the size of the Event won't get bigger because of the Hard Links of the media. However my question was if you used the duplicate & create snapshot feature (with a CC in) and changed the CC would the Hard Link scenario still exist OR would it create a completely new CC and increase the size of the Event.
Reason I ask is because if you have a really big project your working on and you are doing a lot of versioning of projects the Event size could start getting a lot bigger if its treating the duplicate snapshot projects as separate entities opposed to a standard duplicate which wouldn't increase the Event size because it would be taking advantage of the Hard Link feature.

I don't think this is right. Increasing the number of compounds never increased the media nor appreciably increased the size of the event, though it did increase its complexity. I don't think there is any use of hard links here. Compounds are just part of the library/database database. Snapshots don't create another compound in the event oddly, not until you try to use Shift-F, at which point a new independent compound master is created in the event. Compounds are really just nested sequences that have always been in FCP.

Duplicating Compound Clips does increase the file size of an Event. The Event gets bigger as you place more media into the CC and when you duplicate the CC in the media the Event file increases in size. It doesn't however increase the Event exponentially due to duplicating the media.

Snapshot do create a Compound clip but it is hidden (from Ripple Training vids) but as you have mentioned when you Shift + F it does reveal it.

The compound isn't hidden. It only exists in the project. The size of compounds is negligible. I think what you're seeing is a build up of render files including peak data and thumbnails.

Tom Wolsky wrote: What do you mean by hard wired? We are talking about software, right?

Mark Spencer used this expression in some interview… and corrected himself to 'symLinks', which seems to be the technically correct wording…

… for simple folks like me, 'hardwired' is very illustrative, in case, you've never heard of the symLinks. :lol:

The term he used is hard links not hard wired and hard links are not used by compound clips. It has nothing to do with compound clips but the way the same media can appear to be in two places at once with duplicating it. It's no more hard links than a clip in the browser and a clip in a project referencing the sane media.