-
Anyone having issues with responsiveness?
I’ve been trying to use X for some of my daily broadcast work, and I noticed that when simply trying to play my sequence full screen I would get stutters and stops.
I’d pause and go back to the top to try again. Sometimes it would take 3 or 4 times before I finally got it playing smoothly.
Yes… I checked my background processes, and nothing was rendering or being analyzed. Other programs were kept to a minimum. There might have been a browser window open.
I often get unexpected unresponsiveness with the skimmer. It may take me a couple of times of forcibly clicking in the timeline before the interface catches up and parks where I want it to.
Other times it runs great. Nice and snappy.
I’m running 10.6.8 on a dual 2.66ghz core i7 17″ MBP with 8gb of ram, running the project from a FW800 lacie rugged drive.
———
Mark Morache
Evening Magazine
Seattle, WA
blogging at https://fcpx.wordpress.com -
7 Replies
-
I’ve experienced the lag you described with the skimmer/playhead not moving to where I clicked right away. IME It seems to be that the playhead really did move, but it just doesn’t show up in the new position. If I click the space bar after this happens, it play’s from the position that the playhead was “supposed” to be.
Anther one I’ve had, which hasn’t been reliably reproducible is if I click on any menu, say “file”, then roll the cursor over the other menu’s like “view” “window” etc.. It may result in a long Beach Ball spin, likely followed by a crash. Seems to only be during render. At least my project re-opens right where I left it…
10.6.8, Mac Pro 2.8GHz 8-core Xeon 8GB RAM
-
I’ve been trying to use X on an older 17″ MBP which meets specs but even proxy footage doesn’t play back smoothly and the interface is laggy. On my early 2008 Mac Pro it’s better but still have issues similar to what you’re describing. That first update can’t come soon enough because otherwise X is looking pretty good. The response issue reminds me of FCP 1.25 however…
-
I’ve had some success by simply turning off background rendering in preferences, even though I don’t need to render. I had some dramatic results with that on my 2006 MacBook Pro (yes I know it is old).
——
T. Payton
OneCreative, Albuquerque -
Mark and David, your machines certainly are within the limits of what is recommended for FCP X but it may be that the media needs to be converted. What codec are you running? For example, did you convert your media to Apple ProRes 422? or 422 HQ?
Rick Lang
iMac 27” 2.8GHz i7 16GB
-
Nick, even before the first update of FCP X, the update of the OS to Lion to be released perhaps within a few days may also bring improvements to performance for FCP X. I recall that this was a possibility but not sure of the details. It’s mentioned in the comments to Philip Hodgetts’ article: What are the Answers to the Unanswered Questions about Final Cut Pro X? Would be good news if that’s all it takes!
Interestingly as an aside, while typing this note, the characters on the screen were taking forever to appear. I quit about a dozen other programs and about eight Tabs in my Safari window and everything is normal again. Sometimes there are strange behaviours that are hard to explain! I’ve been applying various application updates supposedly to prepare for Lion, so maybe that’s part of the explanation.
Rick Lang
iMac 27” 2.8GHz i7 16GB
-
I have the same problems, even when the footage is transcoded it still says H.264 in the Inspector window.
-
I was having this very same issue on my quadcore unit, but lo and behold it only THIS ON MOVE SOLVED IT ALL.
Final Cut Pro X >Prefferences>Playback>Untick the effin “Background Render”
Kaboom! My FCPX just exploded with fast…i can apply multiple layers of color grades, effects, titles, transitions, clip connections, on a non transcoded avchd file ( native baby! ) and I can export all my edits in seconds..what it takes 30mins for premiere to do. Damn!
Reply to this Discussion! Login or Sign Up