Open cdmichaelb opened 1 month ago
cdmichaelb
commented
1 month ago I somehow fixed it. I was just going through enabling/disabling options. Not sure exactly what it was. I suspect Force Full Screen Display but I've returned it to its original settings and the problem is still gone. Attaching a new set of logs. I tried spotting the difference, but I really don't know what I'm looking for.
JellyfinMediaPlayer.log
Snagglebrew
commented
1 week ago Disabling 'Display refresh rate sync' in Client Settings - Video fixed this issue for me. Similar issue with each new episode flickering both monitors as if graphics drivers were restarting. The tooltip states the default is disabled, however I have not touched my settings in a few months with this issue only starting in the past few days.
Please make sure the issue only pertains to Jellyfin Media Player. If it also occurs in the web client, send the issue to jellyfin-web instead. Does not occur in jellyfin web.
Please make sure that your issue is not being caused by errors in custom CSS or note that you are using custom CSS. Nothing customized.
Please provide logs. You can drag the log file into the issue to attach it. JellyfinMediaPlayer.log
Describe the bug When going full screen with the jellyfin desktop app it acts like my display is changing resolution, or I'm trying to play a game in full screen exclusive mode (display drops, signal lost, then comes back full screen... the same happens when disabling full screen). This doesn't happen with VLC or Media Player Classic.
To Reproduce Steps to reproduce the behavior:
Expected behavior JMP should not be doing what it's doing that causes the display signal to crash when entering and exiting full screen mode. Media Player Classic, VLC, Youtube, Jellyfin Web, many other apps do not do this. The HDR issue is likely a windows issue. But that issue wouldn't arrise if JMP isn't doing whatever it's doing.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context This issue has existed for a long time, after a few discussions in the official discord troubleshooting it seems that this is a bug, not a setting or user issue. It's suspected that it may be related to refresh rate syncing, but I tried toggling that on/off and it doesn't change anything.