The studio

Every voice on its own track, at the quality it was actually spoken.

Ottoframe records each participant on their own machine and streams the conversation through LiveKit so nobody waits on anybody’s wifi. What lands in your editor is what the browser captured locally, with server-verified upload progress.

studio — host view, four participants, rundown rail open
Local capture

Isolated camera and microphone tracks

Desktop Chrome and Edge record each published track in five-second chunks. Chunks are stored locally before upload, retried on transient failures, and verified server-side.

Conversation layer

LiveKit under the hood

LiveKit carries the room and adapts the conversation stream to changing bandwidth. Local MediaRecorder tracks are uploaded separately from that transport.

Direction

Layouts, markers, backchannel

Switch grid, speaker or screenshare mid-take. Drop a marker with one key. Producers whisper to the host without the guest seeing.

What the guest has to do

01
Click the link
Browser only. No install, no account, no download of a 400MB app the day of.
02
Pass the green room
We check camera, microphone, browser support, and available storage before they join.
03
Talk
Keep the studio tab open until the verified upload count reaches ready. The browser retries transient upload failures.
Capture specifications
Video1920×1080 session target at launch; browser/device capability may vary
Audio48kHz session target, isolated browser audio track per microphone
Capture locationdesktop Chromium browser, then signed chunk upload
Conversation transportLiveKit WebRTC, adaptive bitrate
Screen shareavailable in the LiveKit room; isolated screen capture is not a launch promise
Retry behaviourfour attempts with exponential backoff while the tab remains open
Deliverablesisolated tracks, program mix, 16:9 / 9:16 / 1:1