Bug: Xbox refresh rate goes from 120Hz to 60Hz the 1st time I start a movie, then down to 24Hz the 2nd time

[DePingus 2]

Reporting a bug. The issue is that when I start a movie right after opening the app, the TV will switch modes from 120Hz SDR to 60Hz HDR. Then, if I back out of the movie and immediately start it again, the mode changes from 60Hz HDR to 24Hz HDR.

The movie looks best at 24Hz (I guess because it matches the framerate) and the mode should probably be going from 120Hz SDR to 24Hz HDR the first time.

My settings are at default, except I have to set ForceSystemDecoder on the Xbox app to get HDR to automatically turn on when I play a HDR movie.

Here is my software and hardware:

• Emby Server 4.8.11.0
• on Linux with Intel HD 630
• Emby Xbox 2.222.70.0
• on Xbox Series XS
• LG OLED 4K at 120Hz with VRR enabled

Here are the steps to reproduce:

• Start Xbox. The console is at 120Hz SDR
• Open Emby on Xbox. The app stays at 120Hz SDR
• Direct Play a HDR movie, the mode changes to 60Hz HDR
• Back out of the movie. The mode stays at 60Hz HDR
• Play the same movie again. The mode changes to 24Hz HDR
• Back out of the movie. The mode stays at 24Hz HDR

And here is a movie:

 

Edited April 17, 2025 by DePingus
typo

[Luke 42077]

Hi, we'll take a look at it. Thanks for reporting.

[softworkz 5066]

Xbox cannot play video at 120Hz. The switch to 60Hz is expected.

But the other switch down to 24Hz should only happen when you have enabled automatic refresh rate switching under "Display Control". Please check whether that's enabled.

Thanks

[DePingus 2]

Thanks a lot for everything you all do. I appreciate the replies.

I do have automatic refresh switching enabled. And I don't have a problem with that; some video looks better at 24Hz. The automatic switching works fine every time, except the very first time when the app is started at 120Hz. Also, the issue isn't just going from 120Hz to 60Hz to 24Hz. It also happens on videos that prefer 50Hz. It will stop at 60Hz the first time it plays. Then subsequent plays will be at 50Hz.

I'm guessing the logic that controls the rate switching doesn't properly account for the initial 120Hz state, since it expects 60Hz to be the highest. A fix might be to have the app set a valid refresh rate at startup.

Here's an example of a a video that likes to play at 50Hz:

[softworkz 5066]

Thanks a lot for the explanation. I'm getting now what you mean to report.

I'll try to reproduce and get back.

Thanks again,
sw

[65535 14]

Can confirm, it only ever switches to 60 from 120 on my SX.

[softworkz 5066]

This should be fixed in the new Xbox beta (https://emby.media/community/index.php?/topic/138418-new-windows-xbox-beta-222500-beta/)

If all goes well, the stable will follow in a few days.

Thanks

[65535 14]

@softworkzIt is indeed fixed, but now the "don't revert display mode" option is broken. Now it doesn't revert regardless of the setting. HDR is not reverted to off either. Stable worked as expected in this regard.

EDIT: Actually it's only an issue with the initial 120 hz, again. It does revert back to 60 if that's your starting point, and HDR gets disabled, but it acts as if "don't revert display mode" is enabled if you start at 120.

Edited May 1, 2025 by 65535

[softworkz 5066]

Thanks for testing, I'll take a another look at it!

[65535 14]

The latest change (2.227.0) made things worse on the Xbox. "Hard limiting" no longer works. At 120 Hz, it tries to match the refresh rate to the content regardless of the automatic switching setting. If it can't find a match, it just goes ahead and tries to play at 120 Hz, which fails on 4k content.

Edited May 4, 2025 by 65535

[softworkz 5066]

Are you sure it was different on 2.226 ?

[softworkz 5066]

How does 2.227 do on Windows?

For Xbox, we can just rollback to 2.222 behavior - I think Xbox has been fine anyway.

[65535 14]

See my PM regarding Windows. As for the Xbox, if you're looking to revert, 2.222 is the safest option. I haven't had much time with 225 to see if it has other problems. It will bring back the original issue of this thread, obviously.

Edited May 4, 2025 by 65535

[softworkz 5066]

Fixed in the new release: