Unfortunately, there is another issue with this MC32 build (and maybe with the older ones, but I did not check): when playing files over the network, and seeking forward (30s) and backward (5s) repeatedly, it sometimes starts playing at a very reduced speed. JRVR records very few frames dropped (like 2 every 10 seconds) but the playback speed looks like a frame every 2 seconds and the audio constantly breaks. If you let the playback continue, it suddenly resumes at normal fps after a very long time (something like 30 seconds or more).
MC 31 on the same file, with the same seeks forward and backward has no such issue, the playback speed is normal.
I have a file on a remote network drive (a 6.62GB high bitrate BluRay ts file which has no internal subtitle, but I use an external ass subtitle with it) on which I can reproduce this 100% of the time: MC32 stutters after a single 30s seek forward, MC 31 doesn't.
It doesn't happen when copying the file to a local SSD and playing back from there.
Please let me know what kind of logs I can provide to debug this.
Edit: seems like having an external ass subtitle file with the same name as the video file increases the chance of running into the stutter on seek. The stutter still happens on seek even when you have no internal or external subtitle, but maybe not after a single seek, I need two or three on that file for instance.
I have no proof, but I suspect this playback stutter is triggered when the latency of the data retrieval from the remote network location (a folder shared on a system running Windows Server 2019 and accessed from another Win10 computer) is greater than some value. Transfer rate over the network for that file is a constant 60MB/s (aka 480 Mbit/s) while the file has an overall average bitrate of 40 MB/s and an overall max bitrate of 48 MB/s according to MediaInfo (avg of 36.2 MB/s and max of 40 MB/s for the H264 video stream alone with the audio being a PCM track with a constant 2304 KB/s - their sum is less than the reported overall bitrates so the rest must be the ts stream overhead), so the cause doesn't seem to be the constant transfer rate.
Later edit: I replaced the lav64 folder used by MC32 with the lav64 folder from MC31... and the stutter on seek doesn't happen. If I go back to the lav64 that MC32 has downloaded, the stutter on seek is there again. Tested this several times, and I got the same result every time: the lav64 folder from MC31 used with MC 32 build 32 doesn't have the stutter on seek, but it stutters when using the new lav64 in MC32 build 32.
So, I guess something in the new lav filters build, or the way it's used by MC, is causing the stutter on seek.