https://bugs.kde.org/show_bug.cgi?id=451257
Heiko Becker changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #15 from Albert Astals Cid ---
Can we close this now that 53 is merged and we warn users that their setup is
"wrong"?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #14 from dnovome...@gmail.com ---
The plug-in will print (example):
You are using rav1e encoder. It is recommended to enable libAOM encoder in
libavif for better near-lossless compression.
It will print only when quality==100 is requested, w
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #13 from Heiko Becker ---
(In reply to Albert Astals Cid from comment #12)
> I think that would be good, Heiko does that satisfy you?
Not really sure which part of the "or" question above is meant, but I'm fine
with either.
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #12 from Albert Astals Cid ---
I think that would be good, Heiko does that satisfy you?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #11 from dnovome...@gmail.com ---
It is possible to detect encoders via libavif C API.
Do you want to detect it in the write test or in the plug-in?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #10 from Albert Astals Cid ---
I don't think skipping the test is good, the situation you're in is bad, you
have a plugin that when reading the file and saving it again makes changes to
the file itself, and that's "bad", so having the test j
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #9 from dnovome...@gmail.com ---
What if we just print a message (about known issue with other AV1 encoders)
when avif write test fails?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #8 from Heiko Becker ---
(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,
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #7 from Albert Astals Cid ---
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".
Sounds fair?
--
You are receiving this mail because:
You are watching all b
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #6 from Heiko Becker ---
(In reply to dnovomesky from comment #5)
> So it happens with rav1e encoder.
>
> Perhaps the reason is that rav1e doesn't have lossless mode? As the
> following issue indicate:
>
> https://github.com/xiph/rav1e/iss
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #5 from dnovome...@gmail.com ---
So it happens with rav1e encoder.
Perhaps the reason is that rav1e doesn't have lossless mode? As the following
issue indicate:
https://github.com/xiph/rav1e/issues/151
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #4 from Heiko Becker ---
Version: 0.9.3 (dav1d [dec]:0.9.2, rav1e [enc]:0.5.1 (0.5.1))
libyuv : unavailable
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #3 from dnovome...@gmail.com ---
It would be good to know how libavif was configured.
Libavif can use different encoders: libaom, rav1e, svt-av1.
avifenc or avifdec utilities can print such information about libavif encoders
and their versi
https://bugs.kde.org/show_bug.cgi?id=451257
Albert Astals Cid changed:
What|Removed |Added
CC||dnovome...@gmail.com
--- Comment #2 from Al
https://bugs.kde.org/show_bug.cgi?id=451257
--- Comment #1 from Heiko Becker ---
Created attachment 147353
--> https://bugs.kde.org/attachment.cgi?id=147353&action=edit
test output
--
You are receiving this mail because:
You are watching all bug changes.
16 matches
Mail list logo
