avisynth_filter: AVSF with the latest Avisynth+ using ConvertToYUV420 or ConvertBits, the player does not respond.
Environment
- Filter version:
v1.3.1 # fa809c3
- AviSynth+ version:
v3.7.0
,v3.7.1_20211103_test23
,v3.7.1_20211104_test24
,v3.7.1_20211105_test25
,v3.7.1
,v3.7.2
- OS:
Windows 10 x64
- Video player:
MPC-BE x64 v1.6.1
- Video renderer:
madVR
,EVR-CP
- AviSynth script1: AvsFilterSource().ConvertToYUV420()
- AviSynth script2: AvsFilterSource().ConvertBits(16)
- Log file link: Logs
- Avisynth+ link: Doom9 - AviSynth+
Describe the bug
AVSF with Avisynth+ released earlier than November 3, 2021, the player works fine. AVSF with Avisynth+ released later than November 5, 2021, the player does not respond. However, SVP’s scripts using these two functions, the player has no playback problems.
AviSynth+ Version | AVSF [ConvertToYUV420] | AVSF [ConvertBits(16)] | ffdshow [ConvertToYUV420] | AVSF [SVP] |
---|---|---|---|---|
v3.7.0 | OK | OK | OK | OK |
v3.7.1_20211103_test23 | OK | OK | OK | OK |
v3.7.1_20211104_test24 | No response | OK | OK | OK |
v3.7.1_20211105_test25 | No response | No response | OK | OK |
v3.7.1 | No response | No response | OK | OK |
v3.7.2 | No response | No response | OK | OK |
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 23 (11 by maintainers)
I can make it configurable. But know that the trade off is that bigger pre-buffer equals longer seek time, meaning your player will only start to update after receiving all the pre-buffer frames. I certainly don’t want to impose the (possibly unnecessary) 2-frame delay to EVERY user just because some of you use TemporalDegrain2(degrainTR=2).
UPDATE: Test build: https://github.com/CrendKing/avisynth_filter/actions/runs/2305758529 Wiki update: https://github.com/CrendKing/avisynth_filter/wiki/Configuration