Wow, that looks like that’s already the best time laps tool for Linux. 
Two questions:
Do you have any plans to add “auto align” of the images ?
And does crop and zoom work? (To make the Ken Burns effect)
I think both is impotent for nice time laps. Both can be don in post, but it would be nice to have in one tool.
the current align module will align the full image, not only do a camera shake correction (i.e. the teapot would not be moving any more). so that’d require a new module.
ah good question. i don’t think the k for keyframe shortcut will work on the ui widget. i just tried to manually put keyframes of the crop module in the .cfg, which works “fine”. actually i think this should probably be done in a different transformation module that will never change the resolution of the output. animating output size sounds like asking for trouble (the current implementation kinda works nontheless but leaves black borders if you animate to crop smaller than frame 0 did). could be a switch in the c/r module i suppose.
Good example and cute stop motion. 
actually the lens module works kinda okay on this one. let me demonstrate with a still image:
these are the interesting lines in the .cfg:
frames:200
fps:24
keyframe:0:lens:01:center:0:2:-0.25157:0
keyframe:199:lens:01:center:0:2:0.24528:0.21384
keyframe:0:lens:01:scale:0:2:1.9:1.9
keyframe:199:lens:01:scale:0:2:2.1:2.1
keyframe:0:lens:01:squish0:0:1:0
keyframe:199:lens:01:squish0:0:1:0.9434
quick diary entry. today: initial wacom pen/tablet support for drawn masks.
i added support for raster masks drawn with a stylus and pen pressure tied to opacity (so far). this was a bit of a journey because glfw does not yet support these pentablet events. luckily there is already a working pull request for it, so i just had to build this branch and publish it somewhere and then link vkdt against this and implement a few callbacks.
because of the non-std glfw (i hope the feature will make it to 3.4!), the vkdt code sits in a branch and requires some manual tweaking to link against the correct glfw version.
in particular, i have the following in my bin/config.mk:
# use our custom glfw from git
VKDT_GLFW_CFLAGS=-I/home/XX/vc/ext/glfw/include/
VKDT_GLFW_LDFLAGS=/home/XX/vc/ext/glfw/build/src/libglfw3.a
which points to a checkout/build of said glfw version.
i suppose i’ll merge it to master with a compile time switch/detection whether glfw supports the callbacks soon, and hope stock glfw will ship pen support at some point.
a bit off topic, but that’s today’s news:
pushed an optional module i-quake to render the animation from the other thread. to test, pull and
config.mk to contain the two lines about VKDT_USE_QUAKE as per instructions in config.mk.defaults
vkdt, you should then have modules/i-quake/*{spv,so}
/usr/share/games/quake
./vkdt examples/quake.cfg
i-quake modulesimilar info is found in the documentation for the module.
this is mostly for fun and may be useful as a testbed for image alignment, denoising, video output, and audio code.
Hey,
I just compiled vkdt which worked after installing a few missing dependencies. When attempting to run it for the first time I got
an error occurred while trying to execute gdb.please check if gdb is installed on your system.
backtrace written to /tmp/vkdt-bt-14646.txt
then after installing GDB I got
[gui] glfwGetVersionString() : 3.3.6 X11 GLX EGL OSMesa clock_gettime evdev shared
[gui] monitor [0] DP-2 at 3840 0
[gui] monitor [1] DP-3 at 0 0
[gui] vk extension required by GLFW:
[gui] VK_KHR_surface
[gui] VK_KHR_xcb_surface
[gui] no display profile file display.DP-2, using sRGB!
[gui] no display profile file display.DP-3, using sRGB!
backtrace written to /tmp/vkdt-bt-14770.txt
with vkdt-bt-14770.txt containing only this one line:
this is vkdt 0.0.1-134-g62b0c2f reporting a segfault:
My GPU might be on the very low end (Quadro K2000 with 2GB GDDR5) so this might be the issue here? I’ll get a new one eventually 
heya,
could you run vkdt -d all to see if it maybe outputs another clue for me? like this and with the backtrace dumping not working it’s hard to guess what’s going on. if you didn’t even have gdb installed before i’m not going to ask you to try and run it manually
ps: wow, how these expensive high end quadros become mediocre over the years is incredible. on the other hand it’s been almost ten years…
Hey
/opt/vkdt/vkdt/bin~ ./vkdt -d all 127 ✘
[gui] glfwGetVersionString() : 3.3.6 X11 GLX EGL OSMesa clock_gettime evdev shared
[gui] monitor [0] DP-2 at 3840 0
[gui] monitor [1] DP-3 at 0 0
[gui] vk extension required by GLFW:
[gui] VK_KHR_surface
[gui] VK_KHR_xcb_surface
[qvk] dev 0: vendorid 0x10de
[qvk] dev 0: Quadro K2000
[qvk] max number of allocations -1
[qvk] max image allocation size 16384 x 16384
[qvk] max uniform buffer range 65536
[qvk] picked device 0 without ray tracing support
[qvk] num queue families: 2
[qvk] available surface formats:
[qvk] B8G8R8A8_UNORM
[qvk] B8G8R8A8_SRGB
[qvk] colour space: 0
[gui] no display profile file display.DP-2, using sRGB!
[gui] no display profile file display.DP-3, using sRGB!
[qvk] available surface formats:
[qvk] B8G8R8A8_UNORM
[qvk] B8G8R8A8_SRGB
[qvk] colour space: 0
[db] allocating 1024.0 MB for thumbnails
[qvk] error VK_ERROR_OUT_OF_DEVICE_MEMORY executing vkAllocateMemory(qvk.device, &mem_alloc_info, 0, &tn->vkmem)!
backtrace written to /tmp/vkdt-bt-2642.txt
The backtrace txt is as empty as before.
Sounds like my 2GB VRAM is not enough, right?
Actually I only bought the Quadro because it was the cheapest graphics card I could find that can drive my two 4k monitors when I wanted to sell my Vega 56 for three times as much as I bought it for. I didn’t expect the GPU shortage to last that long back then 
documentation update:
the readme.md file is now not only used to generate the website:
but also the bullet list for the parameters is extracted as tooltips:
planning to do the same for connectors and maybe for the global module description so you can see it in the ui when configuring the pipe/searching for additional modules.
thanks. yes that looks like a memory allocation problem. i think 4G is a good size to run vkdt, 2G suffers from my slightly happy memory buffers i keep for fast thumbnail generation. i suppose you might have success running ./vkdt /path/to/image/directly.raw, but even then i might allocate the full thumbnail machinery, just in case. i might need a “low memory” mode, but was hoping i wouldn’t have to do that.
alright, thanks for taking the time anyway. I don’t think it’s worth the time to implement a low memory mode. I’ll try again as soon as I can get my hands on a Ryzen 6000 Laptop (german)
ah good. let me know when/if you have this thing and whether vkdt runs on the amd. i’m not usually testing hardware other than nvidia 
so it’s quite possible that i’m breaking things.
the vkdt entry in the open suse build system now has support for arch linux/PKGBUILD based distros.
thanks to @darix for helping me out there.
Hey @qosch
Will keep an eye on your feedback, as I’m very tempted by the Zephyrus G14.
Any later input on using it with vkdt/linux/darktable will be precious as there is not much on AMD CPU+GPU laptops.
Gllm
Oh I’m not specifically looking to buy the Zephyrus G14 but a Ryzen 6000 device in general (more specifically a 13-14" convertible with a U series processor, a good 90-120Hz 16:10 screen and decent connectivity). But I’ll report as soon as I have bought something (which could take a while given the current very limited options)
OK !
today’s updates are mostly in the colour module. it now supports profiles created from spectral sensitivity curves (ssf) created as colour lookup table (clut) textures by a special profiling tool.
it now supports optional input routed from the colour picker module which can be used for spot whitebalancing or deflickering of timelapse videos.
whitebalancing uses CAT16 to match the source colour (D65 white or picked input) to the destination colour (manual rgb sliders or use a skin tone preset).
as a reminder, the i-raw module supports the input of sequences of raw files. the picker can be used to normalise the exposure of these. the exposure parameter of the colour module can still be used to apply keyframes after the deflickering step, to fade in/out your sunset timelapse video for instance.
i had to do a fairly ugly thing to support float atomic add on amd hardware… and i’m not sure i succeeded (because i don’t have access to amd gpus). so if you have such a device and want to give it a spin i’d be curious to hear whether or not it works. in particular the pick module (colour picking) would do odd things and/or crash if it doesn’t work.
Oooh, mkssf looks REALLY interesting. It would be interesting to see that compared to known SSFs for a camera where available, and it would also be interesting to compare ColorChecker-derived DCP profiles to @ggbutcher 's SSF data that he’s collected using his setup.
