Rob Mackintosh
Forum Replies Created
-
[Jeremy Garchow] “Meaning, you kept an Event of just the Project compound clips?”
Yes.
[Jeremy Garchow] “I guess it keeps overall size of any one file down to a minimum but doesn’t reduce the cumulative file size. It is treating the symptoms, but not the overall problem.”
One of the problems being the inefficiency of the FCPX database format when dealing with multiple sequences.
Given the apparent similarities between the .fcpevent and .fcpproject files Apple could easily bring the metadata functions of the event browser into the project library, along with multiple sequences per project. The problem would be the performance.
Apple seem to have forgotten that performance is a feature.
As for screwing up the XML I’m sure someone could write an utility that parsed the event XML and created separate project XMLs for each compound clip.
-
[Jeremy Garchow] “There is the compound clip in the Event situation, but it’s certainly a workaround and causes bloat as has been pointed out. “
Would the bloat occur if you had the “project event” only contain sequences i.e referencing media in other events (preferably on a different drive)?
I created two identical sequences (4 clips, cross dissolves, generator, on primary storyline, one title connected) one in a compound clip within an event, the other as a project.
I was adding media from another event. The .fcpproject and .fcpevent files ended up around the same size, and increased by a similar amount as each edit was made. -
Should mention if you are going to use this to do your primary grade and create a look it is best to apply two instances.
For the grade I apply it to the clip then for the look I apply the effect to an adjustment layer (title without text) like RGB House’s Total Adjustment.
That way you can apply the look across multiple clips and the blending modes don’t mess up your primary grade. You can also easily stack, name and try out multiple looks.
Another trick is to use multiple adjustment layers within an audition to try out different looks.
Tested this with wvl_ColourGrade and the color board.Place an adjustment layer on top of the clip(s) right click and duplicate as an audition (or alt y) Do this for as many looks you want to try. Cycle through each audition and add effects, color board adjustments to taste. You can also name each version in the info tab of the inspector.
[I found that if you drag an adjustment layer onto an existing layer and choose add to audition that the changes in the audition aren’t reflected in the viewer, although if you finalize the audition they are applied]
-
Not sure how you reconnected the media but try this:
Create a new event, import original media for that “reel”, take old event offline, relaunch and reconnect.
-
If you can split the project into smaller sections and turn off rendering.
I think the project database can choke having to reference both the clips and the render files, especially with compound clips.
-
That’s no good.
Have you had a look at the XML?
-
FCPX is reading the flattened preview that’s generated and embedded in the psd when you “maximize compatibility”.
Reproduced this – created file from scratch in Photoshop, layered a couple of stills, adjusted opacity and added a text layer, saved two versions – on with max compatibility and one without.
One with max compatibility is fine. The other version shows a thumbnail in the Finder but is all white in quick view, as it is in FCPX.
When you drag a still from Aperture it does something similar – brings in the preview file at whatever res
you have set in Aperture. -
Since upgrading to 16GB of RAM I’ve had no crashes. Things still get sluggish with multiple layers of titles.
Motion 5, however, crashes repeatedly when editing an effect or title and FCPX is open.
Seems to happen more on Rigs and when you have an instance of the effect applied to a clip in the FCPX timeline. -
Chopping up compounds can cause problems.
Sounds like the project database file has corrupted.
I ran Instruments (comes with Xcode – free download App store) when loading my old project and it returned multiple Core Data Faults:
[NSSQLCore newValuesForObjectWithID:withContext:error:]
[NSPersistentStoreCoordinator(_NSInternalMethods) newValueForRelationship:forObjectWithID:withContext:error:]
Hopefully conforming the project with the original files will fix things.
-
How big is your project file?
I had the same experience with RAM and the swap file. Swap file ate up about 40GB.
Running an older machine than you but with 16GB Ram.The issue was with the project.
Once you have the project open export the XML and have a quick look for anything unusual in a text editor.
Deleting render files and duplicating the project might work. You could try copying the entire timeline and pasting into a new project. This will probably take a while given your issues.
In my case I copied 15 minute sections from the original project into four separate projects.
There was a bit more involved but first have a look at the XML.