{"id":619,"date":"2020-07-01T14:38:54","date_gmt":"2020-07-01T14:38:54","guid":{"rendered":"http:\/\/techministry.blog\/?p=619"},"modified":"2020-07-01T14:38:54","modified_gmt":"2020-07-01T14:38:54","slug":"using-node-js-python-multiple-raspberry-pis-and-usb-lights-to-create-an-inexpensive-wireless-camera-tally-system-that-can-arbitrate-multiple-sources-simultaneously","status":"publish","type":"post","link":"https:\/\/techministry.blog\/?p=619","title":{"rendered":"Using node.js, python, multiple raspberry pi’s and usb lights to create an inexpensive wireless camera tally system that can arbitrate multiple sources simultaneously"},"content":{"rendered":"\n

Update: Version 1.2 is available now; read about it here<\/a>: <\/strong><\/p>\n\n\n\n

At my church, we have two auditoriums, each with their own video switcher and cameras. All of the inputs and outputs of each switcher are on a common video router, so all of these sources can easily be shared across both rooms. However, even with all this, we have no camera tally system. Commercial tally systems can be expensive, and it’s just something we’ve never been able to afford.<\/p>\n\n\n\n

It’s not normally an issue, but sometimes we want to pull up a shot of a camera in Auditorium 1 and show it in Auditorium 2. Because we have no tally system, the camera operator would not know their shot was being used. And, even if we did have a tally system, those systems generally only interface with one tally source\/switcher, not multiple sources at the same time.<\/p>\n\n\n\n

A few weeks ago, I was quarantined from work due to a co-worker testing positive for COVID-19. I set out to use this time to write a tally system for our church to use. Now that we’ve re-opened for church services, we will really need this, because we will have cameras capturing the service to stream online, but won’t necessarily have those cameras visible on the projector screens in the auditoriums during that time, where the operators would at least have a visual reference if their shot was in use.<\/p>\n\n\n\n

And, because we have two video switchers, I needed to come up with a solution that would allow either video switcher to pull up a camera in either auditorium in Preview or Program, and make sure the operator still knew their shot was in use.<\/p>\n\n\n\n

So here is Tally Arbiter<\/strong>. I called it this because the software aggregates tally data from multiple sources and “arbitrates” whether that device is in Preview, Program, or both across all sources and buses.<\/p>\n\n\n\n

\"\"
I played Halo a lot back in the day. A LOT.<\/figcaption><\/figure><\/div>\n\n\n\n

The server software is written in Node.js and can run on a Raspberry Pi. It supports the TSL 3.1 network protocol like what our Ross Carbonite switchers use, but I’ve also written support for Blackmagic ATEM switchers, OBS Studio, StudioCoast VMix, and Roland SmartTally. I plan to one day add support for incoming webhooks, and GPIO inputs for switchers that don’t have network-based protocols.<\/p>\n\n\n\n

\"\"
The settings page of the Tally Arbiter server.<\/figcaption><\/figure>\n\n\n\n

The software supports tally data coming from multiple sources, and each source can vary in protocol type. This could be useful, for example, if you had shared cameras for your production on-screen using an ATEM and also through your live stream using OBS or VMix, and you need the cameras to reflect the tally data of either system.<\/p>\n\n\n\n

You can configure multiple devices in the software. These would be what generally receives tally data, whether it be cameras, CG stations, monitors, etc. Each device can support addressing from multiple sources. This is the “arbitration” portion of the software.<\/p>\n\n\n\n

Once a device is determined to be in preview and\/or program, device action(s) can be run. This can be sending out a TSL 3.1 protocol message (to a monitor\/scope\/multiviewer), an outgoing webhook (to tell another device to start playing a video (“roll clip”), for example), triggering a relay if you have CCUs that need contact closures to turn on the tally lights, or even local console output for logging and testing.<\/p>\n\n\n\n

Some of our cameras have built-in tally lights, like the two Hitachi Z-HD5000 cameras we have. For those, I implemented a separate relay controller client that listens to the data on the Tally Arbiter server. It uses simple USB relays with the Node.js library I created a couple years ago that controls our auditorium window shade<\/a>.<\/p>\n\n\n\n

I bought a project box, put the relay in, ran some CAT5e cable I had laying around and connected it to the relay and the CCU’s with custom DB25 connectors. I had to modify the project box some because I wanted the relay to sit flat in the box, so I used a dremel to remove the bottom of the middle screwposts, which weren’t really needed anyway. Never be afraid to modify something to make it work!<\/p>\n\n\n\n

\"\"
The relay fits snugly inside this box. This particular unit has 8 relays, so I could add 2 more cameras with preview\/program tally control to this unit.<\/figcaption><\/figure>\n\n\n\n
\"\"
The box and the Pi running the server fit nicely on top of one of the CCUs.<\/figcaption><\/figure>\n\n\n\n
\"\"
A clean rack is a happy rack!<\/figcaption><\/figure>\n\n\n\n
\"\"
Preview and Program lights!<\/figcaption><\/figure>\n\n\n\n
\"\"
This will make our camera operators happy.<\/figcaption><\/figure>\n\n\n\n

But what about the cameras we use that don’t have tally lights? For these, I decided to use Raspberry Pi Zero W<\/a>‘s that would run software listening over websockets to the Tally Arbiter server. These particular Pi models are inexpensive and simple to use. I knew that I could get the least expensive cost for physical tally lights out of these Pi’s if I went the GPIO route with some LED lights and custom circuitry, but I wanted to design something that people who may not be comfortable with these concepts could easily implement. And honestly, the thought of soldering something just sounded like something I’d have to possibly maintain down the road. So, I used the blink(1) USB lights by ThingM<\/a>.<\/p>\n\n\n\n

I first started experimenting with these USB lights about a year ago when I created a silent notification system<\/a> for our band to use in case we had a tech issue during a service. The company that makes these has published very easy to use APIs, which makes it a great tool to use with custom software.<\/p>\n\n\n\n

\"\"
I like this simple black case from Vilros. You can get the whole kit minus the SD card for about $30 on Amazon.<\/figcaption><\/figure>\n\n\n\n
\"\"
Here’s a blink(1). A pretty versatile device!<\/figcaption><\/figure>\n\n\n\n

The listener client script is written in Python since that programming language runs so easily on the Raspberry Pi OS no matter what model Pi you have. And, since we are using the socket.io websocket libary, bi-directional real-time communication between the server and clients even though the programming languages vary is not an issue.<\/p>\n\n\n\n

\"\"
I used a USB extension cable to bring the light up by the camera, but the Pi is down on the floor of the platform.<\/figcaption><\/figure>\n\n\n\n
\"\"
Another view.<\/figcaption><\/figure>\n\n\n\n

All together, each wireless tally light should cost between $55 and $60 depending on what Pi case you use, SD cards, etc. Tally Arbiter has no built-in limitation of the number of wireless clients that can be connected, so this makes it a very versatile and flexible system no matter what the size is of your production.<\/p>\n\n\n\n

Lastly, I also created an option to view live Tally data in a browser, like on a tablet or phone. You can select the device from the list and the background of the page will be red, green, or black depending on that device’s tally state.<\/p>\n\n\n\n

\n
\"\"\"\"<\/div>
The web based tally option is nice if you need a quick portable tally option.<\/figcaption><\/figure>\n\n\n\n

The web tally is controllable through the Settings page just like any other listening client, so you can reassign the tally remotely and even send a flash to that client to get their attention.<\/p>\n<\/div><\/div>\n\n\n\n

Here’s a walkthrough video of the whole system in action:<\/p>\n\n\n\n

\n