Aleksoid1978 / MPC-BE

MPC-BE – универсальный проигрыватель аудио и видеофайлов для операционной системы Windows.
GNU General Public License v3.0
2.25k stars 91 forks source link

Mad flicker on fullscreen video with madVR #588

Closed l-l-l-l-l-l closed 1 week ago

l-l-l-l-l-l commented 1 week ago

I really don't know what happened exactly. Recently, I changed monitors and am using a Samsung TV for second (video watching) monitor (I thought that it would have 1080p23 or 1080p24 available, but if it does, it's definitely not through DVI). My first issue after the change was that the video got squished and black bars appeared on top and bottom; the issue happened even with my other monitor, which had been working fine till that moment. I finally managed to fix it by disabling "Correct Monitor/Desktop AR Difference" (which hadn't even been an issue till that moment).

The main problem, however, started a couple of days later, when on first play the monitor started flickering, keeping dark most of the time, until I manually changed the resoltion from Windows configuration to a different one and back. After checking a couple of things, I noticed that the issue was (and is) that the player, while on fullscreen, changes to the optimal screen mode (which is the one I already have) and then keeps changing to the optimal screen mode. I've tried to fix it by disabling screen mode change on both MPC-BE and madVR (and tweaking LAV Filters and other filters to see if the issue laid there), but it keeps happening.

v0lt commented 1 week ago

There is no madVR support here.

I would recommend updating MPC-BE, resetting all settings and checking if the problem is with the built-in EVR-CP renderer or the external MPC Video Renderer.

l-l-l-l-l-l commented 1 week ago

I asked here given that madVR tecnically doesn't do the resolution change. Before (when things worked well), disabling the automatic resolution change in MPC-BE disabled madVR, but now the flicker in fullscreen happeens even with that feature disabled (not to mention that I hadn't done any filter updating in months, mainly because there hasn't been one, yet the issue only cropped up days ago).