[xservzeroman]

Stacked on release/1.0-beta5 (#127).

Saleh: PXPlay does up to 100 Mbps on PS5 Remote Play; MoonCast stopped at 50.

Changes

• Settings → PlayStation, on the handheld and the TV:
  • Home bitrate presets gain 50 / 80 / 100.
  • Custom is 2–100 Mbps for Home and Away (was 2–50).
  • The row says "80–100 Mbps needs a strong 5 GHz / 6 GHz link" (the TV adds "or cable").
• Ps5StreamActivity: the Custom clamp is 2–100. Auto is unchanged: 30 Mbps on fast Wi-Fi or cable, 20 otherwise, at most ~30% of the Wi-Fi link.

What the native side does

• chiaki-ng has no clamp of its own. video_profile.bitrate goes as is into the launch spec's bw_kbps_sent (streamconnection.c) and the encrypted RP-StartBitrate header (ctrl.c). So MoonCast's 50 was the only limit.
• Whether the PS5 itself caps it isn't measured yet. It reports target_bitrate in its connection-quality messages, which chiaki logs only at verbose level. Our Mbps stat is chiaki's measured bitrate. To check: set 100, then compare the Quick menu's Mbps (or stats mbps= in logcat, tag MoonCast-PS5) with 100. PXPlay reaching 100 suggests the PS5 accepts it.

Possible follow-up, not changed here

Takion sets SO_RCVBUF to 0x19000 (100 KB). At 80–100 Mbps a key frame can burst past that if the receive thread is briefly descheduled. Worth raising (say 2–4 MB) in chiaki-ng-mooncast if loss appears at high bitrates.

Testing: compiles (test268).

🤖 Generated with Claude Code