https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #51 from caulier.gil...@gmail.com ---
Git commit adb7178aa0ec3e02ecbf76bb5c29b4544a94a5f8 by Gilles Caulier.
Committed on 10/03/2022 at 07:18.
Pushed by cgilles into branch 'qt5-maintenance'.
As with AppImage, build libaom as static under
https://bugs.kde.org/show_bug.cgi?id=109060
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||7.7.0
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #50 from caulier.gil...@gmail.com ---
Git commit fc125e54fa9a67bfb271b0bd5a4a1d4e8bde2d03 by Gilles Caulier.
Committed on 10/03/2022 at 04:52.
Pushed by cgilles into branch 'qt5-maintenance'.
Same type-mime problem than AVIF for JPX,
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #49 from dnovome...@gmail.com ---
AVIF testfiles:
https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #48 from Maik Qualmann ---
OK, interesting. I searched the web for more AVIF samples. Images that can be
displayed are actually recognized as AVIF by QImageReader::imageFormat.
Maik
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #47 from Maik Qualmann ---
QByteArray QImageReader::imageFormat(const QString )
This function should return an empty string if the format is unknown (PCX for
me). An empty string is probably not an empty QByteArray. Therefore, the
fallback
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #46 from Maik Qualmann ---
Git commit 8c54803387e7af323a9e293359076ba3610c6702 by Maik Qualmann.
Committed on 09/03/2022 at 21:04.
Pushed by mqualmann into branch 'master'.
fix AVIF detection for the database
M +7-0
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #45 from Maik Qualmann ---
Hi Gilles,
For me it is recognized as a "PCX" image. Recognition is done with
QImageReader::imageFormat(). So the image format is still unknown in Qt.
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #44 from caulier.gil...@gmail.com ---
Maik,
For AVIF, the registered image format in database is an empty string.
In fact this is a generic problem. If type mime is empty from QFileInfo, we
must do something at least, not to store an empty
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #43 from caulier.gil...@gmail.com ---
Oh, elementary Mr Watson (:-))
Digikam::ThumbnailCreator::createThumbnail: Trying to get thumbnail from
"/home/gilles/Images/4324477432.avif" ( "" )
The type mime returned from QFileInfo is empty...
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #42 from caulier.gil...@gmail.com ---
And now AVIF support on AppImage. Thumbnail work now...
https://i.imgur.com/JV3Dmoz.png
But the mime-type "AVIF" is not shown as thumb overlay...
Gilles
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #41 from caulier.gil...@gmail.com ---
Git commit 45fa6f27a17d762489821605fd8c47cf3f056a47 by Gilles Caulier.
Committed on 09/03/2022 at 14:03.
Pushed by cgilles into branch 'qt5-maintenance'.
Try to fix AVIF thumbnail extraction.
I suspect
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #40 from caulier.gil...@gmail.com ---
Git commit c4a373ecc34b5d0511b7f583e43da44115fb2849 by Gilles Caulier.
Committed on 09/03/2022 at 13:46.
Pushed by cgilles into branch 'qt5-maintenance'.
AVIF: preload library from the AppImage bundle.
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #39 from caulier.gil...@gmail.com ---
Git commit 1a34c9496c8f262ab88f78927de86a4d2c2d8486 by Gilles Caulier.
Committed on 09/03/2022 at 13:11.
Pushed by cgilles into branch 'qt5-maintenance'.
AVIF in AppImage: no needs dirty libaom touch
M
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #38 from caulier.gil...@gmail.com ---
libaom disapear from AVIF qt plugin :
[root@localhost tools (qt5-maintenance)]# ldd
/usr/plugins/imageformats/kimg_avif.so
linux-vdso.so.1 (0x7ffdeb1b2000)
libQt5Gui.so.5 =>
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #37 from caulier.gil...@gmail.com ---
Et voilà :
[ 0%] Creating directories for 'libaom'
[ 0%] Performing download step (git clone) for 'libaom'
Clonage dans 'libaom'...
HEAD est maintenant sur 87460cef8 Replace AOM_EXT_PART_ABI_VERSION
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #36 from caulier.gil...@gmail.com ---
Git commit dd75814d2dbefdf330d48599ae3446dda96387b6 by Gilles Caulier.
Committed on 09/03/2022 at 13:04.
Pushed by cgilles into branch 'qt5-maintenance'.
AppImage: build AOM static and AVIF as shared to
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #35 from caulier.gil...@gmail.com ---
yes, sure, the removed libaom.so.0 will certainly break ffmpeg, but, as this
lib is very old, i'm sure that loading AVIF file in ffmpeg will not work as
expected...
Rebuild ffmpeg instead to use linux
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #34 from dnovome...@gmail.com ---
(In reply to caulier.gilles from comment #32)
> An ideal solution was to build libavif with a static version of libaom...
>
> Gilles
This is how I build static version of libaom inside libavif:
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #33 from dnovome...@gmail.com ---
I don't know if such hack with deleting old libaom is OK. I am worried what
will happen when someone tries to play some movie with AV1 codec?
Wouldn't be better to rebuild ffmpeg so it will use the new
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #32 from caulier.gil...@gmail.com ---
An ideal solution was to build libavif with a static version of libaom...
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #31 from caulier.gil...@gmail.com ---
Git commit 349c15e545608403a406df47026a8a921cb74d31 by Gilles Caulier.
Committed on 09/03/2022 at 10:27.
Pushed by cgilles into branch 'qt5-maintenance'.
do not mix both libaom shared lib in the bundle
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #30 from caulier.gil...@gmail.com ---
If i remove libaom.so.0 from the bundle, of course it crash:
[gilles@localhost pipo]$ ./AppRun
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #29 from dnovome...@gmail.com ---
When I copied these 3 files from extracted appimage:
kimg_avif.so
libavif.so.13
libaom.so.3
the plugin worked fine in gwenview.
So it works outside appimage.
Are you willing to make an experiment?
Try to
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #28 from caulier.gil...@gmail.com ---
And yes, it's ffmpeg comming from the linux host which use the older AOM lib:
[root@localhost lib64]# ldd libavformat.so.58 | grep aom
libaom.so.0 => /lib64/libaom.so.0 (0x7fbbd0e42000)
So
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #27 from caulier.gil...@gmail.com ---
libavif from the bundle point also on the right libaom version :
[root@localhost lib64]# ldd libavif.so.13
linux-vdso.so.1 (0x7cff9000)
libaom.so.3 => /lib64/libaom.so.3
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #26 from caulier.gil...@gmail.com ---
yes, there are 2 libaom in the bundle. ldd help here :
[root@localhost imageformats]# ldd kimg_avif.so
linux-vdso.so.1 (0x7ffe3a9d4000)
libQt5Gui.so.5 => /lib/libQt5Gui.so.5
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #25 from dnovome...@gmail.com ---
I don't know the real cause but I observed that inside
digiKam-7.7.0-20220308T173410-x86-64.appimage there are two versions of libaom:
libaom.so.0 (this is probably very old version 1.0.0 used by
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #24 from caulier.gil...@gmail.com ---
Hi dnovomesky
So where is the problem under Linux AppImage. I'm lost...
How to turn on the qWarning() messages from KF5 framework. I tried all i know,
but nothing work...
Gilles
--
You are
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #23 from caulier.gil...@gmail.com ---
Compilation trace of KImageFormats for AppImage with AVIF support:
-- extracting...
src='/d/kimageformats-5.90.0.tar.xz'
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #22 from dnovome...@gmail.com ---
I tried
digiKam-7.7.0-20220308T170030-Win64-debug.exe
Opening and saving AVIF works, I just had to add avif into the list of
Additional image file extensions.
libyuv is indeed optional, it can accelerate
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #21 from caulier.gil...@gmail.com ---
compilation trace of libaom and libavif under Linux for AppImage :
[ 0%] Creating directories for 'libaom'
[ 0%] Performing download step (git clone) for 'libaom'
Clonage dans 'libaom'...
HEAD est
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #20 from caulier.gil...@gmail.com ---
AVIF support under MacOS : https://i.imgur.com/BMUti4B.png
All work as expected, expected the thumbnails, as under Windows
Gilles
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #19 from caulier.gil...@gmail.com ---
But... there are qwarning() in AVIF plugin from KImageFormats :
https://invent.kde.org/frameworks/kimageformats/-/blob/master/src/imageformats/avif.cpp#L423
So...
Gilles
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #18 from caulier.gil...@gmail.com ---
I turned on all KF5 framework debug spaces : no warning/error
I tried all to enable all Qt debug trace : nothing special...
Gilles
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #17 from caulier.gil...@gmail.com ---
For AppImage Linux, AVIF export from JPEG inside Image Editor do not work :
Digikam::EditorWindow::startingSaveAs: startSavingAs called
Digikam::EditorWindow::showFileSaveDialog: Writing file to
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #16 from caulier.gil...@gmail.com ---
Maik,
AVIF/AOM image thumbnail is broken, but preview work fine. I think it's due to
file format detection as video file
Gilles
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #15 from caulier.gil...@gmail.com ---
AVIF/AOM support under Windows : https://i.imgur.com/KhNhNLt.png
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #14 from caulier.gil...@gmail.com ---
@dnovomesky
All 7.7.0-pre-release bundles compile currently with AVIF/AOM support. They
will be available in few hours for testing at usual place.
Gilles
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #13 from caulier.gil...@gmail.com ---
Git commit 57b05919f7679e7ce4f5bc9437fbfebb33b0c928 by Gilles Caulier.
Committed on 08/03/2022 at 17:49.
Pushed by cgilles into branch 'master'.
AVIF support: sync with qt5-maintenance branch
M +2
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #12 from caulier.gil...@gmail.com ---
Git commit 8a40ecd93608acba9fdf553ec2c8d9b3d6921bf0 by Gilles Caulier.
Committed on 08/03/2022 at 17:42.
Pushed by cgilles into branch 'qt5-maintenance'.
AVIF supports under MacOS: install libaom with
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #11 from caulier.gil...@gmail.com ---
Git commit 59e7d811308acfac5f74a8b4988f77290920f206 by Gilles Caulier.
Committed on 08/03/2022 at 17:29.
Pushed by cgilles into branch 'qt5-maintenance'.
libavif for AppImage: inst ayasm and fix
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #10 from caulier.gil...@gmail.com ---
Git commit 2d9a589e74866b7574e4b90cdcd5d7b7c3c90952 by Gilles Caulier.
Committed on 08/03/2022 at 17:05.
Pushed by cgilles into branch 'qt5-maintenance'.
Add libaom dependency for AppImage
M +41 -2
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #9 from caulier.gil...@gmail.com ---
Git commit 82ef9588282ab4c0d9f9486cc7d7aa4580ef323a by Gilles Caulier.
Committed on 08/03/2022 at 16:57.
Pushed by cgilles into branch 'qt5-maintenance'.
add AVIF as supported type mime.
M +1-0
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #8 from caulier.gil...@gmail.com ---
Git commit 0d60eb0eb6edeb1b023facd81f5cfd3e08d9b914 by Gilles Caulier.
Committed on 08/03/2022 at 16:50.
Pushed by cgilles into branch 'qt5-maintenance'.
Fix compilation of libaom and libavif with MXE.
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #7 from caulier.gil...@gmail.com ---
Git commit dbb98ebb5857f34d0c1f17f1c90a6b54189b3d35 by Gilles Caulier.
Committed on 08/03/2022 at 16:30.
Pushed by cgilles into branch 'qt5-maintenance'.
add liaom deps under MXE
M +35 -3
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #6 from caulier.gil...@gmail.com ---
Perl must be available everywhere :
MXE (cross-compiling for Windows) -> it's a Linux host...
Macports -> MacOS VM -> ok
AppImage -> Linux of course
Snap CD -> Linux
FlatPak - Linux
Windows native CD ->
https://bugs.kde.org/show_bug.cgi?id=109060
--- Comment #5 from dnovome...@gmail.com ---
Some notes regarding libaom (AV1 decoder+encoder used by libavif):
It needs Perl to build.
For optimal performance on x86_64 platform it needs assembler nasm or yasm.
libaom can be built without assembler
https://bugs.kde.org/show_bug.cgi?id=109060
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|Add support to AVIF file|Add AVIF file format
49 matches
Mail list logo
