https://bugs.kde.org/show_bug.cgi?id=468609
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|Other |Debian stable
--- Comment #13 from caulier.gil...@gmail.com ---
2. Your plugin tool says libde256 does only 8-bit but on GIT they say
that libde256 does support HDR (which makes little sense with 8-bit).
Where does the 8-bit limit come from?
libde265 must be compiled with more color depth support, else it's 8 bits per
default.
3. There should be a warning when saving from a 16 bit workspace to 8-bit Heif
Create a new entry in bugzilla, not only for HEIF but other format supporting
more color depth as TIFF or PNG.
4. IM does HEIF 16 bit, why not using IM to load HEIF?
Because IM is slower and we already use libheif directly. We also seen
instability from IM with certain image formats. The avaialblility of IM under
certain OS is not guaranty (ex, MacOS Macports only support 6.x version not the
7.x)
5. Saving from a 16-bit workspace should offer a way to select the depth.
This is a feature request.
I found that 10-bit depth is a good compromise between space and quality.
Create a new entry in bugzilla in this case.
6. If DigiKam does not like to support 10-Bit Tiff (which is not standard
but understood by IM) then try to reduce colors by masking away lower bits.
Create a new entry in bugzilla in this case.
7. Currently Digikam offers limited 16-bit support, best for TIFF. Hopefully
the future development will allow a wider support for HiColor and or HDR.
There is already a file in bugzilla about this topic, if i remember
8. Your Image Loader Plugin architecture is quite nice, but for several
reasons I would like to use IM codecs, but the IM Loader cannot be selected
for HEIF, JPegXl ... ?
It's due to performance and stability. HEIF use a dedicated loader, JPEGXL a
KDE ImageFormat plugin.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
