Add notes following kickstart livestream

docs/competition/competition-roles.md

@@ -39,7 +39,7 @@ Depending on the nature of the event, some of these roles may not be applicable.
 
 - [Roving Helper](./team-support/roving-helper.md)
 - [Tinker Time Coordinator](./team-support/tinker-time.md)
-- [Livestream Producer](./livestream/README.md)
+- [Livestream Producer](../programme/livestream/README.md)
 
 ### Helpdesk
 

docs/competition/virtual-competitions/README.md

@@ -6,4 +6,4 @@ Due to COVID-19 Student Robotics has held the competition for the SR2020 and SR2
 
 [simulator]: https://github.com/srobo/competition-simulator
 [code_submitter]: https://github.com/PeterJCLaw/code-submitter
-[livestream]: ../livestream/README.md
+[livestream]: ../../programme/livestream/README.md

docs/competition/livestream/README.md → docs/programme/livestream/README.md

@@ -14,6 +14,8 @@ OBS configuration is split into 2 fundamental objects: Scenes and Sources. A sce
 
 For virtual competition livestreams we use [SRComp Mixtape](https://github.com/srobo/srcomp-mixtape) to automate the playback of match videos and the scene transitions at either end of each match. See [Mixtape's documentation](https://github.com/srobo/srcomp-mixtape#configuration) for how to create a suitable playlist file to configure mixtape.
 
+Additional software may be needed if the hosts are [remote](./remote-content.md).
+
 ## Hardware
 
 The hardware requirements for hosting a livestream are not large, however a stable internet connection is a must. A dedicated GPU is useful to ensure the system isn't taxed too heavily.

docs/programme/livestream/remote-content.md

@@ -0,0 +1,22 @@
+# Remote content
+
+All of the content for a livestream may not be coming from the same machine, for example if the hosts are remote.
+
+!!! warning
+    For anything which requires high quality, such as full-screen video, this should be handled by the livestream machine wherever possible.
+
+## Video
+
+To stream video, it's recommended to use [vdo.ninja](https://vdo.ninja), as this creates high-quality low-latency video sources which can be easily dropped into streaming software as a browser source.
+
+`vdo.ninja` also allows hosts to mute themselves, and add background effects such as blurs and green-screening.
+
+For on-site cameras, it may also be useful to use NDI with [`obs-ndi`](https://github.com/obs-ndi/obs-ndi)
+
+## Slides
+
+For presenting slides, it's recommended to run the slides on the livestream machine, so any animated content or videos are as smooth as possible.
+
+If a remote host(s) needs to control the slides, it's recommended to use [Remote for Slides](https://limhenry.xyz/slides/), which also supports showing presenter notes.
+
+To ensure the host can see the slides, use a Google Meet call to share the presentation.

docs/competition/livestream/scenes.md → docs/programme/livestream/scenes.md

@@ -4,6 +4,14 @@ This page documents a few of the core scenes which are used for livestreams. Not
 
 The various assets useful for creating these scenes can be found [here](https://drive.google.com/drive/folders/1pr1vKpnonxFoO8O5chsH5DF7Vsd0Tfih?usp=sharing).
 
+## Presentation
+
+Events such as Kickstart are predominantly a presentation.
+
+For the presentation, it's recommended to use a window-based capture, rather than screen-based, to reduce the risk of accidentally putting sensitive or unrelated content over the slides.
+
+Long presentations should still show the host. Choose a bottom corner of the screen which won't cover any content and keep their camera fixed there. Slides may need modifying to ensure important content isn't covered.
+
 ## Technical difficulties
 
 Things occasionally go wrong during events, so wrong it may be necessary to cut the whole feed. In this case, we show a "Technical difficulties" screen, comprised of a single image, and mute audio whilst we work on a solution.