![potplayer avisynth potplayer avisynth](https://ae01.alicdn.com/kf/HTB1ZUnyRFXXXXX_XXXXq6xXFXXXS/RC-Hobby-Electric-Fuel-Pump-4-8V-6V-100cc-minuntes-For-Nitro-Gas-RC-Airplane-Car.jpg)
![potplayer avisynth potplayer avisynth](https://i.postimg.cc/jdyvGkJv/01.png)
I have mostly been testing with the newest test build of AviSynth+ & AviSynth Filter Players used: PotPlayer 200908(5), MPC-HC (1.9.8) & MPC-BE (1.), both 32bit & 64bit OS: Win7 圆4. I have ruled out LAV Filters hardware acceleration as a potential cause. Some combinations have color distortion issues, while some others crash silently or with Access violation errors pointing to either avisynth.dll or avisynth_filter_**.ax. PotPlayer loads fine, but AviSynth Filter reports that it's actually using YUY2.Įnabling different colorspace combinations seems to sometimes produce different effects from when only one colorspace is selected, some of which might be player/decoder/renderer-combo specific, but only happen with AviSynth Filter enabled. I tested this and got silent crashes with MPC-HC & MPC-BE Using EVR & MadVR. I tried only enabling one colorspace at a time and for me silent crashing happens consistently when loading Input Formats NV12, P010 & P016. Now that i've looked into it, it turns out that the issue persists even while using any variation of the script below: At the time i assumed it was a script problem and planned to get to troubleshooting it later. I was getting silent crashes when i first started experimenting with AviSynth Filter v0.6.0 or so, but got rid of the problem by disabling all input colorspaces apart from YV12. There seems to be a lot of inconsistency in how the Input Colorspaces work with different system configurations.
Potplayer avisynth install#
Just install it.) Currently, Avisynth+ 64-bit is recommended, but you can also use the 32-bit version if you have an old 32-bit computer, or the classic avisynth if you have developed your own avisynth scripts working only with that version. So it might be a bug in AVS+ 3.5 that will never be fixed. (Avisynth is a complex program, but you dont need to use it directly. With AviSynthPlus 3.6, there is no crash regardless of input format settings (well, SVSmoothFps() crashes with YUY2, but you can always ConvertToYV12()). I have no idea why allowing YUY2 would fix the problem. If I disable any of them, even though it eventually only uses NV12, it crashes. If I disable all formats but leave NV12 and YUY2 on, there is no crash. It seems to link to the input format setting in a strange way. The crash will then come from ApplyYUY2(). Since you seem quite satisfied with PotPlayer, then the answer is no, you don’t need LAV Filters. If I disable NV12 and YV12, LAV will convert to YUY2 and feed me. LAV Filters can be used by DirectShow-based media players, or by Avisynth (via DirectShowSource or DSS2mod). The video is H.264 and all formats enabled, so basically NV12. AviSynth.dll!Antialiaser::GetAlphaRect() Line 857Ĝ++ĪviSynth.dll!Antialiaser::ApplyYV12(unsigned char * buf, int pitch, int pitchUV, unsigned char * bufU, unsigned char * bufV) Line 232Ĝ++ĪviSynth.dll!Antialiaser::Apply(const VideoInfo & vi, PVideoFrame * frame, int pitch) Line 201Ĝ++ĪviSynth.dll!Subtitle::GetFrame(int n, IScriptEnvironment * env) Line 1496Ĝ++ĪviSynth.dll!MTGuard::GetFrame(int n, IScriptEnvironment * env) Line 120Ĝ++ĪviSynth.dll!Cache::GetFrame(int n, IScriptEnvironment * env) Line 189Ĝ++Īvisynth_filter_64.ax!AvsFilter::FrameHandler::ProcessOutputSamples() Line 333Ĝ++