7 ms·

That's one way to frame it. Or you could use a plugin to request the h264 version, and keep the battery life gains of hardware acceleration on non vp9 accelera

That's one way to frame it. Or you could use a plugin to request the h264 version, and keep the battery life gains of hardware acceleration on non vp9 accelerating devices (vp9 accel. is quite recent.) And still get to watch in 4k.

guitarbill 10y ago
That's not how it works. If you request h264, there is no 4K option because there's no 4K h264 encoded version* . Edit: As SG- pointed out, I also cannot read and Youtube is processing 4K h264, but not offering it on the main site. So it's puzzling why they're doing this. Bandwidth is a possibility, but you'd think it'd be consistently applied. * You can test this using Chrome + h264ify. Which I use because the battery life when watching VP9 is truly horrific, and I don't care how much Google saves on bandwidth by pulling this stunt.
- deleted 10y ago
  [deleted]
- RichardHeart 10y ago
  You are right and I am wrong. 1440p was max I was offered forcing flash player in opera and mp4 in chrome. Out of curiosity, why was this article safari framed when it affects all browsers that want to use h264 4k including chrome and opera? Is there some way that this is actually a safari-centric change?
  - guitarbill 10y ago
    Because by default Chrome/Firefox/Edge support VP9 but Safari does not. By extension, if you aren't blocking VP9, and most people aren't, Chrome/Firefox/Edge get VP9 = 4K and Safari gets H264 = no 4K.
- SG- 10y ago
  "The necessary support of the VP9 video codec for 4K playback today seems to currently apply to videos being watched directly on YouTube’s site. A quick way to check is to launch an uploaded 4K video on YouTube, and attempt to change the resolution. Recently uploaded videos only show HD options up to 1440p in Safari. Interestingly, if these very videos are embedded on an external page, then 4K video playback is still an option." So it looks like they're encoding h264 in 4K, just not if you're on the actual Youtube site.
  - rasz_pl 10y ago
    lets pray to formatting gods, : D:\_learning>youtube-dl.exe -F https://www.youtube.com/watch?v=4Twcx4QozRc https://www.youtube.com/watch?v=4Twcx4QozRc [youtube] 4Twcx4QozRc: Downloading webpage [youtube] 4Twcx4QozRc: Downloading video info webpage [youtube] 4Twcx4QozRc: Extracting video information [youtube] 4Twcx4QozRc: Downloading MPD manifest [info] Available formats for 4Twcx4QozRc: format code extension resolution note 249 webm audio only DASH audio 53k , opus @ 50k (48000Hz), 811.34KiB 250 webm audio only DASH audio 85k , opus @ 70k (48000Hz), 1.24MiB 140 m4a audio only DASH audio 95k , m4a_dash container, mp4a.40.2@128k (44100Hz), 1.47MiB 171 webm audio only DASH audio 104k , vorbis@128k (44100Hz), 1.44MiB 251 webm audio only DASH audio 127k , opus @160k (48000Hz), 1.86MiB 278 webm 256x144 DASH video 114k , webm container, vp9, 24fps, video only, 1.10MiB 160 mp4 256x144 DASH video 114k , avc1.4d400c, 24fps, video only, 1.67MiB 242 webm 426x240 DASH video 143k , vp9, 24fps, video only, 1.27MiB 243 webm 640x360 DASH video 248k , vp9, 24fps, video only, 2.22MiB 133 mp4 426x240 DASH video 260k , avc1.4d4015, 24fps, video only, 3.71MiB 134 mp4 640x360 DASH video 268k , avc1.4d401e, 24fps, video only, 3.23MiB 244 webm 854x480 DASH video 380k , vp9, 24fps, video only, 3.48MiB 135 mp4 854x480 DASH video 569k , avc1.4d401e, 24fps, video only, 6.62MiB 247 webm 1280x720 DASH video 761k , vp9, 24fps, video only, 6.77MiB 136 mp4 1280x720 DASH video 1101k , avc1.4d401f, 24fps, video only, 12.63MiB 248 webm 1920x1080 DASH video 1726k , vp9, 24fps, video only, 13.09MiB 137 mp4 1920x1080 DASH video 2324k , avc1.640028, 24fps, video only, 24.90MiB 271 webm 2560x1440 DASH video 4744k , vp9, 24fps, video only, 38.59MiB 264 mp4 2560x1440 DASH video 6415k , avc1.640032, 24fps, video only, 62.11MiB 266 mp4 3840x2160 DASH video 11632k , avc1.640033, 24fps, video only, 152.17MiB 313 webm 3840x2160 DASH video 16250k , vp9, 24fps, video only, 175.23MiB 17 3gp 176x144 small , mp4v.20.3, mp4a.40.2@ 24k 36 3gp 320x180 small , mp4v.20.3, mp4a.40.2 43 webm 640x360 medium , vp8.0, vorbis@128k 18 mp4 640x360 medium , avc1.42001E, mp4a.40.2@ 96k 22 mp4 1280x720 hd720 , avc1.64001F, mp4a.40.2@192k (best) so 4K is indeed just hidden in the YT player, but present in the manifest
- LeoNatan25 10y ago
  They are using it because they want to force Chrome and save bandwidth. What's puzzling you exactly? In different eras and with different company, this would be called monopoly.
  - guitarbill 10y ago
    a) Why not do the same to embedded videos? b) The only affected browser is Safari. Edge and Firefox remain unaffected. c) How many people actually watch 4K videos, and how many videos are 4K? So let's not go overboard on the conspiracy theories. For all we know, it could be a bug.
    - milankragujevic 10y ago
      It's most likely not a bug, as YouTube and Google are known for forcing VP8/9/10/A1 down people's throats, because it's theirs and they want to "show it to Apple". For video sites, H.264 is the only option if they want to support Apple devices, and it's hardware decoding is widespread enough that it doesn't cause any issues. The only issue is it's patented and it's bad at encoding compared to VP9/H.265. But we can just switch to H.265 anyways, and given that Google deprecates their codecs every 2 years, I don't think that they will ever have good hardware decoding support.
      - Oletros 10y ago
        > I don't think that they will ever have good hardware decoding support. Almost all modern the GPUs and processors have hardware decoding for VP9
      - Godel_unicode 10y ago
        > The only issue is it's patented and it's bad at encoding compared to VP9/H.265 Your argument is that Google is evil for pushing a codec that's patent-free and better as a codec? Also, as others have stated, VP9 has wide hardware acceleration support (and will have wider support in the future)?
  - rasz_pl 10y ago

guitarbill 10y ago

That's not how it works. If you request h264, there is no 4K option because there's no 4K h264 encoded version* . Edit: As SG- pointed out, I also cannot read and Youtube is processing 4K h264, but not offering it on the main site. So it's puzzling why they're doing this. Bandwidth is a possibility, but you'd think it'd be consistently applied. * You can test this using Chrome + h264ify. Which I use because the battery life when watching VP9 is truly horrific, and I don't care how much Google saves on bandwidth by pulling this stunt.

deleted 10y ago
[deleted]
RichardHeart 10y ago
You are right and I am wrong. 1440p was max I was offered forcing flash player in opera and mp4 in chrome. Out of curiosity, why was this article safari framed when it affects all browsers that want to use h264 4k including chrome and opera? Is there some way that this is actually a safari-centric change?
- guitarbill 10y ago
  Because by default Chrome/Firefox/Edge support VP9 but Safari does not. By extension, if you aren't blocking VP9, and most people aren't, Chrome/Firefox/Edge get VP9 = 4K and Safari gets H264 = no 4K.
SG- 10y ago
"The necessary support of the VP9 video codec for 4K playback today seems to currently apply to videos being watched directly on YouTube’s site. A quick way to check is to launch an uploaded 4K video on YouTube, and attempt to change the resolution. Recently uploaded videos only show HD options up to 1440p in Safari. Interestingly, if these very videos are embedded on an external page, then 4K video playback is still an option." So it looks like they're encoding h264 in 4K, just not if you're on the actual Youtube site.
- rasz_pl 10y ago
  lets pray to formatting gods, : D:\_learning>youtube-dl.exe -F https://www.youtube.com/watch?v=4Twcx4QozRc https://www.youtube.com/watch?v=4Twcx4QozRc [youtube] 4Twcx4QozRc: Downloading webpage [youtube] 4Twcx4QozRc: Downloading video info webpage [youtube] 4Twcx4QozRc: Extracting video information [youtube] 4Twcx4QozRc: Downloading MPD manifest [info] Available formats for 4Twcx4QozRc: format code extension resolution note 249 webm audio only DASH audio 53k , opus @ 50k (48000Hz), 811.34KiB 250 webm audio only DASH audio 85k , opus @ 70k (48000Hz), 1.24MiB 140 m4a audio only DASH audio 95k , m4a_dash container, mp4a.40.2@128k (44100Hz), 1.47MiB 171 webm audio only DASH audio 104k , vorbis@128k (44100Hz), 1.44MiB 251 webm audio only DASH audio 127k , opus @160k (48000Hz), 1.86MiB 278 webm 256x144 DASH video 114k , webm container, vp9, 24fps, video only, 1.10MiB 160 mp4 256x144 DASH video 114k , avc1.4d400c, 24fps, video only, 1.67MiB 242 webm 426x240 DASH video 143k , vp9, 24fps, video only, 1.27MiB 243 webm 640x360 DASH video 248k , vp9, 24fps, video only, 2.22MiB 133 mp4 426x240 DASH video 260k , avc1.4d4015, 24fps, video only, 3.71MiB 134 mp4 640x360 DASH video 268k , avc1.4d401e, 24fps, video only, 3.23MiB 244 webm 854x480 DASH video 380k , vp9, 24fps, video only, 3.48MiB 135 mp4 854x480 DASH video 569k , avc1.4d401e, 24fps, video only, 6.62MiB 247 webm 1280x720 DASH video 761k , vp9, 24fps, video only, 6.77MiB 136 mp4 1280x720 DASH video 1101k , avc1.4d401f, 24fps, video only, 12.63MiB 248 webm 1920x1080 DASH video 1726k , vp9, 24fps, video only, 13.09MiB 137 mp4 1920x1080 DASH video 2324k , avc1.640028, 24fps, video only, 24.90MiB 271 webm 2560x1440 DASH video 4744k , vp9, 24fps, video only, 38.59MiB 264 mp4 2560x1440 DASH video 6415k , avc1.640032, 24fps, video only, 62.11MiB 266 mp4 3840x2160 DASH video 11632k , avc1.640033, 24fps, video only, 152.17MiB 313 webm 3840x2160 DASH video 16250k , vp9, 24fps, video only, 175.23MiB 17 3gp 176x144 small , mp4v.20.3, mp4a.40.2@ 24k 36 3gp 320x180 small , mp4v.20.3, mp4a.40.2 43 webm 640x360 medium , vp8.0, vorbis@128k 18 mp4 640x360 medium , avc1.42001E, mp4a.40.2@ 96k 22 mp4 1280x720 hd720 , avc1.64001F, mp4a.40.2@192k (best) so 4K is indeed just hidden in the YT player, but present in the manifest
LeoNatan25 10y ago
They are using it because they want to force Chrome and save bandwidth. What's puzzling you exactly? In different eras and with different company, this would be called monopoly.
- guitarbill 10y ago
  a) Why not do the same to embedded videos? b) The only affected browser is Safari. Edge and Firefox remain unaffected. c) How many people actually watch 4K videos, and how many videos are 4K? So let's not go overboard on the conspiracy theories. For all we know, it could be a bug.
  - milankragujevic 10y ago
    It's most likely not a bug, as YouTube and Google are known for forcing VP8/9/10/A1 down people's throats, because it's theirs and they want to "show it to Apple". For video sites, H.264 is the only option if they want to support Apple devices, and it's hardware decoding is widespread enough that it doesn't cause any issues. The only issue is it's patented and it's bad at encoding compared to VP9/H.265. But we can just switch to H.265 anyways, and given that Google deprecates their codecs every 2 years, I don't think that they will ever have good hardware decoding support.
    - Oletros 10y ago
      > I don't think that they will ever have good hardware decoding support. Almost all modern the GPUs and processors have hardware decoding for VP9
    - Godel_unicode 10y ago
      > The only issue is it's patented and it's bad at encoding compared to VP9/H.265 Your argument is that Google is evil for pushing a codec that's patent-free and better as a codec? Also, as others have stated, VP9 has wide hardware acceleration support (and will have wider support in the future)?
- rasz_pl 10y ago