You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
📢 Newsroom Update
Final Cut Pro 11 begins a new chapter for video editing on Mac. Learn more >
Final Cut Pro 11 begins a new chapter for video editing on Mac. Learn more >
Can anyone give me a read as to the implications of Mountain Lion and Final Cut X on a Mac Pro? Middle of edit and also about to begin anew, need to know this useful information from a pro. Who was it? Tom Wolsky that I was so impressed with guding us thrhough the first 6 months of Final Cut X ****? Tom, are you there? Any other sigificant hitters within reach? Thanks! William Shanley
Final Cut Pro X, OS X Mountain Lion, Mac 8 core early 2008
Has there been any update from apple on this? Having Optical Flow broken is a very frusterating problem, and I am at the point of rebuilding a project in 10.0.3 where Optical Flow seems to work properly. I would obviously prefer to be using the latest version of FCPX, but with something as major as Optical Flow broken, it's a deal breaker for me.
Anyone found a workaround or heard of Apple recognizing this issue so they can work on a fix?
This issue resolved itself long ago. It was only broken between point releases. I take it as a blessing in disguise, since I purchased Twixtor as a workaround and found that it delivers vastly superior results. I now use optical flow as a quick-and-dirty solution, or for the random cases where Twixtor doesn't produce the result I'm looking for.
Hmmm - that's a bit disconcerting then. I'm finding this is happening on my new MBP Retina with FCPX 10.0.8 and the latest update of ML quite consistently. I have done many reinstalls on 10.0.3, and tested the Optical Flow with success, and then when I install 10.0.8, it stops working. To be sure I wasn't missing something, I allowed a clip to analyze part way in 10.0.3, quit the app, installed 10.0.8, and let it finish analyzing, and sure enough the 1st half of the clip in analyzed fine, and the second half is merely frame blending.
Everything I have is fairly new as of the last month or so (MPB, FCPX, and ML). Anyone have any insight into this?
Oh, darn. It was a huge issue for me with 10.0.4, but went away with 10.0.5. I haven't seen it since. I'm wondering what else may have changed. I assume you're also installing the Pro Application support package. I know it's supposed to just be codecs, but who knows what it means for the way Final Cut handles them. I suggest you submit a bug report to Apple. When they removed the offset slider for letterbox in 10.0.6, I submitted a feedback report and a member of the FCPX team emailed me immediately with a temporary fix.
Final Cut X and Mountain Lion
