News for hackers. Stuff that matters.

A comment on QOI: Lossless Image Compression in O(n) Time. Parent comment

Re:QOI: Lossless Image Compression in O(n) Time by formerly_proven on Wednesday November 24, 2021 @02:06PM (#29333808)
> An absolute color space exists. It's called XYZ. We could use it. Some image formats support it.

XYZ is really annoying to work in though. ACES is a pragmatic solution here, quite literally: https://blog.frame.io/wp-content/uploads/2019/09/ACES-APO.jp...

Okay, fair enough two out of three primaries are imaginary colors, but nobody said you have to use the whole color space when your processing pipeline is meant to be using 32 bit floats. Delivery formats might want to be using a more real color space.

[ Parent | on HN ]
Re:QOI: Lossless Image Compression in O(n) Time by pixel_fcker on Wednesday November 24, 2021 @02:22PM (#29334017)
ACES (AP0) is an archive format for when you want to be absolutely sure you’re not clipping any colours. As a working space it’s terrible and AP1 should be preferred, either as ACEScg or ACEScc
[ Parent | on HN ]
Re:QOI: Lossless Image Compression in O(n) Time by Dylan16807 on Wednesday November 24, 2021 @04:28PM (#29335381)
AP1 is almost the same as rec.2020? I'm not sure what you mean by 'working space' but if preserving all colors was a primary or even secondary goal I definitely wouldn't cut myself down that far.
[ Parent | on HN ]
Re:QOI: Lossless Image Compression in O(n) Time by pixel_fcker on Saturday November 27, 2021 @01:25PM (#29362194)
AP1 is essentially Rec.2020, yes.

By working space I mean a space in which a user manipulates the data in some way, e.g. image editing, grading, compositing or rendering.

[ Parent | on HN ]