Raw Tracks & Processing

In addition to the composed video, the Recording System captures raw tracks — individual audio and video recordings for each participant. Raw tracks enable flexible post-production editing and serve as a high-quality fallback.

What Are Raw Tracks?

During a recording, HotMic captures each participant's audio and video as separate files stored in S3. These are called raw tracks. Unlike the composed video (which combines all participants into a single frame), raw tracks preserve each person's original feed at full quality.

Each participant produces:

• One video track — Their camera feed.
• One audio track — Their microphone feed.

If a participant shares their screen, additional screen video and screen audio tracks are captured.

How Raw Tracks Are Captured

Raw tracks are recorded server-side, not in the browser. This means:

• Recording quality is independent of the host's computer performance.
• Tracks are stored directly in S3 by HotMic's recording infrastructure.
• No additional CPU or memory usage on the host's machine.
• Tracks are available after the recording stops (with up to 30 seconds of processing delay).

Accessing Raw Tracks

After a recording is stopped:

1. Go to the Recording page (Playback Mode).
2. Click View Raw Tracks to open the Raw Tracks modal.
3. The modal shows all participant tracks with details:
   • Participant name
   • Track type (video or audio)
   • Duration
   • File size
4. Click on a track to preview or download it.

MP4 Conversion

Raw tracks are captured in WebM format (VP9 video, Opus audio). For compatibility with editors and devices that require MP4:

1. In the Raw Tracks modal, click Convert to MP4 on any track.
2. The conversion runs in the background (powered by FreeConvert API).
3. The recording page polls for conversion status. Once complete, a download link appears.
4. Converted MP4 files are cached — converting the same track again reuses the existing file.

Post-Recording Processing Pipeline

When a recording is stopped, the following processing happens automatically:

1. Composed video finalization — The multipart S3 upload is completed and the video URL is saved.
2. Raw tracks sync — Recording data is fetched and raw track locations are stored in the recording metadata.
3. Scene JSON generation — A scene file is created for the Post-Production Editor. It includes:
   • Canvas dimensions and background configuration.
   • Host positions, shapes, and layering at each point in the timeline.
   • Pause/resume intervals (so paused sections can be trimmed automatically).
   • AI Producer hook display timestamps.
4. Automatic clip creation — A clip is automatically generated from the recording for quick sharing.

Using Raw Tracks in the Editor

The Post-Production Editor can load raw tracks to enable advanced editing:

• Re-compose — Rearrange host positions, change layouts, or swap backgrounds after recording.
• Individual track editing — Adjust audio levels, trim specific participants, or replace a track.
• Timeline replay — The scene JSON maps composition changes to the recording timeline, allowing the editor to reproduce the exact layout at any point.
• Pause trimming — Paused intervals are automatically identified and can be cut from the final export.

Storage

Raw tracks and composed videos are stored in S3 with the following structure:

• Composed video: Stored under the recording ID, accessible via CloudFront CDN.
• Raw tracks: Stored under the room name and recording ID, organized by participant.
• Stitched tracks: After processing, individual participant tracks are merged into single continuous files for the editor.

All recordings are scoped to your organization and are not accessible to other tenants.