UDP connection

A

alonso

Member
Hello Friends, I have some problems with drops when monitoring the NDI signal from Tricaster TC2´s multiview, so I try to force the connection to UDP. so in access manager i checkmark AllowUDP, but my ndi discovery said that the connection is using single TCP. there is something that i missing?

1787136025112.png
 
Is this screenshot that is showing Discovery Server and Access Manager the same computer that is running the Tricaster software? Since both the sender and receiver must agree on which transmission mode is used, can you show the Access Manager from both the Tricaster AND receiving machine? Have you tried changing Receiver mode to force Reliable UDP instead of Auto?
 
Changing the receive setting in Access Manager will only affect an NDI application after they restart. If Studio Monitor is current running when you make the change, you have to quit (all instances), then launch new copies and test again.
 
BARP said:
Is this screenshot that is showing Discovery Server and Access Manager the same computer that is running the Tricaster software? Since both the sender and receiver must agree on which transmission mode is used, can you show the Access Manager from both the Tricaster AND receiving machine? Have you tried changing Receiver mode to force Reliable UDP instead of Auto?
Click to expand...
Hello friend.
this is my workflow
Tricaster TC2
PC1, running discovery server
PC2, running NDI Monitor ( the screens are from this machine)
Tricaster have the Received mode in auto, since I understand that the destination is the ones that define what protocol will be used. so on my PC2 with NDI monitor I force to UDP but nothing change, it only works with TCP , MTCP and RDUP
kanep said:
Changing the receive setting in Access Manager will only affect an NDI application after they restart. If Studio Monitor is current running when you make the change, you have to quit (all instances), then launch new copies and test again.
Click to expand...
Hello Mr Kanep, i close NDI monitor each time i made the change on the access manager ( not restard the PC only close and reopen NDI Monitor) but seems UDP not work here i dont know why
 
alonso said:
Hello friend.
this is my workflow
Tricaster TC2
PC1, running discovery server
PC2, running NDI Monitor ( the screens are from this machine)
Tricaster have the Received mode in auto, since I understand that the destination is the ones that define what protocol will be used. so on my PC2 with NDI monitor I force to UDP but nothing change, it only works with TCP , MTCP and RDUP

Hello Mr Kanep, i close NDI monitor each time i made the change on the access manager ( not restard the PC only close and reopen NDI Monitor) but seems UDP not work here i dont know why
Click to expand...
Reliable UDP (RUDP) is the choice you want. The old legacy UDP mode probably isn't supported anymore during the negotiation handshake between the sender and receiver. Is there a particular reason you are trying to use UDP over Reliable UDP?
 
BARP said:
Reliable UDP (RUDP) is the choice you want. The old legacy UDP mode probably isn't supported anymore during the negotiation handshake between the sender and receiver. Is there a particular reason you are trying to use UDP over Reliable UDP?
Click to expand...
Thanks for reply,
i have a lot of drops on my tricaster output, sometimes all the MIX outputs dissapear ( INs are ok), so i read that UDP is better when there are network problems
 
You must log in or register to reply here.
Back
Top