# Using NDI® sources in a MediaConnect flow
<a name="sources-using-ndi"></a>

AWS Elemental MediaConnect can ingest [Network Device Interface (NDI®)](https://ndi.video/tech/), a protocol for high-quality, low-latency video and audio over IP networks, and convert it into MPEG transport streams. This capability enables direct content ingestion within your network, connecting IP-based video production systems with traditional contribution workflows. 

Using NDI sources, you can create streamlined production workflows that take content from your NDI-enabled production systems—such as cameras, vision mixers, and graphics engines—and ingest it directly into a MediaConnect flow from your Virtual Private Cloud (VPC). MediaConnect then converts this NDI input into transport streams, which can be distributed to traditional broadcast infrastructure using protocols like SRT or Zixi. This integration works with your existing NDI infrastructure, requiring no modifications to your current VPC setup. 

## Key points
<a name="using-ndi-sources-key-points"></a>

### Understanding NDI terminology
<a name="using-ndi-sources-terminology"></a>

In video and audio workflows, the terms **source** and **output** have specific meanings that vary between contexts. Understanding these differences helps you work with NDI sources across your production workflow.
+ In MediaConnect flows:
  + A **source** is the entry point of a flow. **NDI sources** ingest NDI content into your flow from an upstream NDI sender.
  + An **output** is the exit point of a flow. **NDI outputs** send NDI content from your flow to a downstream NDI receiver.
+ In NDI implementation:
  + An **NDI sender** is a network endpoint that sends video and audio streams over IP networks using the NDI protocol.
  + From the perspective of your MediaConnect flow, the NDI sender is the upstream device that provides content to your flow’s NDI source.
  + When you add an NDI source to your MediaConnect flow, MediaConnect acts as an NDI receiver by connecting to an NDI sender in your network. Your flow can then convert this content for distribution through traditional broadcast protocols. 

### How NDI sources work
<a name="using-ndi-sources-how-it-works"></a>

At a high level, here’s how your content moves through MediaConnect when you use NDI sources in your flows:

1. Set up your VPC infrastructure with at least one NDI discovery server and active NDI senders within the VPC.

1. Create a large-sized flow with an NDI source, configuring your discovery servers and the NDI source settings.

1. Start your flow to discover the NDI senders that are broadcasting content within your VPC.

1. Connect to your selected NDI sender to start receiving content into your flow.

1. Convert and distribute the content through your flow outputs using transport stream protocols such as SRT or Zixi.

This workflow maintains compatibility with NDI-based production systems while adding the flexibility and networking advantages of traditional broadcast distribution.

### Considerations and limitations
<a name="using-ndi-sources-considerations"></a>

When planning your NDI source implementation in MediaConnect, keep in mind the following.

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/sources-using-ndi.html)

## Next steps
<a name="using-ndi-sources-next-steps"></a>

To get started, [create a flow](flows-create-ndi.md) with an NDI source.

## Additional resources
<a name="using-ndi-outputs-additional-resources"></a>
+ [Flow sizes and capabilities](flow-sizes-capabilities.md)
+ [Best practices](best-practices.md)