I started to look at logging in a rather long and torturous grab-and-rehack-and-add evolving avisynth+ template script with:
Code: Select all
SetLogParams("__vid__.debug.log", LOG_INFO)
LogMsg(Time("%Y-%m-%d %I:%M:%S %p, %z") + ": Start of debug logging", LOG_INFO)
Code: Select all
INFO: DGDecodeNV_DGSource() does not have any MT-mode specification. Because it is a source filter, it will use MT_SERIALIZED instead of the default MT mode.
WARNING: RemapFrames_x64_RemapFrames() has no MT-mode set and will use the default MT-mode. This might be dangerous.
WARNING: Deflicker_Deflicker() has no MT-mode set and will use the default MT-mode. This might be dangerous.
WARNING: DGDecodeNV_DGSharpen() has no MT-mode set and will use the default MT-mode. This might be dangerous.
WARNING: DGDecodeNV_PVBob() has no MT-mode set and will use the default MT-mode. This might be dangerous.
Code: Select all
Prefetch(6) # or see what happens with Prefetch(8)
Code: Select all
SetMemoryMax(4096) # 4096 8192 16834
Should I perhaps add these to the top of the script ?
Code: Select all
SetFilterMTMode("DGSource", MT_SERIALIZED) # GPU Filter
SetFilterMTMode("PVBob", MT_SERIALIZED) # GPU Filter
SetFilterMTMode("DGSharpen", MT_SERIALIZED) # GPU Filter
RemapFrames
DeFlicker
and perhaps these ?
cnr2
MDegrain1
MDegrain2
MDegrain3
neo-dfttest
AutoAdjust
DeSpot
dctfilter
RemoveDirt
MedianBlur
ColorYUV2
asharp
awarpsharp2
TUnsharp
I'm hoping this at the top of the script as well takes care of them automagically:
Code: Select all
SetFilterMTMode("DEFAULT_MT_MODE", MT_MULTI_INSTANCE) # http://avisynth.nl/index.php/SetFilterMTMode
Import("C:\SOFTWARE\AVISynth\AvisynthRepository\AVSPLUS370_x64\plugins-to-choose-from\mt_mode_definitions.avsi") # filters listed with MT_modes https://publishwith.me/ep/pad/view/ro.rDkwcdWn4k9/latest