-
Large projects
-
[Rob Mackintosh] “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.”
Yeah, it looks like you’ve identified a repeatable bad behavior. Smells like a bug, and you’ve got specific tests you can point to that demonstrate it. You should file a bug report.
Databases like SSDs, but bugs need to be squashed.
Best,
Andy -
[Oliver Peters] “it’s stunning at just how slow the UI is in general. “
Some of the UI sluggishness seems to come directly from the animation effects, heavily used throughout the UI. Animation by its very nature takes time, so even if the system is responding instantly, time must be used to display the animation.
Just one example – when pressing arrow keys to go to next/previous edit, the cursor sliiiides to the next edit point. It takes a second.
Contrast this with Avid MC — next/previous edit, even stepping in and out happens instantly. The UI feels responsive because as much as possible, it displays the results of the user’s action as quickly as possible. This is UI 101.
I have to sincerely ask — what is the professional justification for fancy FCPX animation? Outside a Core Animation demo, what practical purpose does it serve? It is completely inappropriate in a professional application, and at the very least, there should be a preference to turn it off.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
Oliver Peters on Nov 25, 2011 at 9:57:08 pm
Ironically FCP 7 feels like it’s working better under Lion. At least it appears to render faster.
Thanks for the heads-up – sounds like it’s maybe time to make the move.
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com -
[David Lawrence] “Some of the UI sluggishness seems to come directly from the animation effects, heavily used throughout the UI. Animation by its very nature takes time, so even if the system is responding instantly, time must be used to display the animation.”
I completely agree. There should be a preference to turn off all animations. This is possible in Lion in general or via tweaking utilities. The default should be OFF.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Yes, a couple of weeks ago.
-
[Andrew Richards] “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.
“Andrew, I’m delighted to hear that the source material can remain on regular RAIDS. BUT, we are talking big projects, right? I’m doing advertising packages for multiple seasons of broadcast TV over the next four months, most of it in 1080i@29. I’m guessing I will have a little over 50 hours of programing as source material. I will need access to all material throughout the project, and each promo has multiple versions. So, to follow your plan, I’m guessing that I need more than just one of those 480GB SSDs. So, maybe not $15000, but maybe 4000 or 6000 plus the cost of a Glyph? It still seems to me an issue.
-
[David Lawrence] “Just one example – when pressing arrow keys to go to next/previous edit, the cursor sliiiides to the next edit point. It takes a second.”
[David Lawrence] “Contrast this with Avid MC — next/previous edit, even stepping in and out happens instantly.”
After examining this carefully, the viewer actually changes to the next edit and then the animation completes. So it is ironic that those animations might now actually slow down editing, it sure makes it feel and look like it is moving slowly.
I actually feel that some of the animations are appropriate. Specifically on ripple and roll edits. They give you excellent visual feedback on what your edit is actually doing.
I stil would vote for a preference to minimize animations.
——
T. Payton
OneCreative, Albuquerque -
I believe the two products references are just tracks of code bases as a practical method of software development. They have one with code base “B” containing the development of multitrack and broadcast monitor out, while they have another code base “A” with the current version and any incremental fixes needed, like the 10.0.2 update we just received. “A” is just getting a few patches as needed, while the real work is being done in “B’
We can only hope someone in the FCP group is reading our posts and wishes they could tell us that “B” fixes alot of these DB issues.
Therefore:
“Dear FCP Group Member, please throw us a bone. Or leak through a rumor site or two of the existence of a bone fix to the project file problem. It would give us some hope!”
——
T. Payton
OneCreative, Albuquerque -
Correction from my last post:
“it is ironic that those animations might NOT actually slow down editing, but it sure makes it feel and look like it is moving slowly.”
——
T. Payton
OneCreative, Albuquerque -
some notes regarding FCPXML vs FCP 7 XML.
FCPXML at the moment is a very basic thing. most of the parameters (and metadata) are not transported into the XML. so it is obvious that the xml is very small compared to the project. so it does not make to much sense to compare project and XML.
another thing is that if you look at the XML it is still connected to the original event (by the uuid) this allows the eco system to refer to the project where the XML came from even though it creates a copy of the project.
This can be good or bad. with legacy XML versions people like me where able to change references and parameters. this is not possible at the moment with this version of FCPXML. as many of the parameters are not listed in the new XML type, much of those stuff you might have changed is gone – means you never got a real copy of the clips parameters, effects etc. but everything which is related to the project itself is kept by reference to the original project.
the marker stuff is interesting, i have not tried that, but definively will have a look.andreas – and i hate typing on the ipad
Spherico
https://www.spherico.com/filmtools
Reply to this Discussion! Login or Sign Up