-
FCPX developers, please optimize disk access
-
Whatever the way a NLE may works, USB is not up to the task of moving three Prores streams in real time.
[Ladislav Zamba] “”However, for larger projects, compound clips that aren’t nested inside each other can actually make the system run better. If you are loading lots of clips into the Timeline, Final Cut needs to track each of these clips individually. Instead, if there is a section of the Timeline that you are done editing, select all the clips in that section and convert it to a compound clip using File > New Compound Clip.”
This has been discussed in this forum months ago, but makes no sense to blame the NLE or the complexity of the project when you system do not reach the minimum performance.
Get rid of the USB HD.
rafael -
[Ladislav Zamba] “So, I believe that FCPX developers can avoid some unnecessary disk activity and make editing on slow drives and machines faster.”
Sure, they could. But why?
Isn’t the whole concept of X to be a “new paradigm in editing”? Isn’t it about moving into the future? Once you sign on to a deal like X, it is not a smorgasbord. You have to take it all, including frequent hardware upgrades to the latest and greatest in order to keep up.
When you (FCP X users) start saying developers need to write code in order to accommodate your (FCP X users) hardware deficiencies, or even that the app isn’t getting everything out of the hardware that it can, well this sounds like the previous FCS/FCP7 users complaints.
need to upgrade and move into the future.
Oh, BTW apple will be happy to supply you with a faster machine and drives.Scott Sheriff
Director
https://www.sstdigitalmedia.com“If you think it’s expensive to hire a professional to do the job, wait until you hire an amateur.” —Red Adair
Where were you on 6/21?
-
Yeah, but – every other NLE has no issue whatsoever to play a single stream of, say, 720/25p ProRes from a measly USB2 drive. And simple cuts editing is fast.
FCPX has BIG issues working with larger projects, even from eSATA G-Tech RAID 0 with speeds over 130 MBps on a 8-core Mac Pro. Opening a keyword (bin) almost always slowly re-reads thumbnails, with RAID thrashing. When I switch to another bin and back, it SLOWLY rereads thumbs again. And most of my 22 GB RAM sits there unused. FCPX should be WAY more aggressive with RAM.
Reply to this Discussion! Login or Sign Up