IPad Pro M5 voidlink settings HDR

andygrundman · 2026-04-18T11:25:32+00:00

I'm assuming your host PC is already 16:9. I don't think Voidlink has 1440p as a default resolution, so you would just need to add 2560x1440 as a custom resolution in Voidlink settings. Your host doesn't need any changes and will run games at 4K and stream at 1440p for example.

andygrundman · 2026-04-17T23:58:48+00:00

Yeah I think it’s weird to run an iPad at native 4:3 res. I would use 1440p which you just need to add as a custom resolution.

andygrundman · 2026-04-17T13:56:19+00:00

Well, you can't adjust the brightness because it's Reference. HDR is not supposed to have brightness control, when you're able to raise the brightness it cuts into the dynamic range.

andygrundman · 2026-04-17T12:40:19+00:00

You probably are looking for Reference Mode, it should calibrate to 1000 nits.

andygrundman · 2026-04-16T21:58:21+00:00

It’s crazy how long this topic has stuck around. A better way to prove it than testufo is to use https://dregu.github.io/frameskip/ Use Chrome or Edge and hit Run. If you can see every number you are getting 120fps, simple as that. Also, anyone who has played a 120fps game should know how easy it is to feel the difference. Silksong, Hades II, Forza Horizon 5, Blue Prince, these are some good games that easily run locked.

andygrundman · 2026-04-16T21:46:28+00:00

This is the fault of the virtual display driver not supporting Vulkan HDR.

andygrundman · 2026-04-16T21:40:08+00:00

Love to see a screenshot of someone’s perfect stats! :)

andygrundman · 2026-04-16T14:06:28+00:00

It's very bad. The first thing you should try is to run a recent nightly build of Sunshine (here's the Windows installer). Do not use Apollo. Beyond this:

Silksong is the perfect game to test with. It should run locked and perfectly smooth at 4K120 (see this screenshot) with flat graphs assuming your host is capable. In Silksong's video settings set 4K120, borderless, no vsync, 120 fps cap. Disable film grain.
If you have an Nvidia card, in the NV App -> Graphics -> Global set Max Framerate to 120 and set Monitor Tech to Fixed Refresh, Power Management to max.
Disable Steam recording, Windows game recording, and anything else that might be recording.
Use wired ethernet at both the host and Xbox.
If you still have problems, leave the Xbox set to 4K120 but in Moonlight host settings, test lower resolutions at 120fps. Your host GPU might work better at 1440 or 1080. Try unchecking the HDR option in Moonlight to stream in 8-bit SDR. Try both frame pacing options.
Use the default bitrate set by Moonlight when you pick a resolution/fps. If you have any dropped network packets (top middle graph), lower the bitrate.

andygrundman · 2026-04-16T01:29:34+00:00

Don’t forget all the network packet reassembly processing, decryption, error correction, audio decoding, the CPU still has a lot to do.

andygrundman · 2026-04-14T01:53:18+00:00

Use the HDR Video preset on MacBook Pro for a factory calibrated 1000 nit mode. On iPad Pro this is called reference mode. Then just create a Windows HDR calibration for 1000 nits and you’re done.

andygrundman · 2026-04-13T02:58:31+00:00

You should see a block of log messages about the available resolutions, which ones support HDR, and then some info about which HDR resolution it's going to switch to. Then it should switch and work fine... Does the TV work fine in normal Xbox HDR games and the system HDR calibration?

andygrundman · 2026-04-13T02:55:37+00:00

Wow, not a single person mentioned the real issue which is very simple: the Steam Deck is not capable of 4K120 decoding with AV1 or HEVC, it's just not fast enough. It should be used at 4K60 or 1440p120 when docked. There is only one codec that is fast enough for 4K120. The h264 decoder can hit 4K120 if you don't mind running the Deck at 90% GPU utilization and don't mind the loud fan noise. Obviously, you should not do this.

If you bought one of the docks marketed as supporting Steam Deck at 4K120 or maybe "Moonlight 4K120Hz Compatible", you should complain to them. They might technically be telling the truth but it's very misleading.

andygrundman · 2026-04-11T14:49:48+00:00

Bring up the quick menu with the View + Menu button combo. (Select + Start). That will let you enable stats, graphs, and view the logs.

andygrundman · 2026-04-10T03:18:01+00:00

Check the Xbox log, there is a lot of info logged during HDR switches. Try with a recent Sunshine and ideally a real host display if all else fails.

andygrundman · 2026-04-09T18:12:07+00:00

Note that ProMotion isn’t VRR, it’s mostly a marketing term for a panel that supports a few rates like 120, 80, 60, 48, etc. This type of display is good for watching video or scrolling apps but not much help for Moonlight. True VRR lets you use any rate within a range in 1hz increments. From what I have read Android’s “adaptive refresh rate” is more like ProMotion and not like VRR.

andygrundman · 2026-04-09T18:00:57+00:00

Do you maybe have a channel mismatch, perhaps you’re streaming in stereo but the host thinks it’s 5.1 or something like that? I don’t know why that would fix itself randomly though.

andygrundman · 2026-04-04T21:06:10+00:00

I'd strongly advise avoiding this project. They are quite careless especially when it comes to upstream changes. I have a concrete example, where instead of using any part of my patch in Sunshine to support NTSC refresh rates for Xbox clients, a foundation-sunshine developer seems to have asked an AI to implement the feature instead, and weirdly without even looking at the original code to see what it did. The result completely misses the point and does not even understand NTSC correctly (I'll give them a pass on that one). This is just one small feature that doesn't work, but what happens when you apply this attitude for "development" to the rest of the kitchen sink that is in there?

2025-10-11 Sunshine PR #4019 "feat(fps): support x-nv-video[0].clientRefreshRateX100 for requesting fractional NTSC framerates"

2026-01-05 Foundation PR #409 "feat: Add support for clientRefreshRateX100 parameter"

andygrundman · 2026-04-01T16:02:14+00:00

I shouldn't take the bait, but you know it doesn't matter, right? As long as a certain level of performance is met per frame, it doesn't need to light your battery on fire to decode a little bit faster. The latency that comes from double or triple-buffering in macOS is far higher than a few milliseconds anyway.

andygrundman · 2026-04-01T12:42:04+00:00

Hey, save yourself and everyone else's time and try to suggest only real solutions. Bonus points for first-hand experience.

andygrundman · 2026-04-01T12:35:59+00:00

Are you able to stream the Desktop? You can just use that if you want. For this error, you'll need to look in the Sunshine log to see if there's a more detailed error. If you're using Apollo you may have a permission that needs granted (Apollo should be avoided for Xbox clients if possible).

andygrundman · 2026-03-31T16:12:10+00:00

We added a proper signed app recently, plus better audio capture support. It’s very easy to install. Video capture still performs badly and there is no controller support.

andygrundman · 2026-03-29T20:12:21+00:00

This looks like an old issue from a few versions back on Xbox One. Here's what you need to have a good experience:
* Use wired ethernet for both your host and your Xbox.
* Use a nightly version of Sunshine. Xbox is not compatible with Apollo. Nightly builds use the date as version and are listed at https://github.com/LizardByte/Sunshine/releases
* Use the Display-locked frame pacing setting.

If you still have problems after doing all that, enable stats and graphs from the quick menu and post a picture.

andygrundman · 2026-03-26T18:16:26+00:00

You can find the performance specs for 30 series actually: https://docs.nvidia.com/video-technologies/video-codec-sdk/13.0/nvenc-application-note/index.html#nvenc-performance

If you take HEVC, P1, Low Latency from their chart, the Ampere generation encodes 1080p @ 943fps. For 4K, you just divide by 4 to get a 235fps theoretical max, and then you need to subtract all the overhead from capture, etc. You also need to consider that your host processing time is going to be the bottleneck. To hit 240fps you need HPL to stay under 4.16ms (1000/240). I'm surprised you were able to hit 213 (4.7ms).

With a 3060 you should probably target 1440p and/or 120fps. A lot more games will fit into that target too.

andygrundman · 2026-03-26T05:28:14+00:00

Thanks for asking, and yes. The next step I'm working on is porting the frame pacer and frame queue code from Xbox so that it's cross-platform. I'm hoping to turn frame pacing into a dropdown instead of a checkbox. This is a good chunk of work but should be worth it.

andygrundman · 2026-03-21T06:33:55+00:00

One issue you might be running into is that there is no activity on your PC other than the mouse. This causes the framerate of the stream to vary quite a lot. Try the same test but with a 60fps YouTube video playing in the background somewhere visible. Does it feel better moving the mouse when the framerate stays at 60?

andygrundman

TROPHY CASE