lkpcoupons.blogg.se - Davinci resolve crashing while editing

So even though you'd assume the system is reading from the SSD it is somehow seems like its calling on the original media. When the original R3d file were on a slower RAID, and even when the Media was optimized onto an SSD it still caused issue of cache disappearing like the above clip. What did finally work was making sure all the media and cache files were on an extermely fast SSD drive (I bought a Thunderblade 8TB drive which gets 2400MB/sec). I optimized R3d files onto an external SSD which gets about 800MB/sec and was using a 2k timeline. To work around this I tried a bunch of things - playing around with optimized media, changing the GPU setting in Neat etc. And I assume if Neat Video can cause this issue, perhaps other OFX plugins can do this too.

Even in a 2k Timeline is causes weird rendering behaviour.

If you are using Neat Video it causes problems.

I've done a lot of experimenting on this in the last few days and I think I have a few workable clues I can share: And it's then hard to tell when it will decide that everything will need to be re-rendered. Any clues as to what's going on here? I've got lots of RAM 127 GB, 10 core 3.2 GBZ i9 iMac and lots of SSD Cache. I assume the timeline is doing multiple passes at different node layers. I've noticed this behavior for years, but I've never got to the bottom of what's going on. It's not a big deal on a 2 minute edit but when it's a 30 minute program with 8K raw footage inside it, it's the difference between exporting a timeline in 5 minutes vs several hours. That becomes a major issue when I'm relying on the timeline's rendered cache to speed up exports. So unlike other editing software, I can't assume that the rendered areas are fully rendered and I can't trust that they will stay rendered.

I find on big projects timeline turns blue in parts, then those blue patches become red again. I've experimented with both Smart and User modes and caching individual node, and using the Cache colour output methods. I find on long complex timelines, Resolve's timeline rendering behaves in unpredictable and weird ways.