FilmConvert/ColorFinale/iZotope RX5 Plugin Problems?

[Nick Rucka]

First, in answer to your question, yeah just output a master clip and bring it back in. It’s not an elegant solution – and in fact eats up drive space – but it’ll solve your issue in the short term.

Definitely let us know what your Color Finale test shows. As it turns out, an editor in my office knows those guys so we might be able to talk to them about it if the situation can be recreated.

Lastly, it’s not your 5k iMac. We have four work stations in our office – some supped up iMacs some mac pro (trash can) – and the issue occurs independent of it. It seems to be something that occurs in certain libraries that somehow get borked. What we don’t know is what exactly causes this, but I really do suspect it’s certain plugins and their interactions.

Have you optimized your footage? Transcoded it to ProRes before ingesting? Are you working with proxies? If so, has the problem continued independent of this?

Anyway, I hear you with your frustration with the plugin situation but I’ve found that all editing platforms have their weaknesses and quirks. FCP7 had it. Goodness knows that Premiere still has it. And should we talk about Avid? FCPX is doing some serious processing and some fancy footwork, so I try to cut it some slack. Hopefully the situation can be figured out soon, though! :/

[Jim Adams]

[Nick Rucka] “The issue of the renders disappearing or randomly getting lost is also a real hassle.”
[Nick Rucka] “Now I’m especially intrigued by the Color Finale plug in issue that you mention.”

I am currently running tests with library and media on my internal SSD. Nothing is connected externally – not even my audio monitors (I’m getting superstitious). My event contains only 6 fairly short 4K clips that have been “multiplied out” over about 26 minutes of timeline. I’ve added some of those as connected clips. The only plugin installed (on a clean install of the OS and FCPX) is Film Convert.

So far there have been no crashes or freezes. And no strange graphic corruption of the UI that I experienced with the FilmConvert test (orange splotches over the adjustment areas in the Info Browser when mousing over the numerical values). But the oddball re-rendering keeps occurring. I render all. Close FCP. Open FCP. A couple clips will need re-rendering (which, BTW, seems really slow; but maybe that’s my unfamiliarity in working with 4K media). After those clips re-render, if I close and reopen, it doesn’t need re-rendering. But if I trim one clip, render all, close and reopen, new render bars appear in a couple places.

I haven’t talked with Apple about this yet. More testing to do. I sure hate the idea of losing FilmConvert!