What is NDI video?

Network Device Interface, or NDI®, lets you transmit and receive broadcast-quality, low latency over existing LANs using cost-effective CAT5/6 cables and the quality is virtually lossless.

NDI allows the flexibility to choose from a wider variety of video input sources. Across the same network, you can access multiple cameras, software on computers, mobile devices, and more on the network using a single LAN port. No expensive multiple-port HDMI switches or SDI routers are needed.

The number of NDI sources you can add to your network is practically limitless. To access NDI devices across subnets, you can manually enter the IP address of devices on those other subnets using NDI Access Manager.

With NDI, taking your video production to a different location is a lot simpler without a whole mess of HDMI and SDI cables to manage. All your video sources are readily accessible from anywhere over the network. CAT5/6 cables are also a lot cheaper than traditional SDI or HDMI cables.

NDI and network bandwidth

High Bandwidth NDI, as the name suggests, uses a lot of local bandwidth to share audio and video. This is because the protocol transmits high-quality, low latency, uncompressed video streams that are virtually lossless. Every pixel captured by the camera’s sensors is sent without any reduction – resulting in a lot of data.

Transmitting uncompressed video, especially at higher resolutions, requires at the very least a Gigabit network, though the ideal transfer speeds ultimately depend on the number of concurrent High Bandwidth NDI streams.

A single 1920×1080@30 fps NDI stream needs approximately 100 Mbps of dedicated bandwidth.

The bandwidth required will change, however, depending on the resolution, framerate, and how much motion is being captured by the camera. For example, a 1920×1080@60 fps NDI stream requires 150 Mbps. Meanwhile, a 4K@30 fps NDI stream is roughly 250 Mbps.

It’s recommended to leave approximately 25 percent of headroom so that the signal remains smooth just in case any unexpected network traffic pops up during production.

So, if you have three PTZ cameras sending their video to an Epiphan Pearl-2 at 1920×1080@30 fps, that’ll cost you approximately 300 Mbps of bandwidth. If the Pearl-2 is also outputting the NDI stream in 4K, that puts your bandwidth at 550 Mbps. Reserving 250 Mbps for the suggested headroom, three sources and one output already totals 800 Mbps, just enough for the Gigabit network to handle the transfer

High Bandwidth NDI vs. NDI|HX

There are two variations of NDI to work with: High Bandwidth NDI and NDI|HX.

Both are great options for transmitting video and embedded audio signals across a local network, the main difference between them being compression and latency.

High Bandwidth NDI is uncompressed and requires a lot of bandwidth to transmit. NDI|HX is the high-efficiency alternative, functioning almost exactly the same way but requiring significantly less bandwidth thanks to the advanced compression  – making it an ideal choice for any environment where bandwidth is limited. The high efficiency of NDI|HX will add some latency compared to the High Bandwidth version, but at most, it’s only a frame or two. Audio is uncompressed in both High Bandwidth NDI and NDI|HX.

Here’s how much dedicated bandwidth is recommended for NDI and NDI|HX:

• A single 1920×1080@30 fps High Bandwidth NDI stream needs at least 100 Mbps of dedicated bandwidth
• A single 1920×1080@30 fps NDI|HX stream needs 8 Mbps of dedicated bandwidth

It’s worth noting that these figures are estimates and the actual bandwidth required will vary based on resolution, framerate, and motion.

NDI|HX allows creators to take advantage of almost identical, exceptional quality without worrying so much about bandwidth availability. Of course, the bandwidth available should always be something to consider, but NDI|HX was designed to work over low-bandwidth networks.

Available NDI tools

More and more software applications like Zoom, Microsoft Teams, Skype, NewBlueFX, EasyWorship and others offer native NDI support.

To help spur adoption, there are free NDI plugins for popular applications like VLC and Adobe Creative Cloud. For all the rest, NDI offers simple-to-install free tools. For example, NDI Screen Capture lets you turn a computer into multiple NDI inputs that any other NDI device on the network can access. You can define live video sources like the computer’s webcam, the full-screen display, different windows or combination of windows. Even different software applications running on that computer can be converted into an NDI input.

A couple more options include the NewTek NDI Connect and the NDI|HX Camera app (available for a nominal fee). NewTek Connect makes any camera or device connected to a computer’s capture card (or the local webcam) available to other NDI systems on the LAN. And NDI|HX Camera converts the output from iOS devices and Android phones into NDI video inputs. If you want to take your content further and out onto the WAN, consider using SIENNA Cloud for NDI.

The many free tools and flexible options that are available are definitely helping to drive adoption.

NDI adoption

Adoption of NDI is spreading since its introduction to the public early in 2016. Designing NDI into your AV system is getting easier as more hardware and software options become available. There are also more NDI enabled cameras to choose from companies like PTZOptics, or Panasonic, as well as full-featured video production systems like the Epiphan Pearl-2 that support NDI and NDI|HX. Additionally, Pearl Mini can support up to two NDI|HX inputs, making it a perfect choice to build a small studio.

If you already have existing cameras and AV equipment, NDI is still within your reach. You don’t have to make a huge commitment to switch over all your gear. NDI converters are readily available. These converters connect existing NDI unaware HDMI or SDI video sources to the network – and convert NDI into HDMI signals for your average monitor or video projector. NDI converters range in price and features. For example, the BirdDog Mini offers 1080p60 NDI encoding, 1080p60 NDI decoding, tally, and power over the Ethernet.

Practical NDI applications

Here are some practical ways you can start using NDI.

NDI for live events

Using NDI can offer several advantages when capturing live events such as lectures, conferences, or performances.

NDI eliminates the need for cabling, which can be challenging to set up and manage. By connecting cameras and other devices to an all-in-one production system like the Pearl-2 or Pearl Mini, everything you need to stream or record the live event is acquired in less time and in a much more organized fashion.

If the live event uses presentation software like Microsoft PowerPoint, this can easily be added to the LAN using the free NDI Screen Capture or NDI Screen Capture HX. With this app, the presentation computer becomes another NDI input for your video production system to ingest. It can be added to Pearl-2 or Pearl Mini like any other NDI or NDI|HX source, recorded, streamed, and switched between as needed for the production.

Certain venues won’t have the network bandwidth required for an effective NDI production. It is possible to work around this, however. With NDI Bridge, you can securely connect two entirely different NDI networks from anywhere in the world. This is particularly useful for remote production workflows or transmitting signals to other locations.

Adding remote guests to broadcasts with NDI

Adding a remote guest to a live production was once a tricky proposition. However, with the addition of NDI-out to all major video conferencing apps such as Microsoft Teams, Zoom, and Skype, it’s possible to bring the remote guest’s audio and video to your production tool or system of choice.

When enabling NDI-out on Microsoft Teams, Zoom, and Skype, the feeds can be ingested by Pearl-2, allowing you to switch, record, and stream video with these remote sources as well as any physical input available. Create interesting layouts with NDI inputs using the built-in custom layout editor and add text, custom backgrounds, and transparent images.

NDI and NDI|HX FAQ

Is NDI free?

Yes! NDI is free to use. Costs only come from acquiring the hardware or software licenses. But the ability to access NDI is free.

Should I use a hardware or software encoder with NDI?

While software encoders have advantages, the reliability and performance of hardware encoders make a huge difference when working with NDI.

Software encoding needs computers with state-of-the-art GPUs and ample memory to operate efficiently in an NDI workflow. If the computer doesn’t meet these high standards, it may crash or freeze while trying to process the uncompressed video. Software encoding also has been known to add latency to the NDI feeds.

Hardware NDI encoders, like the Pearl-2 or Pearl Mini, were designed explicitly to encode video, obtaining high-quality video and audio with no additional latency or competing programs.

How do I find my NDI sources?

There are a few ways to find your NDI sources. It depends on the devices being used.

If you’re using an NDI camera, start by logging in to the camera’s interface and making sure NDI is enabled. Once enabled, you can check the stream using NDI Studio Monitor.

The NDI discovery server, available in the NDI Software Developer Kit, can help you find your NDI sources as well. The NDI discovery server automatically discovers NDI sources on the network and provides a list of available sources that can be accessed by authorized users without having to manually search for their exact network location. To make sure each user has the appropriate access to NDI devices on the network, the NDI Access Manager app allows network administrators to set permissions and control access.

How do I connect my NDI sources?

If you’re connecting an NDI source to a Pearl, access the device’s admin panel.

In the Inputs menu, click Add input. The Add input page will open with all available NDI resources listed.

If it’s there, you can press Add and your NDI source will be connected to Pearl. If you don’t see it, enter either the “Group name” if it’s been assigned a group or the IP address of the NDI device in the “Extra source IP addresses” field to discover and receive the signal.

How does NDI transport audio?

Although NDI is commonly associated with video sharing, it can transport both video and audio over networks.

NDI can transport up to 16 channels of uncompressed, high-quality, low latency, 48 kHz, 24-bit audio data in the same stream as video in three ways: embedded audio, analog audio, or digital audio.

The most common way of transporting audio via NDI is by using embedded audio. With embedded audio, the audio data is carried within the video signal, making it easier to keep the audio and video in sync and allowing multiple audio channels to be carried within a single NDI stream.

To transport analog audio via NDI, it must be connected to a physical, NDI-enabled device like a mixing console that converts the analog audio to digital.

Transporting digital audio via NDI can be accomplished with the Audio Direct tool. This set of Virtual Studio Tools (VST) audio plugins allows virtually any audio software to select, receive, and generate multichannel audio.

Wrap up

NDI opens up new opportunities to make your live video production workflow easier and more flexible. You can save money on cables and infrastructure by using the existing Ethernet network and gain easy access to a lot more video sources at broadcast quality. There are free plugins and tools to help you start incorporating NDI into your current AV system right away.

If you’re considering a new AV system and want to start taking advantage of the benefits of NDI, an all-in-one video production system like Pearl-2 makes a lot of sense. Pearl-2 accepts multicast and unicast NDI sources, as well as high-efficiency NDI|HX. Pearl Mini also accepts NDI|HX, allowing to work with any NDI|HX source in low-bandwidth settings.

With Pearl-2 or Pearl Mini, you can bring in video and audio from a multitude of different NDI and NDI|HX sources, such as:

• Remote NDI-enabled PTZ cameras
• Any NDI-unaware HDMI/SDI source using a converter or the free NDI Virtual Input software
• Webcams connected to remote computers using the free NDI Connect application
• Output from iOS and Android mobile devices using the NDI Camera app
• Direct input from NDI-compatible software (Zoom, Microsoft Teams, Skype, EasyWorship, etc)

NDI output from Pearl-2 is recognized as a webcam and is compatible with other NDI applications and devices that support webcams as an input, like Skype and many more.

Network bandwidth

The first step when using NDI is to assess the available bandwidth on your local network. Regardless of the NDI encoder’s make, model, or features, the encoding can only be performed to its full potential if the local network can transport the signals.

At a minimum, the workflow should be running on a Gigabit network – throughput speeds, full duplex ports, and upstream and downstream data speeds must all be capable of transferring the data. Insufficient bandwidth can negatively affect the final product – dropped frames, frozen video, audio glitches, and sudden disconnection.

The general rule of thumb is to reserve 25 percent of bandwidth for headroom so that the signal transmission remains smooth should there be any unaccounted for traffic while your production is underway. So, if a Gigabit network isn’t doing the trick, consider upgrading to a 10 Gigabit network.

A typical High Bandwidth NDI stream at 1920×1080p@30 fps needs approximately 100 Mbps per stream. But the bandwidth required to use NDI effectively will vary depending on the number of video sources, the resolutions, and the frame rates. Ultimately, the bandwidth required is unique to the video production at hand, making it wise to test the network if possible.

In 2016, one year after High Bandwidth NDI was released, a high-efficiency version of the IP-based solution called NDI|HX was released. It was specifically designed to work on low-bandwidth networks.

One 1920×1080p@30 fps NDI|HX stream needs approximately 24 Mbps, making it highly versatile. However, the efficient compression used by NDI|HX does add some latency to the stream. The added latency varies depending on the device, frame rate, and resolution, but it’s typically not more than one or two frames of delay – hardly noticeable to the eye or ear.

NDI and NDI|HX bandwidth recommendations

Hardware over software

When choosing any encoder – and NDI encoders are no different – we always face the same question: hardware or software?

Software encoders have their benefits in certain situations, but the performance and reliability hardware encoders offer compared to software alternatives are essential for an NDI production. Software encoding can be resource-intensive, requiring very powerful computers with state-of-the-art GPUs and plenty of memory to run effectively in an NDI workflow.

Unless one or several computers already meet the requirements of processing NDI’s high-quality, low-latency video, encoding software can crash mid-record or stream. At best, the software encoder will add latency to the NDI feeds, undermining one of the biggest benefits of the solution. Determining a system’s requirements to run an NDI software encoder effectively may be challenging as it can vary depending on the content being produced.

A hardware NDI encoder is an investment in performance and reliability. Optimized from the ground up to encode video, acquiring high-quality and audio inputs with no added latency and no other competing programs makes hardware a wise choice.

Multi-encoding support

Multi-encoding is the process of encoding one or more inputs multiple times with different settings. As a result, you have a wealth of redundancy by capturing all your assets simultaneously at different resolutions, bitrates, and frame rates. For example, you can send a 720p@30 fps live stream to a media server while saving a 1080p@30 fps recording to the device’s internal storage.

Depending on the encoder, multi-encoding support can offer far greater depth than just encoding at different settings. Hardware encoders that feature multiple programs or channels can encode assets independently of the content being shared. For example, if your hardware encoder allows for content to be mixed and switched within the device, you could have several layouts streaming a 720p@30 fps to a media server in one channel, a 1080@30 fps recording saved to internal storage, and ISOs of each video asset recorded in separate channels as additional backups.

This is particularly useful any time you are streaming live events where there are no second chances. Should the stream stutter or fail, you have the recorded backup with its layouts, but you can also work off individual camera feeds to create a produced broadcast.

Input versatility

While NDI has many advantages, keeping your options open and having plan B’s readily available is always a good idea in video production. When searching for an NDI encoder, a device that can accept networked signals and physical cables ensures you can create the best possible video in any circumstance.

When an encoder can accept HDMI, SDI, and NDI or NDI|HX equally, you can stream and record your content regardless of the network’s condition. Plus, you eliminate the need to add converters for any incompatible hardware. But the most significant benefit is that physically connecting certain devices can help keep the network clear to acquire the essential NDI signals with greater reliability. On the other hand, putting every device on the same network could cause network congestion.

Be prepared for any situation with an NDI encoder that works with everything.

Remote device management

An NDI encoder sits at the heart of your workflow. As such, if it’s interrupted in any way, it can grind your video production to a halt.

Whether dealing with a single or several NDI encoders, it’s essential to have the chance to access it from anywhere and mitigate any downtime. Remote device management is an extraordinary asset for any NDI encoder.

By accessing it in the cloud or receiving customized alerts from 24/7 monitoring, you can take corrective action immediately and begin troubleshooting from anywhere.

When a device malfunctions, it’s stressful for all stakeholders. Giving yourself the convenience and flexibility to manage the device remotely in these high-pressure situations is insurance against production interruptions.

Interoperability

On top of delivering high-quality video with greater convenience, NDI’s rise to prominence can also be attributed to its interoperability. As an open standard protocol, it’s publicly available to anyone, allowing any hardware manufacturer to implement it.

When choosing an NDI encoder, selecting a device that shares NDI’s commitment to compatibility will make it a seamless fit in almost any situation.

Integrations with content management systems like Kaltura or automation controls like Creston or Q-SYS can make your productions vastly more efficient and easier to use. Devices with an open API allow owners to customize the hardware to suit their exact needs, further optimizing the exact workflow.

Investing in an NDI encoder that can’t complement the systems already in place, either with built-in integrations or through the open API, can lead to frustration, downtime, and even the complete overhaul of video tech stacks.

To take full advantage of the quality NDI offers, a device that works with virtually everything, like NDI itself, is a huge boon for integrators.

The best NDI encoders: Epiphan Pearl-2 and Pearl Mini

The award-winning Epiphan Pearl production systems, known for their reliability and versatility, can be featured at the center of your NDI workflows.

Pearl Mini accepts two NDI|HX inputs, allowing you to connect high-quality, low-latency video more efficiently over your local networks.

Pearl-2 allows users to receive up to six NDI|HX, up to three High Bandwidth NDI inputs, and output 1080p@30 fps High Bandwidth NDI or one 4K@30 fps High Bandwidth NDI stream.

Discover what Pearl can do for your NDI workflows.

Built to adapt to any network conditions

Unlike NDI’s reliance on high-speed, local networks to achieve low latency video, the Secure Reliable Transport (SRT) protocol is designed to deliver broadcast-quality content over any network conditions.

Created with resilient error correction to compensate for packet loss, bandwidth fluctuations, and other connectivity issues, SRT is better suit to share content over the Internet. That’s why Epiphan Connect extracts isolated audio and video feeds from any Microsoft Teams meeting and makes them shareable via SRT.

By using SRT, a protocol that was built to adapt to the unpredictability of public Internet, Connect removes a huge barrier of Microsoft Teams’ NDI-out feature. Once the feeds are isolated, simply place them into any SRT-enabled production tool like vMix and you’re free to start creating. No need to redo your local network infrastructure. Connect is ready to work as soon as you create an account.

Powered by cloud

When using Epiphan Connect to get video and audio from Microsoft Teams to vMix, local hardware and networks aren’t responsible the extraction process. That all happens in the cloud.

The isolated video and audio feeds are securely received directly from Microsoft servers and made available via SRT in your Epiphan Edge account. Because all the heavy lifting is done by servers built for scalability, the resolution of the extracted video is much higher than a standard call: up to 1080p.

Rather than make your computer do all the work generating, acquiring, and streaming, you can rest easy and let powerful servers shoulder some of the heavy load. This frees your system up for better performance for the actual production.

Isolated audio with a single click

Though Microsoft Teams NDI may deliver broadcast-quality audio, the audio feeds leave a lot to be desired. Whether selecting the primary speaker stream or individual users, the incoming audio is always mixed together. A single track for multiple is an audio engineer’s worst nightmare as it’s impossible to mix.

When you use Epiphan Connect to add Microsoft Teams to vMix, you have the option of isolating each speaker’s audio. Simply select the “Isolated Audio” when the extraction begins and then you’re free to start, stop, and mix each participant’s audio inside vMix.

Virtual confidence monitoring

If you have ever joined someone else’s vMix project as a remote guest, you’ve no doubt felt a bit disconnected from the show. Despite a producer’s best efforts to keep you in the loop, nothing quite compares to seeing the finished product right in front of you.

With Epiphan Connect, you can help remote guests stay involved in the action the virtual confidence monitor. By enabling the return feed in Connect’s admin panel, a live look at the broadcast is added directly to the Microsoft Teams meeting. Guests can easily see the layouts, switches, and everything else the audience is seeing to keep the broadcast flowing seamlessly.

A more reliable way to join

vMix users already know that the f has a built-in feature to get guests into a project known as vMix Call. This feature, however, is only available with the HD, 4K, and Pro vMix licenses, which cost $350, $700, and $1,200 USD respectively.

Some users may prefer the native Call feature to live stream with guests, but this method is not without its challenges. For example, vMix Call doesn’t allow participants to share their screens, limiting how guests can contribute to the show. But the biggest issue is actually getting guests to join.

It’s very common for firewalls to block vMix Call. This can be solved if you have time to do extensive testing and loop in the IT department as needed. But the time to test the vMix Call with guests and the IT team may not always be available.

Rather than gamble your project’s success on the IT department’s availability, it’s far safer to lean on Microsoft Teams. It’s an app available on every device and trusted by IT professionals around the world.

Adding a Microsoft Teams to vMix with Epiphan Connect

To take advantage of the stream stability, improved video quality, isolated audio, virtual confidence monitor, and streamlined guest experience that Epiphan Connect has to offer, follow these steps:

Step 1: Log in to Epiphan Edge, select Epiphan Connect, and add the Microsoft Teams meeting URL.

Has NDI been enabled in Teams?

It may seem obvious, but the most common issue creators have with Microsoft Teams NDI is that it hasn’t been properly enabled. If you can’t find the purple “Broadcast over NDI” button in Teams then this may likely be your issue.

To enable NDI in Microsoft Teams, you – or whoever serves as your organization’s Microsoft administrator – must first access the Microsoft Teams’ client.

Start by entering the Microsoft Teams admin center. Select “Meeting policies” under the “Meetings” tab on the lefthand menu.

In the “Meeting policies” menu, click “+ Add” and scroll down to the “Audio & video” section. Find the “Allow NDI streaming” button and toggle it on. Save the policy.

Once the policy has been saved by the Microsoft admin, you can now go into Teams, select the three dots next to your profile picture and choose Settings. In the Settings menu, select the Permissions tab and toggle on Network Device Interface (NDI).

Start a Microsoft Teams meeting, select More actions and click the purple “Broadcast over NDI” button.

If the option to broadcast over NDI still isn’t available, the issue may be your operating system. The NDI function is not currently supported on M1 Macs.

Are you meeting the hardware requirements?

If you notice frames dropping or your system keeps crashing, it’s possible that your hardware is not powerful enough to run Microsoft Teams NDI. NDI can be extremely taxing for certain systems’ CPU usage. Microsoft support even recommends “…limiting the number of NDI®-out video streams to two or three on any single computer” for maximum performance.

With the right hardware, the NDI broadcast should only be taking up about 50% of your CPU. However, some creators report that running NDI causes their CPU to spike up to 90% usage. When all that memory is being used up, overheating, freezing, and crashes are commonplace. To ensure your record or stream can be completed, keep an eye on how your computer is managing its resources.

To check this, start a Teams NDI broadcast. On a Windows PC, open “Task Manager.” In Task Manager’s “Processes” tab, check to see the CPU usage on Microsoft Teams. If it’s hovering above 50% – your hardware could use an upgrade.

There are a couple of ways you can approach the hardware upgrade. You could shop for a new computer. A PC with an Intel i5 Sandy Bridge CPU or better with integrated NVIDIA discrete GPU with 2 Gb video or more as well as 8 Gb of system memory ought to do the trick.

Alternatively, you could rely on a hardware production system that supports NDI – like the Pearl-2 – to do the heavy lifting. A hardware production system is more reliable than the average computer because it was built specifically to encode and decode all manner of video signals. Whereas the most powerful computer available was built for a variety of tasks, including everything from processing video to keeping dozens of browser tabs open.

Either way, if your CPU is approaching 90% usage when broadcasting NDI from Microsoft Teams, your current setup can’t handle the labor-intensive requirements. If upgrading your hardware is out of the question, you can always look into an SRT-based alternative.

Are you meeting the bandwidth requirements?

If your PC’s CPU usage looks fine and you’re still dealing with dropped frames, freezing, and all-out crashes, then there’s just one culprit left: your local network.

NDI video consumes a lot of local network bandwidth. A single 1920×1080 NDI stream running at 30 fps needs at least 125 Mbps of dedicated bandwidth. And that’s just a single example. Higher framerates, higher resolution, and more streams will require more bandwidth.

Ideally, you should use a Gigabit Ethernet connection when working with any NDI stream. Public Internet or networks just don’t have the stability to handle transporting low-latency video. So, if it’s a bandwidth issue, you may need upgrade the existing infrastructure – look into wiring, switches, and anything else you’ll need to maximize the transfer speeds needed.

If you have the fastest network available, it could be that other people are clogging the network with their own activity. If that’s the case, it may be as simple as telling the other people on the network to cease their uploads and downloads until after the recording or stream concludes.

An alternative to Microsoft Teams NDI: Epiphan Connect

Microsoft Teams’ NDI feature is just one method of getting high-quality, low-latency video signals from the communication app. Another way to get the video you need from MS Teams – which doesn’t require a computer or network upgrade – is Epiphan Connect.

Epiphan Connect is an accessible alternative to Microsoft Teams NDI because the onus is not on your local network or system. The extraction happens in the cloud, freeing up your hardware and bandwidth to do the actual recording or streaming.

Once Epiphan Connect has been added to your Microsoft Tenant by the administrator, you can add it to any Microsoft Teams meeting. Just login to Epiphan Cloud, select the Epiphan Connect button on the left-hand side and click on the green “Connect to a meeting” button. Enter the Microsoft Teams meeting URL, select your audio preferences, and then hit “Connect & Join.”

After Epiphan Connect joins the Teams meeting, each participant’s video and audio will be available as SRT streams. SRT was specifically designed to deliver media across unpredictable public networks. It’s becoming increasingly popular with broadcasters because it’s a cheaper and logistically simpler alternative to satellite trucks and private networks.

The SRTs can be added to any production tool that supports the protocol – which almost all do. Because the extraction performed by powerful servers, the video resolution will be higher than a typical Teams call – up to 1080p. You can control and customize the resolution as desired, as well as select your preference between mixed and isolated audio.

NDI is no longer the end-all and be-all of getting exceptional video signals from Microsoft Teams. Now, thanks to Epiphan Connect, there’s a much more feasible of getting great video and audio from the app. One that doesn’t have such strict hardware and network requirements to work.

An easier way to connect Microsoft Teams and OBS

Before Epiphan Connect, using OBS to capture, record, or stream a Microsoft Teams meeting could be a tricky proposition. There were a few different methods available such as installing virtual camera plugins or ingesting Microsoft Teams’ NDI-out. But these methods had their risks given the strain they put on operating systems and networks.

Thankfully, Epiphan Connect doesn’t rely on local hardware or monopolize network bandwidth to provide OBS users with high-quality, stable signals for their production. All the heavy lifting is done by the cloud, enabling OBS users to focus on the actual content of their recording or stream rather than mitigating technical difficulties. And freeing up your CPU and network to run the actual production is just the start of why Epiphan Connect is a more reliable solution when using OBS and Microsoft Teams together.

But alleviating the load on networks and hardware is just the beginning. Here are three more reasons why Connect is the perfect link between OBS and Microsoft Teams:

Improved video quality

A common complaint about using OBS’s virtual camera to capture Microsoft Teams content and participants is the low video quality. There are typically two explanations for why the virtual camera looks blurry or laggy:

• Your PC lacks the horsepower to run multiple virtual cameras at 1080p or 30 fps along with all the other programs and media supporting the production, causing it to drop frames and compromise quality.
• An issue within your network connection, such as low bandwidth, may be causing packet loss in the incoming video feed, resulting in dropped frames, jitter, or low resolution.

And while you may be able to resolve these issues by adjusting the virtual camera settings, buying a new computer, or calling your Internet service provider about a plan upgrade, Epiphan Connect bypasses these common issues by doing the hard work of extracting a video signal in cloud servers.

Epiphan Connect isolates participant and screen share video feeds in Microsoft Teams and sends them to the cloud. The feeds are received directly from Microsoft servers so at no point in the process are you relying on local hardware or network bandwidth for the signal. This allows Connect to capture a clean image in a much higher resolution than a standard call: up to 1080p. And because the isolated video feeds are sent in Secure Reliable Transport (SRT), you don’t need to worry about packet loss or jitter. Learn more about what makes SRT protocol for streaming a reliable way to send video.

Isolated audio

Clean audio is nearly impossible to achieve when relying on OBS’s Virtual Camera feature to capture Microsoft Teams content. Even with the Virtual Audio Cable plugins available for OBS, it’s only possible to receive a single, mixed audio track featuring all participants. There’s no real way of controlling individual audio feeds, leaving the door open for a crowded sonic experience.

Even if you are working with experienced guests who have developed a keen sense of timing and tact, there’s no guarantee you’ll get a good balance of their audio. You may find yourself mixing the audio live during the stream to compensate for guests who are too loud or too quiet, which can be risky.

Rather than rely on live sound mixing or guests’ audio competency, take control of the audio with Epiphan Connect. It allows you to capture isolated audio feeds from each participant. You can take full control over who the audience hears, balancing their levels perfectly well in advance, in separate tracks. Anyone who works in video will tell you that sound is just as – if not more – important than video, and Connect makes participant audio capture easy.

Virtual confidence monitor

Getting guests to join your OBS project via Microsoft Teams is incredibly convenient. It’s free, familiar, and available on all devices. But when using NDI or OBS’s Virtual Camera to get their Teams feeds them into the production, they can sometimes feel disconnected from what’s happening in the show. This can sometimes lead to guests missing their cues, not realizing they are live, or skipping over important content.

Epiphan Connect can help remote guests stay involved in the action with the virtual confidence monitor. By enabling the return feed in Connect’s admin panel, a live look at the broadcast is added directly to the Teams meeting. Guests can easily see the layouts, switches, and everything else the audience is seeing to keep the broadcast flowing seamlessly.

Enjoy the freedom and flexibility it provides while elevating the production value of any OBS project that features remote guests.

Add MS Teams to OBS in 3 steps with Epiphan Connect

Sign up for an Epiphan Cloud account and register for Epiphan Connect.

Add Epiphan Connect to your Microsoft Tenant. If you are not the Microsoft administrator, get in touch with the person who is and ask them to add Epiphan Connect.

Once Epiphan Connect has been added, follow these steps to use Microsoft Teams with OBS.

Step 1: Add Epiphan Connect to the Teams meeting and copy the SRT URLs.

Why your next launch event should be virtual

As exciting as it can be to browse around for theaters, convention halls, or rooftop terraces, it may be more advantageous for your brand to host the event virtually.

Increased reach

Only a handful of brands have a following dedicated enough to fly across the country to attend the latest launch. When all the audience has to do is click a link, attendance goes way up. You can now spread awareness to customers wherever they are.

Flexibility for guest speakers

Even with the incentive of an all-expenses-paid trip to your city, some guests simply won’t be able to fit your event into their busy schedules. By making the event virtual, their three-day commitment becomes a 15-minute appearance, which is far more feasible and appealing to those high-powered, in-demand influencers that can bring extra attention to your event.

Seamless engagement

Chats, polls, and other interactive elements allow the audience to actively participate in the action without disrupting the show’s flow. Their real-time reactions are an invaluable resource. It’s a finger on the pulse allowing you to get to know your audience better for future ventures.

Cost-effectiveness

Renting a venue is expensive. The space itself is always costly, but there are additional, sometimes hidden costs to consider, like flying guests in, catering staff, AV support staff, stage design, printed materials, or gift bags. Virtual launches may still require some professional assistance, but the labor and associated costs will be significantly lower.

Hosting a virtual product launch event

If you’re ready to engage customers worldwide and create some big buzz around your upcoming release, follow these steps to create an unforgettable virtual event.

Workshop the story you want to tell

How do you get the audience excited? How do you make this event memorable? What would you like reporters to say after the event? It all starts with figuring out what you want to say.

Thankfully, by now you have unique value propositions for the latest release. The key now is to distill those value props down to a digestible, compelling message.

Follow-ups and VoD

There’s a certain “you had to be there” to an in-person launch. Even if it’s recorded, when it’s over, it’s over. Virtual events, on the other hand, tend to be a little bit more permanent thanks to their accessible nature. Anyone with a link can feel like they are a part of the action even if it’s been months since you went live.

While the live show is great for those who can attend, the video-on-demand of the event’s stream might get 10 times the views with the right promotion, keywords, and tags. Send out follow-up emails, post links to social media, and leave no stone unturned to make sure you’re taking advantage of the longer shelf-life this format affords.

Unlock the full potential of virtual events

Product launches are special occasions that don’t come around too often. However, that doesn’t mean you can’t apply the strategies and tips discussed above to other kinds of virtual events. They may not require the same level of planning or promotion, but any virtual event can help galvanize customers into a real community.

All it takes is your creativity. And with Epiphan Connect and Microsoft Teams, you’ll be able to execute your vision from anywhere with trust in the stability and ease these tools provide for virtual events.

Quick-look comparison

Isolated speaker screen-capture

Effort level: Triathlon

Feasibility: How much gear you got?

Results: Decent, with a high risk of failure

Setting up an isolated full screens:

• Start your Microsoft Teams call
• On separate computers, pin and fullscreen the individual speakers, creating the equivalent of an independent video signal
• Capture the separate speakers’ feeds using a hardware encoder or streaming software
• Crop, mix, and switch between sources, add lower thirds or graphics in your production tool of choice

MS Teams NDI

Effort level: A steep hike

Feasibility: Very doable with admin access and available hardware

Results: High quality in controlled environments  

How to enable NDI in Microsoft Teams:

• Start your Microsoft Teams call
• Check the settings to make sure NDI broadcasting is enabled. Contact your Microsoft Teams administrator if you don’t see it available
• Click the “Broadcast with NDI” button
• Make sure your hardware or software encoder is connected to the local network.
• Add the speakers’ NDI feeds to the encoder
• Crop, mix, and switch between sources, add lower thirds or graphics in your production tool of choice

Epiphan Connect and MS Teams

Effort level: A walk in the park

Feasibility: Cloud efficiency for greater flexibility

Results: Highest quality and vastly simplified setup

How to use Epiphan Connect:

• Create an Epiphan Connect account and pair it to your Microsoft Teams account
• Paste the MS Teams meeting URL in Epiphan Connect
• Epiphan Connect bot joins the meeting
• Connect isolates each participant and screen share into separate feeds
• Pull the participants’ isolated feeds into your production tool of choice (check out Epiphan Unify if you want to produce from the cloud)
• Crop, mix, and switch between sources, add lower thirds or graphics in your production tool of choice

What is the SRT protocol?

SRT is an open-source video transport protocol developed by Haivision. SRT stands for “Secure Reliable Transport,” which reflects two of its major benefits for video and audio streaming: security and reliability.

The goal of SRT is to deliver high-quality, low-latency video streaming over unpredictable public networks, which it does by:

• Offering unparalleled control over video and audio transmission, including the ability to adjust latency, buffering, and other key parameters to suit network conditions
• Incorporating a unique, bi-directional User Datagram Protocol (UDP) stream that continuously sends and receives control data during streaming
• Compensating for packet loss, jitter, and other threats to quality based on UDP stream data

SRT is shaking up not just the realm of Internet streaming but the broadcast world as well. That’s because SRT technology can replace costly (and logistically problematic) satellite trucks and private networks for many remote video applications. Think reports from the field and contributions from guests in another city, country, or continent.

Is SRT better than RTMP?

From a technological standpoint, yes, SRT is superior to the Real-Time Messaging Protocol (RTMP). A lot of it comes down to the fact that SRT is a more modern protocol. Ready for a little history lesson?

RTMP was created way back in the early 2000s primarily as a way to stream video, audio, and data from servers to Macromedia’s Flash player. When Adobe acquired Macromedia in the mid 2010s, along with RTMP, the company repurposed the protocol for broader streaming. Ultimately, RTMP served its purpose. But it’s just not cut out for many modern streaming contexts.

So, what sets SRT apart from RTMP? Built into SRT is a unique, bi-directional UDP stream that continuously sends and receives control data during streaming. Through this, SRT can adapt to fluctuating network conditions to minimize packet loss, jitter, and other threats to quality. This makes the protocol a viable solution for sending video over the worst networks, or unpredictable networks such as the public Internet.

Is SRT secure?

SRT is a highly secure streaming protocol. It’s what puts the “S” in “SRT,” after all.

The SRT protocol offers up to 256-bit Advanced Encryption Standard (AES) encryption, safeguarding data from contribution to distribution. And the protocol plays nice with firewalls. Multiple handshaking methods and flexible network address translation (NAT) traversal mean there’s rarely a need to ask a network admin to make policy exceptions, or engage one in the first place.

Who uses SRT protocol?

Since its invention by Havision in the early 2010s, SRT has quickly become the go-to streaming protocol for remote contribution. For example, NASA uses SRT to distribute live video across control rooms for low-latency, real-time monitoring. One of the largest demonstrations of SRT’s potential was the 2020 virtual NFL draft, where producers used SRT to deliver more than 600 live feeds.

Beyond high-profile examples like these, there are the countless content creators that have made SRT a key part of their video production workflows. That includes Epiphan: the SRT protocol is involved in the lion’s share of live show episodes, webinars, and other live productions we do.

What do you need to use SRT?

You’ll need solutions that can encode and/or decode the SRT protocol, depending on your application. Any remote guests will need an SRT encoder on their end to send an SRT signal over the Internet to the production encoder, which can then decode the signal and work with it for production.

How is SRT latency calculated?

There’s a bit of a learning curve with the SRT protocol, specifically when it comes to the latency tuning mechanic. If you’re wrestling with this side of it, no worries. Here, we’ll break it down step by step.

Master SRT with award-winning solutions

Epiphan Pearl hardware encoders fully support the SRT protocol. Pearl systems feature multiple built-in inputs for video and professional audio, simplifying setup by letting you directly connect advanced video and audio gear for the highest-quality SRT streams. Plus, end-to-end control through Epiphan Cloud makes it possible to configure and test contribution encoders located anywhere in the world. This reduces the chance of errors and simplifies production for everyone involved.

Learn more about SRT protocol support on Pearl systems on our website. And be sure to stay up to date on Epiphan Unify, a new cloud-powered video production platform that will work with any SRT-capable encoder or camera.

1. Get that background sorted out

Think about what your viewers will see in the shot besides you. You want your background to be simple yet aesthetically pleasing. Things like large bookshelves, plants, and brick walls always look great. Avoid busy backgrounds, and eliminate distracting elements.

Make sure the background is nice and tidy – especially if it’s a shared-use space or you’re working from home. The last thing you want is to discover a rogue pair of socks in the frame after you’ve finished filming. Be sure to check all surfaces visible in the shot.

If your background looks too bland or flat, liven it up with a few decorations. For example, you can hang something on the wall (e.g., a painting, a guitar, string lights) or arrange a few of your favorite knickknacks on a shelf. Dim accent lights like salt lamps or LEDs can add some vibrance to the environment.

An alternative to using a practical background is to set up a vinyl, paper, or cloth backdrop. These can be solid colors, prints (e.g., brick), or even a green screen that you can replace with any image you want.

2. Use a good camera

If you want to look your absolute best, a USB webcam won’t cut it. The best option is to get a DSLR or mirrorless camera with a clean HDMI out signal. Some affordable options include models like the Canon M200, Sony a6400, and Panasonic Lumix GH5.

For example, in the video below, Dan is using a Canon M200, and George is using a Sony a5400 digital camera:

3. Position your camera properly

Position your camera at eye level or slightly above. The ideal distance between you and the camera will depend on the camera’s lens and how much space you have to work with.

The more distance you have, the better. By allowing enough space between the subject and the camera (at least 5 feet) and the subject and the background (another 5 feet), you’re creating depth of field and adding dimension to the shot. Plus, with the right camera lens, the background will have that neat blur effect (called bokeh) you’ve probably seen in lots of professional productions.

4. Light it right

Good lighting makes a huge difference, so investing in a few video lights is worth it. Using natural light as a source is possible, but it’s tricky since that lighting is apt to change with the weather and as the day rolls on. Artificial lights are best.

A set of LED lights will serve you well. These are easy to work with and won’t run hot. A tripod is the simplest solution for mounting these, though clamp mounts can also work.

Three-point lighting

The standard, most basic way of setting up lighting is known as three-point lighting. It goes like this:

• Place one light about four to five feet in front of you. This will be your main (or key) light.
• Set a second light the same distance, about four to five feet in front of you, spaced out about three feet from the first light. This second (or fill) light will counterbalance any harsh shadows on your face cast by the key light.
• Position a third light behind you to create a nice rim of light around your silhouette, helping separate you from the background.

For a more in-depth look at three-point lighting, check out our clip on that subject:

5. Get yourself ready

The clothing you wear and how you do your hair and makeup are important to consider beforehand. Reason being, not everything looks great on camera. Here are a few guidelines.

Clothing

A solid shirt and dress colors work best. Avoid:

• Prints with overly saturated colors, small prints, or stripes – they might create a jittery effect on video
• Anything green if you’re planning to shoot in front of a green screen
• Clothing that’s pure white or black – it creates too much contrast.

Hair and makeup

• Check for flyaway hair (a bit of hairspray will help if you find any)
• Control perspiration. It’s only natural to sweat more when you’re before bright lights and are under pressure to perform. Use blotting paper and translucent powder to help prevent shine.
• Choose natural lip, blush, and eye shadow colors if you’re wearing makeup. This is known as “no makeup” makeup, which is what looks best on camera.

6. Action!

Your on-camera performance matters just as much as your appearance. If you’re avoiding eye contact with the camera while mumbling under your breath, not even the best camera in the world could save you.
Remember to sit up straight and elongate your neck. This will improve your posture and help avoid a double-chin situation. Don’t forget to smile!

Often, feeling comfortable in front of the camera makes all the difference. Take a moment to loosen up before shooting the video. It may also help to record yourself and watch it back. If you’re recording, there’s no harm in doing a few takes before finding that keeper.

What is remote video production?

Remote video production describes any situation where the producer isn’t in the same room, building, city, state, country, continent, whatever, as the people on camera.

Here’s an example to illustrate what we mean. Imagine there’s a conference underway that’s being streamed and recorded simultaneously. The panelists and participants are at the venue, on stage, doing what they do in front of the cameras. Meanwhile, the producer (or production team) could be anywhere: at the company’s head office a state away, in a local coffee shop, even their own living room. Not only that, but the producer could be monitoring a separate event happening on the other side of the country, all from the comfort and convenience of wherever they work best.

Maybe that all sounds like a stretch. In fact, it’s totally possible with today’s technology. Plenty of companies are producing video remotely to cut costs, drive efficiency, and unlock flexibility for their production teams. That’s especially crucial these days, when working from home is far more common.

How remote video production works

Video production is quite a different beast when you’re doing things remotely: a different production process, different workflows, and different tools if your existing gear lacks remote capabilities.

What goes into your remote production kit will depend on the specifics of your project. For example, your setup might include:

• Pro-grade cameras (e.g., mirrorless, PTZ cameras)
• A video switcher for multiple inputs/layouts
• A remote controlled audio mixer (remotely accessible or with local controls extended through a VPN or remote desktop software)
• Lighting with Digital Multiplex (DMX) protocol support

Three setups for remote live streaming and recording

There are numerous ways to set up for remote production. Here we share three different workflows built on our own remote-capable hardware and cloud video services.