The Intermission scene is the break scene you'll go to between runs to give the audience a chance to pause, and your volunteers the time needed to get the next run prepared. This page will go into the functionality of this graphic. For details on:
changing the design, check out the Design Variables guide, which includes a section specifically for the Intermission scene.
the up next/on deck game and panel covers, check out the Intermission Covers & Panels guide.
In the top left corner is the Rainwave Music Player, enabled by default but can be disabled in the stuk-nodecg.json config file. Rainwave.cc is an internet radio station that just plays video game music with no interruptions or downtime. STUK is programmed to only play its OC Remix playlist, as these tracks are royalty free and shouldn't raise any copywrite concerns on Twitch or YouTube.
As long as its enabled, Rainwave will play automatically whenever you go to the Intermission, Opening, or Closing scenes - there is no playback control or user input required. The volume can be managed on the Live Audio Monitor, and by default the ON AIR setting is locked so that the music goes out to the stream, but isn't played back to the restreamer - you don't want to hear the Intermission music playing whilst trying to audio balance your next run.
The details are fixed to always displayed the track name and artist(s) on the top line, and "OC ReMix via Rainwave.cc" on the bottom line. This should not be altered, as it's important to give credit to Rainwave for using their tools. Some tracks do feature a very long artist list; these will simply get cut off at the end of the line should it be too long to fit.
The waveform visualiser isn't built into NodeCG but is a separate source on OBS. If you wish to use your own music player, you'll need to disable Rainwave in the config file, add your music source to the Intermission, Opening, and Closing scenes in OBS, and ensure the waveform visualisers are pointed at those music sources. Be sure to name the Music source with a "♪" to have it show in the Live Audio Monitor. The method to add the track details of your music player to OBS will vary depending on the music player you're using.
The timezone and format of the date & time area is managed in the stuk-nodecg.json config file.
The logos area will adapt in size and position depending on whether your marathon is raising money for charity, and if you're using the intermission cam display. The examples below show the different configurations. It should be noted that if charity and the intermisison cam display are both enabled, the charity logo doesn't include the QR code, as it'd be pretty small on the screen.
This display allows you to add a source behind the Intermission scene in OBS to display on the Intermission scene. By default, OBS includes sources for a webcam (if you're doing a live event, you might have a camera pointed at the audience), or a video (for adverts, interstitials etc.), but you could add any source you like to this area if you wanted.
The cam display is enabled or disabled in the stuk-nodecg.json config file.
The starting soon box is always enabled and displays information of the current run in the Run Player. Using the Live Switch panel to go to Intermission automatically moves the Run Player on to the next run, so the Starting Soon field should never show the run's that just finished. It does take a moment for the graphic to load and display the correct information, so it's recommended to use a transition stinger on OBS that lasts at least 1.5 seconds to avoid that update being seen on stream. As long as an image with the same name as the game title is placed in the assets\stuk-nodecg\gameCovers folder, the game cover image will display.
The number of up next/on deck runs displayed can be adjusted in the stuk-nodecg.json config file. The estimated time shown is based on the setup times and estimates of all previous upcoming races against the actual time the graphic first loaded. For that reason, the Intermission overlay browser source on OBS should have "Refresh browser when scene becomes active" ticked in the properties to ensure that time remains accurate. Every run in your marathon, including interviews and setup/sleep blocks must have accurate estimates and setup times to keep these times working correctly. It also means when starting your marathon, you should only load the Intermission scene before your first run for the time of that run's setup time. Streaming the Intermission screen and leaving it on for a longer period of time will suggest to your audience that the second run of the day will start much sooner than intended. If you plan to leave your Intermission up for a large period of time before the start, make sure your first run's setup time reflects that time.
The host of the run starting soon is displayed at the bottom, and will shift positions should a game cover not be in use. Declaring no host in the run editor will hide the field.