If your gaming replay is already saved as a video file on the computer running OBS, use an OBS Media Source. NDI is for a different job: carrying a live video source from another computer across your local network.
That distinction matters whether you are streaming from India or elsewhere. The recommendation here follows the documented functions of OBS and NDI; it is not based on hands-on testing, and it makes no claim about how a particular home network will perform.
First decide what “replay” means
“Replay” can mean a clip you saved after a match, a pre-recorded highlight you want to play during a live broadcast, or live gameplay being sent from a second PC. Those are different workflows. Before choosing a source type, ask: is the clip already a file, or is the video arriving live from another computer?
If you have an MP4 highlight on your streaming PC and want to show it between matches, OBS can play that file as a scene source. If you want to capture the last few minutes of gameplay while you are live, that is a recording or replay-buffer task. If the game is running on one computer and OBS on another, you need a way to move the live picture between them; NDI may suit that arrangement.
The distinction is not just terminology. A saved clip needs file playback. A live feed has to cross a connection while it is being produced. NDI is an IP-based video connectivity method that can carry video, audio and metadata between network-connected systems. NDI describes itself as not being a codec, so do not treat the name as a particular fixed file format or universal bandwidth figure. See NDI’s overview of what NDI does.
This article compares the source workflows, not the quality of particular recordings, computers or Indian internet connections. Your local network carries an NDI feed between computers; your streaming software separately sends the programme to YouTube over the internet. For policies around what you broadcast, consult YouTube’s current rules and our practical map of YouTube Creator Policies and Guidelines.
For a saved clip, use OBS Media Source
When a saved highlight is on the same computer as OBS, add it as a Media Source in the scene where it should appear. OBS documents Media Sources as a way to play audio and video files in scenes. You can configure whether playback loops and whether it restarts when the source becomes active, which lets you match behaviour to the role of the clip. The OBS Media Sources guide explains the available controls.
For a one-time replay, you might want the clip to play once and then leave the scene or return to your regular gameplay layout. For a short bumper that should repeat while a scene stays on air, looping may be appropriate. Decide the intended behaviour before going live, then test it in the actual scene: a looped source and a one-off highlight should not be configured as though they have the same job.
This is the straightforward choice for a single-PC creator because no second computer has to send that clip over the LAN. OBS reads the file as a source on the streaming machine. NDI would add a networked-source workflow without solving a problem that exists in this case. A clip played locally does not need NDI.
Keep the source file available at the path OBS expects, and avoid moving or renaming it after configuring the scene. If you maintain a folder of match highlights, use clear filenames so you can identify the intended replay under time pressure. A video source that freezes during an OBS loop is a separate playback reliability issue worth understanding before relying on a repeating clip overnight.
If you want a highlight to be part of a longer, continuous sequence, prepare the order and transitions deliberately. A playlist-style stream has different failure points from a single replay source; our guide to FFmpeg loop streaming for an Indian YouTube channel covers a different tool and operating model, not a reason to add NDI to a local file workflow.
Use NDI for a live source from another computer
NDI is relevant when the source is live and lives on a different system. For example, one PC may run the game while a separate machine handles OBS and the YouTube output. In that arrangement, NDI can carry the live source over the local network so the streaming machine can use it in its production workflow.
That is a different requirement from playing yesterday’s saved highlight. A file is already recorded and can be opened from storage. A second-PC feed is continuously produced and transmitted. NDI can carry video and audio, but it does not itself replace the streaming application or the internet connection used to send the finished programme to YouTube.
NDI’s bandwidth guidance gives up to 150 Mbps for a typical 1080p60 stream. This is NDI’s stated typical figure, not a guaranteed or universal rate for every NDI format and setup. Its documentation also says bandwidth is not deterministic and should be planned around average utilisation. Read the NDI bandwidth guidance for the format and workflow you plan to use rather than assuming the name NDI implies one network load.
A two-PC workflow can keep game processing and broadcast control on separate machines, but it adds components to diagnose: both computers, the NDI source and receiver, the local network, and OBS’s scene configuration. If your only goal is to replay a saved clip, this extra arrangement adds work without a corresponding need. If you need a live feed from a separate gaming PC, it may be useful, provided the network is suitable.
Compare the choices and the network work
The useful comparison is source type and operating complexity, not which label sounds more advanced. The table summarises what changes when you select either workflow.
| Question | OBS Media Source for a local file | NDI for a live remote source |
|---|---|---|
| What is being sent to OBS? | A saved audio or video file on the streaming computer | A live source arriving from another networked computer |
| Is a second PC required for this source? | No | Usually the source is on another system in this workflow |
| What carries the source to OBS? | Local file access on the streaming PC | The local IP network between source and receiving systems |
| Main setup to check | File selection, scene placement, loop and restart behaviour | Source and receiver configuration, network capacity and format requirements |
| Does it send the finished stream to YouTube? | No; OBS’s stream output is a separate step | No; NDI moves the source locally, while streaming software handles internet output |
NDI says gigabit networking is essential in production workflows on its bandwidth page. That guidance makes a wired gigabit LAN a sensible consideration for a high-bandwidth workflow, not a promise that every Wi-Fi setup will fail or that a cable alone resolves all issues. NDI documents wired networking and notes that formats vary in bandwidth and latency; check the requirements of the format you intend to use on NDI’s video technology page.
For a two-PC setup, consider whether the computers connect through the same local network, what other devices share that connection and whether the chosen format fits its capacity. A wired Ethernet connection can be useful where the equipment and layout allow it. A Cat6 cable is an optional way to make a wired connection if your devices and network support the relevant ports; it is not mandatory, and it cannot fix every network or configuration problem.
Multicast is a conditional network consideration, not a setting every creator must change. If your NDI arrangement uses multicast, NDI’s implementation guidance discusses multicast filtering, including IGMP snooping, to avoid unnecessary network burden. Check your network equipment’s documentation and the requirements of your particular setup before changing router or switch settings. See NDI’s performance and implementation guidance.
Choose the simplest workflow for one PC
If one computer runs the game and OBS, and your replay is a saved clip, use a Media Source. The file is already available to OBS, and the controls for looping and restarting address how it behaves in a scene. You do not need a second computer or an NDI feed just to put a highlight on screen.
If you have a two-PC gaming arrangement, decide which system produces the live picture and which system sends the broadcast. NDI becomes relevant if you want the source from the gaming PC to reach OBS on the streaming PC over the local network. Check format and network needs before committing to the workflow, and leave time to confirm that both systems see the intended source.
There is a third case: you are live on one PC and want to save highlights for editing or later playback. OBS’s Replay Buffer is designed to save recent content using a configured hotkey. That is not the same as piping a second computer’s live output into OBS. OBS also documents recording alongside streaming and offline recording in its overview guide and recording output guide. Choose recording controls when your aim is to retain footage, and a Media Source when your aim is to play an already-saved clip.
Your internet upload to YouTube is a separate part of the system. NDI carries a source across the local network; it does not replace OBS’s internet output. For the final broadcast, use YouTube’s current setup instructions and check the stream’s status in YouTube Studio rather than assuming that a working local feed means the internet stream is also ready.
Test the scene before relying on it
A scene can look correct in the editor and still behave differently when you switch to it. Build a short test around the same transitions you expect to use in a broadcast. For a local clip, select the file, activate the scene, watch the beginning and end, then switch away and return to check whether restart behaviour matches your intention.
For a loop, let it reach the end and confirm that the next pass behaves as expected. Listen as well as watch: decide whether the clip’s audio should be heard, whether it should overlap the game or commentary, and whether a separate audio source is already carrying the same sound. If your channel depends on continuous sound between visual elements, the guide to keeping audio playing on a 24/7 YouTube stream is relevant to planning that behaviour.
For NDI, test with both computers powered on and connected as they will be for the broadcast. Confirm that OBS receives the intended live source, that audio is included as intended, and that switching scenes does not leave the wrong source visible. Observe the actual workflow over a useful rehearsal, but do not treat one successful session as proof of future performance under every network condition.
If a source is missing, isolate the question: is the file accessible, is the source active in the scene, is the remote source available, or is the network configuration the issue? Change one thing at a time. That makes troubleshooting less guesswork-heavy than rebuilding the entire scene when only the source path or a network setting needs attention.
Send the finished programme to YouTube Live
Once the scene behaves as intended, configure OBS’s streaming output for your YouTube channel using current YouTube and OBS instructions. OBS’s output is the stage that sends the composed programme over the internet. It is separate from the method used to bring a clip or live source into the scene.
For a local replay, the path is simple in concept: OBS reads the file, composes it with the rest of the scene, and streams the result. For NDI, the path includes another step: the source computer sends video over the local network, OBS receives and composes it, and then OBS sends the finished programme to YouTube. Keeping those paths distinct helps you work out where a fault may lie.
Do not infer YouTube readiness from a successful NDI connection or from a clip playing in the OBS preview. Check that YouTube Studio shows the expected incoming stream and that the intended scene is actually on air. If you are planning a sustained channel rather than a short session, also consider how the computer and source file will remain available; a desktop-based OBS setup depends on that computer continuing to run and the necessary local resources remaining accessible.
If the recurring problem is leaving a computer on just to play a prepared file, StreamNeo removes that specific burden: it turns an uploaded video into a YouTube live stream, so your computer can be off after setup. It is YouTube-only and is intended for uploaded video playback, not for receiving a live NDI source from another PC. That distinction makes it relevant to a prepared-file channel, not a replacement for a two-computer live gaming workflow.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is NDI better than a local file for a saved gaming replay?
No. If the replay clip is already saved on the computer running OBS, use Media Source to play the file. NDI is relevant when a live source needs to arrive from another computer over the network.
Do I need two computers to use OBS Media Source?
No. Media Source can play a local audio or video file in an OBS scene, so the file and OBS can be on the same computer. A second computer matters only if your chosen workflow needs a remote live source or some other separate role.
Does NDI send my stream to YouTube?
No. NDI carries a source between systems on the local network; OBS or other streaming software still handles the finished programme’s internet output. A working NDI feed therefore does not, by itself, confirm that YouTube is receiving the broadcast.
Is Wi-Fi always unsuitable for NDI in India?
The cited guidance does not establish an India-specific rule or say that every Wi-Fi setup will fail. NDI’s bandwidth and format requirements vary, so check the needs of your particular workflow and network; a wired connection is worth considering where practical.