This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[HELP] Fragments disappear in hand-drawn animation
#21
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.
No clue what you did, the example above worked fine here for preview and encoding.

Let me know whether KillerSpots worked for you.

Cu Selur
Reply
#22
Helper(1) finished with exitCode: -1073741819 and exitStatus: 1
-> 2022-02-20@13_11_18_3410_03_video crashed: Helper1, exitCode: -1073741819
Aborting '2022-02-20@13_11_18_3410_03_video' due to: Helper1, exitCode: -1073741819
---
Helper(1) finished with exitCode: -1073741819 and exitStatus: 1
-> 2022-02-20@13_15_10_4710_03_video crashed: Helper1, exitCode: -1073741819Aborting '2022-02-20@13_15_10_4710_03_video' due to: Helper1, exitCode: -1073741819

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.
Reply
#23
The log you posted starts with:
Quote:This log is only intended for user information.
It should not be part of a bug/problem report!!
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
Reply
#24
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.
Reply
#25
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
Reply
#26
Everything works with the "Limit thread count", thank you.
Reply
#27
Imports
import os
import sys
import vapoursynth as vs
# getting Vapoursynth core
core = vs.core
# Import scripts folder
scriptPath = 'D:/Progs/Hybrid/64bit/vsscripts'
sys.path.insert(0, os.path.abspath(scriptPath))
# Loading Plugins
core.std.LoadPlugin(path="D:/Progs/Hybrid/64bit/vsfilters/DenoiseFilter/RemoveDirt/RemoveDirtVS.dll")
core.std.LoadPlugin(path="D:/Progs/Hybrid/64bit/vsfilters/Support/libmvtools.dll")
core.std.LoadPlugin(path="D:/Progs/Hybrid/64bit/vsfilters/GrainFilter/RemoveGrain/RemoveGrainVS.dll")
core.std.LoadPlugin(path="D:/Progs/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/vslsmashsource.dll")
# Import scripts
import killerspots
# source: 'C:\Users\Dmitry\Desktop\Kroshka_Enot_new.mp4'
# current color space: YUV420P8, bit depth: 8, resolution: 720x544, fps: 25, color matrix: 470bg, yuv luminance scale: limited, scanorder: progressive
# Loading C:\Users\Dmitry\Desktop\Kroshka_Enot_new.mp4 using LibavSMASHSource
clip = core.lsmas.LibavSMASHSource(source="C:/Users/Dmitry/Desktop/Kroshka_Enot_new.mp4")
# Setting color matrix to 470bg.
clip = core.std.SetFrameProps(clip, _Matrix=5)
clip = clip if not core.text.FrameProps(clip,'_Transfer') else core.std.SetFrameProps(clip, _Transfer=5)
clip = clip if not core.text.FrameProps(clip,'_Primaries') else core.std.SetFrameProps(clip, _Primaries=5)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# making sure frame rate is set to 25
clip = core.std.AssumeFPS(clip=clip, fpsnum=25, fpsden=1)
clip = killerspots.KillerSpots(clip=clip, limit=25)
# set output frame rate to 25.000fps
clip = core.std.AssumeFPS(clip=clip, fpsnum=25, fpsden=1)
# Output
clip.set_output()
scripts looks fine.

"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"
encoding call seems fine (aside from using a 6.1 level while restricting vbv that much).

->
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
Reply
#28
(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")
Reply
#29
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. Sad
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
Reply
#30
Thumbs Up 
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.
Reply


Forum Jump:


Users browsing this thread: 6 Guest(s)