Comments (4)
What's the output of darktable-cltest within the flatpak environment?
from darktable.
Running darktable-cltest
, I get the following -
darktable 4.6.0
Copyright (C) 2012-2023 Johannes Hanika and other contributors.
Compile options:
Bit depth -> 64 bit
Debug -> DISABLED
SSE2 optimizations -> ENABLED
OpenMP -> ENABLED
OpenCL -> ENABLED
Lua -> ENABLED - API version 9.2.0
Colord -> ENABLED
gPhoto2 -> ENABLED
GMIC -> ENABLED - Compressed LUTs are supported
GraphicsMagick -> ENABLED
ImageMagick -> DISABLED
libavif -> DISABLED
libheif -> DISABLED
libjxl -> DISABLED
OpenJPEG -> ENABLED
OpenEXR -> ENABLED
WebP -> ENABLED
See https://www.darktable.org/resources/ for detailed documentation.
See https://github.com/darktable-org/darktable/issues/new/choose to report bugs.
0.0217 [dt_get_sysresource_level] switched to 1 as `default'
0.0217 total mem: 15832MB
0.0217 mipmap cache: 1979MB
0.0217 available mem: 7916MB
0.0217 singlebuff: 123MB
0.0501 [opencl_init] opencl library 'libOpenCL' found on your system and loaded, preference 'default path'
0.9430 [opencl_init] found 4 platforms
0.9431 [check platform] platform 'Intel(R) FPGA Emulation Platform for OpenCL(TM)' with key 'clplatform_intelrfpgaemulationplatformforopencltm' is NOT active
0.9431 [check platform] platform 'Intel(R) OpenCL' with key 'clplatform_intelropencl' is NOT active
[opencl_init] found 2 devices
[dt_opencl_device_init]
DEVICE: 0: 'Intel(R) UHD Graphics 630'
PLATFORM, VENDOR & ID: Intel(R) OpenCL Graphics, Intel(R) Corporation, ID=32902
CANONICAL NAME: intelropenclgraphicsintelruhdgraphics630
DRIVER VERSION: 23.35.27191.42
DEVICE VERSION: OpenCL 3.0 NEO
DEVICE_TYPE: GPU, unified mem
GLOBAL MEM SIZE: 12666 MB
MAX MEM ALLOC: 4096 MB
MAX IMAGE SIZE: 16384 x 16384
MAX WORK GROUP SIZE: 256
MAX WORK ITEM DIMENSIONS: 3
MAX WORK ITEM SIZES: [ 256 256 256 ]
ASYNC PIXELPIPE: NO
PINNED MEMORY TRANSFER: NO
USE HEADROOM: 600Mb
AVOID ATOMICS: NO
MICRO NAP: 250
ROUNDUP WIDTH & HEIGHT 16x16
CHECK EVENT HANDLES: 128
TILING ADVANTAGE: 0.000
DEFAULT DEVICE: NO
KERNEL BUILD DIRECTORY: /usr/share/darktable/kernels
KERNEL DIRECTORY: /home/atharva/.cache/darktable/cached_v3_kernels_for_IntelROpenCLGraphicsIntelRUHDGraphics630_23352719142
CL COMPILER OPTION:
CL COMPILER COMMAND: -w -DINTEL=1 -I"/usr/share/darktable/kernels"
KERNEL LOADING TIME: 0.0196 sec
[dt_opencl_device_init]
DEVICE: 1: 'NVIDIA GeForce RTX 2070'
PLATFORM, VENDOR & ID: NVIDIA CUDA, NVIDIA Corporation, ID=4318
CANONICAL NAME: nvidiacudanvidiageforcertx2070
DRIVER VERSION: 545.23.08
DEVICE VERSION: OpenCL 3.0 CUDA, SM_20 SUPPORT
DEVICE_TYPE: GPU, dedicated mem
GLOBAL MEM SIZE: 7974 MB
MAX MEM ALLOC: 1994 MB
MAX IMAGE SIZE: 32768 x 32768
MAX WORK GROUP SIZE: 1024
MAX WORK ITEM DIMENSIONS: 3
MAX WORK ITEM SIZES: [ 1024 1024 64 ]
ASYNC PIXELPIPE: NO
PINNED MEMORY TRANSFER: NO
USE HEADROOM: 600Mb
AVOID ATOMICS: NO
MICRO NAP: 250
ROUNDUP WIDTH & HEIGHT 16x16
CHECK EVENT HANDLES: 128
TILING ADVANTAGE: 0.000
DEFAULT DEVICE: NO
KERNEL BUILD DIRECTORY: /usr/share/darktable/kernels
KERNEL DIRECTORY: /home/atharva/.cache/darktable/cached_v3_kernels_for_NVIDIACUDANVIDIAGeForceRTX2070_5452308
CL COMPILER OPTION: -cl-fast-relaxed-math
CL COMPILER COMMAND: -w -cl-fast-relaxed-math -DNVIDIA_SM_20=1 -DNVIDIA=1 -I"/usr/share/darktable/kernels"
KERNEL LOADING TIME: 0.0234 sec
[opencl_init] OpenCL successfully initialized. internal numbers and names of available devices:
[opencl_init] 0 'Intel(R) OpenCL Graphics Intel(R) UHD Graphics 630'
[opencl_init] 1 'NVIDIA CUDA NVIDIA GeForce RTX 2070'
1.0738 [opencl_init] FINALLY: opencl is AVAILABLE and ENABLED.
[opencl_init] opencl_scheduling_profile: 'very fast GPU'
[opencl_init] opencl_device_priority: '*/!0,*/*/*/!0,*'
[opencl_init] opencl_mandatory_timeout: 400
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[dt_opencl_update_priorities] 1 1 1 1 1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 1 1 1 1 1
[opencl_synchronization_timeout] synchronization timeout set to 0
UNIFIED MEM SIZE: 3958 MB reserved for 'intelropenclgraphicsintelruhdgraphics630'
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[dt_opencl_update_priorities] 1 1 1 1 1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 1 1 1 1 1
[opencl_synchronization_timeout] synchronization timeout set to 0
from darktable.
The kernel paths point to a non-flatpak location. Are you sure this is a flatpak installation? Not related to your issue, but I would disable the Intel iGPU on your dt processing settings.
Normally you will need a command line like this: flatpak run org.darktable.Darktable -d all
from darktable.
Lemme get Back to you about the flatpak stuff
Why should I avoid the iGPU though?
from darktable.
Related Issues (20)
- 1:1 crop is not a square when exported
- Zjednodušení použití nastavení pomocí "Datacolor Spyder Checkr" HOT 3
- segfault when creating a style from history HOT 5
- Addition to $(VERSION_IF_MULTI) HOT 4
- [Bug] No GPU leads to OpenCL always trying to start HOT 4
- SegFault when opening CR2 from Canon Rebel XT HOT 29
- git pull for current master broken HOT 2
- How to enable OpenCl with Intel Arc A770 HOT 16
- BUG: the line to change image rotation using rotate & perspective module is not visible HOT 6
- latest Master compiling error: "unknown type name ‘bool’" HOT 13
- function dt_history_hash_read() takes a full second despite speedy HDD HOT 14
- Sharpen module based on wavelet decomposition HOT 6
- Problem with the "brightness " slider in the new "Color Equalizer" module HOT 11
- Panasonic DC-S5M2 HOT 1
- Suppport to Nikon Z8 camera HOT 2
- Auto-apply pixel workflow defaults (Sigmoid) HOT 2
- X-Touch midi controller: darktable appears to use the wrong channel to write to the controller in its default factory configuration HOT 7
- iPhone 14 Pro HOT 5
- Nokia 9 PureView HOT 5
- iPhone 11 - Simple RAW Crash HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from darktable.