Chroma is broken when using LWlibavVideoSource+MPC-HC+AVSF

[Disaer]

Environment

• Filter version: v1.4.5 # 3ec5059
• AviSynth+ version: v3.7.2 r3661
• OS: Windows 10 x64 [Version 10.0.19045.2251]
• AviSynth script: no
• Log file: https://pastebin.com/nyQs1pS7

Describe the bug

Chroma is broken when using .avs file with LWlibavVideoSource as source with MPC-HC+AVSF Note that MPC-BE+AVSF or MPC-HC without AVSF have no this problem

To Reproduce

1. Create single string .avs file with LWLibavVideoSource as source : LWLibavVideoSource("BalloonRide.mp4")
2. Open created .avs file with MPC-HC+AVSF (no script in AVSF is set)
3. Chroma is broken

Sample video file: https://www.mediafire.com/file/p8d1qm98h83wl8c/BalloonRide.mp4/file

[flossy83]

I am able to reproduce it. Seems to be an issue with LAV Splitter, as I can resolve it by using Microsoft's splitter instead (MPC-HC settings > internal filters > source filters > untick Avisynth). This may not work if your system is configured to use LAV Splitter as highest merit. You can override that with Codec Tweak Tool:

Another way of resolving it is to untick "enable remote control" in AVSF to remove it from the list of active filters during playback, but this will only work if no .avs file is specified in AVSF.

[CrendKing]

If you do not use AvsFilterSource() as your source, there is no point of using this filter. You can simply open the .avs file in the video player. And remember to disable AVSF in the player.

untick "enable remote control" in AVSF

When you don't specify an avs file in AVSF, AVSF should automatically disconnect itself from filter graph, unless "enable remote control" is ticked. Unticking it is the way to go.

[CrendKing]

Assuming you get the answer. Feel free to re-open if needed.