Ok. Tried on another pc (vkdt-nightly-1-g1eb2ebe4-win64.zip)
PS C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt> .\vkdt.exe -d all -D perf
[pipe] base directory C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt
[pipe] home directory C:\Users\gross/vkdt/config
in C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt/modules/ciediag/params.ui!
for param ref in C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt/modules/ciediag/params.ui!
in C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt/modules/colour/params.ui!
for param rbmap in C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt/modules/colour/params.ui!
in C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt/modules/const/params.ui!
in C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt/modules/rt/params.ui!
for param zone in C:\Users\gross\Downloads\vkdt-nightly-1-g1eb2ebe4-win64\vkdt/modules/zones/params.ui!
[pipe] loaded 76 modules
[gui] glfwGetVersionString() : 3.3.9 Win32 WGL EGL OSMesa MinGW
[gui] monitor [0] Generic PnP Monitor at 0 0
[gui] vk extension required by GLFW:
[gui] VK_KHR_surface
[gui] VK_KHR_win32_surface
[qvk] dev 0: vendorid 0x8086
[qvk] dev 0: Intel(R) Iris(R) Xe Graphics
[qvk] max number of allocations 4189191
[qvk] max image allocation size 16384 x 16384
[qvk] max uniform buffer range 134217724
[qvk] dev 1: vendorid 0x10de
[qvk] dev 1: NVIDIA GeForce RTX 3070 Ti Laptop GPU
[qvk] max number of allocations 4096
[qvk] max image allocation size 32768 x 32768
[qvk] max uniform buffer range 65536
[qvk] num queue families: 3
[qvk] picked device 1 with ray tracing and with float atomics and with coopmat support
[qvk] available surface formats:
[qvk] B8G8R8A8_UNORM
[qvk] B8G8R8A8_SRGB
[qvk] A2B10G10R10_UNORM_PACK32
[qvk] colour space: 0
[gui] no joysticks found
[gui] no display profile file display.Generic PnP Monitor, using sRGB!
[gui] no display profile file display.Generic PnP Monitor, using sRGB!
[qvk] available surface formats:
[qvk] B8G8R8A8_UNORM
[qvk] B8G8R8A8_SRGB
[qvk] A2B10G10R10_UNORM_PACK32
[qvk] colour space: 0
[db] allocating 1024.0 MB for thumbnails
the GUIs does not start.
In addition, later on, I have tried to click directly on the vkdt.exe to no avail.
The previous “official” version worked extremely well on this same pc.
I notice in your log and mine some of the lines have paths that switch from backslashes to fwd slashes… do you think this is the issue… not sure how to correct that if so?? vkdt log.txt (1.3 KB)
ouch. CRLF problem. probably happens during git checkout on the github workers. will look into it.
for some good fortune, windows is resilient against this. you can actually operate with normal ‘/’ or with a weird mixture with backslashes and colons… now i wish plain windows would also understand msys2 kinda paths which make C:\CONFIG.SYS equivalent to /c/config.sys.
This is one of the latest vkdt appimages, apparently running natively on Wayland. Unfortunately I could not include a terminal window where the output of xlsclients is nothing, because vkdt covers the whole desktop, maybe that’s Hyprland’s fault since it’s the tiling Wayland compositor.
This is a live Arch based system running from a pendrive with active Nvidia drivers, Arco Linux B Hyprland.
Well and as you can see, vkdt covers every window under it except the Waybar at the top of the screen which covers a small part of the vkdt window.
Well and this is a different topic but I also want to mention that I would use vkdt more often or even regularly if it could save exif data such as focal length or lens model in the exported files. That’s the feature that I miss the most (I have set up my website so it automatically extracts some metadata from the jpegs and writes them under the photo). I was thinking about a workaround with a python script that uses exiftool but that is also difficult because vkdt does not preserve the original file name in the export either. And I would not mind if it could export to AdobeRGB or so and add a profile to the exported file.
Edit: never mind about the original file name, I just found the option. But the exif data thing would be nice.
Tried today’s nightly build.
Now it works fine (Windows 10 - NVIDIA GeForce GTX 1650 with Max-Q Design)
I am reading the documentation and I have noticed that you are supposed to close the application with the shortcut CTR+W. On my pc it does not work. In order to close the software I am forced to close the CMD window (or power shell)
Just of curiosity…
It is a bit strange (at least for me) to not have a “fixed window” for the GUIs.
At present, vkdt is “floating” over the desktop and it is not possible to resize its borders.
As you know, quite often, on the upper bar you have, for instance, on the right, 3 icons to minimize, maximize, close the GUIs etc etc
You wrote that I am supposed to clean the cache to avoid future problems.
In the directory (the one with my unzipped nightly window) there is no folder like this (named cache, I mean…)
I have also checked whether there are some “hidden” folders (not displayed)…
Is it possible to find somewhere, displayed on the GUIs, the current version of vkdt (e.g. its GIT build)?
IMHO, It may be useful whenever you take some screenshots for the bug reports?
I think this works on Debian/Ubuntu and Fedora. On Arch exiftool is in the directory /usr/bin/vendor_perl/exiftool apparently.
I mostly use Kubuntu these days so it should work for me too, today I had this Hyprland testing orgy, but probably it won’t be easy to make Hyprland work on Ubuntu/Debian.
I think this should be fixed in the Arch exiftool package.
Yes, exif data is included in the jpegs on Kubuntu now, however, I noticed that the orientation of the portrait format shots is wrong, on both Kubuntu and Arco Linux Hyprland.
Ah, and I noticed another interesting thing. Generating the thumbnails is much faster on Arco Linux than on Kubuntu 22.04, like two or three times faster.
sounds like a window manager thing. i don’t use window managers with that stuff so i’m not sure what to answer.
that’s probably ${HOME}/vkdt/cache, i think on my test system it was something like /c/Users/jo/vkdt/cache (still confused about windows file system names… it appears there’s the “NT” style file names that are single-rooted too, but not understood anywhere. oh, also you can prepend \?\\ or something similar to decorate paths…)
gui i don’t think. you can call vkdt --version as customary.
yes this is just a quick hack. the metadata expander includes the full exiftool command in your config.rc, the jpg output module should probably pick it up from there too. or rather, the appimage/windows zip should ship exiftool and ffmpeg binaries and use the basedir path to find the distributed one.
i’ll need to revive pascal de bruijn’s 2010 blacklist of exif tags, as darktable has it. the orientation is of course already applied and also some other things make no sense now (colour matrices etc).
uh, did they run from the same ssd or something? or did one not use the right gpu? thumbnail generation is mainly io and raw parsing bound. you’ll notice a big difference for some compressed RAF between rawler and rawspeed, the rest of the processing can be assumed to sum up to 0ms.
Yes, same SSD, same GPU, this PC only has one Nvidia GTX 1660 Super, the CPU has no integrated GPU.
My guess is that its either the newer driver or Wayland. I will do more performance tests.
Or maybe something is broken in my Kubuntu installation.
I am only working with ORF files.
Just tried the nightly (vkdt-0.7.99-199-g34c52bbd-win64)
Windows 11 - NVIDIA GeForce RTX 3070 Ti Laptop GPU
It works fine!
oh, where is that? i use ctrl-q to quit.
You are right! I was confusing it with GIMP…
Actually I have indeed tried ctr+q on many computers (W10 and W11) and it does not work
sounds like a window manager thing. i don’t use window managers with that stuff so i’m not sure what to answer.
Yep. I was expecting this reply from you
Joking aside, on Windows you can minimize a software even by clicking on the upper bar (Menu bar). I suppose it is the same on Linux. My last recollection of this Unix system dates back over 20 years ago (Mandrake). Afterwards I have always used Windows (lazybones, I confess).
BTW, if you prefer I can write my reports on github (Issues · hanatos/vkdt · GitHub)
Hopefully, reporting back on this forum may be useful for other users as well…
