Buying guide
Starter gaming stream: PC and console signal paths explained
Build a first stream with separate PC and console capture workflows, deliberate audio routing and a repeatable recording test.

Start your streaming setup by deciding how the game reaches the viewer. You might stream from the same PC you're playing on, use a console's own broadcast feature or connect a console to a computer through a capture device.
Choose that route first so you know which connections and equipment you need.
Make a local recording with equipment you already own before going live. Listen to speech and game audio, watch busy gameplay and scene changes, and look for anything private on screen.
The examples below explain the connections and tests using published guidance. Your game, computer and connection will determine suitable output settings.
Choose one of three starting routes
| Route | Basic path | Main limitation to investigate |
|---|---|---|
| Single gaming PC | Game and microphone into broadcast software on the same PC | Shared computing resources and audio routing |
| Console-native broadcast | Console's supported broadcast feature to platform | Available scenes, services and accessory support |
| Console plus capture computer | Console HDMI through capture hardware, then USB or PCIe to computer | Capture compatibility, passthrough and separate audio paths |
A single-PC setup often needs no capture hardware because software can capture the game directly. Console-native broadcasting may be a useful first experiment if the console and chosen platform support it.
A capture workflow adds scene control and external sources, but also requires a suitable computer and more compatibility checks.
Do not add a second PC merely because established creators use one. First identify a limitation in the current arrangement and verify that another computer would address it. Each extra device introduces connections, audio routing, maintenance and desk space.
Streaming from the PC you're playing on
The game produces video and audio on the computer. Broadcast software captures the intended game view and audio, adds the microphone and any optional camera, then encodes the result for recording or streaming. Your headphones provide monitoring.
The source you capture should expose only what you intend viewers to see.
OBS's official quick-start guide recommends its automatic configuration process, explains scenes and sources, and encourages a short test before going live.
It distinguishes game, window, display and video-capture sources. Use the supported source for your operating system and application rather than assuming every capture mode behaves identically.
Capturing the entire display is convenient but can reveal notifications, account details or unrelated windows. A narrower game or application source may reduce that exposure, though you still need a privacy check.
Create a simple holding scene that contains no sensitive screen content and test switching to it.
Console capture: preserve a direct playing view
A common external-capture route is console HDMI output to capture-device input, capture-device HDMI output to the playing display, and capture-device USB output to the computer.
The computer receives the captured feed while the display receives the supported passthrough signal. The broadcast preview is not automatically the best screen on which to play.
Elgato's HD60 X Xbox setup instructions document that arrangement and distinguish the analogue line input from a microphone input.
They also state that HDCP-protected signals cannot be used. Follow legitimate platform and capture-device instructions for permitted game capture; do not try to bypass protection on restricted video services.
Verify the current system requirements, USB capability and supplied cable for the exact capture device. A USB-C connector describes shape, not necessarily the transfer mode needed by the device.
A charging-only cable or unsuitable hub may not provide the required connection.
Passthrough and capture are different specifications
A capture device may pass a higher resolution or refresh rate to the playing display than it records or sends to software. Read the full matrix for the intended input mode, not one large number on the product box.
Also check HDR, variable refresh rate and operating-system support where those features matter.
The HD60 X supported-resolution table is an example of manufacturer documentation separating input/passthrough and capture formats.
It notes that software can impose additional constraints. Treat the matrix as a compatibility reference for that device, not evidence about a similarly named older or newer model.
If you want to play at one mode and stream at another, write both requirements down. For example, “retain the supported high-refresh playing mode while producing a lower-resolution stream” is a more precise purchasing question than “buy a 4K capture card”.
Confirm the complete console, display, cable, capture and computer chain.
Decide who should hear each sound
List what the player hears, what viewers hear, what chat participants hear and what the recording stores. These can be different mixes.
Game sound may reach the player through a console headset while the capture computer receives HDMI audio; your microphone may need to reach both the stream and a chat application.
Do not assume connecting a headset automatically supplies every destination. Some console settings change where game or chat sound is sent when a headset is connected.
A controller microphone path and a computer USB microphone path are separate unless a supported arrangement joins them. Check the exact platform and capture documentation.
Make a row for each sound: game, your microphone, party chat and any alerts. Beside it, write who should hear it and whether it belongs in the recording. Test one row at a time.
You'll find it much easier to trace missing chat or doubled speech when the other sources are temporarily muted.
Prevent duplicated audio and feedback
One sound captured through two routes can create an echo or doubled effect. For instance, capturing a game's audio directly and also capturing the entire desktop output may duplicate it.
Monitoring a microphone back through speakers can create a separate feedback path into the microphone.
OBS's application-audio guide explains per-application capture on supported Windows versions and warns against leaving duplicate global desktop capture active when using that arrangement.
Its macOS audio guide describes the supported sources for that platform. Follow the guidance matching your installed version and operating system.
Use headphones during the initial routing test. Mute one source at a time and listen to a recording, rather than assuming moving mixer meters prove the correct sound is being captured.
Keep the source names descriptive so a later change does not require remembering which “Audio 2” represents the game.
Make the microphone understandable before upgrading it
Use an existing headset microphone or supported USB microphone to establish a baseline. Place it according to its instructions and maintain a comfortable speaking position.
A distant microphone with high gain may capture more keyboard and room sound than a modest microphone positioned well.
Record quiet speech, normal speech, an excited sentence, typing and a pause. Listen for distortion, missing syllables and background noise. Adjust position and level before adding several filters.
A noise gate set too aggressively can remove quiet words, while heavy processing may sound unnatural without fixing the source problem.
The peripheral guide includes headset fit and microphone checks.
If speech remains unclear after a controlled test, you now have a concrete reason to consider a different microphone, arm or room position.
Add a camera only when it serves the stream
A camera is optional. If you want one, choose the frame and light before judging image quality. Check the background for private information, reflections and household movement.
A narrow, dependable view may work better in a shared room than a wide lens showing every corner.
Test at the time you expect to stream. Daylight can change, and a bright game scene can illuminate your face differently from a dark one. A controlled lamp may improve consistency.
The small-room video-call guide covers framing and microphone placement in more depth, while the gaming lighting guide addresses display reflections.
Do not place a camera or light on an unsupported clamp. Check the desk, mount and equipment requirements. Keep cables clear of controls and monitor movement so adjusting the camera does not disconnect the capture device mid-session.
Choose settings your setup can sustain
Pick stream settings you can actually test with your game and computer. The encoder, your connection and the platform you use all affect what will run smoothly.
Start with the software's supported configuration guidance and the platform's current broadcast requirements. A lower-resolution stable stream can be more useful than a higher setting that regularly drops or stalls.
Test sustained operation during the intended household conditions, not only a speed-test result with everything else idle. Other uploads, wireless conditions and the computer's game load can change the outcome.
If a wired network connection is available and suitable, compare it as part of troubleshooting rather than assuming it guarantees success.
Do not copy another creator's bitrate or encoder settings without knowing their hardware and connection. Record your settings and change one major variable at a time. Keep the test game and scene comparable so you can identify what actually improved.
Record the same short test after each change
Make a short recording containing a menu, ordinary gameplay, a busy scene, quiet and louder speech, a scene transition and a brief pause. Include any chat source only with participants' agreement.
Check the file on another device with ordinary headphones or speakers, not solely through the live preview.
| Test section | What it reveals | Useful next check |
|---|---|---|
| Quiet speech | Missing words or excessive processing | Microphone position, input level and filters |
| Busy gameplay | Motion breakup or overloaded resources | Output settings and software statistics |
| Scene change | Missing sources or privacy exposure | Source order, visibility and transition behaviour |
| Chat exchange | Absent or duplicated voices | Routing and participant permissions |
| Pause | Fan, room and notification noise | Source selection and avoidable noise sources |
Review software statistics for the kind of problem reported, distinguishing rendering, encoding and network issues where the software provides that information.
A local recording helps test the capture and encoding path, but cannot alone prove internet delivery. Follow it with an appropriate platform test using the platform's supported privacy or test facilities.
Test synchronisation and monitoring separately
Compare a visible action with its sound in the recording, such as a permitted simple clap on camera. Check game audio too. Different capture and audio paths can introduce different delays.
Use the software's documented synchronisation controls only after confirming the routing and reproducing the issue.
Do not judge timing solely from delayed microphone monitoring in your headphones. The player's monitoring path and the recorded result may differ.
Record a second test after any adjustment and keep the earlier version for comparison so you do not alternate between two guesses.
For console capture, play through the intended display path and listen through the planned audio path. A technically synchronised stream is not useful if the player experiences distracting delay or cannot hear chat. Both sides of the arrangement need to work.
Protect privacy and participation
Disable or manage notifications that could expose private messages, and check browser tabs, filenames and account screens before capture. Keep stream keys and other credentials out of scenes and recordings.
Use the platform's supported security settings and avoid sharing configuration files that contain secrets.
Agree with chat participants and household members before including their voices or images. Respect the platform's rules and the rights associated with music, video and game content.
A purchased song or visible streaming-service window is not automatic permission to rebroadcast it.
Prepare a simple holding scene and a reliable mute control for interruptions. Test both before going live.
In a shared living room, the console setup guide helps preserve ordinary household use around the broadcast arrangement.
Let the test decide what to buy next
If the voice is consistently unclear, investigate microphone placement and compatible audio equipment. If the room is dark, trial lighting. If console-native broadcasting lacks a required source or scene feature, assess a capture workflow.
If the computer is overloaded, understand the resource limitation before buying decorative streaming accessories.
If your trial still points to an audio or lighting upgrade, the beginner streaming shortlist shows what each item would change in the recording.
Add cables, mounts, capture hardware and any necessary computer changes to the gaming budget planner.
Check the complete cost before ordering the capture device, especially if your existing computer falls short of its requirements. Keep the rest of the budget until your next recording shows what would help.
Starter-streaming questions
Do I need a capture card for a single gaming PC? Start by trying software capture on the same PC. Check how the game and recording run together before deciding whether you need extra equipment.
A capture device serves a specific external-source or multi-system workflow, not a universal requirement. Test the supported software path first.
Why can viewers hear the game twice? Check whether it is captured through both a direct application source and desktop or capture-device audio. Mute sources one at a time in a recording test and keep only the intended route.
Why is party chat missing? Console and headset settings may route it differently from game audio. Verify the platform's supported output arrangement and capture documentation. The fact that you hear chat does not prove it reaches the stream.
Does 4K passthrough mean 4K recording? No. Read the exact input, passthrough and capture matrix, including software and operating-system limits. Choose the device for both the playing mode and broadcast mode you require.
When should I go live? After the local recording and supported platform test show understandable audio, stable video, correct scenes and no unintended private content.
Keep a simple fallback scene and mute control available for problems that occur during the session.
Keep exploring
Related gaming setup guides
Gaming headset, keyboard and mouse: compatibility and fitChoose starter peripherals by platform connections, microphone behaviour, keyboard footprint, mouse space and realistic comfort checks.
Gaming lighting and cables: glare, controls and reliable routesControl display reflections and room lighting, install supported LED systems and keep gaming signal, audio and power routes accessible.
Small-room video calls: camera, light and clear audioImprove small-room video calls with camera framing, daylight layouts, microphone checks and a before-buying recording sequence.