Shaduf.Research preview
Real-Time AI Video/Vidu S2 documents live feed editing, not another H3 clip path

Pool topic: Real-time, continuous, and interactive AI video generation. Question revision: 1. Exact question: What can generate continuous, interactive AI video today, and which setups work at which cost, latency, hardware requirements, and quality?

Checked 30 September 2026 · Vidu S2 documentation

Vidu S2 can edit a live feed. The documented route costs $18 per billed hour before delivery.

Provider says: S2-Editing receives an incoming video stream, edits it, and returns a live stream. The API documents an RTC source and edited RTC output, with optional relay to an operator’s RTMP destination. That is a different job from generating a new H3 clip from a prompt.

What the API makes possible

The client publishes camera or file video to the supplied AliRTC channel and subscribes to the edited result. A reference image or editing scenario can change during the session. Vidu says the new picture appears within a few seconds, but a successful switch has no separate acknowledgment. A relay failure ends the live session. This pool has not measured the time from a control signal to a viewer’s screen.

Do not confuse this with S2-Avatar or S2 Avatar Component. Those are character routes; Editing transforms an incoming feed. The model map also lists an offline Avatar mode that returns an MP4, not a stream.

Cost boundary

The Editing API bills one credit per second from a successful live-start acknowledgment until hangup. Vidu lists a standard international credit at $0.005. That makes 3,600 billed seconds $18 before tax. It excludes the RTC service, RTMP destination, storage, failed sessions, and any other delivery cost. This is list-rate arithmetic, not a measured invoice or a guaranteed price for an hour viewers actually see.

Before using it for a show

Test one camera feed, one visual change, and one RTMP destination. Record live-start, signal send, first changed RTC frame, first changed receiver frame, hangup, billed seconds, and any relay failure. If the result cannot hold a useful session at an acceptable delay and cost, its live transport is not enough.

Unknown: independent control-to-viewer latency, long-session reliability, frame loss, output quality under a pinned scenario, region/account access, and a delivered-hour bill. The vendor’s paper reports 720p and 25–42 FPS for S2-Avatar; those numbers do not measure this Editing route.

Search published pools, pages, reports, and evidence.