Atem pgm+aux combination

[lenstar]

Hi I'm a camera controller and like to create a tally when a source is switch on the ppm (me1) of a ATEM and on a specified aux. So I know a camera is active when I'm viewing it on my monitor and don't make big changes in the actual camera.

Example input 2 is actual on PGM (me1) and on aux2 input 2 is switch swell it needs to give a tally.
If for example camera 4 is switched on the PGM and aux2 is watching input 2 there shouldn't be a tally. but when I select input 4 on aux2 the tally go on.

Is this possible?

[josephdadams]

It's a great idea. I will keep it on the list and let you know if it's something that can be added. Until then, you could possibly work around it by having a Tally client monitoring Input 2, and if you used something like Bitfocus Companion, you could press a button that changes both the Aux assignment on the ATEM to Input 4 and reassigns the Tally Arbiter tally client to Input 4 as well.

[scoobiekw]

This is related to my issue. I'd like tally for Key source in Atem. If Auxes and Keys were exposed as ME1-6 are currently, then a Device with AND logic could solve this issue, as well as allow for Tally of Key contents.

[lenstar]

I think I don't understand your workaround. What Scoobie say is right, you need a AND logic. if me1 and aux is the same a tally/gpo need to go on.

And one last question I want to run it all on a raspberry would that be possible?

[josephdadams]

I get what you're saying. I'm just proposing a solution that reassigns a tally client on the fly. That's really what you're doing anyway: you have a single tally light device at your shader station, and when you pull Camera 2 up on your station, you want to know if Camera 2 is in PGM or not, and light up the tally light in front of you if it is. So if you reassign what that tally client is looking at when you change what is feeding that Aux, you can get what you want.

Tally Arbiter is based around Device (camera) tally state. To incorporate the "AND" logic would require you to have multiple Devices configured - one that the actual Device/camera uses when they are in PGM (because they might be in PGM whether they are on the Aux or not) and another one that looks for when they are in a PGM bus AND the Aux bus. This can get hard to manage if you have a lot of cameras. Reassigning the tally client on the fly (which you can do today if you want) is easier to maintain long term, in my opinion.

Yes, no problem to run the Tally Arbiter server on a Raspberry Pi. Mine has been running for 8 months (as of this post) on a Pi3B+ with no issues. You can run the blink(1) or GPO clients on a Pi as well. I run my blink(1) clients on Pi Zero W's. They work great. I designed TA to run on Raspberry Pi's.