I’ll be trying to reproduce the problem on the asset from @szaimen and from my own library.
We’ve identified that hardware-accelerated decoding in Chrome causes the video artifacts but does not cause the audio skipping. There’s one more step to completely eliminate Chrome’s decoder.
Below is an ffmpeg command that remuxes an MKV into direct playable MP4. Theory is, if this file plays correctly then the issue is caused by direct streaming. While if this file plays poorly then it’s a decoder issue.
I leave this here for anyone that’s interested in the details and wants to sherlock along with us.
ffmpeg -i "input file.mkv" -c:v copy -c:a aac -ac 2 -metadata:s:a:1 title="" "output file.mp4"
-
ffmpeg-
-i "input file.mkv": name of the input file, be sure to quote paths with strings -
-c:v copy: copy the video stream untouched -
-c:a aac -ac 2: convert audio to stereo AAC -
-metadata:s:a:1 title="": set thetitleof the first audio stream to an empty string. I noticed in my testing that the originaltitlewas used by default. It was confusing to see the originaltitleon the new audio stream. -
"output file.mp4": name the file anything you choose so long as it ends in.mp4
-