Greetings and thank you for your work on Voukoder, I've recently came up with an interesting concept which could be useful to users:
Piping to a foreign process would give the user the freedom to feed their video (not audio sadly) to whatever encoding CLI tool that supports input from stdin and let the users do whatever kind of FFmpeg filtering they want.
I was inspired the VapourSynth CLI tool vspipe which can you use like so:
vspipe .\script.py --container y4m - | ffmpeg -i - -vcodec <blabla encoding stuff> output.mkv
I'm unsure the potential i/o speed bottlenecks nor y4m's pixel format support, but it opens a lot of possibilities for specific use cases.
Here is what it could look like in the Voukoder dialog:
(the arguments field would clutter fast, but it's easy
to copy it to a new notepad window,
type out your stuff and paste it back in)
Arguments could as simply as:
-i - -c:v libx264 %output%
(i might be wrong, from what I've seen most of the metadata can be passed programmatically)
Automatically filling in variables would also be a great QoL improvement, though much more work for you
%height%, %width%, %fps%, %pixfmt%
In that concept I specified an output folder but that could also be named something like %specified_output_path%
And they could be documented via a tooltip:
(you could also parse dollar variables like this: $variable instead of %variable%)
That could be used as an alternative to frameservers