Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Module presets not being applied #18282

Open
1 task done
kevbradwick opened this issue Jan 24, 2025 · 4 comments
Open
1 task done

Module presets not being applied #18282

kevbradwick opened this issue Jan 24, 2025 · 4 comments

Comments

@kevbradwick
Copy link

kevbradwick commented Jan 24, 2025

Is there an existing issue for this?

  • I checked and did not find my issue in the already reported ones

Describe the bug

Using Darktable 5.0.0 on macOS 15.1.1, it appears that selecting module presets are not applying values after selection. Here are some screen recordings to demonstrate.

Screen.Recording.2025-01-24.at.16.33.44.mov
Screen.Recording.2025-01-24.at.16.34.43.mov

Steps to reproduce

  1. Go to any module
  2. Apply a preset

or

  1. Make some adjustments to a module
  2. Save a preset
  3. Apply the preset

Expected behavior

Apply default and saved user presets

Logfile | Screenshot | Screencast

No log entries are printed using -d common or -d opencl or -d all.

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

5.0.0

What OS are you using?

Mac

What is the version of your OS?

15.1.1

Describe your system?

Mac Mini M4 Pro, 48 GB Ram

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

M4 Pro

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

@siamak01
Copy link

I have same issue with my IMac 3.8 HHZ 8-Core Intel Core i7
name of preset are available to use in hamburger icon but it seem none does change any of the sliders!

@clnhlzmn
Copy link

clnhlzmn commented Feb 7, 2025

I have a similar problem but the weird thing is it just started happening and as far as I know nothing has changed. I'm on DT 5.0.0 and macOS 12.7.6 (I realize this means I'm in the wild west). I've been on 5.0.0 for a little bit now and I haven't had this problem until today.

I even went back to some older edits I made where I know for a fact I successfully applied presets, reset the module (color balance rgb in this case), and tried to apply the same preset again only to find that it wouldn't work.

Edit: rebooted and now it works 🤷

@siamak01
Copy link

siamak01 commented Feb 8, 2025

My problem also was fixed. I did number things and I am not sure what did fixed it. I even did reinstalled the DT and did not fixed it. I also deleted all xmp files and that may have helped fixing it, I do not know. I was also tinkering with OpenCL. I think is a cache memory corruption issue and rebooting the computer may clear and fix it before taking any other steps. Interesting enough is that around this time OSX did wanted to update. Part of that update is the reboots and restart. So essintially the update may also fix DT due to its reboot/restart step

@ptilopteri
Copy link

ptilopteri commented Feb 8, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants