Thanks for updating the builds so regularly. Usually, I have no problems but this time I can’t run openCL.
I did a darktable -d opencl and got this output. It shows that the device is detected but dt still can’t implement OpenCL.
/Applications/darktable.app/Contents/MacOS/darktable -d opencl
0,2916 [opencl_init] opencl disabled via darktable preferences
0,2916 [opencl_init] opencl library '/System/Library/Frameworks/OpenCL.framework/Versions/Current/OpenCL' found on your system and loaded, preference 'default path'
0,2916 [opencl_init] found 1 platform
[opencl_init] found 1 device
[dt_opencl_device_init]
DEVICE: 0: 'Apple M4 Pro'
CONF KEY: cldevice_v5_appleapplem4pro
PLATFORM, VENDOR & ID: Apple, Apple, ID=16940800
CANONICAL NAME: appleapplem4pro
DRIVER VERSION: 1.2 1.0
DEVICE VERSION: OpenCL 1.2
DEVICE_TYPE: GPU, unified mem
GLOBAL MEM SIZE: 36864 MB
MAX MEM ALLOC: 6912 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
AVOID ATOMICS: NO
MICRO NAP: 250
ROUNDUP WIDTH & HEIGHT 16x16
CHECK EVENT HANDLES: 128
TILING ADVANTAGE: 0,000
DEFAULT DEVICE: NO
KERNEL BUILD DIRECTORY: /Applications/darktable.app/Contents/Resources/share/darktable/kernels
KERNEL DIRECTORY: /Users/nick/.cache/darktable/cached_v5_kernels_for_AppleAppleM4Pro_1210
CL COMPILER OPTION: -cl-fast-relaxed-math
CL COMPILER COMMAND: -w -cl-fast-relaxed-math -DAPPLE=1 -I/Applications/darktable.app/Contents/Resources/share/darktable/kernels
UNSUPPORTED (log once): buildComputeProgram: cl2Metal failed
0,3227 [opencl_build_program] could not build program: CL_BUILD_PROGRAM_FAILURE
0,3227 [dt_opencl_device_init] failed to compile program `demosaic_ppg.cl'!
[opencl_init] no suitable devices found.
0,3227 [opencl_init] FINALLY: opencl PREFERENCE=OFF is NOT AVAILABLE and NOT ENABLED.
I usually erase the device lines in darktablerc and let dt rebuild but this time no luck. Would anyone have an idea what is happening please?
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> "
Can you please shed light on the AgX module? Does it replaces an existing module? A brief note on how to use it. I have never used Blender so have absolutely no idea how to use this.
Thanks
this thread isn’t intended to be a general discussion topic for new stuff - just a place to find development builds for older macOS configs. Use the links to get information …
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> "
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> "
Is there an idiots guide to running this (via terminal?) without messing up the current 5.2.1 as I don’t understand whether this installs or runs as a stand alone app?
I would like to try Agx, but know bugger all about using command lines to run things
Or should an idiot like me not tinker and wait for the Dec release?
just open the dmg (darktable doesn’t come with an installer) and then type the second command (that with a user defined configdir)
By default darktable uses $HOME/.config/darktable as a config dir and so you might mess up the config + librariy files of your existing darktable 5.2.1 if you don’t give a different directory.
Stepping up to newer darktable versions isn’t an issue (darktable converts what needs to be converted) but there’s no way back except using a backup…
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> "
Thank you for the build. Is working in iMac intel with an issue that was reported previously in gitHub. The preference window is block, once opening it shows the left side panels and a blank right side and nothing can be done on it. Using the previous .conf from the last version that was working as expected in OS 15.6.1 (+333) the preferences seems to be read and apply, so it can be used until the issue is solved.
Anyway, thank you again for the build.
Thank you @zurdo for your post. I reported the issue . I started to wonder if it was an issue with my setup. I could not even download the newer Nightly to test because not longer available for our x86 osx. My approach was to manually edit darkablerc file or edit it thru other versions and copy.
