Avahi dependency in NDI

jainrajath

New member
Hi,
I tried to use the NDI in a docker but ran into an issue. When I try to use it in a single docker it works fine but when I start a second docker in the same machine, NDI refused to start. I narrowed the problem to the avahi-daemon which could not be started in both the dockers at the same time. So is there a way to remove the dependency on avahi in NDI? Can we give the IP address of the sender directly? Or is there any other way to run NDI in multiple dockers?
 

gizah

New member
you could run the NDI discovery server and then create the .newtek folder in the home folder of the user (within the docker instance) running the ndi stuff, containing the ndi-config-v1.json file:
{
"ndi": {
"tcp": {
"send": {},
"recv": {
"enable": true
}
},
"groups": {
"send": "Public,",
"recv": "Public,"
},
"unicast": {
"send": {},
"recv": {
"enable": true
}
},
"networks": {
"ips": "comma seperated list of IPs/hostnames",
"discovery": "ip of discovery server"
},
"multicast": {
"send": {
"ttl": 1,
"enable": true,
"netmask": "255.255.0.0",
"netprefix": "239.255.0.0"
},
"recv": {}
}
}
}

Unfortunately you cannot supply multiple discovery servers, so running the discovery server creates a single point of failure
 

jainrajath

New member
Hi,
Thanks for the help. I was able to fix it without using discovery server.
Just keeping this out here for future visitors: the file name is not "ndi-config-v1.json" but "ndi-config.v1.json".
The ndi instance won't connect to the discovery server if the config file is wrong
 
Top Bottom