that is correct. i mean the ui is you press ‘k’ while hovering over the ui control and it will insert the keyframe for this parameter at the current animation frame (in the ‘esoteric’ tab).
i used to have ‘e’ as shortcut key but removed it. probably a good idea to introduce a real keyboard shortcut/configurable thing, i’ll put that on the list. maybe double click is also an expected action here?
yeah that’s built-in in the colour module. each module needs to read/write to global memory, so a lower number of modules is faster. also for ui i think it makes more sense to have fewer modules.
anyhow, picking i would do as outlined here: https://jo.dreggn.org/vkdt/src/pipe/modules/colour/readme.html and apply one of the colour-monk-XX presets (ctrl-p). they will go towards skin tone, not white, but it’s easy enough to reset the target colour to neutral white from any of them.
oh very good point indeed. for a quick fix, edit the bin/default-*.i-jpg files (one is for thumbnails and one for darkroom mode) and just remove the llap and probably also the filmcurv modules
from the default pipeline. i shall make vkdt load such files with priority if i find them in your .config/vkdt directory in the future.
in the past this has worked. macintosh computers don’t do graphics, so you need moltenvk in between vulkan and the hardware. i think maybe newer drivers already include this but i don’t know.
let’s politely say that i do not regret that the least.
impressive effort… i thought this would be pretty much impossible by now. travelling at this point, but once i’m back let me have a look at github, i can probably factor out the hard dependencies on linux kernel interfaces to a shared place so freebsd people can drop in their code easily too. started to put some of it into fs.h
i talk to the sys and proc interfaces and v4l2 and use posix libraries. this are not dependencies on libraries but on linux.
please do read the readme or see here