bitfocus / companion-module-bmd-atem

companion-module-bmd-atem

Getting started

Executing a yarn command should perform all necessary steps to develop the module, if it does not then follow the steps below.

The module can be built once with yarn build. This should be enough to get the module to be loadable by companion.

While developing the module, by using yarn build:watch the compiler will be run in watch mode to recompile the files on change.

Adding a new model

Each model of ATEM has a definition file in src/models describing the functionality of the device. This allows us to know this information for offline programming. If the module is left on auto-detect, we match the definition to use based on the model the atem reports, and if one is not defined we can build the definition on the fly from the ATEM. This generally gives us good results, but there are a few things we don't know how to detect from the atem.

To add a new model to the list:

• Create a new file in src/models/ for the new model, based on one of the others (mini.ts is a nice and simple one)
• Run yarn ts-node-esm dump-model.ts 10.42.6.125 (substitute in the atem ip)
• Copy the contents of state.json to the file you created, replacing the existing spec
• In the new file, replace any magic numbers with their enums (this aids readability, but is not essential)
• Add the new spec to the ALL_MODELS array in src/models/index.ts
• Recompile the code and test it out!

Changes

v3.10.1

• Improve increment camera iris and exposure

v3.10.0

• Add PREV TRANS support
• Add fairlight solo support
• Improve fairlight headphone support
• Add incrementing camera control

v3.9.0

• Add timecode as a variable
• Actions to set the ATEM timecode
• Fix bug in model selection
• Fix ISO record feedback not updating
• Add support for fairlight audio delay (this may not be correctly defined for all models)
• Expose record filename as a variable, and support variables in action
• Add action to delete a still
• Add action to set media player source from a variable
• Support switching upstream keyer type

v3.8.3

• Build tooling update

v3.8.2

• Build tooling update

v3.8.1

• Build tooling update

v3.8.0

• Enable/disable ISO recording
• Multiviewer layout control
• Basic camera control
• Stream cache variable

v3.7.1

• Fix auto-detect not reporting state correctly

v3.7.0

• Add variables for fairlight audio master/monitor

v3.6.1

• Add definitions for TVS 4K8

v3.6.0

• Use Companion builtin ATEM discovery
• Track last connected model, to provide a better experience when offline
• New action to arbitrarily alter the presence of every component in the next selection

v3.5.2

• Attempt to make discovery a bit more reliable

v3.5.1

• Add definitions for Constellation 4K 4ME

v3.5.0

• Support variables in 'Stream: Set service' #256
• New tally feedback, to provide tally for ME2 #188
• Fix potential feedback reactivity issue
• Add multiviewer window source variables #245
• Add CUT preset #224
• Adjust master pan in classic audio mixer #180
• Set T-bar position #241

v3.4.0

• Use builtin invert support for all feedbacks
• Update atem library, to get more responsive multiviewer feedbacks

v3.3.3

• Fix TVS HD8 ISO being based off wrong model

v3.3.2

• Fix connection stuck in a crash loop unable to open configuration

v3.3.1

• Fix SSrcBoxSourceVariables feedback

v3.3.0

• Add Television Studio HD8 models

v3.2.2

• Fix build errors

v3.2.1

• Some feedbacks off by one on me index

v3.2.0

• Add capture still action

• Add display-clock actions

v3.1.0

• Add feedbacks which support variables

• Add more actions which support variables

v3.0.0

• Updates for Companion 3.0

v2.18.1

• fix audo feedbacks

v2.18.0

• add macro looping action/feedback

• fix reset peaks actions

• expose device ip as variable

• add variables with input ids

• add invert checkbox to some feedbacks

• add actions to set inputs from variables

v2.17.3

• fix 'Fairlight Audio: Audio fader gain' feedback missing

v2.17.2

• fix unable to set multiviewer label to blank

v2.17.1

• fix performance issues with fairlight input updates

• hide multiview label when name set to nothing

v2.17.0

• add sdi model range (untested)

• add dsk rate

• add dsk premultiplied key

• add usk mask

• add usk dve properties

v2.16.0

• more granular supersource actions and feedbacks

• support learning values for actions and feedbacks

v2.15.1

• fix constellation hd high cpu usage

v2.15.0

• add constellation hd models (untested)

• correct order of input fields for some actions and feedbacks

• fix macros to use name not description

• flying key control

• atem mini extreme headphone basic controls

• audo mixer master gain control

v2.14.0

• set input names (both text and multiviewer)

v2.13.0

• duration variables have a ms variant

• save and clear startup state actions

• variables for supersource box inputs

v2.12.2

• rewrite upgrade scripts to new api

v2.12.0

• fix supersource art feedbacks

• supersource art action has more flexible placement control

• discover and suggest atems in the instance config panel

v2.11.0

• reset audio peaks

• atem mini recording filename accepts variables

• supersource art source

v2.10.0

• feedbacks updated to new format. allows more customisation of style

v2.9.3

• fix utf8 characters in variables

v2.9.2

• fix build issues

v2.9.1

• fix in electron (in new module workflow)

v2.9.0

• Add mini-extreme and mini-extreme-iso

v2.8.3

• fix offline programming

v2.8.2

• fix on windows

v2.8.1

• fix companion exiting on uncaughtException

• fix 1me models having supersource commands

• fix tvs4kpro erroring when generating actions list

v2.8.0

• Relative fader levels adjustments

• Fader level fades

• Expose missing audio faders (madi & trs)

• fix aux variables not updating

• fix autodetect model being a bit broken

• fix supersource2 not being a valid source

v2.7.0

• mini-pro streaming and recording

• Classic audio input actions and feedback

• Fairlight audio input actions and feedback

v2.6.0

• Improved connection library

• Add mini-pro-iso

• Feedback for running transition

• Add action to go to next/previous still in media player

• Add action to do relative changes to supersource boxes

• Fix downstream key input action

v2.5.1

• Add presets for transition selection component

• Add dsk tie

v2.5.0

• Send multiview to aux on mini-pro

• Add individual transition selection component control

v2.4.2

• Add mini-pro

v2.4.1

• Revert connection library change

v2.4.0

• More stable connection library
• Variables for media pool
• Variables for media players

v2.3.0

• Add definitions for Mini
• Add tally feedback

v2.2.0

• Set fade to black rate
• Execute fade to/from black
• Variables for current aux source
• Add definitions for TVS Pro models

v2.1.0

• Change transition selection
• Set SuperSource box On Air
• Change SuperSource geometry properties
• Change media player source

v2.0.0

• Update atem-connection to support v8 firmware.
• Add support for ATEM Constellation.
• Rewrite in Typescript with some linting and formatting rules.
• Fix changing supersource box resetting other properties
• Fix keyer toggles sometimes getting stuck
• Add support for setting transition type and rate

v1.1.0

• Module in ES6 format (no self and use of =>)
• this.states[] use abstracted to getXX(...) and updateXX(...) calls
• Model parameters moved to 'CONFIG_MODEL' array

companion-module-bmd-atem's Issues

Custom ATEM Feedbacks based on more than one source at a time. 2, 3, or 4 Based on MEs Available

Describe the feature
If source 1 is sent to ME1 Program/Preview && source 10 to ME2 Program/Preview then trigger feed back for button that controls that, etc... It would also be helpful to be able to select more than one input/ME for change than just one input/ME at a time.

Is this platform dependent (windows, mac, ..)?
No

If documentation is required to implement, do you know where to find it?

Usecases
For different events, I setup a few simple buttons for non tech people to use that might send logo to center screen and live cameras to the side screens. I would like the one button that triggers those events to change to show its active. Not all of the other buttons that contains just source1 or just source 10. That gets confusing when trying to see what button is active.

ATEM: AUX bus dynamic variable

Describe the feature
Show which input is currently assigned to a particular Aux in ATEM.

Is this platform dependent (windows, mac, ..)?
Shouldn't be.

Usecases
The ability to see what input is on Program & Preview buses as well as the keys currently exist. Would be a natural part of having an overall view of what's going on via the stream deck.

Sending actions to disconnected ATEM crashes Companion

To recreate:
-Connect ATEM, make sure it's "OK" in Companion.
-Disconnect ATEM power or network cable.
-Press a button that has an ATEM action.
-Full Companion crash, no error

In dev mode, this in the info being returned when following the above steps:

I first discovered this crash at the same time as this was happening, not sure if it's related. It seems to be disconnecting repeatedly and if the button press happened to be while it was disconnected it would crash Companion.

ATEM Mini Pro: missing Multiview option on Aux 1 (HDMI out)

Set AUX Bus action is missing a dropdown option in Input for a MVW/Multiview. Likely because other ATEMs cannot display Multiviews on Auxes, but ATEM Mini can.

Down Stream Key Fade Not Working

I was attempting to define a button to do a fade on BlackMagic Design (ATEM 1) down stream keyer number 2. I was able to make the button work with DSK 1, fade and cut. I then changed the button to do a fade on DSK 2. Nothing happened. Changed the button to do a cut on DSK 2. Worked just fine. Changed back to fade on DSK 2 and nothing happened.

The problem seems to be related, and confined, to using a fade on DSK 2. Cuts work. Fade and cuts on DSK 1 work. Just not fades from DSK 2.

Any way to resolve this issue?

Support for Atem Constellation 40 inputs 24 outs willing to test

Describe the feature
A clear and concise description of what the feature does

Is this platform dependent (windows, mac, ..)?
Explain

If documentation is required to implement, do you know where to find it?
If applicable, add screenshots, protocol description PDFs, etc to help the developers along

Usecases
Add a couple of usecases for why this should be implemented and when/why to use it.

Unable to enable the PIP (Picture In Picture) button on ATEM mini

I haven't been able to find a way to turn on/off the PIP button on my ATEM Mini. I use this feature a lot. Please advise if I have overlooked how to turn this feature on/off with Companion.

ATEM: Supersource and DVE Key box incremental increases

Describe the feature
Allow for the user to create a directional pad of buttons on the StreamDeck to increment the x&y coordinates, crop and scale by some factor each button press. It would be helpful if this worked for DVE AND Supersource boxes.

Is this platform dependent (windows, mac, ..)?
Shouldn't be.

Usecases
Positioning super source boxes are a pain. On the ATEM panels, you can use a joystick to move the boxes. If I could replicate that behavior using 4 buttons to position them and every press of the button it moves the box some additional amount (x++) in some direction would be wonderful.

Transition selection toggle for ATEM mixers

Currently the ATEM module allows you to select which elements will be subject to the next transition. For a particular element (background, key{1-4}), you can set that selection to on or off.

I would like to see the option to toggle the current setting rather than explicitly setting the next transition state to on or off. This would replicate the behavior of the transition selection button on the ATEM software interface or physical control surface.

The toggle feature in companion is not a good solution here, as if a particular element is the only remaining selection, it cannot be deselected, and the state of the button and the on/off state of the companion button toggle will get out of sync.

Be able to change the media player source.

Be able to change the media player source.

Once we have these, we can do full show programming in Companion. Thanks!

Log not showing ATEM Models

From @cxselph on September 5, 2018 21:0

Companion 518d6ed

Describe the bug
Not an issue with functionality, but the official names disappeared and show up as numbers in the log. Also the Broadcast Studio 4ME shows up as the 2ME Broadcast Studio model. #7

Desktop (please complete the following information):
OSX 10.13.2 and 10.12.6
Version 68.0.3440.106 (Official Build) (64-bit)

Copied from original issue: bitfocus/companion#218

Feature Request - Fade to Black

I would like to request the ability to activate "Fade to Black" with feedback for all ME buses.

So very thankful for all of your hard work. Companion is awesome!

BUG Report on Blackmagic ATEM

I want to report a bug on Blackmagic Atem, when u use the option TOGGLE on Downstream KEY 1 or 2, it dosen't toggle the DSK off just stays ON AIR all the time

Request: Dynamic Variable for Media Player Source Name

I'm looking for a way to dynamically change the name of a button to display the name of a Media Player source image.

The source image name is displayed in the "Change Media Player Source" dropdown menu, but is not available for use as a dynamic variable to modify button text. I don't see a way to be able to grab the name shown in the dropdown and use it elsewhere.

In the below example, I'd like to be able to make the button's text be "BeginShortly".

Auto transition type and delay

Hi,

Unsure if this is a bug or if I am blind.

Is there a way to change the transition type between mix and dip? And also to change the transition time? I could do this with a macro but wondering if there is a native way.

Cheers

Toggle upstream keyers being tied to transition

I can't find a way to configure a button for the following features of my Blackmagic Design 4ME:

BKGD -> Background in Preview
KEY 1 -> Tie Key 1 to Preview
KEY 2 -> Tie Key 2 to Preview
KEY 3 -> Tie Key 3 to Preview
KEY 4 -> Tie Key 4 to Preview
DSK 1 TIE -> Tie DSK 1 to Preview
DSK 2 TIE -> Tie DSK 2 to Preview

Can't find a way to configure them neither via preset nor via manual button configuration, am I overlocking anything?

Is this platform dependent (windows, mac, ..)?
No

If documentation is required to implement, do you know where to find it?
Not needed

Usecases
Useful button ;)

ATEM Constellation 8K not connect.

I use companion beta with stream deck XL.
Companion not working properly with Constealation 8K, only as "4 ME Broadcast 4K" model with firmware 8.1 but GUI Status is always "Reconnecting", but MACROS are working ok.

But firmware 8.1 is buggy (Atem Software don't save chroma color configuration).
When do you plan support higher firmware as 8.2?
I tested 8.2.3 and companion don't connect to ATEM.
(Few days ago i used companion with older 2 ME Production Studio 4K with success.)

More Auxs on PC for black magic

Hello I am trying to use this with the Aux on the constilation as well as more inputs for PC is there anyway to use this I dont see any other option besides the 3 aux and 8 input

Need Support For ATEM Mini Pro

When connect device at osx , system get warning
Unknown model: ATEM Mini Pro. Some bits may be missing

Button functionality for all ATEM supersource parameters

Describe the feature
As well as function for setting the box input source I would like to have the ability to also set enable, size, position and crop parameters for a supersource box. This would eliminate the need for a lot of ATEM-macros for us.

Is this platform dependent (windows, mac, ..)?
No it´s an ATEM thing

If documentation is required to implement, do you know where to find it?
Se supplied screenshot

Usecases
User wants to change an entire atem supersource setup (which boxes to enable, the size, position and crop and input) using one stream deck button.

Request: audio mixer input mutes

I have an ATEM 1 M/E and I'd like to be able to control the audio input mutes. I have different audio sources plugged into both the RCA and XLR jacks, and I use one or the other depending on the situation. Right now I have to open the atem control software, go to the audio tab, and toggle the "ON" buttons for each input. I would also need the buttons on the streamdeck to change color depending on each audio input state so I know which is on and which is off.

input 9 and 10 not available on 1M/E production studio 4K

1.3 1333

there seem to be a bug on the Atem 1M/E production studio 4K which does not show input 9 and 10 in the dropdown an older config where the inputs are used works so its probably just a problem with the parsing of the Atem it shows the right outputs

Select "Next Transition" type

We are getting so close on the ATEM to ditching macros. But we need a couple more functions.

1. Be able to select the "auto/cut" transition "NEXT TRANSITION" from background to any of the keys in any combination. (and on any ME)

[BUG] Does not update instance status on initial connect

The module does not update the connection status to STATUS_WARNING while connecting, or STATUS_ERROR on disconnected, when you start companion, and the atem is unavailable. I have not tested if it updates correctly when it successfully connects first.

Instance feedback for Macro

Describe the feature
Hi i need instance feedback for Macro Button like a change color for preview and program.

Is this platform dependent (windows, mac, ..)?
MAC

If documentation is required to implement, do you know where to find it?
If applicable, add screenshots, protocol description PDFs, etc to help the developers along

Usecases
Add a couple of usecases for why this should be implemented and when/why to use it.

Request: T-Bar functionality or AUTO TRANS Feedback?

It would be awesome to use the T-Bar functionality or to have a feedback on the already existing AUTO TRANS. I can use the AUTO TRANS button, it works just fine. But there is no feedback, that it is doing the transition. This would be perfect, if that was added to the features.
Otherwise: Awesome work!

Action to change box input in SuperSource

To start, let me just say Thank You for this module to Companion! It is a huge help to me! As I've been experimenting with this, I'm realizing that it would be very helpful to have an action to change a box input inside of SuperSource. I thought about adding it myself, but a cursory look at the code showed that it's a pretty sizeable module and would take quite a bit of my time just to understand how the current code even works. I was wondering if someone familiar with the code could add this functionality?

It's not outside the realm of possibility for me to attempt to add it, but I'd need some direction on how to set up a dev environment and the code layout of the extension.

Thanks!

ATEM Blackmagic pb to import config

Hi I am on macOs High Sierra and I want to import a configuration
When I try to "replace current configuration" I obtain this message :

Can you help me ?
Sorry for my bad English, I am French
Xtof

Atem function to change supersource input doesnt work

Describe the bug
When in Companion creating a button that uses the Atem function to change Supersource box source, it has errors.
The supersource box source in atem changes to the assigned input on the companion button, but at the same time the box inactivates and the settings (size etc) resets.

To Reproduce

1. Create a supersource setup in Atem with chosen sources
2. Create a button in companion to change Atem supersource box source and assign a source to one of the boxes (another source than already chosen in Atem).
3. Press the button in Companion.
4. Check the supersource in Atem. The source is probably changed but inactivated/resetted

Expected behavior
Only the box source should change. No other settings or inactivation should happen

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• W10 64bit
• Browser: Chrome
• Companion Version: 2.0.0-fd488b6-1762
• Atem version: 7.5.1

Companion on Blackmagic ATEM. Connection lost

I've got a Stream Deck with Companion installed on PC to run a Blackmagic ATEM. Everything is on static IPs and when I initially setup everything works fine. Then when I power off Companion and then restart it (or turn everything off and reboot the next day etc) the Deck buttons appear but don't work and no feedback is happening (on Companion as well as the physical buttons). Companion is showing everything is connected and OK. All the IPs are correct but the bottons do nothing. No amount of restarting/rebooting the PC/ATEM/Software in various different orders makes any difference. The only way to solve is to go into the GUI and remap the buttons (ie drag the template buttons over to the Deck buttons again), Then it works fine (with feedback) until I close down (and try to restart) Companion again. No other software is running (ie StreamDeck/BM ATEM front end). If I do use the Stream Deck program with the Companion plugin, I get exactly the same problem. Any ideas?

Blackmagic Macro triggered everytime from the beginning

When creating an Macro in Blackmagic ATEM with an "User Wait" Companion triggers the Macro everytime from the beginning, not where the Macro is actually….
So User Wait Macros can´t be used with Companion....

Media player next/previous buttons

Be able to cycle through the stills rather than having to go to a specific still

Add Hyperdeck Support to ATEM Module

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:

• record
• play
• stop
• clip selection

Error on Dragging Preset to Button

Attempted to drag a preset onto a button. Appears to occur for all presets in the catalog.

After clicking OK to the dialog, the preset does otherwise seem to apply correctly.

ATEM Mini Pro: set M/V on AUX bus

Describe the feature
You can set the AUX bus source on BlackMagic ATEM Switchers as action.
The ATEM Mini Pro also features a Multiview that can be put on the AUX/OUT with the integrated button.
Feature Request: Add entry for multiview on AUX bus for ATEM Mini Pro.

Is this platform dependent (windows, mac, ..)?
No.

If documentation is required to implement, do you know where to find it?

Usecases
For the ATEM Mini Pro the functionality is incomplete and we have to fall back to using the original hardware buttons on the ATEM because Multiview cannot be set through companion.

Unknown model: ATEM Mini Pro. Some bits may be missing

I'm running 2.0.0 (62b280c-2271) on raspberry pi (official companion image on pi 4 4gb).
Getting this message while adding ATEM mini pro.

also I have this in log UI

03. 23:26:15 CORE(cb): db.tmp->db failed: Error: ENOENT: no such file or directory, rename '/home/pi/companion//db.tmp' -> '/home/pi/companion//db'

Kindly advise!

[BUG] It is not possible to define which ME to get instance feedback from

When configuring instance feedback in Companion version 1.4, it was possible to pick between the two ME's, but in version 2.0 (alpha/beta) you can only pick camera input, and the feedback is activated if either ME has the camera input in preview/program.

Screenshot from Companion 1.4, where it's working as expected

Screenshot from Companion 2.0, where it's not possible to pick ME

Companion - ATEM DSK Dissolve

Using the ATEM Television Studio HD "atem 1: Set Downstream KEY OnAir" toggle it only cuts on and not a dissolve. And it will not Toggle. The latch (toggle) check box seems not to make a difference.

1 build button "atem 1: Set Downstream KEY OnAir"
2 set on air options to toggle.
3 hit button either on a stream deck or in the emulator

I expected the DSK 1 to dissolve on and off in a toggle manner. however what happens is it cuts on and won't clear.

However the on/off works I can make it cut on and off. but I would like it to dissolve which is allowed in the Blackmagic switcher software if you click on the auto button.

IOS 10.13.6
Companion v1.3.0
Blackmagic 8.0.1

Make sure you're on the latest bleeding edge build (remove this section from the bug report)
Before you report a bug, make sure you're not reporting something that have been fixed in the master branch by downloading a "latest" build from https://builds.bitfocus.io/companion/

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Atem change supersource box properties: different parameter-scale in Companion versus Atem

Hi!
I really appreciate the new functionality to set Atem Supersource parameters with a Companion action. Great work!

However there are a couple of small issues I hope can be adressed in future releases.

First: Companion and Atem uses different decimal scales, so a size parameter 0.35 in Atem has to be 350 in Companion. This works but is a bit complicated, if you for example draw up a box setting in atem and want to program a button in Companion. All parameters has to be recalculated instead of just copied.

Second: the fields in the setting in companion are too small so you don´t see the full parameter.

Request: Renaming input labels

It would be nice to be able to have a custom text field with new label text for a specific input number. For example, we use Companion to control our VideoHub router and sometimes the source going to an input on our switcher will change, but the label on the multiview won't without editing it manually. The idea for this would be to add an action from the ATEM instance to where we could enter the text for the new input so it changes automatically.

Request for Live And Program For BlackMagic Atem

Describe the feature
To allow for feedback from the Atem studio to highlight which input is currently active.
Or the ability to change the background colour based on if the input is active on the atem studio.
Both for program and preview.

Is this platform dependent (windows, mac, ..)?
Blackmagic Atem Studio

If documentation is required to implement, do you know where to find it?
https://www.blackmagicdesign.com/uk/developer/product/atem

Usecases
So the button for program 1 would turn red if it is switched to program on the software. If it is not active then background would turn black.

Blackmagic Atem DSK 2 not functioning

Using a Blackmagic ATEM Television Studio (https://www.blackmagicdesign.com/products/atemtelevisionstudio) and using the DSK auto trans command for DSK 1, it works fine, select DSK 2 and it doesn't seem to work at all.

ATEM DSK Toggle

The DSK toggle appears to turn on DSK, but subsequent presses will not turn the DSK off. You can manually turn off DSK in ATEM software, or with a separate "OFF" key in companion. Do I understand the function corretcly? One press should turn it on, second press should turn it off-correct? Would also be nice to toggle the DSK auto instead of the cut in the same way...

Also, feedback appears to not work, key background doesn't change when DSK is on-air.

ATEM 1M/E 4k, v6.9, companion v 1.2.0-85393af-1109

TypeError: Cannot read property 'auxilliaries' of undefined at Object.GetParsedModelSpec

TypeError: Cannot read property 'auxilliaries' of undefined
at Object.GetParsedModelSpec (/Users/.../code/companion/lib/module/bmd-atem/dist/models.js:311:34)
at Atem.atem.on (/Users/.../code/companion/lib/module/bmd-atem/dist/index.js:275:39)
at emitNone (events.js:106:13)
at Atem.emit (events.js:208:7)
at AtemSocket.Atem.socket.on (/Users/.../code/companion/lib/module/bmd-atem/node_modules/atem-connection/dist/atem.js:50:46)
at emitNone (events.js:106:13)
at AtemSocket.emit (events.js:208:7)
at AtemSocket._parseCommand (/Users/.../code/companion/lib/module/bmd-atem/node_modules/atem-connection/dist/lib/atemSocket.js:153:18)
at AtemSocket._parseCommand (/Users/.../code/companion/lib/module/bmd-atem/node_modules/atem-connection/dist/lib/atemSocket.js:172:18)
at AtemSocket._parseCommand (/Users/.../code/companion/lib/module/bmd-atem/node_modules/atem-connection/dist/lib/atemSocket.js:172:18)

[Bug] AUTO DSK Transition only activates if DSK is on air

The "AUTO DSK transition" will only activate if the DSK is already on air. With the DSK off, "AUTO DSK transition" does nothing, with the DSK on, "AUTO DSK transition" will work as intended and AUTO it out. Same issue with DSK 1 and DSK 2 both.

build companion-2.0.0-5e2c920-2061
Stream Deck XL 32-key
ATEM Firmware 8.1, ATEM 1 M/E Production Studio 4K
Windows 10 Pro, 1903 (Build 18362.657)

Was working previously on build companion-2.0.0-8b6d53c-2055, all other specs identical.

[BUG] Instance Feedback do not retain - ATEM

• Add key up/off action

'Instance feedback' do not retain, if software crashes, or when importing full configuration files.

To Reproduce
Steps to reproduce the behavior:

1. Add ATEM instance
2. Add buttons from ATEM presets - Program M/E1 - Input 1 (set to button 1.2) Program M/E1 - Input 2 (set to button 1.3). Preview M/E1 - Input 1 (set to button 1.10) Preview M/E1 - Input 2 (set to button 1.11). (the preview buttons 1.10 and 1.11 will have instance feedback of green background when in use, indicating which camera is in preview, the Program Buttons (1.2 and 1.3) will have a instance feedback of red background when those cameras are selected.
3. Export the full configuration
4. Reset Configuration
5. Import the Configuration
6. Close and Restart Companion / GUI
7. When buttons load, the instance feedback will not retain.

Expected behavior
The instances feedback will not retain, after crash or restarting Companion, or importing configuration

Desktop (please complete the following information):

• Windows 10
• Internet Explorer
• Companion Version 2.0 companion-2.0.0-873cae1-2092-win64

Additional context
Zipped config file attached.
ATEM_Config_2.zip

ATEM Mini Pro Recording Actions

Hi,

With the new ATEM Mini Pro, they have the ability to record a stream to a USB/SDD drive. This is awesome and I would love to integrate it into my work flow. I saw in the SDK in Sec.12 they have predefined functions for recording state, errors, and of course start and stop recording. Is this possible to integrate these feature into the companion app? It seems doable but my lack of coding knowledge makes it difficult for me to do anything.
Thoughts??

thanks

ATEM 1 M/E Production Studio DSK 2 not functional via companion

Starting with Firmware 8.x DSK 2 on blackmagic ATEM(and maybe other functions too) are not responding to companion.

Blackmagic ATEM Module - Macro Name on Button

Describe the feature
Add the ability to automatically take the name of a specific Macro on an ATEM and make that the text on a button.

Is this platform dependent (windows, mac, ..)?
No.

If documentation is required to implement, do you know where to find it?
https://www.blackmagicdesign.com/developer/

Usecases
This would allow a user to have a page of macro buttons that update as new macros are made. This way the user doesn't have to mess with changing the button title each time they write over a macro.

Add Dynamic Text for ATEM Macro Names

Describe the feature
I see in the dev build there's support for dynamic text for the sources and various other things, however, not for the macro's yet. If its possible, please pull these in so they can be linked to macro fire buttons.

Is this platform dependent (windows, mac, ..)?
No

If documentation is required to implement, do you know where to find it?

Usecases
So buttons to fire ATEM macros can mirror the name of the macro instead of simply being called "Macro 1" or having to duplicate the name manually in Companion.

Thanks,
Keith