The processing and module ui code are fairly intermingled, I don’t think it is really worth the time.
Hello,
I have recently been having a problem with my X-Touch MIDI controller.
For example, when I want to slightly increase the exposure, the slider goes straight to the maximum, and then I can normally reduce and increase it to adjust the exposure.
I suspect there is a problem with the horizontal sliders when used with a shortcut.
https://github.com/darktable-org/darktable/issues/19587
Have a nice day,
Christian
1 Like
There was some fixes done to support Wayland. At this point we feel that Darktable is usable under Wayland.
If you still are using X11 you can test the following points to ensure there is no regressions introduced:
- The preset and style dialog keep their geometry (same width / height) when called multiple time and if resized the next time it is opened it has the new size.
- The tagging using Ctrl+T on lighttable is working. The mini entry opens, you can type in a tag and the completion (inline in the entry) and the popup dialog is working too.
TIA.
3 Likes
Do I have to do anything special to launch dt under Wayland?
No, nothing special. Launch dt as usual.
Alright. Then I am probably running dt for one year under wayland without any issues so far EXCEPT: When using d&s and switching from “high quality processing” to regular preview before the image has finished rendering it crashes. I have not yet been able to consistently reproduce this issue though.
Not really, it was probably Xwayland which has been removed as default since Nov 2nd. So since this date we target Wayland by default and to run under Xwayland one as to use GDK_BACKEND=x11.
Again starting darktable as usual since Nov 2nd as now changed to Wayland and that’s what we want to be tested.
1 Like
Running Darktable-5.3.0+805.gb982017164 still launches into X11 (at least kwin debug console lists it as X11). Both when launching via the .desktop gearlever creates for me (which does not include GDK_BACKEND=x11) and by directly launching the appimage.
I’m using X11, I’ll try to test (DT 5.3.0-788)
- what do you mean with preset and style dialog? Edit preset dialog (triggered in lighttable) and edit preset (triggered in the darkroom, from module itself)?
- tagging using Crlt+T is working, I see mini entry, I type a new tag, the tag is created and attached to the selected items. What popup dialog do you mean? How to trigger it exactly?
The popup which opens on top of the entry where you type the tag. This popup displays the matches.
Yes both.
Tested with X11, working ok with DT 5.3.0-809
1 Like
There might be a problem, related to DT on X11.
I minimize DT and when I click again on the icon it is not restored (I don’t see this issue with other applications).
To restore it I need to hold the mouse over the icon and click on the preview:
And do you see this same behavior with 5.2.1 or is it new?
I’ve just tested also 5.2.1, behaves as expected.
Anyway, this issue is in 5.3.0 pretty new, I would look in the last 1-2-weeks changes.
1 Like
Yes probably related to the work for Wayland hence my request to test on X11. Can you open an issue here: GitHub · Where software is built
We’ll see if we can find the regression. TIA.
I found something that is not really a ‘bug’ since its working as intended, but could use a ‘ignore camera’ option somewhere. At least there is a simple workaround.
I am using a Fringer adapter to mount Canon EF lenses on a Nikon Z camera. Works perfectly with great results. However…
The ‘lens correction’ module detects my Nikon and subsequently hides every other lens that does not work on the Nikon…logical. The exif contains
"Exif.Photo.LensSpecification":"170/10 400/10 400/100 400/100",
"Exif.Photo.LensMake":"",
"Exif.Photo.LensModel":"VR 17-40mm f/4G",
"Exif.Photo.LensSerialNumber":"",
as per exiftool extraction.
my workaround: I select the Canon R6ii (also 24 MP) in the ‘lens correction’ module and then I can select the proper Canon lens, in my case the 17-40 f/4 which needs some corrections, especially at 17mm. The corrections are then applied to the image 
Q: does this influence any other part of the pipeline? or just the lens correction module? (i can live with that btw, but it probably is also the case with megadap, viltrox and other obscure Chinese adapters, for other brand mixes as well.)
This is not a bug. Ideally, you should provide the images or data to lensfun so the correction matches your camera/lens configuration.
Of course I’m aware it is not a bug. I don’t thing we should go down the road of submitting every possible foreign lens + adapter combination. Lensfun would explode.
I think my workaround is pretty workable because if you use such an adapter, you already are aware and on special terrain anyway
But my question is: does changing the cam in lens correction influence other modules in the workflow? My guess is not. Just a guess though