-
The Ghost of Optical Flow Analysis
I have checked over this inherited file clip by clip.
All Retimed clips are set to Normal and no Optical Flow used.
But I still get this stupid Optical Flow Analysis under Transcoding and Analysis in Background Tasks.
It hangs up the project and I even tried the following:Select all Retimed clips and Disabled
Copy Project to a New Library
Export XML and imported to new LibraryAll of the above is not letting me shed this background task.
Is there any other way of removing this?
Btw letting it try and finish is futile.
The app hangs after a few minutes.
If I pause the process I can move around for a few minutes then it hangs.
Constantly have to restart FCPX. -
14 Replies
-
Ask the original creator of the project whether they used proxies, and if the optical flow was used on the proxy? I know you might not need to use proxy workflow but it might be a weird bug with that workflow
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
[Tom Sefton] “Ask the original creator of the project whether they used proxies, and if the optical flow was used on the proxy?”
I thought about that.
I deleted generated files and started from scratch.
The issues are still there but currently, I am able to move around in the timeline without crashing.
That’s a step forward after spending some time on this last night.
As I write I am playing back the whole doc without issues.
But the Optical Flow Analysis tasks are still persistent. -
I also forgot to add that I set the Retimed quality to Frame for all suspect clips to see if the analysis stops.
It didn’t but as I explained prev the crashing seemed to have stopped. -
The issues still persisted after all my posts.
Now I just deleted all the clips.
I had to do screenshots of each suspect file so I can rebuild later.
Maybe use a diff app for slo-mo.
Guess whats still showing 😛
Yep, the Optical Flow Analysis is still there.
Its showing five items on the list.
Now I def have to check all CCs and see if there are any hiding. -
Forgot to add that the crashing is almost every step I make.
Fun times here 😛 -
Exactly how stable my project is when I switch from proxy to original files. Starts analysing optical flow, 0% stays forever and if you quit the analysis it crashes the app. Final resort for this project was an xml to resolve after manually collapsing all multicam segments and switching off all custom transitions and titles. Then export clip by clip from resolve and rebuild the project in fcpx to add the titles. Terrible.
Anything with optical flow or speed adjustments with high resolution I can’t go to fcpx anymore until the bug is fixed
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Thanks, Tom that’s exactly my next attempt.
I was going to do that days ago but I figured to give this a chance.
I told the original editor to step off when it comes to stuff like this.
Sadly he wasn’t clear as to how it would react in the end.
Not really his fault, I removed the clips and them issue persists.
Not sure if that’s what’s causing the constant crashing but Ill assume it is 😛 -
Update:
The client took the project back to check on their end.
They claim no issues at all.
I have to visit to see for myself.
Found this same issue at FCP.CO and wonder if its a High Sierra problem?
My specs are:
MacPro 2013
D700
64GB
High Sierra
FCPX 10.4.3 (tested on 10.4.2) -
Maybe it’s a Mac Pro 2013 thing? We’ve got virtually the same spec machine with libraries on an external raid right?
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
A new twist to this project.
When the client said things worked on their end.
They failed to tell me that they didn’t hook up the other drives.
Part of my job was to move the Libary into a faster Thunderbolt 2 drive.
However, they have more files to deal with sitting in other USB3 drives.
Once they connected those drives, the issue reared its ugly head :p
So now I have them copy the files they need to that drive via finder, then run FCPX without the suspect drives online.
Crossing fingers that it’s not the files.
According to the client, the minute they started the Library, it started crashing similar to my results at my studio.
Again hoping its not the files.
Reply to this Discussion! Login or Sign Up