Who this setup is for

This setup is for lessons, interviews, commentary and presentations where the presenter is the main subject. This blueprint starts with the signal path and the host connections, because a list of popular gear cannot show whether the parts can exchange the required video, audio, control and power signals.

Placement, light and sound path usually matter before a camera’s maximum resolution. Map the exact computer, ports, sources and equipment already owned in the setup builder. Resolve every required port, cable and software mode before buying around it.

Choose the smallest complete path. A control surface, second light, premium camera or external mixer can improve operation, but none repairs a missing host port, unsupported mode or audio return that feeds back into itself. Add optional parts only after this base route records cleanly.

YOUR SIGNAL PATHSingle computer
  1. CameraUSB video → computer / OBS
  2. MicrophoneUSB audio → computer / OBS
  3. Headphones3.5 mm ← microphone monitor
  4. Stream outputComputer Ethernet → router → platform

Detailed wiring diagram · scroll to follow the path →

View the connection diagram
Video, audio and network connectionsCamera video and microphone audio connect by USB to the computer running OBS. OBS sends the stream by Ethernet through a router to the platform. Headphones return the monitoring mix from the microphone.USB videoUSB audio3.5 mm · monitorEthernetUploadCameraWebcam · USB outMicrophoneUSB out · headphonesYour computerUSB inputs → OBSHeadphonesYour monitoring mixRouterLAN → internetYour streamPlatform previewPower → hostDirect USB example. Select your gear to check the exact ports.
━━ Video┄┄ Audio··· Network┄ Power

Signal path

Camera or webcam → computer capture source; close microphone → USB directly or XLR interface → computer; wired headphones → monitoring output; one or two lights → presenter; slides or browser → OBS scene. The program then records locally and goes to the destination.

Write each hop as source output → cable → receiving input → software source → destination. Put the connector name and required protocol beside the cable. A USB-C plug describes a shape; it does not prove USB 3 speed, video support, charging power or device compatibility.

When the route uses capture, keep capture and passthrough as two rows. Capture is what the streaming computer receives; passthrough is what the display receives from HDMI output. A device can pass a high mode while capturing another, so never copy the larger passthrough number into recording settings.

Eight component decisions

Resolve these eight decisions in order. Each either removes a signal-path blocker or defines a destination that later routing depends on.

  • Framing: Choose headroom, crop and eye line for the intended scene before choosing camera resolution.
  • Camera path: Use UVC for a direct webcam or verify clean HDMI, continuous power and capture for a separate camera.
  • Focus/tracking: A fixed desk benefits from stable framing; a moving presenter may need tracking and clear mechanical space.
  • Voice pickup: Keep a suitable microphone close and outside the most distracting part of frame.
  • Room sound: Reduce reflective distance and background noise before relying on processing.
  • Key light: Place a soft source near camera axis, then adjust distance and angle before adding fixtures.
  • Background: Separate subject and background physically when possible; avoid making exposure solve two incompatible brightness zones.
  • Monitoring/presentation: Route slides, media and guest audio once, and keep the presenter’s headphones on the intended monitor mix.

Place the voice, camera and lights around the room

Make a short unprocessed recording of speech followed by silence. A ringing tail after words suggests reflections; a steady fan or traffic sound during silence suggests a noise source. A delayed second voice only in headphones may instead be duplicate software monitoring. Diagnose that before treating the room.

Move the speaking position away from a bare wall or corner and bring the microphone within its intended working distance. For a cardioid microphone, aim its least-sensitive rear toward a nearby noise source while keeping the speaking side toward the voice. This does not erase reflected sound or make every microphone behave alike. RØDE’s technique guide explains close speech placement; use the exact mic’s manual for its addressing side and distance.

Set camera framing and the boom together so the microphone can stay close without covering the face. Place the key light where it illuminates the face without reflecting into glasses, then check the key/fill/background placement procedure. Move a noisy computer farther from the mic when cable limits permit; keep cooling vents open.

Use existing curtains, rugs or upholstered surfaces to try reducing an identified reflection, then record the same phrase from the same position and gain. Compare the word endings and silence at matched playback level. Soft furnishings are a room-reflection experiment, not soundproofing or a measured acoustic-performance claim. Keep only changes that improve the actual recording.

    Top-down speaking position and room sound pathsThe speaker faces a close microphone and camera. The microphone rear faces the computer beyond the desk. A dashed speech path bounces off a bare wall back to the microphone; curtains or a soft surface are a placement experiment. Keep camera framing and key light clear of the boom.Bare wall: reflected speech pathComputer / fanDeskCameraMic front ↓Speaker facing mic + cameraTry a softsurface hereKey light → face
    Scroll the plan horizontally on narrow screens. Placement schematic, not to scale or an acoustic simulation. Test the direct voice, reflected voice and steady noise separately; moving the camera and boom together preserves close microphone placement.

    Compatibility checks before purchase

    Run the pre-stream checklist after drawing the physical plan. Match the exact model, host operating system, port mode and destination.

    Match each model suffix and generation to its manual. If a required cable, mode, included part or operating system is not listed for that exact device, keep that requirement unresolved and choose another route when it is essential.

    • UVC/HDMI distinction: USB file transfer or charging does not prove live UVC video; HDMI needs a clean feed and capture input.
    • Continuous operation: Test the camera and power path for the full intended duration.
    • Working distance: Fixed-focus cameras and lenses need a framing-distance check at the actual desk.
    • Host bandwidth: High-resolution camera modes may require a direct faster USB mode.
    • Mount safety: Verify thread, clamp, stand, cable strain and any motorized camera clearance.
    • Exposure: Confirm the intended frame rate and light level can coexist without visible flicker.

    Connect and configure in this order

    Mount and power the equipment before connecting data cables. Leave slack at camera and microphone sockets, keep power bricks from hanging on ports, and label both ends of any cable that disappears behind the desk.

    Connect one signal family at a time: display, capture or camera, microphone and monitoring, then control. Confirm the operating system sees each device before opening OBS, and select exact device names instead of an unspecified default.

    Build one scene and one monitoring route first. Record representative content and alerts locally, then add secondary scenes, effects and automation only after the file contains the intended picture and every required audio source exactly once.

    • Draw the physical route and label every source, input, output and host port.
    • Connect display passthrough, where used, and prove the display mode before configuring capture.
    • Connect the video source to a direct suitable host port and select its supported capture mode.
    • Connect the microphone or interface, then plug headphones into the output that owns monitoring.
    • Add OBS sources one at a time; disable duplicate global devices or duplicate source audio.
    • Set OBS canvas, scaled output, frame rate and encoder to the selected destination profile.
    • Make a local recording, inspect it outside OBS, then run a private destination test.

    Realistic ways to apply the blueprint

    A seated presenter can use a fixed USB webcam at eye level, a close USB/XLR microphone and one softened light slightly above camera axis. The camera may occupy only part of a 1080p scene, so 4K is optional crop room.

    A standing presenter who moves across a teaching area may value a tracking camera, but must provide free gimbal movement, stable mounting and enough light. Record a full movement pass before relying on tracking live.

    If neither pattern matches, use the cable and port guide to identify the physical links, then return to this blueprint. The related pages webcam versus camera guide, lighting layout guide cover the decisions that commonly change this route.

    Four failure states to diagnose

    Change one variable at a time. Start at the first missing hop in the diagram instead of replacing the most expensive component; a local recording separates a source or routing fault from a destination or network fault.

    • Soft or hunting focus: Set the real working distance, add light and disable unnecessary tracking before replacing the camera.
    • Voice sounds distant: Move the microphone closer, lower room reflections and reset gain for normal speaking level.
    • Light flickers: Test the fixture, power source and regional frequency-related camera setting.
    • Slides audible twice: Keep desktop/media audio on one capture path and remove duplicate application or global sources.

    What to keep, verify and buy last

    Start with equipment already owned. Keep an item when its exact ports and modes cover the route. Mark it conditional when one required fact is unresolved, and blocked when a hard mismatch prevents the signal from reaching its destination.

    Buy connection-critical parts before convenience parts. In this blueprint the first purchase should resolve the earliest blocked framing or camera path decision. A second light, larger control surface or higher camera mode belongs later unless one of the eight decisions identifies it as the actual blocker.

    Match every product label, suffix and generation to the linked record and manual. Family names can hide different cables, software, mounts, host requirements, input counts and capture matrices; count an unlisted included part as a separate purchase.

    Enter current costs when assembling the setup. Compare the complete path, including microphone, monitoring, cables, power and mounts, with the cost of keeping a working route. Buy an upgrade only when it solves a named signal, workflow or reliability problem.

    Five tests before going live

    Run a representative test after the computer has reached its normal load and every intended USB device is connected. A brief preview does not exercise heat, power management, sustained USB traffic or a full audio return.

    Keep the first destination test private or unlisted where available. Inspect the received feed on another device with its volume low enough to avoid sending room audio back into the microphone.

    Save the working OBS profile and scene collection, exact device names, physical port map, output mode and any per-source delay or routing assignment. When a later change fails, restore one known working element at a time.

    Call the result ready only when every required path passes together. A conditional route works only with a named accepted mode, port or workaround; a blocked route is missing a required source or destination and is not ready for a live session.

    Check the distinct OBS Stats counters if the received feed stutters or the rehearsal reports dropped frames.

    • Record several minutes of motion and speech; inspect picture continuity, lip sync and dropped-frame counters.
    • Listen on the creator headphones and in the recorded file; confirm each source is present once and muting works.
    • Exercise the real display resolution, refresh rate and HDR choice while capture remains stable.
    • Trigger scene changes, alerts, guest audio and any control actions used during the session.
    • Run the destination test with upload headroom and confirm the received feed on a separate device.

    Equipment for these connections

    Start with the needed role. Check the complete profile before adding a product to your setup.

    Sources