Version 0.14. Every picture is the app itself, running a sample Sunday service, except the three drawings of a Stream Deck, which say so. Select a picture to see it full size.
Blue is Preview: what comes next. Only the operator sees it.Red is Live: what people can see right now.
New in 0.14: pull Sunday's service from Herald Workspace
The team prepares the service together online during the week, in Herald Workspace. Herald now pulls what they publish: the order, the songs, the Scripture, the sermon slides and the files, copied onto the media computer so that Sunday still needs no internet. The workspace in these pictures is a stand-in on the same computer, with a made-up service. The real workspace is built but not open yet, and Herald has not yet pulled from it over the internet.
Where it is.Click the service plan's name, top left. Above the plans kept on this computer is Pull from Workspace.Connecting, once.An owner makes a code in the workspace (People → Media computers). Typed here, it connects this computer. The code works once, for ten minutes. The key it earns can only fetch what has been published, and stays on this computer: it is never in the library or a backup. (The last line appears only on a computer that cannot encrypt saved keys, as the one these pictures were taken on cannot.)What is published, and a pull.Each service shows its day, its version and who published it, and a warning if the team has changed it since. Pull brings it in as a new service plan: nothing already in the library is replaced. A part the team published unfinished is named here.The pulled plan.An ordinary Herald service plan, named after its version. The song is in the song library with the arrangement the team chose; the Scripture is read from Herald's own Bible; the sermon slides have their private notes. The unfinished part is a blank screen marked not finished, with the reason in its notes. From here it is checked and run like any other plan.On Air, nothing is swapped.If someone pulls while Herald is On Air, the pulled plan goes into the library and the plan on the screens stays open. Open the new one from Service plans when the time comes.
New in 0.13: a Record button, and a Stream Deck
Two things the desk asked for. The HyperDeck can now record, started by a button the operator presses. And the service can be run from an Elgato Stream Deck: Next, Previous, Go live, Black, the sections of the song on the screen, On Air, and the HyperDeck. The HyperDeck in these pictures is a stand-in on the same computer, and the three pictures of a Stream Deck are drawings. Herald has not yet met a real HyperDeck, and the plugin has not yet been tried in Elgato's Stream Deck software or on a real Stream Deck.
Recording onto the deck.Once a HyperDeck is connected, the right-hand column has a HyperDeck panel with Record. While it records the panel is red, with the running time. Stop recording takes two presses. Nothing else Herald does stops a recording: not the next cue, not a HyperDeck clip cue going live (the clip is not played, and Herald says why), and not the Stop that ends playback.Stream Deck, in Displays.Displays → Stream Deck. Show the plugin file opens the folder with the plugin; double-click it once Elgato's free Stream Deck software is installed, then drag keys from CTW Herald onto the deck. The link answers this computer only, never the network, and can be switched off here.The keys, with Herald open (a drawing).The colours mean what they mean in Herald: blue is Preview, red is Live, gold is Next. The numbered keys are the sections of the song on the screen, and the live one is red. A key with nothing to do is dim. Going back to Rehearsal, and stopping a recording, each need the key held.With Herald closed (a drawing).When the Stream Deck is plugged in and Herald is not open, the keys together show the church's mark. The mark is the church's own picture, laid across the keys; it is not redrawn. Open Herald and the keys become controls again within a couple of seconds.On a Stream Deck XL (a drawing).The mark is cut for each layout of keys: 6, 8, 15 and 32 keys, and the wider layouts of the newer decks. Each key shows the piece for where it sits, so the mark lines up. Put a Herald key on every key of the page to see all of it; the Logo tile key is there to fill the gaps.
New in 0.12: transitions, several pictures at once, a Teams caller, a HyperDeck
Four things a vision mixer does, now in Herald: one picture can fade, dip, wipe or push into the next; up to four live pictures can share the screen, each in its own box; a laptop and someone on a Teams call are their own kinds of cue; and a Blackmagic HyperDeck can be told which clip to play when its cue goes live. Every camera, NDI source, Teams caller and the HyperDeck in these pictures is a stand-in made for the pictures. Herald has not yet met a real Teams call or a real HyperDeck.
Transitions.Settings → Audience. Cut is what Herald has always done; Fade, Dip to black, Wipe and Push are new. Show me plays the choice on two made-up slides, caught here half-way through a fade. Any item can also be given a transition of its own, in Plan.A super source.Add cue → Super source. Choose a layout, then what each box shows: a camera, a capture device, an NDI source, a window or a screen. Each box can carry a name. One box at most is heard.Two pictures at once, as the room sees it.A camera beside someone on a call, each with a name. Both pictures here are stand-ins: a made-up camera picture, and a flat colour where a caller would be.Someone on a Teams call.Add cue → Teams caller. Teams can send each person on a call to the network as an NDI source; Herald lists them by name. The steps to switch that on in Teams are in the same window. The names here are made up, and the call is a stand-in.A HyperDeck.Inputs → HyperDeck. Type the deck's address and Herald lists its clips; Add to the service makes one a cue. The deck's picture comes in separately, through a capture device. The deck here is a stand-in on the same computer.A clip on the deck, live.When the cue goes live On Air, Herald tells the deck to play that clip from its start; moving on stops the deck. Under the Live monitor: what the deck is doing, Play again and Stop. In Rehearsal the deck is left alone.
New in 0.11: Giving, looks for the livestream, and Inputs
A Giving page with the QR code, the account name and the account number; the account kept on screen while the offering song is sung; a different look on the livestream for each part of the service; and one place to see every camera and sound input. In these pictures the account number and the giving address are made up, the camera is a stand-in that says so, and the sound inputs are test devices.
Giving time: the whole page.What the room sees: the account name and the account number, each on a line of its own, and the QR code large at the right. The account number is never broken across two lines.Then the offering song.The lyrics as usual, with the account name and number kept in a strip along the bottom. Set on the song in Plan (Giving details); it goes when the service moves on.Giving, on the livestream.Giving has its own look: a panel at the side instead of the bar that lyrics use, with the same account and QR code. The rest of the picture is transparent, so OBS lays it over the camera.The offering song, on the livestream.The lyrics along the bottom as usual, and the account in a strip along the top, clear of them.A Giving item.Add cue → Giving, then three boxes: account name, account number, and the web address the QR code opens. The small code beside them shows the address was understood.A look for each part of the service.Lyrics, Scripture, sermon points, announcements, giving and speaker names each use the usual look unless you choose another. Show me previews one without touching the real stream. Copy a look to change its shape, place, colour and size, and to give it an OBS scene of its own.Inputs.The Inputs button in the top bar. Each camera shows its live picture, so you can tell which is which; Add to the service makes it a cue. Each sound input has a meter; Bring this one in chooses the one Herald passes on to the livestream or the room.
New in 0.10: Teams messages
The media account's Teams chats now show inside Herald, so the operator can see that slides have been sent without leaving the control window, and bring the attached file straight into the library. Herald only reads: it cannot send, change or delete anything in Teams. It needs CTW Herald registered once in the church's Microsoft 365 by whoever administers it. In these pictures Microsoft 365 is a stand-in made for the pictures, and the people and messages are made up.
Slides have arrived.A notice names who sent slides and the file, and the bottom of the window says Teams: 1 new message. A message with no slides only changes that count during a service, so nothing pops up over the operator.The chat, in Herald.Who wrote, in which chat, what they said and what they attached, for the last two weeks. A presentation has Bring in; anything else is named with a note to open it in Teams. The amber line about a key store appears only on a computer without one, such as the one these pictures were made on.Brought in.One press fetches the file from Teams and makes every page a slide in the library. Add to service puts it in the service order. Nothing is downloaded and uploaded by hand.Setting it up, once.Your Microsoft 365 administrator registers CTW Herald and gives you two IDs. The steps for them open from this button as a PDF. Then you sign in as the media account on Microsoft's own page; Herald never sees the password.
New in 0.9: Dante sound in, and slides sent on Teams
Sound from the mixing desk can now be brought into Herald and passed to the livestream: Dante arrives through Audinate's own software or adapter, which the computer sees as an ordinary sound input. And Herald watches the presentations folder, so slides posted in a Teams channel are announced and brought in with one press.
Sound input.Choose the device, where it goes and how loud. It runs only On Air, and says so along the bottom of the window. In this picture the device is a stand-in made for the picture, not a real Dante device.Slides inbox.A file lands in the folder that OneDrive keeps in step with the Teams channel; Herald says so, and one press makes every page a slide. Switched on, it brings them in by itself, but only in Rehearsal.The maker's credit.The credit now carries TK Software's own logo, taken from its brand sheet, in its label typeface, with no effects added.
New in 0.8: word animation, and web streams
The words can now arrive with a little movement, chosen separately for songs, Scripture and sermon slides, and off until you choose it. And a stream from the internet can be played like a video, with its sound to the room and the livestream.
Word animation.Dissolve, Rise, Zoom, Focus or Line by line, at three speeds. Choosing one plays it on a made-up slide; the real screen is not touched. The stage display and Preview never animate.A web stream.Paste the stream's address and check it: Herald goes and looks, and says in plain words whether it will play. In these pictures the stream is a test pattern from a stand-in server on the same computer.Live.Play and pause under the Live monitor, sound to Room and Stream as for a video. The stage is shown the server's name, never the address. If the internet drops, the room sees black and the operator is told why.
New in 0.7: the remote, on an iPad or phone
A page Herald serves to an iPad or phone on the church Wi-Fi: nothing to install. A device can only ask to connect; the operator at the desk decides what it may do, and can change that or remove it at any moment. Going On Air, the livestream, displays, sound and editing stay at the desk.
At the desk.The iPad scans the code and asks. Until the operator answers, it sees and does nothing. View only watches; Speaker moves through one item's slides; Operator runs the service.Operator.The service plan, every slide, Preview and Live, Scripture, stage messages, Black and Clear text. The desk and the iPad are both in control; the latest press wins.Speaker.The pastor's own slides, notes, the clock and any message from the desk. Next stops at their last slide: it cannot start the next song or video.
New in 0.6: a song bank, and presentations
Songs and this week's slides live in a shared place, such as a SharePoint folder, and Herald pulls them onto the media computer. What is pulled is copied into the computer's own library, so Sunday does not depend on the shared place or the internet.
The song bank.Herald looks first and changes nothing: new songs are ticked, a song that differs from the one on this computer is left for you to decide, and a file it cannot read says why.Presentations.A PDF or PowerPoint from a file, a folder or a link. Every slide becomes a picture kept on the computer, and Pull again fetches a newer copy.In the service.One tile per slide. It runs like everything else: Preview, then Live, Space to move on.On the projector.The slide, full frame.
New in 0.5: the look, and NDI
The control window is now a dark console drawn with fine glowing lines. The colours still mean what they meant: blue is Preview, red is Live, gold is the next thing to press. The screens the congregation, the band and the stream see have not changed.
The opening screen.Shown for a moment while the library opens. The same credit sits in the strip along the bottom of the main window.Herald as an NDI source.Two switches under Displays: the audience screen, and the lower thirds on a see-through background, for vMix, OBS or a mixer to pick up over the network.
Running a service
The service order is on the left, the slides of the selected item in the middle, and Preview and Live on the right. Space moves on. The buttons above the slides jump straight to a chorus or a verse.
The main screen, On Air.Verse 1 is live (red). The chorus is next (blue). Small monitors show what the stage and the livestream are getting.
The preacher calls out a Scripture.Press F2 and type it the short way. The King James text is on the computer, so no internet is needed.Then back to where you were.While the passage is up, Herald shows exactly which slide the service will resume at. Press R.
One slide, three screens
Each output has its own layout. Private notes and messages only ever go to the stage.
Audience (projector).Full-screen words in the CTW theme.Stage.Clock, countdown, the words now and the words next, and the band's notes.Livestream.A see-through lower third that OBS lays over the camera. The squares stand for the camera picture.Scripture on the projector.With the reference and translation underneath.
The stage display: on a cable, or on a tablet over Wi-Fi
Choose a starter layout or arrange your own by dragging the boxes. Any tablet, phone or TV on the church network can show it in a web browser after entering a code once.
Arranging a layout.Drag a box to move it, a corner to resize it. Tick boxes on and off, and set each one's text size and colour.Displays, and Stage on Wi-Fi.Send Stage to a monitor on a cable, and switch on the Wi-Fi stage display: a QR code, an address and a six-digit code.On a tablet.The same stage display in the tablet's browser, here with a message from the operator along the bottom.The code, once.A device that types the address is asked for the stage code. Scanning the QR code skips this.On a phone, with its own layout.Each device can pick a different layout. This one chose lyrics only.
Before the service
Pre-service check.Displays, media files, OBS, sound devices and stage tablets, with anything that needs fixing marked.Plan mode.Build the service and edit slides here. In Run mode the editing tools are out of the way.The quick guide.Shown the first time the app opens, and under Help after that.
Livestream and sound
OBS still makes the stream. Herald chooses where it goes and starts it, and sends a video's sound to the room and to the stream separately.
Where the broadcast goes.YouTube, Facebook, or both through Restream. Starting takes two clicks so it cannot happen by accident.Sound to two places.One device for the room and one for the livestream, each with its own volume, mute and test tone.A video, live.Under the Live monitor: play controls, a level meter, and Room and Stream buttons to mute either one.
A camera, or a guest's phone or laptop, on the projector
Live video comes in three ways: an NDI source on the network, a USB capture device (HDMI in), or another program's window, such as a wireless receiver. Herald puts it on the projector like any other slide: Preview first, then live.
Choose what to share.NDI sources on the network come first, then capture devices, other programs' windows, and whole screens.Live.The operator sees the guest's screen in the Live monitor.On the projector.The guest's slide fills the audience screen.
How these were taken. On a test computer, with stand-ins for everything outside the app: three simulated monitors, a stand-in for OBS, a desktop browser standing in for the tablet and the phone, a small separate program standing in for a wireless receiver (its "Six weeks in Vanuatu" slide is made up for the picture), and a stand-in for NDI's software, which is where the two "STUDIO" camera names in the share list come from. No NDI software or NDI device was involved. The song bank and the slides folder are ordinary folders made for the pictures, with made-up songs and a made-up sermon deck: no SharePoint was involved. The Teams messages come from a stand-in for Microsoft 365 on the same computer, with made-up people and messages: no Microsoft account, Teams chat or OneDrive file was involved. The camera in the Inputs picture is a test camera built into the app's browser engine, shown a still picture that says so, and the sound inputs are that engine's test inputs: no real camera or microphone was involved.
None of this has been run on the church's own computers, screens, tablets or sound system yet. The rehearsal checks that come with the app cover that.
NDI® is a registered trademark of Vizrt NDI AB. CTW Herald was built by TK Software for Church Triumphant Wellington.