Page 1 of 2

Slower rendering in FCPX 10.0.6

Posted: Thu Oct 25, 2012 1:23 pm
by valleo
It seems to me, that Neat Video renders dramatically slower in FCPX 10.0.6. Maybe it's because FCPX uses the GPU for rendering in the timeline now...(?)
I have a 36 second range from the timeline with two clips powered by Neat Video (1920x1080p25, temporal radius 2) and the export as Quicktime-File takes horrible long 15 minutes!!! This is really really bad! I'm on a MacBook Pro Retina 15' with 2.6 GHz i7, GeForce GT 650M and 16 GB Ram.
In my opinion the export from 10.0.5 was way faster!

Do you know this bug?

Posted: Thu Oct 25, 2012 3:38 pm
by NVTeam
We haven't yet observed such an issue but we are currently investigating some possibly related problem introduced by FCPX 10.0.6, perhaps a bug in FCPX.

Please wait for an update from us. We will either update the plug-in itself with some workaround solution or will post a description of the FCPX bug in our list. As soon as we have it sorted out, there will be an update.

Thank you,
Vlad

P.S. If you are in the middle of a project, do not yet update FCPX to 10.0.6. Or generally: if you are in the middle of a project, do not update your tools unnecessarily.

Neat does not remove Noise in fcpx 10.0.6

Posted: Thu Oct 25, 2012 8:01 pm
by nav6785
Please help. The plug-in runs as normal in final cut pro x 10.0.6 however when a clip has been rendered after neat noise reduction has been applied to a clip there is still noise there in that clip as if the Neat plug-in has done nothing. in my line of work Neat is an imperative part of making wedding videos look smooth. I know you've previously stated there will be an update but i just wanted to inform you of this issue.
Also Terminal came up to inform me of the millions of clips that have not been filtered:
"Error: Incorrect Input Data. Frame is not filtered."

Posted: Thu Oct 25, 2012 8:07 pm
by NVTeam
Yes, we are aware of that issue, which is the main problem of this new version 10.0.6. There seems to be a new bug in 10.0.6. We are working to find a workaround (because it will again take quite some time to fix FCPX itself).

Vlad

General note: if you are in the middle of a project, do not update FCPX to 10.0.6 yet.

Posted: Sat Oct 27, 2012 1:40 am
by paulthompson
Seriously? A "new bug" in 10.0.6, and of course it's FCPX at fault because everyone else's plugins broke as well, right? I really like Neat Video, there's nothing else like it. But it's getting more difficult to justify using it in a production environment due to its tendency to break. I hope you have it fixed sooner rather than later. This is disappointing.

Posted: Sat Oct 27, 2012 8:57 am
by NVTeam
Seriously. We have already reported one new bug to Apple and are trying to find a workaround before they fix FCPX. There also indications that there may be more issues in 10.0.6.

Vlad

General note: if you are in the middle of a project, do not update FCPX to 10.0.6 yet.

Posted: Sat Oct 27, 2012 3:40 pm
by paulthompson
Hi Vlad, sorry about my tone. It was late and I was dealing with other FCPX bugs. Yeah this NLE is buggy as heck but it's worth it. I'm glad you guys are willing to deal with the headaches so that we FCP users can benefit from your great software. Many other plugin developers haven't even attempted a FCPX version. Thanks for your efforts and keep up the great work! Looking forward to the next release. :)

Posted: Sun Nov 04, 2012 12:40 pm
by simonpwood
Yes, these days I always wait until I get confirmation that both NeatVideo and Magic Bullet Look are working before I upgrade.

Hoping there is a fix soon; and thanks for all your hard work on these updates!

Posted: Sun Nov 04, 2012 1:03 pm
by NVTeam
I can see other plug-in developers also reporting problems with 10.0.6 to Apple. In the meantime, we have been working on workarounds for several new issues of 10.0.6. We now have an intermediate build that allows to avoid several of those issues. If you want to test it please contact support [at] neatvideo.com, we will send you a link.

Thank you,
Vlad

Intermediate build

Posted: Mon Nov 12, 2012 7:18 pm
by nav6785
I've tried the intermediate build. However there are still bugs that cause some frames within a project to turn green and upside down. Rendering seems to take longer too. Just though it let you know, hope this info helps.
Thank you

Posted: Mon Nov 12, 2012 8:04 pm
by NVTeam
Yes, there are still bugs in FCPX 10.0.6, at least 2, perhaps even 3-4. We have reported them to Apple and they are investigating why FCPX is not working properly. BTW, not only with Neat Video, with other third-party plug-ins too. Which is only logical, because the bugs are in FCPX itself.

Vlad

Posted: Mon Nov 12, 2012 10:25 pm
by SheepsheadStudios
I love the plugin, and have been using for a few months now. However, like everyone else - I've experienced some issues with the update to FCPX.

Sometimes it previews wrong in the timeline and renders correctly (aspect ratio stuff)... other times it goes very slow. Then sometimes it renders green space. Throughout all of this, the terminal window pops up with the error "Error: Incorrect Input Data. Frame is not filtered." This happens all the time.

However, I have been able to render things more or less correctly so far. Things are just slower and more confusing... and I'm assuming this is because Apple did something to plugins!

Just thought I would pass this along and I look forward to some of these issues being resolved, even though it's still working for me so far.

Posted: Mon Nov 12, 2012 10:46 pm
by NVTeam
The problem indeed originates in FCPX itself. In some cases, FCPX itself works in a wrong way and plug-ins (different plug-ins, not only Neat Video) simply help to expose that.

Have you contacted support to get the latest build, which includes some workarounds allowing to limit the damage (perhaps not entirely) caused by FCPX 10.0.6 bugs?

Vlad

FCPX latest version speed

Posted: Mon Nov 12, 2012 11:35 pm
by garters
I too have noticed a dramatic slowdown of rendering when the Neat video plugin is used. I do a weekly 30 minute TV show using footage originating off Sony EX3's in low light, and what used to take 4-5 hours to render now takes 13 - 15 hours. Is there any new information that is leading to a solution.
Neat video does such a good job on our 720p footage that I am loathe not to use it, but the new ultra slow rendering is an annoyance and holds up the MacPro from doing other things.

Posted: Mon Nov 12, 2012 11:46 pm
by NVTeam
The best solution (until Apple has fixed those bugs in FCPX 10.0.6) is to go back to 10.0.5. Believe me, that is the most efficient way for now. You will save your time.

But if you have time for testing and want to try workarounds that we have been able to implement so far to deal with those 10.0.6 bugs please contact support [at] neatvideo.com.

Thank you,
Vlad