Tally Arbiter Version 1.4, with multiple ME support for ATEM, a new Bootstrap framework, and more!

It took long enough, but version 1.4 of my Tally Arbiter software is released!

Here are some of the highlights:

First of all, the entire web interface has been rewritten to support the use of the Bootstrap framework. This makes it a lot easier to use, and it looks much better too! Huge shoutout to Matthijs (mg-1999) for taking the time to do this. The bulk of the Bootstrap rewrite is his work.

This is the new interface!

Secondly, Tally Arbiter can now monitor multiple ME’s on ATEM sources, whereas previous versions could only monitor ME 1. This is great if you have more busses that you need to track for on-air sources! If a source goes into preview or program on the ME’s you’ve selected to monitor, and a Device is associated with an address on that source, it will show up.

It’s easy to choose which ME’s will be “on air”.

Third, the Blink(1) and GPO listener clients have been updated to support automatic attempts to reconnect to the Tally Arbiter server, if they start up and the server is offline. This will make it even easier to keep everything connected!

Also, support for Analog Way LiveCore devices has been added, thanks to Alberto (albertorighetto)! So if you have one of those devices, go check it out!

If you use the phone tally viewing page (a very convenient way to turn any phone or tablet into a tally light!), Tally Arbiter has two updates: a QR code has been added to the home page, making it easier for users to navigate to your Tally Arbiter server, especially if you’re running locally and you want to avoid typing in IP address information. Also, your device (if supported) will vibrate or pulse when the selected Device for tally goes into preview or program.

A QR code is automatically generated to facilitate phones and tablets connecting to your Tally Arbiter server.

Lastly, there were a few bug fixes here and there to help with performance.

Here’s a video to show it in action!

You can get the latest source code at the Github repo: https://github.com/josephdadams/TallyArbiter


  1. Hello Joseph,

    Thanks for all your hard work, your software is awesome !

    I’m working on a project where I think I’ll have to deal with TSL over serial (RS422 I believe) instead of ethernet, the switcher would be a Ross Vision, older generation. What do you think would be my best option here ? I’ll be on linux, do you think if I forward the serial data to TCP socket (based on this idea : https://stackoverflow.com/questions/22624653/create-a-virtual-serial-port-connection-over-tcp ), would that work ?

    Also, I’m curious about line 158 : //adds the GPIO input type option if the software is running on a Raspberry Pi. Would that mean that I could use the GPIO on the Pi to trigger a tally for a device ?

    Thanks again !


    1. Hey Sebastian! I don’t have any experience with socat or ser2net but you could try it! Let me know how it works. It would definitely expand the user base if that’s an option.

      GPI is not implemented at this time. But maybe down the road I will implement it. Or if someone else wants to, they can. 🙂


  2. Sorry, but now with Atem 2 M/E Production Studio not worked at all from bus M/E 1 – always monitoring bus M/E 2, regardless of settings “MEs to monitor”. Return to v1.3 – all worked nice. What what’s wrong with the version 1.4 ????


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s