@expo/serve-sim 0.1.41 → 0.1.43

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -15,7 +15,7 @@ https://github.com/user-attachments/assets/fbf890f4-c8c7-4684-82be-d677b8a188f8
15
15
 
16
16
  ## Features
17
17
 
18
- - Up to 60 FPS over HTTP, or low-latency 30 FPS over WebRTC.
18
+ - Low-latency SimulatorKit capture with a 60 Hz IOSurface seed poll and configurable WebRTC cadence.
19
19
  - Swipe from the bottom to go home.
20
20
  - gestures like pinch to zoom by holding the option key.
21
21
  - Simulator logs are forwarded to the browser for browser-use MCP tools to read from.
@@ -92,7 +92,7 @@ Options:
92
92
  --video-bitrate <bits-per-second>
93
93
  H.264/WebRTC target bitrate
94
94
  --video-fps <fps>
95
- H.264/WebRTC frame rate (1-120)
95
+ H.264/WebRTC frame rate (1-140)
96
96
  --list [device] List running streams
97
97
  --kill [device] Kill running stream(s)
98
98
 
@@ -112,6 +112,12 @@ WebRTC uses HTTP for SDP signaling and RTP for video. Simulator input and screen
112
112
  metadata continue over the existing helper WebSocket. ICE prefers a direct UDP
113
113
  path when one is reachable, even if the page was loaded through a tunnel URL;
114
114
  TURN is used as a fallback when direct/STUN candidates fail.
115
+ While a peer is connected, one absolute-cadence publisher continuously submits
116
+ the latest captured frame at the configured `--video-fps`. SimulatorKit change
117
+ callbacks are supplemented by a 60 Hz IOSurface seed poll; that poll is a
118
+ fallback cadence, not a capture FPS ceiling. The libwebrtc
119
+ source adapter uses a 1,000 FPS safety ceiling and the RTP sender has no separate
120
+ FPS cap, so neither can phase-collide with the publisher cadence.
115
121
  Multiple WebRTC viewers can use the same simulator simultaneously. They share
116
122
  one SimulatorKit capture source, while each viewer has an independent peer
117
123
  connection, encoder, congestion controller, and helper WebSocket. HTTP streams