summaryrefslogtreecommitdiffstats
path: root/2022
diff options
context:
space:
mode:
Diffstat (limited to '2022')
-rw-r--r--2022/organizers-notebook.org4
1 files changed, 3 insertions, 1 deletions
diff --git a/2022/organizers-notebook.org b/2022/organizers-notebook.org
index fb347ae3..7dc96386 100644
--- a/2022/organizers-notebook.org
+++ b/2022/organizers-notebook.org
@@ -180,10 +180,12 @@ DEADLINE: <2022-11-20 Sun>
- Issue: corwin needs assistance to not be locked in his chair for the whole conf. Premptively, zaeph can do it by broadcasting OBS scenes via the rtmp (instead of just his webcam).
- With a long day, we may want to be able to schedule hosts/streamers/publishers in shifts
- Ideal: Easy reproducible setup to spin up an OBS VM with scenes set up, allowing multiple users to connect to it at the same time. Maybe x2go or vnc? VMs with 8 vCPUs and a vGPU cost more, so it would be good to figure out what's needed, spin it down, and then spin it up maybe the day before or something like that.
+- Plus points if we can control the OBS via password-protected websocket so we can tell it to switch scenes (and even more points if we do so from Emacs, maybe via that obs-websocket.el ;) ). MPV is also controllable via IPC, so we can use the same MPV player and then switch videos around. Maybe mpvc? https://unix.stackexchange.com/questions/664728/how-can-i-control-mpv-in-command-line
+- Probably Linode's Dedicated 32 GB + RTX6000 GPU x1 at $1.50 an hour for 2-3 days + dev time, since live.emacsconf.org is in Linode as well
Resources:
- https://blog.wirelessmoves.com/2021/07/running-obs-studio-in-the-cloud.html
-
+
**** TODO corwin: plan an approach to use a centralized OBS/nginix "bouncer" :corwin:
**** TODO corwin: document such that someone else could use/fix it :corwin:
**** TODO corwin: recruit at least one more person to help operate the "video bouncer" :corwin: