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?
September 15, 2020, 11:45pm
I assume that youtube re-encoded your video as avc1 instead of vp09, right? Right click on the youtube player and click on “Stats for nerds” to check.
Unless I’m missing something, H.265 and HEVC are two names for the same thing. You can call that codec by either name.
September 15, 2020, 11:59pm
Interesting. vp09 is the highest quality codec at youtube. See if that’s something you can report to google about.
& i mistyped, 264
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)
September 16, 2020, 2:28am
I’m curious did you use the “YouTube” export or just the h264 export?
September 16, 2020, 3:51am
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.
Youtube, then modded stuff & saved as preset:
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.
h264 upload to AV: https://www.airvuz.com/video/🐝-Dithery-Do--Aggressive-7-Multi-Rotor-Cruising?id=5f614004afc1f02e29dca458
h264 first upload to YT: https://youtu.be/wNLr0BL8-mk
h264 re-upload to YT: https://youtu.be/eUqHvsgnGEM same problem
h265 GOP=5 upload to YT: https://youtu.be/J_vg_vFYfVY no scramble!! (but my desktop cannot hardware export hvec_vaapi, my laptop can…) A good step forward!!
hevc_vaapi (h265) seems to be the fix. reduce GOP for “fast motion” video, but i have zero clue if is a part of the fix.
September 16, 2020, 3:25pm
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)
September 19, 2020, 8:04am
what kind of GPU do you have?
Makes sense to use NVENC if you have a Nvidia card.
none, CPU based Intel HD.
September 19, 2020, 11:24pm
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)
September 20, 2020, 6:07am
Here is makes sense to Use Software encoding only.
Hardware encoding on Intel has been unreliable so far in my Experience with i3 and i5 hardware.
December 14, 2020, 11:13pm
This topic was automatically closed after 90 days. New replies are no longer allowed.