Broadcast · Overlays and data feeds
The score, the down and distance, the drive, the leaders — all of it reaches your switcher from the same taps the scorer is already making on the sideline. Nothing keyed by hand, and nobody in the booth retyping a score.
Set the addresses up in August. Flag a game. That is game night.
The score bar as it is shipped. It is an ordinary web page with a transparent background, sized for a 1920×1080 browser input — the team colors come from the game you built, not from a graphics editor.
Two ways in
Both are in every account, and using one does not rule out the other. Most crews start with the shipped overlays and bind a feed or two later, once they know which numbers they actually put on screen.
No graphics work
Transparent pages you add as a browser input. The graphic draws itself in your school’s colors, with the opponent’s taken from the game you built, so week two looks right without anyone opening a graphics editor. Each one has its own switches — compact, no down and distance, rotating — set on the setup page and baked into the address.
Your own package
The same data as JSON or XML at a plain address. Every field describes football rather than a vendor, so one feed drives vMix title fields, an OBS browser source or a CasparCG template without translation. Nothing is computed twice — the feed reads the same play log the stat sheet does.
Field names are the real ones. Team and player names here are invented.
What is on the shelf
There is no graphics tier. A school that streams its games is not a different customer to us, so the whole package is in the same $250.
Both teams, the score, the quarter, down and distance, possession and timeouts. The graphic that is up most of the night, with a cut-back version for the stretches where the picture needs the room.
The same bar with a wide black box in the middle, left empty for your own game clock and play clock, and the quarter and down carried around it. Two arrangements, each with a see-through version that lets the field show through the team blocks. The columns are a fixed width, so the black box sits at the same coordinates in every game however long the visiting school is called — your operator positions the clock once and never touches it again.
Plays, yards, and where the drive started. It hides itself between possessions rather than sitting there reading zero, so it is safe to leave in a bank all night.
The side-by-side comparison, with each team’s passing, rushing and receiving leader underneath. Full width for a lower third, or tall for a side slot.
Offense, defense and special teams, as a lineup card in one column or two. Built from a lineup the coach types once on the game setup screen, so nobody is reading names off a program into a graphics editor an hour before kickoff.
Rushing, passing, receiving, tackles, kicking and punting — for the season so far or for the game on air. The season boards read finished games only, so one cut to air mid-game will not change under the director.
One input that cycles those categories on a timer instead of a switcher input for each, and skips any nobody has qualified in yet — so it is never a card reading zeroes in week one.
Every score in the game with the drive behind it — plays, yards, time of possession, longest gain. Built for a booth monitor at a glance, and the answer to “how did they get that one?” without scrolling a play log.
Not a keyed graphic — the live page your commentary team keeps open on a phone. Score, current drive and leaders, updating as the sideline enters plays, so nobody is asking the scorer what just happened.
Friday nights, as they happen. Real overlays from real broadcasts, plus what we are building next.
Setup
The addresses never change. There is no game id in them and no week number — every overlay and every feed follows whichever game is marked ON AIR in StatChat, which is one menu item on the dashboard.
The setup page builds each one for you, with the switches you want already in it. Paste them into your switcher at the start of the season.
One person, one menu item, before kickoff. Every overlay and every feed follows it — including the ones the crew never touches.
No re-mapping when the opponent changes, no editing a URL each week, and nothing to redo when a game moves to a Thursday.
Putting the game id in the address would mean editing every input every week — in a control room, twenty minutes before kickoff, by whoever happens to be there. The flag moves that job to one click on a dashboard, and it moves it off the crew.
Compatibility
Nothing here is written for one vendor. The overlays are ordinary web pages with real transparency; the feeds are a URL that returns JSON or XML.
Overlays go in as a Web Browser input at 1920×1080. Feeds go in through the Data Sources Manager as XML, with an XPath per view.
Add an overlay as a Browser source at 1920×1080. Nothing else to configure — the transparency is real, so it keys straight over the program feed.
Same browser input, same address. Where a package prefers to bind fields rather than key a web page, the XML feed does that instead.
CasparCG, Singular, a scoreboard someone on your crew wrote. If it can poll an address for JSON or XML, it can read StatChat.
Use XML in vMix. Its data sources expect an array of objects; the JSON view is a single object, so the XML view is the one that binds.
Read first
All three are public and need no account, so you can read them before you buy anything and send them to whoever runs the switcher.
Every dialog, the XPath each feed needs, and the column names to bind to in the Title Editor.
The NFHS rules behind every number the graphics show — and where they differ from the NFL conventions people assume.
For whoever is entering the plays. What to do on a lateral, a muffed punt, and a penalty that wipes out a touchdown.
Pricing
A season, not a subscription that renews while nobody is playing. No broadcast add-on, no per-user charge, and no overlay held back for an upgrade.
Football today. More sports coming.