“bloatware” 
but in all seriousness, probably that is easy to do. note to self: set glfwWindowHint(GLFW_DECORATED, GLFW_TRUE) and struggle to remove the extra decorations for fullscreen mode again.
hehe same for me and windows 98 or so. and now that i read more about the api i’m surprised it still works… 
here works. especially for these little things that are probably resolved more quickly than what it takes to write an issue.
Never mind I just rebooted and the strange slowness has disappeared.
uhm i pushed something, but of course here it makes absolutely no difference. maybe it does on your machine?
Yeah, as I recall even decades ago under good (?) old actual stinky MS-DOS you could use / in code. It was only the shell (command.com in those days) that didn’t parse them properly. Made coding easier than having to escape back slashes (\) everywhere.
But that’s about the extent of what I remember… 
The appimage does work on Ubuntu/Wayland/Hyprland (with Nvidia) as well but a different question: how does color management (setting a screen profile) work with the appimage? vkdt does not pick up the profile file if it is in the same directory as the appimage does it? In which directory do I have to put it?
I downloaded the icc python script from github but when I try to use it I get this:
anna@anna-ms7c96:~/Downloads$ python3 vkdt-read-icc.py /home/anna/Downloads/benq.icc
/bin/sh: 1: iccdump: not found
Traceback (most recent call last):
File "/home/anna/Downloads/vkdt-read-icc.py", line 34, in <module>
if isfloat(tokens[5]):
~~~~~~^^^
IndexError: list index out of range
Edit: never mind, argyll (iccdump) was not installed on my system.
Yes, the appimage definitely does not pick up the profile file from the directory where it is.
$ vkdt -d all
[pipe] base directory /home/jo/vc/vkdt/bin
[pipe] home directory /home/jo/.config/vkdt
..
this is the default location, and also it’ll look in your home dir:
openat(AT_FDCWD, "/home/jo/.config/vkdt/display.HDMI-0", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/jo/vc/vkdt/bin/display.HDMI-0", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/jo/vc/vkdt/bin/display.DP-0", O_RDONLY) = 50
is the output of
$ strace vkdt -d all -D perf 2>&1 | grep open | grep display
so:
…but i think you’re right, it doesn’t work for the appimage… fixed.
with [ vkdt-0.7.99-206-gba794493-win64.zip ]
after i corrected the path of exiftool on my pc, I got
Error: File not found - 'C:/Users/olivier/Pictures/Playraw/DSCF2925.RAF'
I guess the issue come with ‘/’ vs ‘\’
… can you share a raw?
the one above?
Nice, thanks.
I noticed that when I export a photo to jpeg, two files are created, one of them has the name image.jpg_original, and apparently this one has no exif data. Is that intended?
Edit: and I also noticed that now vkdt is completely fullscreen, the waybar does not cover the window.
most certainly not. i didn’t get this kind of behaviour here, but added some option to exiftool now that may avoid this.
oh i suppose that is an improvement then. also it’s less lines of code, so this has been a good patch.
thanks, confirmed that somehow i fail to load the colour matrix from the exif data. until then you can (of course completely untested on windows so it probably doesn’t work)
vkdt mkssf 20190228_114736.dng
vkdt mkclut SM-N950W
mv SM-N950W.lut "${VKDT_DIR}/data/samsung SM-N950W.lut"
apply the clut preset (ctrl-p) and:
which is like a dcp profile (dual illuminant for white balancing) but uses a lut based on spectral sensor responses (so it never goes out of gamut/negative as a linear profile would).
attaching the lut for convenience:
samsung SM-N950W.lut (3.0 MB)
thank you very much
i will try your workaround
btw, this image is one of “playraw” . it’s just a test photo
The issue with this DNG file is that the CalibrationIlluminant1 and 2 are set to Daylight and Tungsten as opposed to the more common D65 and StdA.
Also the rawler RawImage xyz_to_cam field which is used as a fallback if there is no D65 matrix found is deprecated and is always filled in with zeros for dng files.
Hello @hanatos
Just a short question.
Are there, somewhere on YouTube (or such likes), some video tutorials regarding vkdt?
Nothing special or in depth.
Just a dummy introduction for beginners.
I suppose the answer is no, but I am making sure it is so
I am particularly interested in the node editor since, in my view, it is the most “innovative” feature compared to other “similar” raw processors (darktable, RawTherapee etc).
Perhaps, I should check blender in order to compare its features (node editor) to vkdt…
