External Device Control – Source Switching

[Josh J]

Hello,

I would like to select “sources” on the Core256 using a control system (Crestron, AMX, josh.ai etc).  The MOM controller works well, but we have an interesting use case where video switching is involved as well, so would like to be able to control the sources externally providing a single button to switch both video and audio routing options.

Is there a rest api or tcp/udp command port that the Core256 listens on? If so, is there a documented API you can share?

 

 

[Philippe Beaudoin]

Did you get any come back from DAD about that subject ? Would love to be able to control features from custom devices…

[Jon Schumann]

Hi all,

(and Philippe – you’ve got mail. 🙂 )

As it stands right now – This is not possible.

However, we are always looking to play better with the other kids.

Best,
Jon

[Aram Piligian]

I’d like to add another voice to this! Both for Control Pack and for monitor/preamp/matrix functions. I know there has been development for control pack specifically, but being able to unify control pack, MOM functions and more under one API would be excellent, since it opens up options like Companion, allowing integration with an enormous ecosystem of gear.

One Control Pack example use– I’d love to be able to change channel strip colors on my console based on which preset is active. And also be able to trigger a preset change manually from my console. This would be a trivially easy task in Companion if there were a DAD module.

MOM/Monitor/Matrix example– An open API could allow for preamp control and state monitoring of DAD devices. Quickly controlling preamps from an external hardware device makes setting up for a large recording session a breeze with much less clicking.

As I’m sure you’re aware there’s a ton of possibility here. Looking forward to seeing what comes down the pipe!

[Jon Schumann]

Hi Aram,

All good inputs!

We are always putting the squeeze on the Elves and Dwarves in the dungeons under Mount Development.

/J

[Philippe Beaudoin]

Since there’s no like button to posts in this forum just want to “Like” Aram’s post…

[Josh J]

One thing that’s possible is someone can wireshark to sniff packets from mom <-> dad and then build a control system based on that.
time-consuming, sure, but offers a lot of flexibility that D.A.D. doesn’t seem to want to support.

I understand the “potential” to cannibalize sales by creating an official API, but trust me, a MOM is going to be way less expensive to implement than 3rd party control. An external control API will only serve to enhance the DAD/MOM userbase and further the reach of DAD/MTRX DSP products into more PRO spaces.

• This reply was modified 4 months, 3 weeks ago by Josh J.

[Jon Schumann]

Hi Josh et al,

Just a quick ping to let you know that we appreciate your inputs always.

Best,
/J

[Marcus Marshall]

I work for a major enterprise(Broadcaster) and we use AX64/AX Center/Avid MTRX/ and MOM units at multiple facilities. We have reached out to our contacts at DAD over a year ago officially asked them for a way for the DAD boxes to be controlled by third party control systems. We specifically use a company called Densitron IDS. It said because the DAD gear is the bottle neck in some of our systems that does not allow control. We mainly need to be able to automate source selection and monitor control. This type of automation is not possible with the MOM. The implementation of an API for control would not keep us from purchasing a MOM. Especially if a MOM V2 that could run standalone were available. An API or way to control DADman via third party control is highly needed on the enterprise level. Especially once they release the ST-2110 card.

[Author]

Posts