About a year ago, I released some camera tally lights software because we desperately needed it at my church. Since that time, a ton of new features have been added, both by me and by the community.
It’s now in use in hundreds of places, from churches to event venues to sports stadiums.
Version 2.0 was silently released a few weeks ago, which includes a compiled application that can run natively on Windows, MacOS, and Linux, without the need to install Node.js and other dependencies like the command line. And, of course, it still runs on a Raspberry Pi.
Lots of people in the community have shared how they are using it, made their own tutorials, and added to the existing documentation.
It’s truly becoming a community project, and I love that. We now have an official Facebook user group to help facilitate conversation amongst users, and I’m excited for the new features on the roadmap in the coming days.
A few features to note since version 1.5:
- An entirely new User Interface and native applications for the Big 3 OS models
- Easily installed for command line via new NPM image or Docker image
- 1-second updates function for TSL Clients (provides compatibility with certain tally products like Cuebi)
- Recording/Streaming statuses for OBS and VMix now available for tally states
- Generic TCP Device Action improvements
- TSL 5.0 source support
- New Ross Carbonite source type to monitor any bus regardless of the “on air” settings
- Web tally page can now be loaded directly by Device Id, and chat can be disabled
- Pimoroni Blinkt! Listener Client
- TTGO_T Display Listener Client
- Improved Outgoing Webhooks – support for https and content-type selections
- Roland Smart Tally emulation for use with STAC
- Panasonic AV-HS10 support
- Support for ATEM super sources in tally states
- Bug fixes and performance improvements
If you’re new to Tally Arbiter, go check it out! You can also join the new Facebook user group here: https://www.facebook.com/groups/tallyarbiter
And to everyone in the community who has helped to make TA what it is, thank you! Your contributions are helping everyone.
Is it possible to update via Raspberry Pi CLI to 2.0? What should the text look like for that?
Thanks. I saw that and tried it but it didn’t seem to update. I was able to get use git pull in the TallyArbiter folder and it looks like it updated but it gives me this error when I go to the 4455 website: Error: ENOENT: no such file or directory, stat ‘/home/pi/tallyarbiter/views/index.html’
I was able to get this exact message on a remote Mac with the host IP:4455 and with 127.etc:4455 if that helps.
Sorry, I’m coming from v1.3.
I didn’t get 2.0 installed on the NUC running Raspbian but I did install it on an iMac. I just want simple green red output on the m5stick C but I don’t know what Output Type to use in settings. What should I use?
Hello, how much RAM I need to install this version on ubuntu 20.04?
I would recommend at least 2GB.
Hey Joseph, I’ve got everything setup to the point where the listeners are working with TallyArbiter, but I don’t quite understand what I need to enter/configure to get my Ross Carbonite Black Solo to communicate. Our Carbonite has never been setup to send/use tally data, so not sure what needs to be configured on it. We have 4 cameras on inputs 1-4 that we want to use with the tally lights.
I feel like we’re so close! Any help is greatly appreciated.
Thanks for everything you’ve done.
TA will act as a server, and the Carbonite will send data to it as a client. So add a new Source (use TSL 3.1 as the ones named Ross Carbonite seem to not work correctly at the moment) and pick a port number like 9800 for example. Then follow these instructions: http://help.rossvideo.com/carbonite-device/Topics/Devices/UMD/TSL.html
For the Carbonite side setup, do I need to do this process for each input for both preview and program? Meaning that if I have 4 inputs, I would need to run through this process 8 times?
No. Just need one source in TA and the Carbonite sends all of the tally data. Then create your Devices in TA and assign Device Sources that specify addresses 1-4 for each of the Devices/Cameras. You can reach out to me on the contact form if you want to set up a time for us to work together, or there’s also videos on YouTube.
Perfect! Going to give it a shot this afternoon. I think that was the one missing piece for us. Thanks again and I’ll reach out via the contact form if needed. I really appreciate your time 🙂
Setting up the TSL Source and then configuring the Carbonite to send the TSL data to the IP/port of TA was all I needed to do! It’s working! The team is so excited to give this a try as soon as we receive the extra tally lights. Thanks again!