- This topic has 7 replies, 4 voices, and was last updated 1 week, 3 days ago by
.
-
Posts
-
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?
Did you get any come back from DAD about that subject ? Would love to be able to control features from custom devices…
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,
JonI’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!
Hi Aram,
All good inputs!
We are always putting the squeeze on the Elves and Dwarves in the dungeons under Mount Development.
/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.
- You must be logged in to reply to this topic.