current OSX Build

Rajkhand · July 19, 2024, 10:30am

Found that my secondary SSD had some permission issues. In Get Info of the disk I gave all the read write permissions but the problem was not solved, but only after checking the Ignore ownership of this volume the problem was solved. This box is not there in my other attached drive!

MStraeten · August 11, 2024, 11:01am

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+268~g623415e310_arm64.dmg (macOS >= 11.0)
darktable-4.9.0+268~g623415e310_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: [Comparing release-4.8.0…darktable-4.8.x · darktable-org/darktable · GitHub ](Comparing release-4.8.1...master · darktable-org/darktable · GitHub)

MStraeten · August 24, 2024, 7:46pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+293~g9c5316789c_arm64.dmg (macOS >= 11.0)
darktable-4.9.0+293~g9c5316789c_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: [Comparing release-4.8.0…darktable-4.8.x · darktable-org/darktable · GitHub ](Comparing release-4.8.1…master · darktable-org/darktable · GitHub )

MStraeten · September 8, 2024, 7:35pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+478~g9cd57bdc9d_arm64.dmg (macOS >= 11.0)
darktable-4.9.0+478~g9cd57bdc9d_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · September 14, 2024, 12:45pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+501~g02a5e6b2f3_arm64.dmg (macOS >= 11.0)
darktable-4.9.0+501~g02a5e6b2f3_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · September 21, 2024, 4:27pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+549~g0f5bd178e3_arm64.dmg (macOS >= 11.0)
darktable-4.9.0+549~g0f5bd178e3_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · September 28, 2024, 9:55am

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+588~g5048954e9b_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+588~g5048954e9b_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · October 5, 2024, 11:19am

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+698~g413253f29e_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+698~g413253f29e_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · October 12, 2024, 3:50pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+806~g4efdb84a83_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+806~g4efdb84a83_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

paperdigits · October 12, 2024, 4:00pm

@MStraeten for the lens profiles from Kameratrollete, how are you integrating those? Just copying the XML in?

MStraeten · October 12, 2024, 8:38pm

I merged them into a local copy of the lensfun database if there were no ‚official‘ correction. After lensfun-update-data i check the official list for changes and then update the xml files in my local database…

MStraeten · October 19, 2024, 6:39pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+891~gfa7de9bd45_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+891~gfa7de9bd45_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · October 26, 2024, 11:59am

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+925~gb7288e18b2_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+925~gb7288e18b2_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

Johan_Beeckaert · October 29, 2024, 10:32am

Some strange behavior when using multiple instances of the same module. When using another instance of the for example the exposure module (creating a vignet) makes the module jump at the top of the pixel pipeline. You can drag it in the correct place, but I think this is no normal behavior ?

nwinspeare · October 29, 2024, 12:00pm

I noticed the same behaviour. It started with the previous build to my knowledge. I hadn’t caught on to the fact it was a new instance of a module but you are quite right. I isn’t systematic, I need to test more but the exposure module seems particularly prone to this.

MStraeten · October 29, 2024, 12:36pm

feel free to report an issue at Sign in to GitHub · GitHub

MStraeten · November 2, 2024, 12:49pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+971~gbf01ac5dee_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+971~gbf01ac5dee_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · November 9, 2024, 6:05pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+1048~g0739a92dea_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+1048~g0739a92dea_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

MStraeten · November 16, 2024, 12:52pm

current 4.9 build + a couple of RF lensfun data from: Kameratrollet

darktable-4.9.0+1116~g42b588cb8f_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+1116~g42b588cb8f_x86_64.dmg (macOS >= 10.14)

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> "

Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md

difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub

Rajkhand · November 18, 2024, 12:28pm

I have recently bought a new Mac mini M4 base model.

My collection is date based and and are very small like max is around 30 pics in one folder but on an average <=15.
When I click on any collection the thumbnails are regenerated all the times and even for 10-15 images it takes few seconds. In the same session I can go to some other collection and come back and it will not regenerate but after exiting Darktable and again opening it will again regenerate the thumbnails.

DT 4.9.0+1048

What I am doing wrong? What setting in the RC file will stop this behaviour ?