18.02.2024, 12:33
(13.02.2024, 22:31)Selur Wrote:Quote: It is theoretically possible to extend "VsViewer" so that can be launched using the command line like "VSpipe" ?if your rewrite most of it,... yes
Hello Selur,
I applied some changes to vsViewer released in your github repo: https://github.com/Selur/vsViewer/tree/master
The usage is the following
vsViewer --nogui [optional] --y4m [optional] --i [python script] --enc [encoder path] --cmd [encode command]
where:
--nogui : if present the encoding gui will not be visible
--y4m : if present will be provided the y4m header
--i : input vapoursynth script
--enc : encoder program
--cmd : encoder command
Examples:
1) Encoding with encoding Gui and with y4m header (*)
vsViewer.exe --y4m --i "VideoScript.vpy" --enc "x265.exe" --cmd "- --y4m --crf 18 --preset fast --output-depth 10 -o \"{sd}\{sn}_x265_gui.hevc\""
2) Encoding with no-Gui and with y4m header (*)
vsViewer.exe --gui --y4m --i "VideoScript.vpy" --enc "x265.exe" --cmd "- --y4m --crf 18 --preset fast --output-depth 10 -o \"{sd}\{sn}_x265_gui.hevc\""
(*) for script and encoder pass the full path not only the name as in this example
I like the Gui enabled version please try it, in case of no-Gui I was unable to write any message on Console (I have only a limited knowledge of Qt).
I attached an archive with only the changed files and with a build in debug mode of vsViewer.
I tried to don't apply too many changes, more important this version is compatible with the version release with Hybrid.
I hope that this modded version can be useful (you can abandon "vspipe" and all the encoding will be under your control)
Dan