Didn't try the new NR effect in earnest, when 10.4.4 came out. Now I've just finished editing a private travel video, just five minutes, three shots needed some NR. Was pleased to find that playback (with the effect applied) remained smooth, and the effect was only rendered on the frame the playhead was paused on. Also liked the quality, didn't bother to compare it to Neat (which I also have). Good enough, at least for my purpose, I only have a few noisy shadows after lifting the mids in slightly underexposed clips, not too distracting at all without NR.
BUT: after exporting the project, the said clips stuttered!
I vaguely remembered an old rule about Neat. Someone somewhere had stated that it should always be the first effect - which never made a lot of sense to me and an advice I never followed myself. Never ran into trouble. However, just to make sure I dragged the effect on top of the CC instances and exported the ranges - same stuttering.
Maxed out iMac 2015, Mac OS 10.14.1, FCP 10.4.4, 2160 XAVC @ 23,98, Original Media, exported to ProRes422 as Master. Anybody noticed this?
I read somewhere, user manual or something, that Apple states Noise Reduction needs to be the first effect applied to a clip.
And watch the sharpening in that new effect, it's not good. Noise reduction is good, but I find the sharpening function really badly implemented. The Sharpen effect does a much better job. This new one stair steps really badly.
I have just had a need to apply some NR to a shoot I did recently. The 10.4.4 effect did an OK job, and there is no stuttering.
But... my old late 2013 MBP had to work long and hard to render the effect. Appears to do it one frame at a time, and each frame taking maybe a couple of seconds.
Up until now, I have been able to 'cope' doing a multicam edit (with a mix of 4k and 1080p), despite dropping frames occasionally, the performance has been 'bearable' using this now old machine (bravo, that it has performed well for so long). But not with this effect.
Me thinks very very strongly that it's time to upgrade. Question is, to whose who have a recent MBP, what is the rendering performance like applying this NR effect.
Late 2013 Macbook pro retina here. NR takes a lot of time , much more than Neat Video. The other problem I'm facing is that it crashes fcpx while rendering. I also don't like the sharpening effect. I'm now using Lucas effect sharpening plugin and it's really nice, specially for me coming from photography.
As with any noise reduction filter, the results you get depend on many different factors. Generally, I find the NR filter in FCP X quite good. The main advantage over things like Neat is that it runs in realtime and it does not bog your system down, even on lower-specced hardware.
I did a test with a 20" iPhone 7 clip slowed down to 50% with Optical Flow, to which I applied the NR filter with medium reduction and medium sharpening. The sharpening actually wasn't necessary because I find that the FCP X NR filter does not blur the footage as much as many other noise reduction filters. But I applied the sharpening anyway, just for the test.
On a regular MBP 2014, the unrendered 20" clip exported in 45 seconds which I find quite fast for noise reduction. And it plays perfectly smooth in QT player. So I think there may be other factors involved than just the NR filer if you experience very long render times, if your computer crashes while rendering, or if the processed clip does not play smoothly.
Hey Ronny, I've also found fcpx NR very nice and with an organic feel, something that is difficult to accomplish with Neat video. An of course that checking the effect in real time is a big plus also.
But in my case is crashing the rendering and the exported video plays choppy exactly on that clips with NR applied.
I've used Neat video instead, with no problem while rendering or playing smoothly the exported file.
But as you mentioned, many factors could be affecting the performance. I'm using Magic Bullet Mojo II, Luca Visual FX Image Sharpener and color finale on almost all of my clips. Magic Bullet is very slow to render but it never crashes fcpx.
Maybe is something related with NR and the graphic driver (Nvidida GeForce 750M) on Mac Os Mojave. Nvidia panel alerts me that is out of date on every restart, but there is no newer driver available or web drive alternative.
I agree that the graphics card is the culprit here, especially if you have an external monitor connected to your MBP. The NR filter uses Metal2, and the 750 M works very badly with Metal. There have been quite some reports about this, and it looks like there won't be a solution from Nvidia any day soon. There are workarounds, but they seem quite convoluted to me. Here's some extra information:
Mmmmhh, Maybe I should buy a good external graphic card. I cannot afford a new macbook right now and some coleagues told me that they overheat very easily after 15' of intensive tasks and the performance is affected. Can I avoid the nvidia 750M and just use an externall one or the system uses both?
I just would like to get back to this problem. I discovered the same behavior using the FCPX noise reduction.
Clips with noise reduction applied to won‘t play back without stuttering even though FCPX has analysed the noise and rendered the clips. Somehow FCPX is not using the render files for playback. When I place the playhead on a rendered track with noise reduction it is also analysing the noise again and I‘m wondering why.
Any hints here on this?
hi all, while desperately searching for a way to denoise my Mavic 2 footage i came across this thread...Oh my, looks like Noise reduction is expensive. If it takes Neat, or Redgiant for 199,-. Because, the on board NR in FCPX 10.4.8 does not work here. Maybe its also because of my graphics card INtel Iris Pro? (15" MBP late 2015). UNfortunately the Pixelfilmstudios effect does not work with Intel GC.... I'm new in video and never thought this would be such a huge problem. Even for footage shot in daylight, dark areas (woods in the shadow) are flickering like crazy with noise...