QOI benchmark indicates worse compression than PNG edit

I might be reading the description section wrong. It currently says

Figures specified in the announcement and the video claim 20–50x encoding, and 3–4x decoding speed compared to PNG, with compression better or significantly better.

citing https://qoiformat.org/benchmark/.

However, the compression ratio for PNG is smaller than QOI, signifying that PNG compresses better. If the intention of the quoted passage is that PNG compression is better or significantly better, I think it should be worded as "with *PNG* compression better or significantly better", or something similar.

--MysticalData (talk) 14:49, 3 May 2022 (UTC)Reply

Thank you. I have adjusted it. (Hohum @) 16:13, 3 May 2022 (UTC)Reply

FFMPEG? edit

I'm slightly concerned about the addition of FFMPEG as implementing QOI because I'm not sure if the reference is considered reliable and I'm not sure if the editor, who is anonymous, is the person who did the work reported (which might be considered original research). I don't know how to resolve either issue. David Spector (talk) 12:15, 5 June 2022 (UTC)Reply

The reference is a Git commit which isn't in the stable release of FFMpeg yet. I'll revert this until QOI support becomes stable (planned for version 5.1), and it would probably be better to reference the changelog rather than a random commit when that happens. Arthomnix (talk) 18:41, 5 June 2022 (UTC)Reply

File format section copied from specification document edit

The File format section appears to be a copy of the entire QOI specification document. I have added an inline citation to make sure this does not violate plagiarism guidelines, but it would probably be better long-term to rewrite the section. Arthomnix (talk) 19:10, 5 June 2022 (UTC)Reply

The specification is public domain, and I'm not sure how it could be rewritten anyway, since its a specification, and if not repeated verbatim, it's likely to mean something else. I'm more concerned that it's more jargon that the article needs. (Hohum @) 21:03, 5 June 2022 (UTC)Reply