what? the codec is built into the browser, it doesn't use DirectShow or whatever
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
this is just Edge, default stuff
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
that is not the problem here. they're using the same decoding code.
1 reply 0 retweets 0 likes -
Your GOP size is probably the x264 default of 250, more than both YT (160) and Twitter (180). Your video is also shorter, exacerbating the problem by having only 1-2 I frames that you could quickly seek to for the entire video. That's why this isn't a problem for other people.
1 reply 0 retweets 1 like -
this is a thread about different codec binaries possibly being used across the same browsers. not about the video material.
1 reply 0 retweets 0 likes -
This is a thread about how someone said their browser works fine on videos encoded and played back by two services which aren't your video, because you didn't provide your video for other people to test, and not all videos are created equal.
0 replies 0 retweets 1 like -
This Tweet is unavailable.
I'm just pointing out that encoding settings make a huge difference. Most people would think h.264 is h.264, but you can configure it from free perfect seeking like Sorenson on that ancient Mac, to potentially having to decode the entire video to seek.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.