Neat Video & Neat Image community

Shoot...Spoke too soon. I went to edit a clip that's only 2 seconds long (in the timeline) and it first gave the FCP "Out of Memory" error, followed by the aforementioned NV error. As a reminder, this entire sequence is only ~12 minutes long. I see no reason why this should be happening--...

First of all, thank you for replying in this forum. It's great to find a developer who cares about the buyer. Not sure any project would be sufficiently small since it's for clips that are in HD; even though they're just a few seconds long, that's big for ProRes 422....and my upload speeds aren't ev...

OK, I've tried allocating 60% memory to FCP. I've tried deleting all my stills. I've tried opening it in only one sequence will all others closed. I've also tried adding just a single, 1-second clip to a *new* project and I'm still getting the error. :shock: I've even uninstalled all other 3rd-party...

Thanks. FCP doesn't even use all cores right now because it's not written for it (yet). So I knew that NV's setting wouldn't affect FCP. :) Based on some searches, I may have found the culprit. I had two large still images, which somehow kills FCP. I reduced their size. While I still see the error, ...

I've been getting this error every time I try to render a short (5-second clip). I have a 2x2.4 GHz Quad-Core Intel Xeon with 8gb RAM on a 512 SSD. I've tried disabling multiprocessor support. I've rebooted many times. The error reads: Error! Line: 185 Error: Neat Video cannot get free memory block ...