20.02.2022, 11:16
because for some reason it does not render with the settings that I threw off. Only the preview runs, with the example that you described above.
Let me know whether KillerSpots worked for you.
Cu Selur
[HELP] Fragments disappear in hand-drawn animation
|
20.02.2022, 11:16
because for some reason it does not render with the settings that I threw off. Only the preview runs, with the example that you described above. Let me know whether KillerSpots worked for you. Cu Selur
20.02.2022, 12:19
Helper(1) finished with exitCode: -1073741819 and exitStatus: 1 Rendering error, tried on different codecs. The debug file is not being created for some reason. The preview runs for 30-40 seconds, then crashes sometimes.
20.02.2022, 12:23
The log you posted starts with:
Quote:This log is only intended for user information.so I do not know why you posted it, assuming you do not want to insult me. -> Read the sticky and provide a proper debug output of what you are doing and I can look at it. Also check whether the Preview works properly or whether it shows an error. Cu Selur
20.02.2022, 12:30
I have enabled this in the settings. The debug file is not being created for some reason. The preview runs for 30-40 seconds, then crashes sometimes.
I'm sorry, I'm looking for it at the specified path, and it's where the file appears.
If you have a NVIDA card try enabling: "Filtering->Vapoursynth->Misc->Source->Use DGDecNV when available"
If you have an Intel card try setting: "Filtering->Vapoursynth->Misc->Source->Libav hardware deocding mode" to 2 or 3 If the script is this still unstable on your system set: "Filtering->Vapoursynth->Misc->Script->Limit thread count" to 1 Quote:I'm sorry, I'm looking for it at the specified path, and it's where the file appears.Assuming the output folder is specified, and debug output is enabled it directly should create a file. Cu Selur
20.02.2022, 12:42
Everything works with the "Limit thread count", thank you.
20.02.2022, 12:46
Imports "D:\Progs\Hybrid\64bit\Vapoursynth\vspipe.exe" "C:\Users\Dmitry\AppData\Local\Temp\encodingTempSynthSkript_2022-02-20@13_38_59_2010.vpy" - -c y4m | "D:\Progs\Hybrid\64bit\VCEEncC.exe" --y4m -i - --codec h265 --vbr 7500 --max-bitrate 10000 --ref 0 --motion-est q-pel --profile main --level 6.1 --tier main --level auto --vbv-bufsize 20000 --slices 1 --sar 1:1 --fps 25.000 --output-file "C:\Users\Dmitry\AppData\Local\Temp\Kroshka_Enot_new_new_2022-02-20@13_38_59_2010_02.265" -> 1. try lowering the Vapoursynth thread count to 1 and see if that works. 2. try whether using another decoder helps 3. does it work with another encoder Cu Selur (20.02.2022, 12:42)Dmitry Wrote: Everything works with the "Limit thread count", thank you.Happy that worked. May be it would be enough to limti the numbedr od threads just for the decoder. -> will try adding an option for that (send you a link to a dev version with "Filtering->Vapoursynth->Misc->Source->Limit decoder threads")
20.02.2022, 20:56
Sadly RemoveDirt for Vapoursynth is totally unstable.
The project was simingly abandomned 8 years ago. pinterf who made an Avisynth++ port of it confirmed that the project was so much of a mess that he went back to the old Avisynth version for the Avisynth++ port and he thinks it's unlikely he will port the Avisynth++ version to Vapoursynth. So anything that is based on RemoveDirt is Avisynth(++) only atm. for the time being. -> Will adjust KillSpots to drop the advanced code and remove RemoveDirt from Vapoursynth during next week. Cu Selur
21.02.2022, 16:25
Thanks, well. Unfortunately, most of the video cleaning solutions now seem to be based only on old developments that are difficult to be compatible with new equipment.
|
« Next Oldest | Next Newest »
|