So you end up interpolation chroma twice, once in ProRes then in Resolve to YRGB. So when converting to ProRes from a 4:2:0 source to import into Resolve you have an additional forced chroma up sampling which cannot be lossless to my understanding. I'm also thinking that ProRes might not be a good choice for 4:2:0 sources as it only seems to do 4:2:2 and 4:4:4. Then it might be quite a nice alternative all GPU enc/dec. Open a terminal and direct it to the directory containing the H.265 encoded files, assuming you have ffmpeg and the appropriate libraries installed and assuming they are in MKV format copy and paste the following into the terminal window.
I'm curious if it would rank higher than ProRes. Would be interesting to try to match ProRes HQ bitrate with lossy H264 all I frames and compute visual scores for both. I'm not aware of a GPU supporting lossless for decoding. No issues with fast cuts or fast forward / reverse playback JKL. ProRes is smoother to scrub with the mouse, but H264 is good enough for me. When you encode a lossy h264 video, you will lose quality, and, most importantly: It is completely irrelevant what your input format is. It should be slower than ProRes, DNxHR (maybe it's GPU decoded).H264 4:2:0 8bit 4k60p lossless all I frames uses about 56% CPU when looping the timeline, ProRes HQ 4:2:2 10bit about 51%. Andrew Kolakowski wrote:I'm just surprised you have good decoding performance with h264 lossless.
0 kommentar(er)
