No OpenCL anymore on Mac M1 Silicon??
I donāt think so, and that is appleās choice, nothing we can do about it.
No not what I mean to sayā¦ there is no OpenCL support in DT 4.0 on Mac M1. DT 3.8.1 does have OpenCL support on the same machine. It makes a huge difference.
Yes but apple has depreciated openCL despite it having originated from them. They want everyone to use Metal, which probably wonāt happen for DT.
Perhaps you need to empty your cached files.
If dt 3.8.x had it you might need to override dt assumptions. With latest opencl tuning dt enables opencl just if itās more performant then cpu. But maybe this calculation isnāt useable for m1. So please file an issue at Sign in to GitHub Ā· GitHub Since the developers are using Linux and never will detect issues arising from m1 macs.
I think this could be it as you say. I think if DT thinks your cou is 3x faster then it disabled Opencl by defaultā¦ if I recall???
current 4.0 branch + support for R3, R7, R10, opencl tuning prs and a couple of RF lensfun data from: Kameratrollet
[darktable-4.0.0+52~g5d1e49434]
(89.13 MB file on MEGA)
ā be aware thats not the official release ā
this build requires at least osx 10.15; donāt forget to backup ā¦
3 Likes
current 4.0.x branch + support for R3, R7, R10 and a couple of RF lensfun data from: Kameratrollet
darktable-4.0.0+88~gee1bc373c.dmg
this build requires at least osx 10.15; donāt forget to backup ā¦
leaving 4.0 for new features:
current master + new segmentation based highlight recovery (https://github.com/darktable-org/darktable/pull/12210) + support for R3, R7, R10 and a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+109~g0cc15a4c0.dmg
this build requires at least osx 10.15; donāt forget to backup ā¦
current master + new segmentation based highlight recovery (https://github.com/darktable-org/darktable/pull/12210 ) + support for R3, R7, R10 and a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+123~g408b36f6d.dmg
this build requires at least osx 10.15; donāt forget to backup ā¦
1 Like
current master + new segmentation based highlight recovery (https://github.com/darktable-org/darktable/pull/12210 ) + support for R3, R7, R10 and a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+140~g2abb826e6_x86_64.dmg
this build requires at least osx 10.15; donāt forget to backup ā¦
1 Like
current master + support for R3, R7, R10 and a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+180~gff1f3fa14_x86_64
latest commits: Pulse Ā· darktable-org/darktable Ā· GitHub
this build requires at least osx 10.15; donāt forget to backup ā¦
current master + a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+215~gab7e37433_x86_64.dmg
latest commits: Pulse Ā· darktable-org/darktable Ā· GitHub
this build requires at least osx 10.15; donāt forget to backup ā¦
current master + a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+236~g78747838c_x86_64.dmg
latest commits: Pulse Ā· darktable-org/darktable Ā· GitHub
this build requires at least osx 10.15; donāt forget to backup ā¦
current master + a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+283~g5cca9d64b_x86_64.dmg
latest commits: Pulse Ā· darktable-org/darktable Ā· GitHub
this build requires at least osx 10.15; donāt forget to backup ā¦
Hi, first issue in a long time. dt can load an image in fightable but crashes when trying to open the image (a test .nef) in darkroom. Same behaviour with or without openCL support. Here is the report:
Translated Report (Full Report Below)
Process: darktable [1293]
Path: /Applications/darktable.app/Contents/MacOS/darktable
Identifier: org.darktable
Version: 4.1.0 (4.1.0.283)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2022-09-03 14:19:34.1028 +0200
OS Version: macOS 12.5.1 (21G83)
Report Version: 12
Bridge OS Version: 6.6 (19P6066)
Anonymous UUID: 87497CFF-84A7-441C-8159-36B651EA99E8
Time Awake Since Boot: 6000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: UNKNOWN_0xD at 0x0000000000000000
Exception Codes: 0x000000000000000d, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1293]
VM Region Info: 0 is not in any region. Bytes before following region: 4477333504
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
ā>
__TEXT 10adeb000-10adfb000 [ 64K] r-x/r-x SM=COW ā¦cOS/darktable
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_platform.dylib 0x7ff80b684073 _platform_strcmp + 19
1 libtemperature.so 0x118643614 generate_preset_combo + 148 (temperature.c:684)
2 libtemperature.so 0x1186459d1 reload_defaults + 1521 (temperature.c:1510)
3 libdarktable.dylib 0x10b6493d9 dt_iop_reload_defaults + 57 (imageop.c:1163)
4 libdarkroom.so 0x118425178 enter + 696 (darkroom.c:3062)
5 libdarktable.dylib 0x10b71fb29 dt_view_manager_switch_by_view + 1657 (view.c:396)
6 libdarktable.dylib 0x10b6caa2e _event_button_press + 110 (thumbtable.c:1092)
7 libgtk-3.0.dylib 0x10c5b5e46 _gtk_marshal_BOOLEAN__BOXED + 97
8 libgobject-2.0.0.dylib 0x10bb739ea g_closure_invoke + 188
9 libgobject-2.0.0.dylib 0x10bb881b7 signal_emit_unlocked_R + 1476
10 libgobject-2.0.0.dylib 0x10bb88ece g_signal_emit_valist + 1927
11 libgobject-2.0.0.dylib 0x10bb8959c g_signal_emit + 120
12 libgtk-3.0.dylib 0x10c579b64 gtk_widget_event_internal + 253
13 libgtk-3.0.dylib 0x10c45ada6 propagate_event + 369
14 libgtk-3.0.dylib 0x10c45a233 gtk_main_do_event + 1077
15 libgdk-3.0.dylib 0x10b25d925 _gdk_event_emit + 49
16 libgdk-3.0.dylib 0x10b281793 gdk_event_dispatch + 50
17 libglib-2.0.0.dylib 0x10b32c88c g_main_context_dispatch + 257
18 libglib-2.0.0.dylib 0x10b32cb72 g_main_context_iterate + 431
19 libglib-2.0.0.dylib 0x10b32cdda g_main_loop_run + 250
20 libgtk-3.0.dylib 0x10c459cca gtk_main + 74
21 libdarktable.dylib 0x10b6e0d0a dt_gui_gtk_run + 202 (gtk.c:1275)
22 darktable 0x10adfaf4e main + 62 (main.c:94)
23 dyld 0x10e8a052e start + 462
Thread 1:: pool-spawner
0 libsystem_kernel.dylib 0x7ff80b6373ea __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x7ff80b671a6f _pthread_cond_wait + 1249
2 libglib-2.0.0.dylib 0x10b370c69 g_cond_wait + 37
3 libglib-2.0.0.dylib 0x10b302f04 g_async_queue_pop_intern_unlocked + 99
4 libglib-2.0.0.dylib 0x10b34fa47 g_thread_pool_spawn_thread + 117
5 libglib-2.0.0.dylib 0x10b34f59a g_thread_proxy + 66
6 libsystem_pthread.dylib 0x7ff80b6714e1 _pthread_start + 125
7 libsystem_pthread.dylib 0x7ff80b66cf6b thread_start + 15
ā¦
you might run dt from terminal with lldb (if you have Xcode or Xcode commandline tools installed) to see where it exactly crashes.
Thank you for the feedback. I donāt have Xcode installed on this Mac. I went back to the backup +236 which is running very well. I will do some more work with the new build and report if I find something.
current master + a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+333~g86e5cb04d_x86_64.dmg
latest commits: Pulse Ā· darktable-org/darktable Ā· GitHub
this build requires at least osx 10.15; donāt forget to backup ā¦
New build behaves as +283, crashes when trying to open an image in darkroom (same message as before āTermination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11ā Is it working on your Mac?