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

Tone EQ cursor lagging on current Windows nightly #15252

Closed
sg456 opened this issue Sep 16, 2023 · 2 comments
Closed

Tone EQ cursor lagging on current Windows nightly #15252

sg456 opened this issue Sep 16, 2023 · 2 comments

Comments

@sg456
Copy link

sg456 commented Sep 16, 2023

Describe the bug

When the tone EQ module is open and active, the cursor (the tone eq 'picker') becomes slow and jerky while over the image, but only when the image preview is smaller than 'fit screen'. For example when the color assessment mode is active, or when the preview size is set to 'small' in the dropdown list.

Not sure what kind of log would be relevant.

Steps to reproduce

Open a raw image (.nef).
Enable tone eq.
enable ISO 12646 color assessment mode
move cursor over image area.
cursor becomes slow and laggy.

Expected behavior

No response

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you install darktable from?

darktable.org

darktable version

4.5.0+613~gfad5e60412 but present at least back to 4.5.0+512

What OS are you using?

Windows

What is the version of your OS?

Win 11 Pro 21H2 build 22000.2416

Describe your system?

OpenCL active on GTX1650 4GB. Issue seems still present with OpenCL off, however only at the 'small' zoom level, not fill with ISO 12646 mode on.

2560x1440 monitor

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

GTX1650 Nvidia Studio driver 527.56

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

No response

@sg456
Copy link
Author

sg456 commented Sep 16, 2023

@sg456
Copy link
Author

sg456 commented Sep 16, 2023

Problem solved... I only discovered in writing the issue that my Nvidia driver was out of date. Updated, restarted, and kernels deleted, problem seems to be solved. Sorry about the noise!

@sg456 sg456 closed this as completed Sep 16, 2023
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

1 participant