-
10.0.6 performance issues
-
In Geoff’s post on Rendering Speed, the large improvements in rendering were on this modest configuration:
“All tests were made using the same machine: Mid-2010 iMac i7 @ 2.93GHz, 8GB 1333 MHz DDR3, ATI Radeon HD 5750 1024MB, running OSX 10.8.2”
It may be a combination of factors but I suspect the end result is the render tuning is related to the CPU architecture and GPU architecture and later architectures will fare better. That mid-2011 iMac with a Radeon 5750 may have been a poor performer that the FCPX changes have addressed but others on different configurations (older or newer) may not see a dramatic change. Still when you see worse performance on playback, it might imply the software is doing things differently, requiring an upgrade to components, but what? If your performance becomes worse while you have more recent gear than the configuration in this message, then “Houston, we have a problem.” Sorry I can’t be more helpful.
Rick Lang
iMac 27” 2.8GHz i7 16GB
-
I just found out something that impacts the lag issue. My sequence had a series of a/v clips with all sync audio disabled. The audio in the mix was coming from VO and music edited into two connected secondary storylines. When I detached and removed the unused sync audio from the a/v clips, the play start response got a lot better.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I’ve done a bit more testing on this issue of stop/play lag. It seems to be an issue with existing projects. The cause appears to be related to the fact that the audio configuration has changed to accommodate the new multichannel editing features. On the test sequence I was playing with, I had originally disabled the audio for the sync clips. When I checked that today, they had the new configuration but the clips were all enabled. Yet they were silent. So clearly an update anomaly. When I selected all the clips and toggled the audio tracks off again, stop/play performance improved. My guess is that it’s probably fine on an entirely new project.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Oliver
“My guess is that it’s probably fine on an entirely new project.”Makes sense. When Apple tweaks anything in the Aperture database with every minor revision then they completely rebuild affected components in the database. This isn’t what happens when FCPX is given a minor update–existing things (like compound clips) function in the same way which may be best considering the repurcussions of converting a video project, but new things adopt the new changes.
Rick Lang
iMac 27” 2.8GHz i7 16GB
-
[Oliver Peters] “My guess is that it’s probably fine on an entirely new project.”
I had a bunch of issues with audio configurations and compound clips on old projects/events. No show stoppers, just weirdness. Haven’t seen any of them on new projects. YMMV… 😉
————————————————————-
~”It is a poor craftsman who blames his tools.”~
-
Oliver I’m getting a very similar issue in a new project, retina MacBook Pro, and a FireWire 800 drive using either proxy or optimized media. Footage in the browser plays back fine and skimming is smooth for the most part. However if I go to play the sequence I get a 1-2 second delay if editing off the internal ssd and up to a 15 second delay if the media is on the external drive. I think it might have to do with some sort of preloading, as the delay gets longer the earlier in the sequence you start (although its only a minute long sequence). I’ve tried trashing preferences, using a different drive, and transcoding the media but nothing seems to help much. The lag makes the program extremely irritating to use.
-
[Kyle Prince] ” I think it might have to do with some sort of preloading, as the delay gets longer the earlier in the sequence you start (although its only a minute long sequence). “
Wow, I’ve never had anything quite so bad. How complex are the sequences? Filters? Effects?
NLEs all have something called “building the pipeline” . That’s essentially having to look forward and backwards through the timeline so that at any given point when you play forward or reverse, it knows what media to have ready. In the older Avid days, there was a console command called “toggle playlength”, which let you change the lookahead interval to 1 minute. So the timeline would play for a minute and stop. This greatly improved speed when making tweaks in the full timeline for a full feature film. That issue is largely gone thanks to better performing machines and optimized software. Nevertheless, it seems like this sort of buffering is a result of the same type of issue.
With X, it doesn’t seem consistent to any one thing. Try a brand new project and see if you still have the issue. I’ve found most of my projects that were created before the upgrade, all have various little quirks when I try to do anything with them now after the upgrade. Probably due to the change in audio configurations. This has definitely messed up some of my timelines in little ways. Nothing that I couldn’t recover from, but still not a good situation. Then add corrupt renders into the mix. Oh joy!
OTOH, I’m really enjoying being back on Media Composer these past few days 😉
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up