Embedded Files
The Live Switch is the automation powerhouse of the whole package, originally developed by TheLightningStrikes but heavily modified since it's original version. If you have a Stream Deck or similar device, it acts in a similar way, allowing your to assign multiple actions to an individual button to have NodeCG do the work for your tech volunteers. This one panel will massively improve the workflow of your run changes and dramatically cut down your setup time.
By default, you shouldn't need to make any changes to the configuration for this panel, but full details on the options available can be found on the Live Switch Automation Configuration page. You may find you want to tweak certain settings, like adjusting the delay on switching scenes, or removing the function to start/stop local recordings on OBS if you have no plans to use recorded VODs.
The Live Switch panel will create these buttons by default. These should fit the needs of your marathon as they've been specifically designed to be used with the STUK setup.
Whilst each button appears self-explanatory, there are a couple of extra actions taking place on each.
Start Run: The main "Start The Next Run" button, press this when everyone is ready to start. Upon pressing, OBS will:
- immediately unmute the Runner's Mic Out Audio (see audio later about how audio works) meaning any talking in the STREAMING ROOM channel will be heard on the stream.
- start a local recording on OBS
- after a one second delay, switch to the Game Layout scene that matches the Game Layout code in the run's details, and also unmute the Runner's Game Out Audio.Intermission: To go to Intermission only after a run has ended. As you can probably work out, this does the opposite of the previous buttons. Upon pressing, OBS will:
- switch to the Intermission scene; during the transition, NodeCG will also automatically progress to the next run.
- set the OBS Preview to the scene the next runner will be using (assuming the Layout Code for the run is valid)
- mute both the Runner's Mic Out and Game Out Audio, meaning you are free to talk in the LIVE channel without it going to the stream
- stop the local recording
- switch the Runner Stream Source to the next runner, as per the number in the player's Stream code in the run detailsVideo from Run: Does the same as the Intermission button but instead switches to the Video scene - see the Video Player panel for details. Do not use this button if you've already gone to Intermission.
Video from Intermission: This goes to the Video scene but without the audio changes, moving the run along or changing the Runner Stream Source. Use this if you've already gone to Intermission and then it's decided that a video should be played.
Opening: Goes to the Opening scene whilst stopping any local recording.
Closing: Goes to the Closing scene whilst stopping any local recording.
Tech Issue: If you have a tech issue and need to go to Intermission during a run, you should press the Tech Issue Start button (it's a good idea to let runners/hosts know you're doing this first, and pause the speedrun timer). This will go to Intermission and mute the audio, but it won't stop the OBS recording. At this point, you can jump into the 🔊LIVE Discord channel to talk to the host and runner without being heard on stream. Once the issue is over, press the Tech Issue Over button to continue the run - don't forget to unpause the timer as well.
Intermission (Scene Switch Only): Goes to Intermission but the scene switch is the only action that is performed. This is useful whenver you want to go to the Intermission scene without advancing the run player, such as from the Opening scene at the start of the marathon, or if you wanted to interrupt a video early.
When you click any button, every button will be disabled for a couple of seconds - this prevents double clicking, or performing too many actions at once. The amount of time the buttons are disabled for can be adjusted in the config, but by default it is 2 seconds. This is normally enough time for a scene transition to occur, and any delays programmed into the buttons to fire.
In addition, most buttons have some disable conditions. When a button is disabled, a message will appear on the button advising the reason:
OBS Disconnected
If OBS isn't connected to NodeCG, every button will be disabled. You should check the OBS Connection Panel to reconnect OBS.Timer Running
All but the Tech Issue buttons will be disabled whilst the nodecg-speedcontrol timer is running. This avoids accidentally switching scenes whilst a run is under way.Invalid Layout Code
Only the Start Run button uses this disabled condition and triggers if the Game Layout code in the current run is invalid (it doesn't match the name of a scene in OBS). If this is the case, check the current run details in the Run Editor and ensure the Game Layout code matches the next runner's scene code.Current Scene: X
Every button has a condition where it will disable if a specific scene is active in OBS. This prevents you from transitioning to the same scene again, or prevents you from pressing buttons that might advance the run when you shouldn't. These are:Start Run disables on any game scene or the Interview scene (the Interview scene should be treated like any game scene)
Intermission disables on the Intermission, Video, Opening, and Closing scenes. If you need to go to Intermission whilst on one of these scenes you should use the Intermission (Scene Switch Only) button.
Video from Run disables on the Intermission, Video, Opening, and Closing scenes. You should only use this button to go from a run as it advances the run player.
Video from Intermission disables on any game scene, the Interview scene, and the Video scene.
Opening disables on the Opening scene.
Closing disables on the Closing scene.
Tech Issue Start disables on the Intermission, Video, Opening, and Closing scenes.
Tech Issue Over disables on any game scene and the Interview scene.
Intermission (Scene Switch Only) disables on the Intermission scene.
Page updated
Google Sites
Report abuse