Nicholas Kleczewski
Forum Replies Created
-
Yeah, there’s no reason to eliminate the project library. It’s a great place to use as a canvas for ideation and putting together final projects. There’s no reason, just like all NLE’s to give editors a choice. For versioning, donut making etc, the project library isn’t a great place for finals. Take the idea of Compound Clips and go further with it for those people who need that kind of functionality and leave Projects alone for who that works for.
If Projects could reference outside render files and there was a simpler way to switch more quickly between projects that might help the cause, but I don’t see apple doing that as the whole reason they invented separate projects I susposect was to keep media management rock solid and under the hood.
But more options are never a bad thing for Pros.
Director, Editor, Colorist
http://www.trsociety.com -
This is something sort of being discussed abstractly in the other FCPX forum currently as well.
Basically, your issue with the Project Library is one a lot have had. The solution is to use Compound Clips in an Event as sequences. That returns all the duplicating, iterating, donuts, retagging you want while always referencing a single set of render files and only adding what changes from clip to clip.
I like to do what Oliver does and use the Project library as a sort of canvas or work space for ideas, then when I have a sequence im ready to commit, i compound clip the whole thing. This adds it to the Event as its on standalone editable document. You can then duplicate from there or create new clips in which only tags are changed or whatever your situation is.
For a lot of reasons, I’d say its a good thing both options exist, but Apple certainly never thought of Compound Clips having that purpose originally.
Director, Editor, Colorist
http://www.trsociety.com -
I think its basically been stated elsewhere, but broadly: Apple created a monster with Compound Clips. One that it could never put back in its cage.
I dont think they ever originally intended Compound Clips to take on the life that they have. Remember they didn’t even use to populate themselves in an event after creation in a project till after 10.0.6. There was also a time when doing certain things to compound clips directly in the event and not a project didn’t work right, color correction i remember at one point was pretty broken. But Compound Clips fix so many annoyances that separate projects for every sequence iteration has.
How silly is it with each duped project requires its own set of render files to point too? Not with compound clips in an event. They are the missing link to rough cut editing and iterating.
So i think it was said best elsewhere, they’ve been undoing a few things since 10.0 and I’m all for it.
I hope next iteration brings back tracks that you can give dedicated role assignments too. Tracks 1-2 always get audio associated with a Dialogue role. 3,4 always automatically get Music role edited there, etc. Then toggle it so that this only persists with inserts and overwrites are made but when Q is used the video and audio get put into their own outside space until you decide where you want it to go. something like that….
Director, Editor, Colorist
http://www.trsociety.com -
C’mon guys, your arguing pretty stupid shit here. Anyone who bothers to come to this board is well aware of the extremely rudimentary feature set of FCP Legacy your talking about. Its just semantics and no one else educating anyone anything here.
Director, Editor, Colorist
http://www.trsociety.com -
I would agree that asset organization on the front end is better in nearly every way in FCPX than Legacy. Depends on if you throw things like buggy Favorites creation, spinning beach balls on large projects etc, but definitely a step up so large its hard to ever go back.
However, I would say its asset organization on the back end leaves quite a lot to be desired currently, particularly for sizable projects. For one, FCPX doesn’t respect the folder structure media was originally nested in. Yes, I know you can leave media right where it is, but the alias’ that are created in the Original Media folder are made all the same. The problem comes into large projects that very likely have same file names here and there. Due to its all in one folder methodology it can’t have files with the same name inside so it appends these aliases with (fcp2, fcp3, fcp4, and so on). All well and good, but there becomes management issues, for instance in importing XML from other programs like Plural Eyes or Resolve. Only when media is imported into one event does FCPX handle the same file name appending. If you import XML which always makes a new Event and then try any flavor of merging the two (many reasons why this would be desirable) FCPX says there are two files with the same name and operation can’t be performed.
And this doesn’t even get into the whole “addressable objects” issues and others that comes along with that.
I’m all for FCPX trying to make media managing “dummy proof” but I wish there was almost some kind of Advanced user On/Off switch or slider than let you turn off some file management efficiencies and data loading in exchange for better navigation performance which FCPX completely struggles with on huge projects.
I’m sure everything I said is arguable, but I must be on to something since I was contacted directly acknowledging the very problem and the film I ran into these problems with is now the guinea pig in their labs for a hopeful eventual fix.
Director, Editor, Colorist
http://www.trsociety.com -
Possibly even quicker than making new Timelines or Projects as they are actually called would be to make range selections or even multiple range selections and hit Opt-G making Compound Clips that now become your packages to more quickly pull from in your news story beats. You can really blast ass with this method when blasting ass is needed.
Director, Editor, Colorist
http://www.trsociety.com -
4GB of ram is not enough for FCPx frankly. It is a Ram hog. 16GB barely cuts it on a large project.
Director, Editor, Colorist
http://www.trsociety.com -
Cmd-B is all you need. Don’t even have to touch the mouse. You can be real efficient and the select the following bladed material with C and do whatever you wanted to do with it. All without ever stopping play back. Also consider trim start and trim end. Opt-bracket I believe. That decreased the need for blading for me a decent amount.
Director, Editor, Colorist
http://www.trsociety.com -
Also, consider the power of Keywords and Smart Collections more. This took me a long time to get used too, but when you do, I found that I can eliminate most of my multi column workflow, use keywords to describe an interview, b-roll, location, event, type of shot etc. and then either use a marker (which I think I better as it applies to only that moment, not the entire clip like a note column would) or note column. I do wish custom meta data fields were tabable in the browser and not a click to the inspector or multi key press.
Director, Editor, Colorist
http://www.trsociety.com -
He’s talking about Intel’s AVX. I too think there’s something to that. The skimming speed limit mentioned above happened to me on a regular basis on a MacPro which does not have it, and happens to me absolutely never on my MBPr.
Director, Editor, Colorist
http://www.trsociety.com