开云体育

Howdy,
I am a programming novice, and mostly deal with modifying existing code to add basic functions.
I have been trying to integrate 6 NVX's(NVX350,352, 2 D30s, and 2 E30's) into my complex A/V system(two 3- series processors and a 64x64 and 128x128 dm matrix switchers, and a whole lot of endpoints) using a DIR-160, and am a bit lost on how the programming logic should go.? I've been told that the Director should act more or less like a DM switcher, but I am not sure how the logic with streams should go.? It seems to me that with or without the director, I still need to pull the individual streams into a serial strings for the logic. would I be correct in saying so?
My main goal is to get some hands on experience, as there is an expansion that will be all NVX based, so I want to have a head start on how to use these devices.
Thanks!

On Mon, Mar 31, 2025 at 09:03 AM, <jacksonkfortune@...> wrote:

It seems to me that with or without the director, I still need to pull the individual streams into a serial strings for the logic.

You found the secret.? The XIO Director is a completely useless waste of money.

?

To route NVX Streams, simply provide multicast addresses to your encoders, and put the streamlocation feedbacks of encoders into the streamlocation joins for decoders.? How you decide to accomplish that is up to you.

Wow.? The director cant hold more than one firmware version at a time(I still have NVX's on firmware version 2.x), cant handle credentials effectively, and doesn't even have a useful module to make routing easier?
Now I know why my mentor told me they were useless.? Glad I'm not the one who ordered this.

One caveat - the NVX devices will have to be in the same major revision number as each other for the streams to work.? An encoder on 2.x.x can't steam to a decoder on 5.x.x and so forth.

?

And once an NVX is updated to 5.x or beyond, rolling back the firmware to earlier than 5 will brick it.? Learned that the hard way.

?

Best to just go ahead and get everything on 7 right out of the gate.

Yeah, I had to learn that the hard way.? Now I've got about a dozen NVX's that I'll have to manually iterate up to version 7.x

-beware of multicast switch settings-

?

you can use de firmware updater SW to do the FW install job

?

the director then can be used as a nice paperweight in one IT's Office Desk

?

Oh yeah, DM NVX Tool is the swiss army knife that helps with everything.??

On Mon, Mar 31, 2025 at 12:57 PM, <jacksonkfortune@...> wrote:

you can use de firmware updater SW to do the FW install job

?

I noticed that the firmware updater software is also more reliable than using the director.
Also, luckily my network admins have already prepped my network for the multicast settings.? I probably should've at least asked, as when I was setting it up on my own test bench, my whole LAN froze up due to the multicast packets flooding everything on my little switch.

?

One thing about the DM NVX Tool that's nice is you can do batch firmware updates (as long as the batch is the same model).? So you could use it to "discover" all your 350s, and tell it to push the selected firmware to all of them.? It will chew through them 10 at a time until it gets them all, then notify you if any failed.? Saves LOTS of time at big sites.? ?But yeah you'll still have to step using DM NVX Tool, but it's still way, way faster than doing them one at a time.

If you go to the Files section of this group, and search for "liquidpixel" you'll find our free resources for programming NVX systems. Might be a helpful start for you. It shows you how to handle all the multicast addressing and stream location string routing, and there are several free modules in there that do the heavy lifting (and they have real help files).

?

I'm with the others, as far as the Director not being useful. But just to answer your original question... the Director is programmed similarly to a DM frame switcher, where you can just use analog values to trigger routes. This is done by defining the Director in the devices under an IPID and then attaching all your endpoints inside that (not to their own independent IPIDs). The modules included in the liquidpixel demo program also let you handle routing with analog values, so there's really no advantage to using a Director.

?

--

Josh Winn
The LiquidPixel Group