From f2e09c49f9bae57cf47c8c9fb1da8adeda9bcbae Mon Sep 17 00:00:00 2001 From: Simon Willison Date: Wed, 9 Oct 2024 22:32:47 -0700 Subject: [PATCH] Lessons learned --- youtube/livestreaming.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/youtube/livestreaming.md b/youtube/livestreaming.md index 23f7af3306..34fb022e95 100644 --- a/youtube/livestreaming.md +++ b/youtube/livestreaming.md @@ -43,6 +43,8 @@ With hindsight, I could have had the RØDE microphones record audio directly ont I assumed YouTube were more stringent with their Chrome testing than their Firefox testing, so I switched to Chrome for the second half of the event - [video here](https://www.youtube.com/watch?v=GHtMbhG9EIU) - and kept an eye on its memory usage in Activity Monitor. That worked fine. +**Lesson learned:** For this kind of event, losing audio is worse than losing video. Just because test streams that were 5 minutes long worked fine doesn't mean that an hour long stream won't run into unexpected problems. There's a reason the RØDE microphon's have the option to create their own audio backups! + ## Embedding the video I tried embedding the YouTube live video on our [coastsidecivic.com](https://coastsidecivic.com/) website for the duration of the event, but the iframe showed a message saying that the owner of the video had disallowed embedding.