NDI Source Discovery

kanep

kanep

Administrator
I have another new NDI tool to release, this one is helpful in troubleshooting NDI discovery. NDI Source Discovery, will scan your NDI network and display sources that appear using mDNS and Discovery Server methods. Each is displayed separately, so you can verify the method of discovery being used by the device.

Each source is displayed with its channel name, IP address, port and NDI group(s). You can even see sources in groups that you aren't receiving.

In the list of sources, you can double click it open it in NDI Studio Monitor. Or hold down shift and double click to open it in NDI Analysis. You will have to be in the same NDI group as the source in order to perform these functions.

NDI Source Discovery | kanesworld

kanelp7.wixsite.com kanelp7.wixsite.com

1710003131925.png
 
Just an FYI, Chrome has decided that this file might be a problem and blocked download, you have to click on the message and tell it to download it for real. I appreciate them trying, but this is getting in my way more and more often to the point where I'm thinking of disabling the feature due to false positives. Getting that a lot with Edge when I build a fresh system, and before I load Chrome or Brave.
 
My apps aren't code signed, plus they are doing stuff networking wise, it which is probably also going to lead to security software flagging it.
 
Chris Titus went through this with his Windows debloat tool... He has a few videos on buying code signing from Microsoft and the hoops he had to jump through. And if you have any powershell scripting that automatically elevates permissions, you will get flagged, which is happening to his tool. It's odd that MS would allow automatic privilege elevation in scripts, but apparently MS uses this feature often. Doesn't even allow UAC to give a warning, which again is very odd to me from a security point of view.

And yes I do use Chris's tool to de-junk Windows, Win Pro is full of all kinds of nonsense. I'm finding Enterprise Education to be better, and LTSC being best to remove the clutter.
 
Released an update to this app which fixes a bug where some mDNS sources from a TriCaster may appear in a group named 'newtek'. This is a bug in my application's decoding of mDNS information. It's now fixed in version 250221. Also updated to the .NET8 runtime.

NDI Source Discovery | kanesworld

kanelp7.wixsite.com kanelp7.wixsite.com
 
Thanks @kanep

Now I know the reason of

forum.vizrt.com

NDI Groups

Hi, I´m instaling a TC1-Pro with an extrange behabiour. I have double checked both in the access manager of the installed NDI tools and in the Tricaster launcher (although I understand that both are the same) and the -Newtek- group is not configured in either of them. If I try to do an...
forum.vizrt.com forum.vizrt.com
 
Yes, I've been mostly using Discovery Server which didn't have the issue, but once I realized that this issue was limited to mDNS it was easy to fix.
 
You must log in or register to reply here.
Back
Top