you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you donāt disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Iām having issues getting OpenCL to work with this version on MacOS 14.6.1.
With dt 5.2.1, OpenCL works just fine. However, I canāt get it to work with this build. I have already manually enabled it in the darktablerc file, but still no luck. Can anyone please give some advice?
you might run darktable from terminal /Volumes/darktable/darktable.app/Contents/MacOS/darktable -d opencl to get some debug infos regarding opencl to see if opencl kernels are properly built
@Antonio.guerreiro I had similar issues in the past when switching between release/custom builds.
Look inside the cache dir ~/.cache/darktable/, there should be a directory called cached_v5_kernels_..... Removing that directory and restarting DT solved it for me.
current master 5.3.0 (feature freeze) build + a couple of RF lensfun data from: Kameratrollet
also reverted pango library update to fix font selection dialog issue
keep in mind: the timeframe for testing, reporting and fixing issues for the 5.4 release is limited
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you donāt disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
current master 5.3.0 (feature freeze) build + a couple of RF lensfun data from: Kameratrollet
also reverted pango library update to fix font selection dialog issue
keep in mind: the timeframe for testing, reporting and fixing issues for the 5.4 release is limited
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you donāt disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
I noticed an issue with AGX presets.
After a few upgrades, I now run the latest darktable version from this topic.
I have severall presets for AGX. If I apply one of them, 1 or more other presets are also selected.
So I end up with multiple presets activated for 1 Agx module instance.
See attached screenshot.
Ok, thanks.
I will check.
But when ( as in the screenshot) 4 presets are selected and probably have the same parameter settings, does this mean that these parameter settings are applied 4 times ? i guess notā¦
current master 5.3.0 (feature freeze) build + a couple of RF lensfun data from: Kameratrollet
also reverted pango library update to fix font selection dialog issue
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you donāt disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you donāt disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you donāt disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you donāt disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "