Change transition selection component not working

[whizkidTRW]

We have an ATEM Mini Pro (v8.4) and I'm trying to turn the upstream keyer on and off directly before a transition in order to control the state of our custom PIP when using upstream keyer 1 DVE configured to an input. The 'change transition selection component' is exactly what I wanted and have downloaded the latest Companion (2.1.1 - 4797bf3-2584 at the time of this writing) but when I configure it to either 'Key 1 & On Air' or 'Key 1 & Off Air', it does nothing. Even with a dedicated button to turn it on and off, set to Toggle, Off, or On, it does nothing. Is this supposed to work on the Mini Pro or is this a known issue? Otherwise, this appears to be a bug. I'd so like to use this instead of the macros I'm using today, since those only toggle it on or off and don't set it direct to a specific state.

[Julusian]

I have just tested this in the exact same build and it is working for my mini pro iso, so I don't know why it wouldnt be working for you.

Just to check, you are expecting the yellow row of buttons here to be changing. And you have background already enabled? (the atem wont let that it go to nothing)

[whizkidTRW]

Yes, absolutely correct. I’ll double check tonight that the background was still enabled but I’m pretty sure it was. Thanks for checking I’ll get back to you and confirm.

On Mon, Sep 21, 2020 at 6:50 AM Julian Waller ***@***.***> wrote: I have just tested this in the exact same build and it is working for my mini pro iso, so I don't know why it wouldnt be working for you. Just to check, you are expecting the yellow row of buttons here to be changing. And you have background already enabled? (the atem wont let that it go to nothing) [image: image] <https://user-images.githubusercontent.com/1327476/93763237-f810a600-fc08-11ea-949c-b0cd71c16035.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#83 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHWZ2KQL452VMVQCYAGDGKLSG44ZBANCNFSM4RUDEB2Q> . --

Todd Witten todd.witten@gmail.com

[whizkidTRW]

I was able to confirm that you were right. I did not understand the interaction between the "Change transition selection" and the "Change transition selection component" feature. I finally got it to work, though it would be nice if the "Change transition selection component" feature, when setting the Key 1 state to a specific On or Off state didn't do the opposite if that button is hit a second time. That seems to be counter-intuitive as compared to the Toggle feature, which ended up working well for me. It's all about what's left in the Preview state at the end of the steps and I know this may be a BlackMagic thing and not a module thing, but it doesn't work the way I expected it to when setting an explicit state. Thanks again for all of your work on this. This will make our workflow at church much more approachable by those less tech-savy and give more opportunities for those to serve. Very much appreciated. Thanks! Todd Witten todd.witten@gmail.com

…

On Mon, Sep 21, 2020 at 5:23 PM Todd Witten ***@***.***> wrote: Yes, absolutely correct. I’ll double check tonight that the background was still enabled but I’m pretty sure it was. Thanks for checking I’ll get back to you and confirm. On Mon, Sep 21, 2020 at 6:50 AM Julian Waller ***@***.***> wrote: > > > I have just tested this in the exact same build and it is working for my > mini pro iso, so I don't know why it wouldnt be working for you. > > > Just to check, you are expecting the yellow row of buttons here to be > changing. And you have background already enabled? (the atem wont let that > it go to nothing) > > > [image: image] > <https://user-images.githubusercontent.com/1327476/93763237-f810a600-fc08-11ea-949c-b0cd71c16035.png> > > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#83 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AHWZ2KQL452VMVQCYAGDGKLSG44ZBANCNFSM4RUDEB2Q> > . > > > -- Todd Witten ***@***.***

[Julusian]

I dont follow what you mean with:

it would be nice if the "Change transition selection component" feature, when setting the Key 1 state to a specific On or Off state didn't do the opposite if that button is hit a second time

[cybershoe]

Tacking on here, because I feel like I'm running into the same issue and I'm not clear from the thread what the resolution was.

Is there documentation anywhere about what the "Change transition selection component" action is supposed to do? Based on the naming, I would expect that, for example, if Key1 is currently deselected for the next transition, and if I execute the "Change transition selection component" action with following options:

M/E: M/E 1
Component: Key 1
State: On

that it would set Key 1 as "On" for the next transition, but much like OP's initial description, the state of the next transition doesn't change at all for me. I'm also unsure what OP is referring to with the "interaction between the "Change transition selection" and the "Change transition selection component" feature."

Companion 2.1.2 build f4bcaf3-2679
ATEM Mini Pro firmware 8.6 build 2562fc70

[Julusian]

that it would set Key 1 as "On" for the next transition,

@cybershoe yes, that is how it is supposed to work and is whenever I test it

The difference between the two is this:

• "Change transition selection component" - changes one of the background/key1/key2
• "Change transition selection" - changes the whole selection to whatever is specified

[cybershoe]

I noticed that I mistyped my scenario... the state isn't "On", the state is "On Air". That implies that the selection will result in the key becoming "On Air" as part of the next transition (i.e. if key 1 is on air, then key 1 next transition is disabled, else key 1 transition is enabled).

Either this is a terminology problem (in which case I'd suggest "On Air" be changed to just "On", since it doesn't seem to affect "On Air" status, just whether the selection is "On"), or even better, change it to be "Selected" and "Not selected".

We're getting into feature request territory here, but ideally I'd like to see 5 options:

• Selected: The component is selected for the next transition, no matter what
• Not selected: The component is not selected for the next transition, unless it's the only currently selected component, in which case no action is taken
• Toggle: What it currently does, toggle the selection state for the component
• On Air: (only available for key components) If the component is currently on air, the component is not selected for the next transition (component remains on air), otherwise it is selected (component goes on air)
• Off Air: (only available for key components) If the component is currently not on air, the component is not selected for the next transition (component remains off air), otherwise it is not selected (component goes off air).

Admittedly I see this getting pretty hairy, and I expect that it's just a mislabelling of what's supposed to be the "On" option. Getting #1052 in companion core implemented would get away from that though and let us define this behaviour through conditions.