1.0.2

What's New

• Adds the x2.0-trtc realtime generation model and makes it the default everywhere: MediaService, XmaxClient.createMediaService, and the X-Lab example.
• Removes the x2-fast-1080p model. The x2.0-trtc model keeps the same input constraints: 1024×1920 / 1920×1024 resolution buckets and a 2.1M-pixel input cap.
• The china environment now points to the production base URL https://cloud.xmax.22duck.cn/open/api/v1 instead of the temporary integration environment.

API Changes

• RealtimeModel.x2_fast_1080p is removed; use RealtimeModel.x2_0_trtc (x2.0-trtc) instead. Code referencing the removed member fails to compile and must be migrated.
• Default model for createMediaService and new MediaService() changed from x2-fast-1080p to x2.0-trtc.
• No other API changes.

Requirements and Known Limitations

• Camera and microphone require an HTTPS or localhost secure context and user permission. Audio playback remains subject to browser autoplay policies.
• Interpolation requires WebGPU, shader-f16, and requestVideoFrameCallback; at most one frame is inserted per source pair with a 60fps ceiling, and the target rate is not guaranteed on all devices and resolutions.
• The remote frame rate depends on server send pacing and network jitter; interpolation cannot compensate for burst-delivered source frames, so overall smoothness relies on server-side pacing.
• RTC statistics frame rate reflects the raw received stream, and E2E is an RTC-provided estimate; neither represents full end-to-end latency including generation and client-side interpolation.