hm i can probably add that too. it’s really a gamepad menu: hold left shoulder and select with right stick. the mouse was just added in hindsight. you can then confirm (x) or abort/revert (o) i think without gamepad it’s enter and escape.
i suppose you’d want right click to confirm?
btw what’s in the menu is the “favourites”, so you can configure it (right click on some of the ui elements, or edit ~/.config/vkdt/darkroom.ui to taste)
That would make more sense for mouse and keyboard.
pushed.
just a small note, my kingfisher image has a CC-BY-SA licence, not CC0
Congrats on your release.
I doubt this is a bug, but one of the things that prevents me from going further with vkdt is the zones module. It seems like the bottom zones apply only to the brightest highlights, while the top zone applies to more or less the whole image, whereas what I would expect is for the top zone to apply only to the shadows. Therefore, for mid tones and shadows, I find it quite difficult to specify the tonal range that the adjustments will be limited to. In all probability I just don’t know how to use the tool correctly, so for that tutorials would certainly help.
Also, the epsilon default seems too small, often giving harsh edge transitions.
oh, thanks for the hint 
added attribution. always let me know if you find the use inappropriate.
It’s fine. Thanks! Image taken from here Show me how you denoise the denoise plugin thread also does not have attribution unfortunately so I understand why one might not give it.
i’d like to say this is how it happened but probably i’m just sloppy i took this as a comparison to the rawnind/neural denoise algorithm because that yielded really good results on it. and since i need to re-train this network to match my glsl implementation this seemed like a great benchmark. so much good detail on the feathers and nice sharp edges on the beak to be recovered, and all the soft bokeh!
not sure i understand exactly what you mean. are you using the zones in scene or display referred? this thing works best in display referred, i.e. after the film curve. lower dynamic range somehow makes the transitions softer and also it appears to be easier to slice the tonal range into perceptually equal pieces.
there is the gamma parameter to fine tune how the slicing is done:
On my windows 10 system I get the following error message when I double click a raw file in lighttable:
“running the graph failed (VK_ERROR_OUT_OF_DEVICE_MEMORY)!”
Darkroom does open but no image is shown.
which gpu is that and what kind of image? does your os eat up a lot of the device memory?
(i might have a theory… i check if there’s enough device local memory available to allocate, but integrated gpus might not declare their cpu/gpu shared memory as device local…)
Image is a RAF file out of a Fujifilm X-T5 camera, 39.6MP (5164x7678).
System RAM is 16GB, GPU is an AMD FirePro W5100 (4GB GDDR5).
Here below memory utilization. Step up in VRAM is when vkdt is started.
hmm that kind of GPU with only 4GB of memory is really the bare minimum runnable… i can imagine this wouldn’t be fun on 40MP images. maybe suitable for 16MP. you can try to disable the llap module and see if that would work, or run vkdt -d mem to get some diagnostic output on the console as to how much vram would be needed to process this image. plausible that 4GB are too tight for 40MP.
Yes, with a 20.1MP (3664x5488) ARW file from my old Sony is working fine.
…i just tried on an old intel notebook with 1.5GB vram. if you’re fine processing only low-res proxies, you can set the level of detail:
values > 1 will process only a subsampled version of the image. you should be able to navigate to this and set it in darkroom mode even though it complains about low memory.
With level of detail set to 2, also 40MP raw files are loaded correctly.
Still regarding the Windows version, a small detail I spotted is that user application data are stored outside AppData\Local directory.
By the way, today build 969 is crashing on my PC.
Tested today’s version (969) on 2 different pc (notebooks):
Windows 11 (home edition)
CPU: Intel core I7 12700H
GPU: NVIDIA RTX 3070 Ti
RAM: 32 gb
No problem whatsover so far. It starts and runs properly.
Windows 10 (Home edition)
CPU: Intel I7 10710U
GPU: Nvidia 1650 GTX
RAM: 16gb
It does not start (the GUI appears only a few milliseconds)
Here is this short “log” on the command prompt:
PS C:\Users\xxxx\Downloads\vkdt-rawler-0.9.99-969-gdf0ed784-win64\vkdt> .\vkdt.exe
[gui] vkdt 0.9.99-969-gdf0ed784 (c) 2020–2025 johannes hanika
[gui] glfwGetVersionString() : 3.4.0 Win32 WGL Null EGL OSMesa MinGW-w64
[gui] monitor [0] Generic PnP Monitor at 0 0
[gui] vk extension required by GLFW:
[gui] VK_KHR_surface
[gui] VK_KHR_win32_surface
[gui] no gamepad found
[gui] no display profile file display.Generic PnP Monitor, using sRGB!
←[31m[ERR]←[0m ignoring old hotkeys for lighttable, sorry for the inconvenience
←[31m[ERR]←[0m ignoring old hotkeys for darkroom, sorry for the inconvenience
←[31m[ERR]←[0m ignoring old hotkeys for nodes, sorry for the inconvenience
uhm sorry i have no idea what that is.
hmm might it have something to do with the utf-8 merge? win64: introduce utf8 support for windows, following @kmilos' pointers by hanatos · Pull Request #208 · hanatos/vkdt · GitHub
if i understand correctly it has some minimum requirements on windows version.
