-
Large projects
-
Haven’t spotted this at all in all my FCPX projects, but I haven’t been using compound clips or markers very much. It’s a very worrying development.
“My Name is Steve and I’m an FCPX user”
-
Thanks for all the free effects. Brilliant, as they say on The Fast Show.
As Andrew Richards explains there may be issues relating to the autosave and concurrent queries to the database. Some optimizing and faster hardware might solve that.
But that doesn’t explain the weird project bloating, and the resultant sluggishness, that occurs with markers, compound clips and when blading a clip.
As I understand it the undo queue is flushed when you quit. Perhaps the information is retained but not accessible and this contributes to the bloat? I know references to markers persist even when they’re deleted. I deleted over 10,000 of them and my project shrank from over 1GB to around 100MB.
Essentially all media in FCPX can be treated as a sequence.
What are the ramifications of this? -
[Andrew Richards] “Contemporary consumer SSDs at their worst will deliver about 100 times the IOPS performance of a typical SATA HDD. That kind of gap absolutely matters in this analysis.”
and
[Andrew Richards] “I just don’t agree that there is nothing we can do about it, such as it is, out here in deployment-land.”
Let’s see–my current project on FCP7=8TB @ $1,000 (2 4TB Glyphs/GRAIDS at current flood prices) vs. $15,000 (16 480GB OWC Mercury Electras). I’m thinking maybe us here in deployment land don’t like to hunt with that dawg.
-
[Andrew Richards] “Role-based mixing would be handy too, though it is probably be easier said than done.”
Yeah. If I could patch Roles to a mixer–and color code them by type–I’d be happy, I do believe.
-
Aside from large projects, it’s stunning at just how slow the UI is in general. Forget skimming and look at some of the basics.
I’m working on a small project. 80 ProResLT clips marked as favorites and rejects. Event is set to list view and show only favorites. The action to twirl down the disclosure triangle takes about 1 sec. It’s a simple 2 min. timeline of about 35 clips. Rearranging the order of the clips in the magnetic timeline takes about 1 sec. or more for the timeline display to redraw while making the insert. Drag a clip over another to replace and it takes 1-2 sec. for the replace dialogue to appear.
This is using an 8-core MP, 12GB RAM, ATI 5870 card. Mac OS 10.7.2. The media is on a 2-drive RAID-0 internal pair of 7200RPM drives. FCP X responsiveness compared with FCP 7 (or just about any other NLE) is just sluggish.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I don’t believe FCPX works as well under Lion as it does on Snow Leopard, certainly on my system there is less lag on actions and it doesn’t get bogged down on memory leakage as much
“My Name is Steve and I’m an FCPX user”
-
That’s even worse news – I haven’t made the move to Lion yet, I’m still on SL and it’s got major issues!
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com -
[Simon Ubsdell] “That’s even worse news”
Ironically FCP 7 feels like it’s working better under Lion. At least it appears to render faster.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Chris Harlan] “Let’s see–my current project on FCP7=8TB @ $1,000 (2 4TB Glyphs/GRAIDS at current flood prices) vs. $15,000 (16 480GB OWC Mercury Electras). I’m thinking maybe us here in deployment land don’t like to hunt with that dawg.”
An 8TB project file! Wow, that’s gotta be a record… Oh, your media is 8TB. 🙂
Media should stay on spinning disk, of course. Fortunately, we can put projects on one drive and media on another.
The gotcha for FCPX is that it puts render files for the projects alongside the project files. Not ideal, I know. But if you are working on a one hour show, even rendering every frame is going to occupy less than 100GB (ProRes HQ 1080i29.97). One of those 480GB SSDs should handle that easily.
I’m not saying it isn’t a problem, these large and complex project files and the way FCPX interacts with them. I’m just saying there might be ways to tune your hardware and workflow to mitigate some of the issues.
Best,
Andy -
[Rob Mackintosh] “There are no markers in the project. The audio exported from the project hasn’t changed. The project file is over a thousand times its original size.”
That sounds like a bug to me. Have you filed a feedback?
Best,
Andy
Reply to this Discussion! Login or Sign Up