edge.
Three products, one path: the piece is born in the browser, called from the rundown the newsroom already runs, and goes on air composed over the signal.
The same piece, from editor to air
edge.template creates the piece, edge.playout calls it in the rhythm of the script, edge.engine composes it over the signal and delivers fill and key. Three products and a single path — the same HTML piece crosses all three with no conversion. The designer sets the standard once; the newsroom publishes at the pace of the news. And nobody goes back to a specialist at every last-minute change.
From the signal coming in to the destination it reaches.
One machine in the middle of the path: it takes the signal, composes the graphics and hands fill and key back to wherever the operation needs them.
The signal your plant already speaks.
- NDI
- SDI
- ST 2110
NDI, SDI or ST 2110 in — and out in the same standards, with fill and key. edge.engine does not ask the operation to change standard in order to take graphics: it fits what is already in the rack.
- Fill and key out, in the same standards as the input
- A Blackmagic or AJA card in a commodity computer — not an appliance
- Four independent outputs: MCR, studio, LED and streaming
edge.template
The designer sets the standard. The newsroom publishes.
A library of broadcast graphics ready to go on air, edited straight in the browser. The designer closes the standard — the newsroom swaps the content without breaking the identity. The same piece comes out in several formats: broadcast, reels, Instagram and others. And the embed plugin will take publishing into Premiere, APNEWS and Mimir.
- Library of customisable broadcast graphics, ready for air
- Web editor: real-time visual identity, standard held by the template
- One design, several formats: broadcast, reels, Instagram and others
- OGRAF compatible: the rundown calls the template as part of the script
edge.playout
Graphics in the rhythm of the script
The operation interface is integrated with the rundown system the newsroom already uses. Graphics sync with the live script, enter the scheduled queue and pass through preview before publishing. From the same place, the operator inserts graphics into the streaming and controls the studio LED walls. Every action is written to a log.
- Sync with the live script and a queue of scheduled graphics
- Preview before publishing — and a log of every operation
- LED wall control and real-time insertion into the streaming
edge.engine
HTML over the signal, on off-the-shelf hardware
edge.engine takes the signal in NDI, SDI or ST 2110 and composes the HTML graphics on top. On the way out, fill and key — in the same standards as the input. It runs on an ordinary computer with a Blackmagic or AJA card: off-the-shelf hardware, not a dedicated appliance. Four independent outputs, each with its own destination: MCR, studio, LED, streaming.
- Ingest and output in NDI, SDI and ST 2110, with fill and key
- Blackmagic or AJA cards in an ordinary computer
- Four independent outputs: MCR, studio, LED and streaming
No proprietary format between the editor and the air
The piece the designer publishes is the piece the playout calls and the engine composes over the signal. No conversion, no export, no trip back to the edit suite. Even the graphics package from Creative Services arrives like this: an HTML template, ready to edit.
HTML5
The piece is a page: whoever can edit content can edit graphics. The standard the browser already understands is the standard that goes on air.
WebGL
GPU-accelerated rendering, straight in the browser engine. The animation that runs in the editor is the same one that runs over the signal.
OGRAF
The link to the MOS the newsroom already uses. Graphics enter the rundown flow as part of the script — not as a separate system.
See the whole pipeline running on your own signal
A demo with your workflow: rundown, signal and walls.