If dave want's to demonstrate and compare the effect of different import libraries in the same impressive and irrefutable way as in his first video, he just has to add for example shotcut into the comparison. on software that utilizes more recent average H.264 de-/encoding, you will not see so much difference between long-GOP footage and transcoded intermediate files anymore.

but as long as resolve is just using the quicktime framework, which is in fact based on very old legacy code ignoring any possible available hardware acceleration, people have to get the wrong impression, that: 'H.264 is Pure Evil.' - especially on windows.

most actual CPUs and GPUs got dedicated hardware support as well, to accelerate H.264 processing in very efficient ways. there was so much development going on concerning this particular kind of task over the last decade, that even little cell phones or a raspberry pi are now able to decode this kind of stuff in amazing speed. H.264 doesn't have to be perceptible slow in software from 2016. Well - resolve does have a really impressive processing pipeline - that's what we all like about it! - but this doesn't belong to some of its import export capabilities unfortunately. Peter Chamberlain wrote:If you spend the 8 mins at the beginning you get all the benefits of 32 bit float quality and Resolves features, and much faster final rendering into pro formats. Try with a frame based format like DPX, or a MXF/Quicktime DNxHR/ProRes. We'll see what we can do about improving 4K h264 performance, but this is what you are running into.

In general, we recommend using a non-temporal compression codec for editing. For this type of mediaI would recommend generating optimised media in the Media Pool, and that should make it nice and snappy. You are using 4K H264 on Windows I think which is not ideal. Sometimes it will take Resolve 4 seconds to start playing after I hit play whereas Premiere is never over. I have watched several of Alexis Van Hurkman's training courses, I understand that I can use smart cache and many other optimization tools to make editing smoother, but is there something I can do to make the performance better like Premiere Pro without waiting on footage to become optimized? Dave Dugdale wrote:I am not sure why Resolve feels somewhat laggy when making quick edits compared with the same footage in Premiere Pro CC.

Xmedia recode vs handbrake gtx 980