29.01.2021, 21:16
(29.01.2021, 20:20)Selur Wrote: This doesn't happen here, so my guess is that it's LWLibavVideoSource having problems with your source.Tried all suggested workarounds.
Possible workarounds you can try:
a. enable the hardware decoding, which will help if your content is decodable through the vpu of your graphics card / cpu.
b. enable 'Filtering->Avisynth->Misc->Prefer FFMpegSource' (and do not enabled 'LibavVideoSource instead of FFmpegSource'). This way if FFmpegSource supports the input it will be used instead of LWLibavVideoSource.
c. enabling 'Use L-Smash for mp4 input' might also work, not totally sure whether it only works for mp4 or 'mp4 compatible' content.
d. I have also seen this happen when some anti virus or firewall solution ran amok and tried to interfere with Avisynth filter loading.
e. might also happen if the source is broken in some way or the input format is not supported by libav&co.
Quote:Task Manager shows around 3% memory consumption.Task manager would only show something when the memory consumption is slowly increasing. If randomly more memory is requested then available the filter just crash.
Cu Selur
None of them does work.
However in AvsPmod/Virtualdub2 all input filters (LWLibavVideoSource, LSMASHVideoSource, FFmpegSource2) work with the same video flawlessly.