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. 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. 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%.
Hope this helps Sponsored by Grammarly Grammarly helps ensure your writing is mistake-free. Start off with the same bitrate that the H.264 bitstream was encoded with and work your way down. Andrew Kolakowski wrote:I'm just surprised you have good decoding performance with h264 lossless. When you encode a lossy h264 video, you will lose quality, and, most importantly: It is completely irrelevant what your input format is. Once you have that, you can use FFmpeg with libx265 to do the conversion from H.264/AVC to H.265/HEVC pretty easily.
0 kommentar(er)
