Activity › Forums › Apple Final Cut Pro › Render Optical Flow
-
Render Optical Flow
Posted by Thanos Papadopoulos on October 16, 2017 at 6:47 pmIs it only me having problems when I need to render clips with speed segments and optical flow (video quality)?
This thing happens often with different clips and on different macs. These clips cannot be rendered! I have to export it and reimport it to see these clips. Is it a bag?Fix it in Pre.
Eric Santiago replied 7 years, 7 months ago 10 Members · 18 Replies -
18 Replies
-
Noah Kadner
October 16, 2017 at 8:09 pmAnything’s possible with the right combination of source media and system specs but as a general workflow- working fine here.
Noah
FCPWORKS – FCPX Workflow
FCP Exchange – FCPX Workshops
XinTwo – FCPX Training -
Jeff Kirkland
October 16, 2017 at 8:59 pmIt’s just you. Optical flow is working as expected on the three macs in my office.
—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland -
Thanos Papadopoulos
October 16, 2017 at 9:18 pmOptical flow with 2 or 3 speed segments renders normally?
Fix it in Pre.
-
Noah Kadner
October 16, 2017 at 9:22 pmNo issues here. However if you can make it happen consistently-
https://www.fcpworks.com/submitting-better-fcpx-feedback-to-apple/
Noah
FCPWORKS – FCPX Workflow
FCP Exchange – FCPX Workshops
XinTwo – FCPX Training -
Joe Marler
October 17, 2017 at 12:28 am[Thanos Papadopoulos] “This thing happens often with different clips and on different macs. These clips cannot be rendered! I have to export it and reimport it to see these clips”
I have seen this behavior periodically, and I’ve seen others report it. I think it’s a bug. However you don’t need to export and re-import it. The optical flow is usually being calculated correctly upon export, but it doesn’t always render visually properly in the timeline.
I’ve seen reports that deleting generated library files might make the problem temporarily go away. Also if you are using optical flow on a speed ramped clip that can cause it. In that case try blading the clip and only apply optical flow on the bladed section.
-
Jeremy Garchow
October 17, 2017 at 6:41 pmI also think Optical flow cause weirdness if the clip and timelknenframe rate mismatch (30p clip in 24p timeline, or similar).
Not sure if it applies to you, but other than that, I find optical flow to work really well most of the time, depending on what I’m trying to slow down.
-
Thanos Papadopoulos
October 17, 2017 at 8:22 pmI use optical flow really often and helps me a lot too. I don’t think that is a frame rate issue but I’ll check this out next time and I’ll update this thread.
I am a freelancer editor so I use different editing suits and I’ll confirm if it’s a hardware or software problem.Fix it in Pre.
-
Doug Metz
October 17, 2017 at 10:31 pmI also use it regularly, and can corroborate Joe’s findings. Had this problem last week on a 30p animation (matching timeline frame rate). Timeline showed unrendered optical flow sections but was able to output successfully.
Doug Metz
Anode
-
Nikos Papadopoulos
October 30, 2017 at 12:51 pmUsually this happens if the system has NVIDIA instead of AMD. If you’re on a Mac Pro (pre 2013) and have installed a custom NVIDIA card, know that this is usually the cause. If you’re on a laptop with NVIDIA, again its a bug. After working on the latest MBPro 2017, all these issues disappeared for me.
Passion and knowledge put to work
nick314.com
Reply to this Discussion! Login or Sign Up