Neat Video & Neat Image community

No, not everytime. At the moment I've got no footage to look at. It happended on a 50fps GoPro shot, retimed to 50% (for 25fps timeline usage). No issues on 25fps footage so far.

Maybe this is another bug of FCPX:
When I add the NV filter to a clip in the timeline, then the clip seems to show offset in time. Workaround for this is to apply the filter to the clip when open it in a timeline seperately.

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 ...

I have question in case of the BMD Cinema Camera. When I load the "Afterglow" shot 5 into Motion 5, I cannot tell Neat Video to denoise the full range of the shot. The image consists of very dark and mid-tones and Neat Video uses the mid-tones by default. But when I tell NV to fine-tune th...

No, just when I use GPU only or both together.

Okay, thank you very much.
But there is still a problem with the GTX 650M and Neat Video. Everytime I start denoising, the Terminal jumps in and says I'm out of memory.

Frame: 1920x1080 progressive, 32 bits per channel, Radius: 1 frame Running the test data set on up to 8 CPU cores and on up to 1 GPU CPU only (1 core): 1.71 frames/sec CPU only (2 cores): 3.4 frames/sec CPU only (3 cores): 4.69 frames/sec CPU only (4 cores): 5.41 frames/sec CPU only (5 cores): 5.18 ...

I'm on Retina MacBook Pro (OS X 10.8, CUDA drivers 5.0.17) and when I activate CPU+GPU processing in Neat Video (latest version 3.2) the speed is much slower than CPU/GPU only.

Is this a known bug?

Same issue on my side in Apple Motion (latest version and latest 5.x nVidia CUDA driver)...
Have the MBP Retina 2,6GHz and 16GB Ram

Can you please tell me what's fixed.
Because Larry Jordan mentioned something about a huge bug which might be fixed in this version.

Thank you

Since 10.0.4 update the image is flipped in the options window of Neat Video.

I trashed all render files of this project and switched my codec from ProRes422 HQ to ProRes Standard because of archiving. I rerendered it with the command "render all". Now the export works correctly!

That's hard to say whether its faster or slower because I have to rerender the whole project and there are several effects, corrections and filters around that Neat clips. So there is no way to say it clearly.

It's 10 minutes long, up to 10 tracks in vertical.
Lot's of cuts and transitions.
I have a ATI 4870 in my 8 core Mac Pro 2009 and 24GB Ram.
GPU isn't recognized by Neat Video.
But my best cpu combination is 15 (out of 16)...[/img]

Everything was completely rendered before I exported the whole movie. The export movie size is exactly the same as the project size. I did a new test with 2 non-processed clips and 2 processed clips: Export speed was normal. Hm... But in my huge project the export bar starts to slow down dramaticall...