[digiKam-users] Slow raw processing
Locked
[digiKam-users] Slow raw processing
 
|
Hi,
i'm using digikam since years and are more and more using it for everything. However opening a raw file is very slow compared to other raw processors maybe because it uses only one core. I have a Intel Core i5 desktop with on-board graphics and Manjaro Linux. Would a dedicated GPU make a difference (for raw processing, i'm not using face detection)? If so, any recommendations? HP -- --------- 8< ------------- Why taunt me? Why upbraid me? I am merely a genius, not a god. (Nero Wolfe) Meine Bilder: http://jalbum.net/a/1456383 Berge: http://jalbum.net/de/browse/user/album/1823943 |
|
|
On Thu, 5 Nov 2020 18:40:49 +0100
Hans-Peter Huth <[hidden email]> wrote: > Hi, > > i'm using digikam since years and are more and more using it for > everything. However opening a raw file is very slow compared to > other raw processors maybe because it uses only one core. I have a > Intel Core i5 desktop with on-board graphics and Manjaro Linux. > Would a dedicated GPU make a difference (for raw processing, i'm > not using face detection)? If so, any recommendations? I asked the same question a couple years ago and was told that there was nothing specific optimized for GPUs like darktable/opencl. But since I was using KDE (and still do) also on Manjaro, qt should realize that I have an radeon amdgpu, it should speedup things.... -- sknahT vyS |
|
|
Hi,
Raw processing is delegate in digiKam to libraw (https://www.libraw.org) Libraw does not use video cards acceleration for compatibility and stability purposes, but uses openmp to parallelize demosaicing computation. openmp support is optional in libraw. If your digiKam is not compiled with openmp dependency, demosaicing will be processed on one core. Check in Help/Components Info dialog in digiKam if openmp support is enabled. Note: if you want to see libraw to support OpenCL and Co for video card acceleration support, please report this wish on libraw github project. Best Gilles Caulier Le jeu. 5 nov. 2020 à 20:21, <[hidden email]> a écrit : > > On Thu, 5 Nov 2020 18:40:49 +0100 > Hans-Peter Huth <[hidden email]> wrote: > > > Hi, > > > > i'm using digikam since years and are more and more using it for > > everything. However opening a raw file is very slow compared to > > other raw processors maybe because it uses only one core. I have a > > Intel Core i5 desktop with on-board graphics and Manjaro Linux. > > Would a dedicated GPU make a difference (for raw processing, i'm > > not using face detection)? If so, any recommendations? > > I asked the same question a couple years ago and was told that there > was nothing specific optimized for GPUs like darktable/opencl. > > But since I was using KDE (and still do) also on Manjaro, qt should > realize that I have an radeon amdgpu, it should speedup things.... > > -- > sknahT > > vyS |
|
|
On Fri, 6 Nov 2020 10:15:22 +0100
Gilles Caulier <[hidden email]> wrote: > Hi, > > Raw processing is delegate in digiKam to libraw (https://www.libraw.org) > > Libraw does not use video cards acceleration for compatibility and > stability purposes, but uses openmp to parallelize demosaicing > computation. > > openmp support is optional in libraw. If your digiKam is not compiled > with openmp dependency, demosaicing will be processed on one core. > > Check in Help/Components Info dialog in digiKam if openmp support is > enabled. > digikam says: digikam version 7.1.0 CPU cores: 4 Eigen: 3.3.8 Exiv2: 0.27.3 Exiv2 supports XMP metadata: Yes HEIF encoding support: Yes ImageMagick codecs: 7.0.10 KF5: 5.75.0 LensFun: 0.3.95-0 LibCImg: 130 LibJPEG: 80 LibJasper: 2.0.19 LibLCMS: 2100 LibLqr support: Yes LibPGF: 7.19.03 LibPNG: 1.6.37 LibRaw: 0.20.0 LibTIFF: 4.1.0 Marble: 0.27.20 Parallelized demosaicing: Yes Qt: 5.15.1 Qt WebEngine support: Yes Rajce support: Yes VKontakte support: No AkonadiContact support: Yes Baloo support: Yes Calendar support: Yes DBus support: Yes Database backend: QSQLITE HTML Gallery support: Yes LibAVCodec: 58.91.100 LibAVFormat: 58.45.100 LibAVUtil: 56.51.100 LibGphoto2: 2.5.26 LibOpenCV: 4.5.0 LibQtAV: 1.13.0 Media player support: Yes Panorama support: Yes No OpenMP in the component info? But 'Parallelized demosaicing' and OpenCL support are there. Is this something i should report to the packager? I can't crosscheck with the digikam-7.1.0-x86-64.appimage (and one older appimmage) because it does not start ("unknown: Could not initialize GLX") HP -- --------- 8< ------------- Why taunt me? Why upbraid me? I am merely a genius, not a god. (Nero Wolfe) Meine Bilder: http://jalbum.net/a/1456383 Berge: http://jalbum.net/de/browse/user/album/1823943 |
|
|
yes OpenMp is supported :Parallelized demosaicing: Yes
Try 7.2.0 beta2 appImage : https://files.kde.org/digikam/ Best Gilles Caulier Le ven. 6 nov. 2020 à 12:14, Hans-Peter Huth <[hidden email]> a écrit : > > On Fri, 6 Nov 2020 10:15:22 +0100 > Gilles Caulier <[hidden email]> > wrote: > > > Hi, > > > > Raw processing is delegate in digiKam to libraw (https://www.libraw.org) > > > > Libraw does not use video cards acceleration for compatibility and > > stability purposes, but uses openmp to parallelize demosaicing > > computation. > > > > openmp support is optional in libraw. If your digiKam is not compiled > > with openmp dependency, demosaicing will be processed on one core. > > > > Check in Help/Components Info dialog in digiKam if openmp support is > > enabled. > > > > digikam says: > > digikam version 7.1.0 > CPU cores: 4 > Eigen: 3.3.8 > Exiv2: 0.27.3 > Exiv2 supports XMP metadata: Yes > HEIF encoding support: Yes > ImageMagick codecs: 7.0.10 > KF5: 5.75.0 > LensFun: 0.3.95-0 > LibCImg: 130 > LibJPEG: 80 > LibJasper: 2.0.19 > LibLCMS: 2100 > LibLqr support: Yes > LibPGF: 7.19.03 > LibPNG: 1.6.37 > LibRaw: 0.20.0 > LibTIFF: 4.1.0 > Marble: 0.27.20 > Parallelized demosaicing: Yes > Qt: 5.15.1 > Qt WebEngine support: Yes > Rajce support: Yes > VKontakte support: No > AkonadiContact support: Yes > Baloo support: Yes > Calendar support: Yes > DBus support: Yes > Database backend: QSQLITE > HTML Gallery support: Yes > LibAVCodec: 58.91.100 > LibAVFormat: 58.45.100 > LibAVUtil: 56.51.100 > LibGphoto2: 2.5.26 > LibOpenCV: 4.5.0 > LibQtAV: 1.13.0 > Media player support: Yes > Panorama support: Yes > > No OpenMP in the component info? But 'Parallelized demosaicing' and OpenCL > support are there. Is this something i should report to the packager? > > I can't crosscheck with the digikam-7.1.0-x86-64.appimage (and one > older appimmage) because it does not start ("unknown: Could not initialize > GLX") > > HP > > -- > --------- 8< ------------- > Why taunt me? Why upbraid me? I am merely a genius, not a god. > (Nero Wolfe) > Meine Bilder: http://jalbum.net/a/1456383 > Berge: http://jalbum.net/de/browse/user/album/1823943 > > |
|
|
If I remember correctly, we deactivated threads in libraw because Nikon NEF files were incorrectly decoded. We can of course test whether the problem has now been fixed in libraw. Maik Am Fr., 6. Nov. 2020 um 13:57 Uhr schrieb Gilles Caulier <[hidden email]>: yes OpenMp is supported :Parallelized demosaicing: Yes |
|
|
In reply to this post by Gilles Caulier-4
On Fri, 6 Nov 2020 13:56:53 +0100
Gilles Caulier <[hidden email]> wrote: > yes OpenMp is supported :Parallelized demosaicing: Yes > > Try 7.2.0 beta2 appImage : > > https://files.kde.org/digikam/ > does not start on my Manjaro: $ ./digikam-7.2.0-beta1-20201025T153726-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/tmp/.mount_digikalfibT9/usr/lib64/libxcb-dri3.so.0 unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) unknown: Could not initialize GLX /tmp/.mount_digikalfibT9/AppRun: Zeile 166: 2207 Abgebrochen (Speicherabzug geschrieben) digikam $@ HP -- --------- 8< ------------- Why taunt me? Why upbraid me? I am merely a genius, not a god. (Nero Wolfe) Meine Bilder: http://jalbum.net/a/1456383 Berge: http://jalbum.net/de/browse/user/album/1823943 |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |