# Built at the desk, during the show. Maestro Console started because the same line of text had to be cued three separate times on the same night — and because the third time usually did not happen at all. ## Why it exists Surtitling a live performance has quietly become three disconnected jobs. Someone runs the projection desk for the house. Someone else pastes text into the livestream, or nobody does and the stream goes out without captions. And the audience's own languages — the visiting group, the person who reads German but not French — are usually served by nothing at all. Three jobs, three scripts drifting apart, one performance. ## What it is A control surface for live text. It sits between the surtitle script and wherever that text has to appear, and it makes one keypress reach all of those places in the same moment. The script, the languages and the timing stay in one place; the destinations become a setting rather than a separate production. ## What it is not It is not a translation engine, a streaming platform, or a replacement for your projection system. It does not write your surtitles and it does not decide when a line should appear — the operator does. It drives Glypheo, YouTube and the phones you already have rather than asking you to move to something new. ## Where it comes from Built in Belgium by one person, and developed in the place it is used — at the operating position, during real performances, with the lights down and no second chance at a cue. Most of what is in it exists because something went wrong on a night when it mattered. ## What it is built on - **The operator stays in charge.** Nothing advances on its own. There is no timecode chasing the performance and no automation to fight — the cue moves when a person decides it moves, and undo re-fires the previous line rather than merely stepping a counter back. - **Position, not direction.** The projection is told which cue to show, not to go forward one. A missed keypress or a correction cannot leave the house screen a line behind the stream, because every send is an absolute position. - **One destination failing is not a show stopping.** The stream, the projection and the phones are driven as independent paths. A livestream that stops answering, or a projection machine that drops off the network, does not hold up the others or block the next cue. - **Your script stays a file you own.** A spreadsheet, a text file, an SRT or a slide deck goes in; subtitle files and a performance log come out. Nothing about your production ends up locked inside a format only this software can read. ## A note on where this is going Maestro Console is in active use and still moving. If something in your workflow does not fit — a projection system it should speak to, a language pipeline it should respect, a failure mode it should survive — that is worth a conversation rather than a workaround. Most of what it does now came from exactly that kind of message. — Roger