[NixayParticipant]

Yes you can control a Videohub from AHM, I have your exact scenario working with our Videohub. It’s not Telnet but a TCP command.

Within External/IP Control, select IP Control and String. The string might look like this:

VIDEO OUTPUT ROUTING:
21 8
34 3
39 3

Note there are TWO carriage returns / blank lines at the end – the BMD docs state you need one but on the AHM it won’t work unless you have two for some reason.

Set mode to TCP, put in the Videohub’s IP address and port 9990.

Hope this helps.

[NixayParticipant]

Just a bump so this request isn’t forgotten. I still have a weekly reminder to reset the time on our AHM which is annoying.

[NixayParticipant]

You can have an NTP server on your local network, that’s what we do. It’s doesn’t have to be on the internet.

[NixayParticipant]

I would go further and say that an NTP client is *essential* for the AHM. Our AHM loses 5 seconds EVERY DAY. For a system with scheduling as a prominent feature we need much better timekeeping to be useful, especially when coordinating events with scheduled program content.

[NixayParticipant]

I second this request. I currently have scheduling done by another system that is NTP sychronised and connects to AHM with GPI. If I want to move this scheduling to the AHM itself I’ll need it to be NTP sychronised.

[NixayParticipant]

I believe scenes are stored in the mixrack. I can log in using Director from any number of PCs on our network and they all show the same scenes. Surface layout is a different matter though and remains independent of any connected surfaces or other instances of Director.

[NixayParticipant]

I have run into what sounds like a very similar problem. Programming scenes into a surfaceless CDM32 using Director running the latest 1.72 firmware. Each scene had recall filters and crossfade times set. Each time I would store a few scenes and then go back and review what I’d done, the earlier stored scenes would be either the content from another scene or fader positions possibly picked up from when I was simply pushing faders to check levels and hadn’t actually stored anything. I was connected live and had audio running and meters bouncing.

The only way I found I could successfully save the scenes correctly was to turn off all the crossfade times, store the scenes, recall them to make sure they were correct and then reset the crossfade times. Anything I attempted to store while a crossfade was set on the scene would not be stored correctly.

[Author]

Posts