From 57be5bba52d54e2646d725024a01dbea122e560d Mon Sep 17 00:00:00 2001 From: Brandyn / Techy Date: Sat, 31 Oct 2026 15:56:00 -0500 Subject: [PATCH] Plan: burned-in server clock on the Go Live (WebRTC) path via canvas compositing Co-Authored-By: Claude Fable 5.1 --- CommunityDiscordMedia.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CommunityDiscordMedia.md b/CommunityDiscordMedia.md index f3d2619..dac6513 100644 --- a/CommunityDiscordMedia.md +++ b/CommunityDiscordMedia.md @@ -300,6 +300,8 @@ so: a real timecode track for coarse placement + a capture-side reference for th - [ ] `/clock/` page on the main host (behind Authentik): HTTPS offset measurement to the server clock (±few ms), 60 fps time-of-day readout with ms + once-per-second flash — add as an OBS browser source for burned-in timecode (BITC) when shared audio isn't available; optional per streamer +- [ ] live portal Go Live: composite the captured window through a canvas and paint the server-synced clock + into a corner on every frame before publishing (toggle, default on) — burned-in clock on the WebRTC path - [ ] README: editor workflow — multicam: sync by timecode (coarse), then audio waveform (sample-accurate, everyone is in the same voice chat) or the burned-in clock - rejected: LTC audio timecode per PC (needs SRT multitrack + a generator app on every machine)