Can you guys post a logfile ?
Another hint is about the OpenGL flag. Could you try enable or disable it depending on which one you are using ?
Hello LongChair, and thanks for looking into this. I know that asking us to post a log file is a simple request, and if I had more time, I would happily do that. And I am not being deliberately unhelpful as I really want this fixed. But I am just a (paying) end user, and I am a bit frustrated about the issue, as yesterday, after a long day at work, I spent my whole evening on this, and by the time, I had executed a workaround, there was no time to watch any media as I had to get to bed.
This is a busy family household, where we work, and don’t want to use our limited free time in fiddling about with trying to get Plex working properly.
As I said in my first post, after spending considerable time troubleshooting the issue, I decided that the new version of Plex Media Player was just broken. So I got rid of it, from four machines, and rolled back to an older version that I had, luckily, saved in one of the machines download folder.
Why don’t Plex make it easier to find previous versions for when this event occurs?
So, to get log files from the broken version, will mean spending another evening deliberately breaking one of the machines, to get the logs, then fixing it again in order to watch some media. But that will likely take up a second evening, so no time to actually watch any media before bed time.
Back to the matter in hand:
OpenGL has never worked for me with refresh rate switching. When it detects 23.976 fps, it switches the TV to 60hz so the video is always very jerky. I did try this in the new version when I was troubleshooting what the problem was, but that behaviour (with OpenGL) hasn’t changed.
It looks like the common theme is Windows 10, an Nvidia graphics card, and refresh rate switching. That doesn’t sound terribly niche, surely someone within Plex must be able to re-create this issue and get you some logs. Do you not have access to a Windows 10 machine and an Nvidia card yourself maybe?
The developers who rolled out the new version of PMP must have made some changes with the code that effects this, is that you? If not, could that be looked into to get some more info about what has changed?