Viewing a single comment thread. View all comments

randybruder t1_j8xeemv wrote

Every time I see this asked, the person asking gets highly-upvoted answers that are complete bullshit. You want a real answer?

YouTube stores all of their video files and audio files separately. It's a clever way of saving server space—you can have all of the different video files (at a bunch of different resolutions and video codecs), and then a few audio files (at different bitrates and formats), and then on the fly pick the best video file for the user, pick the best audio file for the user, and play them back at the same time. For example, here's all the individual files that YouTube generates/stores for the Costa Rica video from your post.

In a browser, YouTube uses Media Source Extensions which allows them to combine those video and audio streams, and do things like let you switch resolution without the video stopping (or even dynamically switch the resolution based on available bandwidth without interrupting the video.)

Safari on iOS doesn't support Media Source Extensions. So in addition to the multitude of individual video-only and audio-only streams YouTube generates, they also generate a few versions that include both the video and audio in one file—but only up to 720p. That's why Safari only shoes those options, it's all it's capable of playing, because there's no assembly needed by the browser. (Interestingly, Media Source Extensions is implemented in Safari on iPadOS, which is why you'll see more resolution options there.)

4

gordito_gr t1_j8zcv7h wrote

>(Interestingly, Media Source Extensions is implemented in Safari on iPadOS, which is why you'll see more resolution options there.)

How's that 'interestingly'? Apple surely does try to worsen the experience, no reason not to support media source extensions.

0

randybruder t1_j8zt2j3 wrote

> Apple surely does try to worsen the experience

How does Apple "try to worsen the experience"? The obvious guesses are that Apple hadn't gotten to implementing it in a way they want to be performative.

Or maybe Apple intentionally won't enable it because making Safari work smoothly means deciding not to support certain popular technologies, and forcing everyone else to adapt—perfect example of that is Apple's refusal to support Adobe Flash. Was Apple's motivation to not support Flash "trying to worsen the experience"?

1

[deleted] t1_j904ch1 wrote

[removed]

0

randybruder t1_j907pa8 wrote

> Stop D riding Apple

My original comment is explaining how the max 720p is literally Apple's fault, and not YouTube's fault. I'm the only one in the entire thread correctly blaming Apple for this. And I'm D riding Apple?

You should try reading the comments before you say stupid shit.

> literally just a codec.

I explained in my comment that it isn't a codec, but a web specification. It's not "Safari doesn't support the V9 codec" like a lot of people mistakenly think—apparently you're misinformed about that too.

> Bruh, this is a fanboy excuse,

Educated guess, not an excuse.

Still waiting on you to explain how "Apple does try to worsen the experience"

0