qoi VS crunch

Her request is politely-phrased and reasonable. I don't think there's a legal or ethical issue, but respecting the wishes of others when it costs nothing is just kindness.

However, the way that some have seized on it, and then interacted with others in their communities is ... neither polite nor reasonable.

e.g. https://github.com/phoboslab/qoi/issues/35

How do you know it's not a problem for the people who work with computer vision? Let's take this for example - sure, the request itself was presented very unprofessionally, but this is still an example of someone in a computer vision-adjacent field stating in no uncertain terms that they have a problem with the image.

Yes. Without a supporting statement, it's ad hominem. But I provided a supporting statement.

This is the issue I'm taking about: https://mobile.twitter.com/richgel999/status/146443578680850...

Which links to here: https://github.com/phoboslab/qoi/issues/35

Where everyone agrees, yes, the image should be removed. They didn't know about its history. Would he please stop being a gigantic asshole about it.

So if that's not blowing things out of proportion, I don't know what is.

I don't know about CUDA, however I've made an AVX2 based encoder a few months ago : https://github.com/phoboslab/qoi/pull/143

I intend to create an AVX2 based decoder but I had absolutely no time to work on side projects in the past three months.

You might also want to take a look at this streaming encoder if you want to encode large files with a tiny memory footprint : https://github.com/MKCG/php-qoi/blob/main/src/FFI/lib/qoi.c

Not only does compression improve this situation today, but using QOI means improvements may continue to come over time. QOI is a very new, open source image format, and that's already proving to be an advantage. By itself, QOI compression is pretty weak, but YoYoGames have forked it and worked in BZ2 compression to surpass the old PNG format. As QOI itself improves and as YoYoGames continues to work on it, it's almost guaranteed that we'll see the compression ratio in GameMaker get better over time.

As an aside, crunch compression is a bit of a red herring here. While it does reduce the size on disk, it needs to be expanded back to regular DXT when it's first displayed, so it won't solve our memory issues by itself.

Have you considered compressed texture formats? Fixed compression ratio (usually 1 byte per pixel), arbitrary random access, decompress the pixels you need on the fly. Can be further compressed for efficient storage closer to JPEG ratios with https://github.com/BinomialLLC/crunch.

After spending some time trying several libraries, I settled with FasTC for now, but it seems to only be able to manage 32 bits RGBA image formats... I am looking into Crunch2 which is basically Crunch with modern CMake.