Build the OBS scene from the video source
For a console capture setup, connect its HDMI signal to a suitable capture device and add that device as a Video Capture Source in OBS. Check that the capture properties and console output agree on resolution and frame rate. If the OBS preview stays blank, check the console display and capture-device manual before changing anything in Gtuner IV.
Watch the audio mixer while the game makes a recognizable sound. A visible preview does not guarantee that the correct audio track is being recorded. Make a short recording and listen to it before streaming.
Keep capture and controller testing separate
Connect the Titan Two’s controller output using the documented route for the gaming platform. Confirm that a button press works in the game while OBS is closed. Then open OBS and compare the controls on the display where you actually play. The OBS preview may include buffering and processing time independent of controller input.
If a second application needs the same capture device, test one program at a time. Some drivers provide one active capture session. A video source that appears in OBS may fail in another program until the first session releases it. Keep your working OBS scene saved so you can restore it after testing.
Preview a scene before broadcasting
Build a dedicated game scene and review what the capture includes. A whole desktop source can expose notifications or other windows. Record a short sample while moving through gameplay and the console menu. Check the scene edges, audio sources and transitions in the recorded file before going live.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.