Open mrlad opened 4 years ago
There is a Hyperdeck Module -> https://github.com/bitfocus/companion-module-bmd-hyperdeck
@dev-slatto: The problem was the Hyperdecks limit of 1 connection. So they want to have their ATEM always connected to it, and control it from companion via ATEM, since the Hyperdeck module cannot connect to it when the ATEM already is.
@mrlad You could maybe control it using macros on the ATEM, and calling the macros from companion.
@haakonnessjoen , @Julusian suggested on slack I use macros as a workaround as this functionality was unlikely to be implemented in the near term. I was able to write macros to control hyperdeck trick functions (play, record, rewind and fast forward). Rewind/Fast forward did require hand editing of the XML due to the way the macro recorder worked.
However, I've been unable to create a macro to select the previous/next clips. The ATEM macro recorder uses an absolute number and I need something relative. I looked at the syntax and I don't think the XML format supports relative selection.
+1 for this feature, being able to record / play / select clips via ATEM would be hugely useful in any setup with both devices.
is this 1 connection limit existent on all hyperdecks? i think it isn't, cause i'm using a hyperdeck studio mini, and i am controlling it with compainion module AND atem software simultaniously. may be only older/other hyperdecks are affected of this limit?
All current HyperDeck models support multiple controllers. I can control Hyperdeck Studio HD Plus from ATEM Switcher Control, Companion Hyperdeck module, Companion Generic TCP module and ethernet protocol from Terminal, all at the same time. Following is a quote from BMD Developers Forum: The Atem itself is communicating with the Hyperdecks, not the laptop controlling the Atem. You can control the Atem controlling the Hyperdecks using the API or the Software Control application - both only communicate with the Atem.
This means you can program macros containing commands to be sent to hyperdecks, which will then work even with no computer attached.
Our Hyperdeck is connected to an ATEM. Since the Hyperdeck only supports a single IP connection, we can't connect the Hyperdeck Companion module. However, the ATEM Switcher HyperDeck API allows remote control of the Hyperdeck via the ATEM. Could the ATEM module add support for attached Hyperdecks?
Functionality I'd be interested in: