22.09.2024, 15:14
It's Ok
Dan
Dan
Deoldify Vapoursynth filter
|
22.09.2024, 15:14
It's Ok
Dan
Would be good if you could do checks like "HAVC_deepex: method != 0 but sc_framedir is unset" also in HAVC_main before calling HAVC_deepex since atm. one has to wait unnecessarily to get that message.
Updated test version, to include two additional checks that will throw an error during script creation: a. DeepExMethod != 0 requires vsDeOldifySceneFramedir to be set b. Preview will not be started if ColorMNet + sync + frame=0 is used. Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
22.09.2024, 17:18
New RC13 release, where I added some controls (including the the one on DeepExMethod).
I added 2 additional selections for the parameter VideoTune in HAVC_main: deoldify (the more stable) and ddcolor (the more vivid and less stable). Dan
22.09.2024, 17:21
Will test tomorrow and report back.
away from my pc for today
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
22.09.2024, 18:04
I tested the sync mode and is working.
Since the pre-process could take hours to complete (depending on the number of frames). There is something that I can print in output to help you to take track of the progress of the pre-process ? Dan
22.09.2024, 18:12
In theory, vsViewer should see Vapoursynth info messages and pass them through to Hybrid.
Those should be visible in Hybrids debug output iirc. and if they are there, I could write some code to turn the outputs into some sort of progress indication,...
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
22.09.2024, 18:35
This is a sample of current output
D:\Programs\Hybrid\64bit\Vapoursynth\vspipe.exe "sample_720p_2m_colormnet.vpy" - -c y4m -p | D:\Programs\Hybrid\64bit\x265.exe --preset fast --input - --fps 25/1 --output-depth 10 --y4m --profile main10 --b-adapt 2 --crf 20.00 --psy-rd 2.00 --deblock=-1:-1 --no-mcstf --psnr --ssim --range limited --colormatrix bt470bg --sar 1:1 --output "sample_720p_2m.265" I'm using the function vs.core.log_message(2, "Colored Frame: " + str(i)) To write in output the messages. Let me know if I have to change the output to help you to report the progress. Thanks, Dan
22.09.2024, 18:51
If you know the overall frames that get colored, output: "Colored Frame: current/all" this way reporting progress will be easier.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
22.09.2024, 19:51
Also, does that output appear in the Hybrids debug output somewhere?
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
22.09.2024, 20:19
(22.09.2024, 15:34)Selur Wrote: Updated test version, to include two additional checks that will throw an error during script creation: Please remove them because I added the controls in HAVC_main. Thanks, (22.09.2024, 19:51)Selur Wrote: Also, does that output appear in the Hybrids debug output somewhere? I attached my debug output, but to me seems that is not shown the vspipe output. In meanwhile I discovered a bug regarding the debug output. In my configuration I set to adjust the path with output folder, but this adjustment do not apply any more on debug output. As you can see I switched to path sample2 (I provided in input a clip stored in sample2), but the debug output was not updated (still the old path sample3). Even worse, if I unset the debug output, the output file is not saved. Please fix. Dan |
« Next Oldest | Next Newest »
|