logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
gugacdb  
#1 Posted : Friday, May 30, 2025 3:53:32 AM(UTC)
gugacdb

Rank: Newbie

Groups: Registered
Joined: 2/5/2018(UTC)
Posts: 7
Location: Brasil

Thanks: 3 times
Greetings, everyone!

I am a vMix programmer at Casablanca Online, a leading company in broadcast solutions in Brazil. For more details about our company, visit our website: https://www.casablancaonline.com.br/?lang=en.

Current Situation:
vMix handles NDI, SRT, built-in streaming and control traffic over a single network interface. High-bandwidth flows (4K NDI, SRT feeds, live streaming) compete on the same link, causing congestion, packet loss and latency spikes.

Suggestion:
Implement a **per-protocol network-interface selector**, configurable globally and per-input/output:

NDI Inputs: bind to "Video LAN" (e.g. 192.168.10.x)
SRT Outputs: bind to "SRT Network" (e.g. 10.0.0.x)
Streaming: bind to "WAN/Internet" adapter
Control & PTZ: bind to "Corporate LAN"

This allows each service to use its own NIC or VLAN, reducing collisions, jitter and ensuring predictable performance.

Versão em Português:

Sou programador de vMix na Casablanca Online, uma empresa líder em soluções de broadcast no Brasil. Para mais detalhes, visite: https://www.casablancaonline.com.br/?lang=en.

Situação Atual:
vMix envia NDI, SRT, streaming e controle pela mesma interface de rede, gerando congestionamento, perda de pacotes e latência elevada em fluxos de alta demanda (NDI 4K, SRT, live).

Sugestão:
Adicionar um **seletor de interface de rede por protocolo**, configurável globalmente e individualmente para cada entrada/saída:

Entradas NDI: vincular à "Vídeo LAN" (sub-rede 192.168.10.x)
Saídas SRT: vincular à "Rede SRT" (sub-rede 10.0.0.x)
Streaming ao vivo: vincular ao adaptador "WAN/Internet"
Controle & PTZ: vincular à LAN corporativa[color=olive]


Isso garante que cada protocolo utilize NIC/VLAN dedicada, reduzindo colisões, jitter e mantendo performance estável.
danielwinst  
#2 Posted : Tuesday, June 24, 2025 9:50:58 PM(UTC)
danielwinst

Rank: Newbie

Groups: Registered
Joined: 8/1/2024(UTC)
Posts: 2
United States
Location: Texas

Was thanked: 1 time(s) in 1 post(s)
As an idea for you that may help with this.

I do many shows a year where we push upwards of 2.5-3Gbps of input traffic and 30-40 video inputs ranging from NDI, hardwire, SRT and more. I would recommend getting a higher speed USB or Thunderbolt NIC. We are currently using a thunderbolt 4 10Gbps NIC paired with a Multi-gig Switch. All the video traffic comes into the switch and is consolidated to the PC on the 10G uplink to the PC. The outbound stream (SRT, NDI, and RTMP) is then kept to about 500Mbps. With this all the heavy network traffic stays on the local 10G switch and we have plenty of overhead with no network issues. We have used this in hotels, City Parks, and many more bandwidth challenged sites with great success. This can be done for a minimal cost depending on the switch you go with.
thanks 1 user thanked danielwinst for this useful post.
gugacdb on 9/10/2025(UTC)
cwilms  
#3 Posted : Wednesday, February 11, 2026 4:01:03 AM(UTC)
cwilms

Rank: Newbie

Groups: Registered
Joined: 1/15/2025(UTC)
Posts: 4
Canada
Location: Belleville

In multi-NIC setups, it is currently difficult to isolate different types of network traffic, which can lead to performance issues, dropped frames, or security concerns during live productions in corporate or professional environments.

I would love to see additional control over network traffic, allowing dropdown selection of available NICs for specific protocols. For high-bandwidth protocols such as NDI, it would be ideal to have separate NIC selection for Inbound and Outbound traffic as well. This would allow vMix to utilize cameras and devices on a closed LAN while still supporting streaming, software updates, and other Internet functions over a separate NIC.

As stated by the original request, a per-protocol NIC selection feature in vMix would allow users to assign a specific network interface for each supported protocol and network function. I would personally like to see it broken down a little further for even more control:

vMix Environment & Control
  • Web Control (HTTP / HTTPS)
  • vMix API
  • vMix Internet Access
  • OSC Control
  • PTZ Control (VISCA-IP, ONVIF)
  • Network Recording (SMB/CIFS)


Media Traffic
  • RTSP (Inbound)
  • RTP (UDP) (Inbound)
  • UDP (MPEG-TS) (Inbound)
  • NDI (Inbound / Outbound)
  • OMT (Inbound / Outbound)
  • SRT (Inbound / Outbound)
  • RTMP / RTMPS (Outbound)
Users browsing this topic
Guest (8)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.