https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #8 from Heiko Becker <heiko.bec...@kde.org> --- (In reply to Albert Astals Cid from comment #7) > I'd say then we should close this bug, it is actually a good way to find if > libavif is "compiled with the wrongly expected backend". I may be a bit ignorant here, but how am I supposed to know the wrongly expected encoders? libavif enables none by default (it seems to prefer aom at runtime if multiple encoders are present though). Btw. after patching libavif to build with recent SVT-AV1, it shows the same problem (and it doesn't support lossless too: https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/1636) > Sounds fair? How if I come up with a patch instead, that includes a configure check, that checks if aom is available as encoder and if it isn't the write test is skipped (with a message/warning, or maybe even only the two files)? -- You are receiving this mail because: You are watching all bug changes.
