Dealing with NDI and DDR issues

I

imryh

Member
Hello.

We've had several issues over the last few months with our TC2 (case #00165922) and our 3P2 (case #482637) freezing (TC2) or rebooting (3P2) when experiencing unexacting NDI network conflicts.

Is there a way to better implement dealing with NDI errors? Maybe have them appear in the Notification Center, and have the session ignore them rather than try to deal with them through freezes and reboots?

Thanks.

Imry
 
I

imryh

Member
There's lots going on on our NDI production network.
3 x TC2s
1 x TC1
15 x JVC 200 PTZs
8 x BirdDog A200s
1 x 3P2
2 x 3Play 4800
20 x Outputs from Daktronics DMPs
3 x AJT Livebooks
1 x Newtek NC1 IO
1 x AJA Bridge NDI 3G
2 x AIDA NDI cameras
4 x Magewell Converters
9 x BirdDog Studios
4 x BirdDog Plays
6 x Newtek Sparks

Seems like most issues were caused by the AJA Bridge NDI 3G. And we're working with AJA on resolving that. But it would be great if NDI issues on the network resulted in just an alert on our TC2s and 3P2, rather than a freeze or a reboot.
 
Last edited:
kanep

kanep

NewTek SE
I'd make sure all of the BirdDog equipment is current, I've had some issues with older firmware crashing the NDI decoder on systems.
 
I

imryh

Member
Yes. It’s all current. Just to figure out if there can be a more global fix to the way network errors are handled.
 
I

imryh

Member
It happened again! Our 3P2 started rebooting on its own.
The problem went away for a while, but now it's back.

Yesterday, we have 4 sources for the 3P2:
1 - a Magewell NDI encoder
2 - a Magewell NDI encoder
3 - a Newtek NDI|HX3 PTZ
4 - a MIX from a TC2

Every time the operator marked out from source 2, the unit rebooted.
When I switched all the sources to SDI (still the same content, but just converted to SDI before hitting the 3P2) there were no issues and no crashes.
I know it's tough to figure out what's causing this because it's intermittent. But what I really want is for the 3P2 to have a different way to react to NDI issues instead of rebooting. Show a notification in the Notification Center, show the source as black, have a pop-up error message. Anything really. Just not a very disruptive shutdown.

Thanks.
 
S

stp_productions

Active member
I believe this is why vmix has a isolate ndi sources so that if one goes bad it doesnt take everything with it. The result being more CPU usage. The eventual reality of doing that would be that you couldn't bring in as many inputs as before but having the option in this case would be helpful.
 
kanep

kanep

NewTek SE
Something else to verify. Make sure the 3PLAY unit is current on Windows Updates. I've had a few people run into 3PLAY crashing issues (has to do with recording) and once you get current on Windows Updates, the issue is resolved. (I'm not sure which specific update it is, but once you are current you will have it).
 
You must log in or register to reply here.
Top Bottom