11–20 of 229 posts
Fabrice Bellard's BPG image format uses H.265's keyframe compressor: https://bellard.org/bpg/ Here is a side-by-side visual comparison: http://xooyoozoo.github.io/yolo-octo-bugfixes/#ballet-exerci... Amazing. I ported his BPG decoder to Android ARM for a pornographic app. See my comment history for details. It reduced data transfer by more than 60%.
The article starts off with talking about "raw" video containing 3 bytes for every pixel. However, most video is YUV, which is typically 1.5 bytes/pixel. https://en.wikipedia.org/wiki/YUV
But YUV is almost always combined with color subsampling, which gets you to 1.5 or 2 bytes per pixel.
The article starts off with talking about "raw" video containing 3 bytes for every pixel. However, most video is YUV, which is typically 1.5 bytes/pixel. https://en.wikipedia.org/wiki/YUV
Well, if we're being pedantic here, raw RGB video as would be displayed on a RGB monitor does indeed take 3 bytes per pixel. Technically, YUV is either an optimization or a backwards compatibility measure, and hence the adjective "raw" does not apply to it.
But there are clearly other ways to store a pixel of colour information in less than 3 bytes, which is OP's point. It's not an optimization really - it's just a different coding format (Just as ASCII isn't an optimization of Unicode).
Scoooped: https://news.ycombinator.com/item?id=30686148 ;) ;p xx ;p
The article starts off with talking about "raw" video containing 3 bytes for every pixel. However, most video is YUV, which is typically 1.5 bytes/pixel. https://en.wikipedia.org/wiki/YUV
Well, if we're being pedantic here, raw RGB video as would be displayed on a RGB monitor does indeed take 3 bytes per pixel. Technically, YUV is either an optimization or a backwards compatibility measure, and hence the adjective "raw" does not apply to it.
In fact since decoding also often happens in hardware, the raw size may never materialize anywhere in the pipeline, other than the framebuffer of the video card. Even HDMI has compression now [0]
The author probably choose a screenshot as a benchmark, because otherwise it's hard to get your hands on anything compressible but not already compressed.
Fabrice Bellard's BPG image format uses H.265's keyframe compressor: https://bellard.org/bpg/ Here is a side-by-side visual comparison: http://xooyoozoo.github.io/yolo-octo-bugfixes/#ballet-exerci... Amazing. I ported his BPG decoder to Android ARM for a pornographic app. See my comment history for details. It reduced data transfer by more than 60%.
Isn’t that exactly what HEIC is?
Fabrice Bellard's BPG image format uses H.265's keyframe compressor: https://bellard.org/bpg/ Here is a side-by-side visual comparison: http://xooyoozoo.github.io/yolo-octo-bugfixes/#ballet-exerci... Amazing. I ported his BPG decoder to Android ARM for a pornographic app. See my comment history for details. It reduced data transfer by more than 60%.
Fabrice Bellard's BPG image format uses H.265's keyframe compressor: https://bellard.org/bpg/ Here is a side-by-side visual comparison: http://xooyoozoo.github.io/yolo-octo-bugfixes/#ballet-exerci... Amazing. I ported his BPG decoder to Android ARM for a pornographic app. See my comment history for details. It reduced data transfer by more than 60%.