I requested a screenshot to confirm your display signal input. I would hardly call that a lot of information. There is no further action that can be exercised here on the forum to give you resolution. You are welcome to request on Github that they raise the priority for your issue.
Okay, I donāt think we need to argue about what constitutes a lot of information, but I have been disrupting the family viewing and getting up and down with my camera to get the information you asked for, I thought there would be some outcome at the end of it? What did confirming my display signal input tell you?
Did we get to the bottom of why I am having this issue and others are not?
Are the common denominators⦠Windows, display switch to 23.976, and Angle rather than OpenGL? So anyone with that combination in their set-up will have either unwatchable jerky playback (sync to display) or audio and video drift (sync to audio)?
If other people with that configuration and those settings donāt have the issue, why do I, and can I fix it?
PLEASE CAN THIS THREAD BE RE-OPENED, PLEASE SEE BELOW NEW INFORMATION ABOUT A POSSIBLE WORKAROUND, THIS MAY HELP MYSELF AND OTHER USERS?
Process of elimination. Your MPC-HC screenshot showed the display refresh rate mode signal to be 23.97946Hz however PMP is showing it to be 23.976Hz. The last screenshot confirms that is not the issue. Therefore it is a bug that is being reported in the GHI raised on your behalf.
I will close this for now and mark it as pending.
This will allow it to be reopened when we have more information to report regarding any potential fixes.
@RuleZero One final suggestion and then this thread is dead to me.
With PMPv2.10.0.849-e02dbeca installed, copy libGLESv2.dll and libEGL.dll from C:\Program Files\Plex\Plex Media Player and paste that into a current build install. This was tested by @dan-the-man per a discussion he and I had. It should function as a workaround for you. No guarantees.
I am getting mixed results with copying the libEGL.dll libGLESv2.dll files version 2.10 into the newer PMP versions.
On some PCās it works, yet on others it prevents refresh rate switching happening at all. The flashing screen and mouse cursor appears, which I remember as being an old bug. From my limited testing in my house, PCās with Nvidia graphics cards work, but those with AMD or Intel donāt.
Latest news from Github is that the broken sync mode:display may be down to Qt and we are awaiting for the version of Qt to be updated in a new release of PMP.
I donāt completely understand what Qt is other than it being some third party software that is used within PMP. The version of Qt in the fully working PMP 2.10 was 5.9.0, the current version in the latest PMP is 5.9.5, and the current version to be implemented in a āfuture cycleā is 5.12.
So, I am hoping that sometime soon-ish a new version of PMP will be released with Qt version 5.12 and everything will be fully working again.
Another bump. The upgrade QT task was marked as high priority on GitHub on 27th November⦠What is the usual timecale for completing high priority tasks?
No, unfortunately not, it“s still 5.9.5
On my Linux Box, I had audio dropouts with Qt 5.12.1 lately, so there is maybe even something good to it, that they“ve not upgraded to 5.12.1.
Well, it“s not really about the main topic of this post here but its something I want to add.
After some additional movie-watching hours. I now have audio drop-outs with Qt 5.11.3 which seemed stable (I“ve used it for two months without any issues at all).
I think itĀ“s not QtĀ“s fault. The Linux machine is ābuildā with mesa and llvm beta. Issues are therefore obvious. Iām sorry that Iāve blamed Qt. I will reinstall my Linux machine with mesa/llvm stable and Qt 5.12.1. I will post an update.
-> to be continued
Iāve started to get a black screen when a file has finished playing or if I back out (Iāve got display mode switching enabled) - does this happen to you?