-
Is FCPX the Othello of NLEs?
-
[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. -
[Aindreas Gallagher] “Different is.. One word for it…”
Yes. I keep bringing that term up (different) because in my view, FCPX is exactly that.
I don’t know if it’s any better. It certainly is in some aspects for my use, but others aren’t there yet, not sure if it will ever be “there”.
So, different is the only correct term I can use at the moment.
-
[Rob Mackintosh] “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)?”
Meaning, you kept an Event of just the Project compound clips?
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.
That’s an interesting idea, though. I know you have mentioned this idea of splitting everything up before and it does seem like something that could be done. I would rather see the application get a bit more optimized.
As you and Mark Morache have pointed out, there’s no reason for all the duplication of metadata. It seems to me that FCPXML is just not “optimized” at the current time.
Also, this would screw up XMLs, wouldn’t it by defining the compounds as a clip/nest rather than a sequence? A lot of these early FCPXML supported do not support compound clips. More testing is needed on that side. If I do use a compound as a sequence, I eventually copy it in to a Project, but maybe that’s futile.
-
Ah no – absolutely, spot on.
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
[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.
-
What I completely resent in all of this is that none of us has a clue as to what will of will not bloat the Events and Projects folders. Apple is completely unwilling (or so it seems) to generate any sort of best practices tutorials or documentation. They seem to want to rely on the 3rd party training resources. Those are all great at the very basic level, but inadequate for anyone who needs to do something complex with the software. This application is the most unintuitive product they’ve created in a long while if you want to do more than just slap some cuts together.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I’m in the middle of what I thought might be a “FCP X baptism by fire” period and I’ll share share a bit of my/our sense to date. I’ve got seven 30 second TV spots and a short promo film in the project browser so far and X loads them pretty quickly, but I’m already concerned about managing events and projects as preloads…definitely moving to Event Mgr X as soon as I get this stuff out.
Still no crashes after several heavy weeks, but the “no undo” bug has got to be fixed immediately. It’s bitten me twice. Running out of RAM (16 gigs) obviously undoes the unlimited undo concept, and with no warning of such and no RAM purge, Apple seems to be missing a big WTF issue.
I’ve been working on some long term heavy editing and design spots and a couple of “gotta be on the air in 48 hours” stuff. X has been great in building different versions and testing looks really quickly, great for TV graphics, very fast assembly for a lot of stuff.
Have had a few, “I really don’t want these clips connected to anything” moments that I’ve had to work around (easily enough).
I guess to this point (maybe a month and a half) I like it more than I don’t.
Maybe the most salient point I could make given the short sample time – for something I’ve been learning on the fly, the work has been done faster than the same if I were working in 7, and with more time to experiment and develop ideas.
So in that regard, for me, that would suggest good things in the future.
-
[Jim Giberti] “Running out of RAM (16 gigs) obviously undoes the unlimited undo concept”
The “undo stack” is limited to 500 items. It is not unlimited. That number comes straight from Apple. But yes, the bug is inexcusable.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “What I completely resent in all of this is that none of us has a clue as to what will of will not bloat the Events and Projects folders. Apple is completely unwilling (or so it seems) to generate any sort of best practices tutorials or documentation. They seem to want to rely on the 3rd party training resources. Those are all great at the very basic level, but inadequate for anyone who needs to do something complex with the software. This application is the most unintuitive product they’ve created in a long while if you want to do more than just slap some cuts together.”
Well said.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Oliver Peters] “What I completely resent in all of this is that none of us has a clue as to what will of will not bloat the Events and Projects folders. Apple is completely unwilling (or so it seems) to generate any sort of best practices tutorials or documentation. They seem to want to rely on the 3rd party training resources. Those are all great at the very basic level, but inadequate for anyone who needs to do something complex with the software. This application is the most unintuitive product they’ve created in a long while if you want to do more than just slap some cuts together.”
Very well said.
I’m sick of all the half-assed testing I’ve had to do to make this software usable.
Reply to this Discussion! Login or Sign Up