* Things to check or decide
- Can we stream from multiple rooms without getting thoroughly confused?
- Assign rooms shortly before presentation
- *Shortly before presentation:* accommodates reshuffling
- Generating static images
- Before the presentation: Talk title, speaker
- Speaker checked in
- After the presentation: pointer to main conference stream
- After the conference: conference has ended, we'll take some time to prepare the recording
* Tasks
** DONE Assign IDs
CLOSED: [2020-10-20 Tue 00:38]
:LOGBOOK:
- State "DONE" from "TODO" [2020-10-20 Tue 00:38]
:END:
* Workflows
** If we have four rooms
O1 - main organizer, O2 - secondary organizer or volunteer
*** Overview
- Check in via IRC, 4 rooms
- 4 rooms streamed as room mounts.
- Individual talks have fallback mount of room mount.
- O1 streams from room or sets appropriate mount as fallback mount for main conference stream
*** Before the conference
- Do tech checks and get alternative ways to contact speakers (phone number? IRC nick? Something that goes ding?)
- Turn on audio alert
- Install Mute Tab extension if desired
*** Tech check
- Explain process
- Test audio, webcam, screensharing, collaborative pad
*** Shortly before the presentation
- Speaker joins green room (O2 home room). O2 gets alert
- O2 directs speaker to available room
- Speaker joins talk room
- O2 makes speaker presenter and moderator (so they can kick out recorder when done), does tech check
- Speaker tries screen sharing and webcam, then returns to uploaded presentation
- O2 starts secondary stream and recording, checks individual page
- O2 notifies O1 with link to the talk room
- O1 joins meeting
- O1 sets conference stream to individual talk endpoint
- O2 starts recording in BBB
*** During the presentation
- Speaker presents, keeping an eye on the collaborative pad for questions
- O1 stays with speaker to help with questions and timing
- O2 stays with speaker to stream to room source
- If there is another speaker, another organizer (O3) helps with the tech check
*** After the presentation
- O1 announces next steps: If you want to continue the conversation, go to the individual talk page
- O1 goes to next talk when ready
- Speaker continues with extended presentation if they want
- O2 stays in room
*** After the extended presentation (if any)
- If we figure out how to have the recorder/streamer be another user, speaker removes the recorder/streamer user to end the stream and recording, and speaker stops the BBB recording
- Alternatively, O2 stays in room, stops the BBB recording, notifies #emacsconf-org that the room is available, and looks for the next speaker to set up
*** Scenarios
**** Prerecorded presentations
- O1 streams presentation to both endpoints (is there a neat command-line way to do this?)
https://stackoverflow.com/questions/7869190/is-it-possible-to-pull-a-rtmp-stream-from-one-server-and-broadcast-it-to-another
or maybe IceCast can handle the splitting
**** Tech issues
- If can't be easily resolved, play pre-recorded talk early and try again later (or follow up)
- Stream a technical issues slide to the end point
**** Speaker can stream directly from computer over RTMP
- Can skip BigBlueButton entirely if they want
- Speaker starts streaming to talk endpoint
- O2 verifies that it's playing and communicates with speaker through collaborative pad
- O1 switches conference stream to talk endpoint
**** Speaker is giving another talk soon
- Stay in same room
- O2 checks in near the time of the next talk
- O2 stops and restarts recorder, giving it the next talk's stream endpoint
** If we have one room per talk (except for speakers with multiple)
O1 - main organizer, O2 - secondary organizer or volunteer
*** Overview
- one room per talk
- O1 joins the appropriate room and streams it to the main conference stream (or sets the fallback mount)
- O2 streams the talk room to the individual talk room
*** Before the conference
- Do tech checks and get alternative ways to contact speakers (phone number? IRC nick? Something that goes ding?)
- Turn on audio alert
- Install Mute Tab extension
*** Tech check
- Explain process
- Test audio, webcam, screensharing, collaborative pad
*** Shortly before the presentation
- Speaker joins talk room
- O2 makes speaker presenter and moderator (so they can kick out recorder when done), does tech check
- Speaker tries screen sharing and webcam, then returns to uploaded presentation
- O2 starts secondary stream and recording, checks individual page
- O2 notifies O1 with link to the talk room
- O1 joins meeting
- O1 sets conference stream to individual talk endpoint
- O2 starts recording in BBB
*** During the presentation
- Speaker presents, keeping an eye on the collaborative pad for questions
- O1 stays with speaker to help with questions and timing
- O2 wanders off to do the tech check with the next person and pings O1 when ready
*** After the presentation
- O1 announces next steps: If you want to continue the conversation, go to the individual talk page
- O1 goes to next talk when ready
- Speaker continues with extended presentation if they want
*** After the extended presentation (if any)
- Speaker removes the recorder/streamer user to end the stream and recording
- Speaker stops the BBB recording
*** Scenarios
**** Prerecorded presentations
- O1 streams presentation to both endpoints (is there a neat command-line way to do this?)
https://stackoverflow.com/questions/7869190/is-it-possible-to-pull-a-rtmp-stream-from-one-server-and-broadcast-it-to-another
or maybe IceCast can handle the splitting
**** Tech issues
- If can't be easily resolved, play pre-recorded talk early and try again later (or follow up)
- Stream a technical issues slide to the end point
**** Speaker can stream directly from computer over RTMP
- Can skip BigBlueButton entirely if they want
- Speaker starts streaming to talk endpoint
- O2 verifies that it's playing and communicates with speaker through collaborative pad
- O1 switches conference stream to talk endpoint
**** Speaker is giving another talk soon
- Stay in same room
- O2 checks in near the time of the next talk
- O2 stops and restarts recorder, giving it the next talk's stream endpoint
** Other description
#+begin_example
<sachac> All right, time to figure out the schedule [22:25]
<sachac> What I had in mind is that most people will be anonymously viewing
through the stream viewer on the main conference page or on the
individual talk pages
<sachac> I (or whoever the secondary organizer is, here referred to as O2)
will run around doing tech checks with people. The check-in room is
mostly just so that my computer goes ding, but IRC will probably work
too if I remember to check erc-track or /msg =) [22:26]
<sachac> O1 (probably Amin) will join the current talk's room and broadcast
that to the main conference stream. Alternatively, if whatever
streaming docker thingy I make turns out reasonably reliable, he can
just use Icecast to update the fallback for the main conference mount
to be the talk's streaming mount. [22:27]
<sachac> If a speaker wants to keep talking, the streaming thingy will just
keep listening to and streaming that room to the individual talk
mount, and people can continue watching the talk on the individual
talk's page. [22:28]
<sachac> Questions will be organized in the talk's section in the
collaborative pad (might be Etherpad), since that'll be easier than
having an organizer check three or four different IRC channels
[22:29]
<sachac> Ideally, the speaker would keep the collaborative pad open, keep
answering questions, and then wrap up at some point.
<sachac> I think this is better than having audience members join the room
directly because (a) we want to respect the FSF's bandwidth use, (b)
we don't want to tie up organizer resources in monitoring mute/webcam
status, (c) questions can be handled faster than text, and (d) no one
else has to fuss around with sound setup, worrying about
echo/feedback, and so on. [22:31]
<sachac> If speakers announce their arrival by a message in #emacsconf-org and
we're good about keeping that low-traffic, we can use that instead of
a staging room. [22:33]
<sachac> Worked reasonably well last year.
<sachac> If people are watching via the streaming pages instead of in BBB,
then we can bounce people watching individual streams back to the
main stream by setting the Icecast fallback for the individual talk
to the main stream. [22:34]
<sachac> Alternatively, we can change the Icecast fallback to an image that
tells them that the stream has ended and that they can go to the main
conference if they want. [22:35]
<sachac> (or a short video that says that, or whatever we can do with Icecast
- needs testing)
<sachac> At the moment, my BBB account is set up to have a maximum of four
rooms + my home room, so I'm planning for a different model that
involves directing speakers (via BBB or the home room) to whichever
room is available. I'll go to that room for the tech check and set up
the individual talk stream to feed to the source for the individual
talk page. Amin will go between rooms to stream them and to be around
if needed. They can occupy that [22:40]
<sachac> room for the remainder of their talk. When we need to move the main
conference stream on, Amin will help the speaker wrap up, and then
Amin will move to the next room that is ready. The speaker can stay
in their original room for the remainder of their talk. If we run out
of rooms because everyone kept talking for a long time, I'll step in
and ahem nicely.
#+end_example
* Conference recorder
Goals:
- Connect to BBB room and stream to room mount (liveRTMP?)
- Have a convenient way to switch the fallback mounts of the individual talk mount points
