techy/Media-Server-Setup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Plan: phase 12 uses the server clock as the only time reference

Browse Source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Brandyn / Techy
2026-10-31 15:53:40 -05:00
parent b750bdb71c
commit b782621368
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CommunityDiscordMedia.md
View File

@@ -289,6 +289,8 @@ Discord roles); the publish path must start with the user's own name.
### Phase 12 — timecode for multicam editing (frame accurate) (planned) ### Phase 12 — timecode for multicam editing (frame accurate) (planned)
Target: clips from several streamers align to the frame (16.7 ms @60) on a multicam timeline. Target: clips from several streamers align to the frame (16.7 ms @60) on a multicam timeline.
**Reference clock = the server** (NTP-disciplined). Recording start, the `tmcd` track and the burned-in clock
all derive from it; streamer PC clocks are never trusted.
Server-side stamping alone cannot do that (encoder + network delay differs per streamer by 0.1–0.3 s), Server-side stamping alone cannot do that (encoder + network delay differs per streamer by 0.1–0.3 s),
so: a real timecode track for coarse placement + a capture-side reference for the frame. so: a real timecode track for coarse placement + a capture-side reference for the frame.
- [ ] MediaMTX `recordPath` with `%f` (microseconds) — paths section, hot-reloaded - [ ] MediaMTX `recordPath` with `%f` (microseconds) — paths section, hot-reloaded