3 ms·

For static image videos YouTube's H.264 version of the video is generally significantly smaller than either the VP9 or AV1 versions. Either YouTube's detection

For static image videos YouTube's H.264 version of the video is generally significantly smaller than either the VP9 or AV1 versions. Either YouTube's detection and modification of the encoder settings for this type of video or something intrinsic to the x264 encoder delivers better results from their H.264 encoding pipeline. The 480p video-only file sizes for this video as reported by youtube-dl have VP9 at 9.70MiB, AV1 at 9.25MiB, and H.264 at 3.55MiB.

6510 7y ago
So we give them something 13 kb-ish[0] and they compress it to 4.16 MB. I'm sure I'm already not putting it kind enough. Combined with the tiny battery in my phone I really feel like people are pulling a prank on me. I'm a behavioral experiment now! I think my roomba just looked at me. [0] http://i3.ytimg.com/vi/DwHpDOWhkGk/hqdefault.jpg http://i3.ytimg.com/vi/DwHpDOWhkGk/hqdefault.jpg
- clouddrover 7y ago
  YouTube's a video encoding site. The original video that was given to YouTube will have been substantially larger than 13 kb-ish. If your content is audio only then use an audio encoding site like SoundCloud. Or, if you really want to use YouTube, then you need to get them to develop an audio specific option.
  - 6510 7y ago
    I think we already have tons of brilliant people developing video codec. I'm sure they are all well aware there isn't a way to define part(s) of a video a slide show. What is missing is people pointing out how silly this is. The keyframes also define the seek points. Its a mess.
    - acqq 7y ago
      Yes, the formats and players should be changed to also allow more seek points than the key frames, exactly for these "picture not changing" scenarios but with the audio content we want to seek and consume. And then additionally, there should be better recognition of the "picture not changing" conditions, to allow better use of such a feature.

6510 7y ago

So we give them something 13 kb-ish[0] and they compress it to 4.16 MB. I'm sure I'm already not putting it kind enough. Combined with the tiny battery in my phone I really feel like people are pulling a prank on me. I'm a behavioral experiment now! I think my roomba just looked at me. [0] http://i3.ytimg.com/vi/DwHpDOWhkGk/hqdefault.jpg http://i3.ytimg.com/vi/DwHpDOWhkGk/hqdefault.jpg

clouddrover 7y ago
YouTube's a video encoding site. The original video that was given to YouTube will have been substantially larger than 13 kb-ish. If your content is audio only then use an audio encoding site like SoundCloud. Or, if you really want to use YouTube, then you need to get them to develop an audio specific option.
- 6510 7y ago
  I think we already have tons of brilliant people developing video codec. I'm sure they are all well aware there isn't a way to define part(s) of a video a slide show. What is missing is people pointing out how silly this is. The keyframes also define the seek points. Its a mess.
  - acqq 7y ago
    Yes, the formats and players should be changed to also allow more seek points than the key frames, exactly for these "picture not changing" scenarios but with the audio content we want to seek and consume. And then additionally, there should be better recognition of the "picture not changing" conditions, to allow better use of such a feature.