4 ms·
Really neat stuff. Can't wait to see it in FOSS software so we can save some space in our video collections. :)
by nickpsecurity 11y ago
Really neat stuff. Can't wait to see it in FOSS software so we can save some space in our video collections. :)
- dublinben 11y agoYou can already achieve the same result using custom scripts and settings in x264. Most serious encoding groups have been doing this for years.
- nickpsecurity 11y agoDidn't know that. You got a link that makes it easy for people to learn how to do that in VLC player?
- toomuchtodo 11y agoNot VLC player, but equally good: https://handbrake.fr/ https://handbrake.fr/
- nickpsecurity 11y agoBut VLC can play the more clever encoding it generates, right?
- toomuchtodo 11y agoI'm not sure about that. You'd need to research or test to determine that.
- nickpsecurity 11y agoAight. Thanks for the link anyway.
- sangnoir 11y agoVLC can play anything! More seriously: the bitrates do not affect a player's compatibility with the container or video/audio format. For instance, if VLC can play H263, it doesn't matter if you use Handbrake to output 5100kbps or 100kbps.
- nickpsecurity 11y agoSweet! I'll try it out at some point then.
- astrange 11y agoHigher bitrates need higher CPU resources to decode, but it doesn't really matter. You'd run out of wifi bandwidth in your house streaming bluray images, though.
- brigade 11y agoOSS encoders (x264, Theora, VP9, Daala, Vorbis) already tend to have a constant quality rate control mode that they'd very much prefer you use unless you have an actual reason to need a specific bitrate. I'm always surprised at how many people try to reinvent it via abr... Netflix (and streaming services in general) on the other hand needs known bitrates with known constraints so their bandwidth estimation can work correctly without hiccups. Your personal video collection does not.
- nickpsecurity 11y agoSo, it only affects bandwidth and not storage space?
- brigade 11y agoNo - the point is that true constant quality has (almost) no constraints on local bitrate, so one section of a movie might be twenty times the bitrate of another section. Online streaming services continually estimate the current available bandwidth, then choose from a selection of pre-encoded streams to download. For this to work well, the selection must know the maximum local bitrate of each stream to match the estimation. If this local maximum isn't known or constrained, you get buffering because you're attempting to download a stream that's actually currently twenty times more than the available bandwidth. Whereas your personal video collection probably isn't being streamed over any link slower than several hundred MBit/s, which is more than enough for anything short of intermediate codec bitrates, plus significant buffering doesn't count against any data caps.
- nickpsecurity 11y agoMakes sense. Thanks for the detailed explanation.