Does anyone know why youtube ruins video like this?
Sometimes ffmpeg/shotcut will do something similar, but the source video here did not have the scramble.
(source is purposely dithered here, so ignore that effect)
side-question, if my PC supports both h264_vaapi and hevc_vaapi, which is “better” for youtube as the target?
Interesting. vp09 is the highest quality codec at youtube. See if that’s something you can report to google about.
Okay. Well, vp9 which is from google competes with HEVC which is from MPEG. Did you encode that video you uploaded with H.264 or HEVC hardware encoding?
I wonder if google re-encodes a video any differently if it’s fed as vp9 from the start.
source (Shotcut output) was hardware h264, which is what iv’e always done, but willing to modify for best end-results. i dont mind youtube re-encoding, but corrupting the image ruins the art.
i will certainly try hevc h265 now. (<1 hour render)
I would be curious to know if the scramble appeared a second time if you uploaded a second copy of the video to YouTube. That scramble looks suspiciously like a fixity error.
i just re-upped orig h264 again and new h265, youtube processing slow so i will report again in hours. FWIW, Airvuz.com did the same (on h264), just not same spots. it’s a re-encode fail for sure.
Not using VAAPI(hardware encoding) may also be a solution, that’s the AMD GPU hardware encoder just using cpu based H264 may be better(if memory serves it results in smaller files as well)
if your video codec is vaapi you’re using the gpu not cpu encoding(it might work through the intel gpu as well since amd utilizes openCL more than nvidia which will be a cuda encoder)