Skip to content

usage-guide.md

Latest commit

 

History

History
320 lines (239 loc) · 32.6 KB

usage-guide.md

File metadata and controls

320 lines (239 loc) · 32.6 KB
Raw

open-caption usage guide

open-caption shows live captions on audience phones, tablets and screens during a play or musical. A volunteer operator follows the show and presses the spacebar for each line; every device on the venue's WiFi shows the line a moment later. Nothing is installed on the audience's devices, and they never have to touch anything.

This guide covers what to buy and how to arrange it (Deployment), how to set up a show, how to run it, and a day-of checklist. The in-app Help button covers the same ground in smaller pieces, and venue-network-guide.md is written for whoever manages the building's WiFi.

Contents: The pieces · Deployment recommendations · Installing and starting · Setting up a show · Running the show · Day-of checklist · Troubleshooting · Maintenance · Operator quick card

The pieces

Piece What it is
The server The open-caption program, running on one computer (macOS, Windows or Linux). It holds the show file and sends lines to everyone.
Setup page (/admin) Where volunteers prepare a show: show file, images, look, rehearsal. Admin password.
Operator page (/operator) Where the operator follows the show and sends lines. Operator password. Setup's Open the Run page button and Run menu link open it.
Follow page (/follow) A second device, such as a stage manager's tablet, that only watches the show: it sees the lines, notes and position and can send nothing. Optional viewer password; the operator and admin passwords open it too. The Share step of Setup lists it.
Audience page (/) What audiences open on their devices. No password. A browser on a projector or large monitor can show the same page for the whole room.

Everything runs on one computer. The audience, the operator and the setup volunteers all use ordinary web browsers.

Deployment recommendations

The short version

  1. Use a dedicated WiFi access point for captions unless the venue's guest network is known to work (see below). It removes the biggest risk: a network you do not control.
  2. Put the server on a wired connection to that access point, with a reserved address.
  3. Use an access point built for crowds (rated for 100+ devices) placed in the audience area.
  4. Keep the server computer plugged in, awake, and otherwise idle during the show.
  5. Print the QR code and put it in the program and in the lobby.
  6. Rehearse with a few real phones in the real room before opening night.

Network options

Option When to use it Notes
A. Dedicated access point (recommended) Any venue, especially if you cannot change the building's network You bring a router or access point. Audiences join its WiFi (for example "Theater Captions"). No internet connection is needed. You control capacity, reservations and firewalls.
B. The venue's guest WiFi The venue's network staff will confirm guest devices can reach your computer Cheapest. Ask for a reserved address for your computer and for guest-to-server traffic to be allowed. See venue-network-guide.md.
C. Your laptop's own hotspot Rehearsals and tiny audiences only Laptop hotspots usually handle only a handful of devices. Not for a full house.

Option A in detail (dedicated access point)

                 ┌───────────────────────┐
                 │  Access point/router  │  WiFi "Theater Captions"
                 │  (in the audience     │ ─ ─ ─ ─ ─ ─ ─ ─  phones / tablets
                 │   area, 5 GHz on)     │                  projector browser
                 └───────────┬───────────┘
                    Ethernet │
                 ┌───────────┴───────────┐
                 │ Captioning computer   │   ← operator uses this screen,
                 │  (open-caption)       │     or a second device on the same WiFi
                 └───────────────────────┘
  • Equipment: a business-grade or prosumer access point or router designed for many simultaneous devices (look for 100+ clients in its specifications and for 5 GHz support), with an Ethernet port. Cheap home routers often struggle past 30–50 devices. For a ~150-seat house, plan for one capable access point, and a second one for a deep or wide room.
  • Settings:
    • Create one SSID with a short name and a simple, printable WPA2 passphrase, or no passphrase if the venue allows an open network. Print it on the QR sign.
    • Turn 5 GHz on, and prefer it. Use 20 or 40 MHz channel widths in a crowded building.
    • Leave client isolation on if it is offered. Audience devices only talk to the server, never to each other.
    • Give the captioning computer a DHCP reservation (or a fixed address) so the address never changes, and print the address on the sign.
    • You do not need an internet connection, and the program never uses one.
  • Placement: put the access point in the audience area, high and clear of walls, not in a back room or the lobby. Do not put it behind the stage or lighting rack. A laptop on a distant table is fine: it is wired.
  • Power: use a surge protector. A small UPS on the access point and server removes the risk of a tripped plug.

Option B in detail (the venue's guest WiFi)

The program does not care which network it is on, as long as audience devices can reach it. Before relying on it:

  • Ask for guest-to-server access: your computer must be reachable from the guest SSID, on TCP port 80 (and 443 if you enable HTTPS). "Client isolation" between guests is fine; blocking guests from reaching your computer is not.
  • Ask for a reserved address for your computer's network adapter.
  • Plug the computer into the network by Ethernet if at all possible.
  • Test with a phone on the guest WiFi well before the show (the Share step shows the address).
  • Have Option A in a bag as a backup if the show matters.

The captioning computer

  • Any ordinary laptop or mini-PC will do. The program uses very little memory (tens of megabytes) and almost no processor. Use a computer you can keep plugged in.
  • Operating system: macOS, Windows or Linux. Use the same computer for all shows if you can, so the passwords, shows and address stay the same.
  • Make it boring: set the computer to never sleep while plugged in, disable automatic restarts for updates around show dates, close other programs, and keep the lid open or set the lid not to sleep.
  • Firewall: allow the program on private networks (Windows asks the first time; on macOS allow incoming connections for it).
  • Address: wired and reserved (see above). If the address changes, printed QR codes stop working.
  • Time: the clock does not matter.

Who sits where

  • The operator needs a clear view of the stage and a reliable device. The simplest arrangement is the captioning computer itself at the tech desk. The operator page is meant for a computer with a keyboard (Space sends the next line). Use the captioning computer, or another laptop on the same network (http://<computer's address>/operator) so the operator can sit where they can see the stage. A phone or tablet will show the page but is not recommended: a touch screen is easy to mis-tap during a show. A Bluetooth clicker or keyboard is a good alternative.
  • Only one operator controls the show at a time. Anyone else who opens the operator page can watch, and can use Take over if the operator hands over.
  • The setup volunteers use the Setup page from any computer on the network before the show, or from the captioning computer.
  • A shared screen for the whole room: open the audience address on a computer connected to a projector or a large monitor, add ?display=projector to the address for large text and no on-screen clutter, and make the browser full screen (F11, or run Chrome with --kiosk).

Running the server

For most theaters, the simplest way is best: start the program by hand before each show, leave its window open, and press Ctrl+C (or close it) afterwards. The show position is saved continuously, so restarting in the middle of a show is safe (see Troubleshooting).

If the computer should start the server by itself after a reboot, the deploy/ folder has ready-made files for Linux (systemd), macOS (launchd) and Windows (Task Scheduler). Each begins with its own install steps.

Getting people to the page

In order of reliability:

  1. The QR code and sign (Setup → Share → Print a QR sign for the lobby). Put it on the wall, in the program and on the seat-back card. This is what to rely on.
  2. A short address. On port 80 there is no :port to type. The program also announces itself as open-caption.local (change it in Setup → Settings → Network → Use a name): where the guest network allows it, http://open-caption.local/ works on most phones with nothing to set up. Some guest networks block that kind of announcement, so do not print only the name; the QR sign uses the numeric address. A name on the router's own DNS (such as captions.theater) works everywhere but needs the venue to add it.
  3. The access point's splash page (a "guest portal" or "captive portal" that redirects to your address after joining). This is configured on the router or access point, not in this program. See venue-network-guide.md.
  4. DHCP option 114 and /captive-api (advanced, experimental). Option 114 is a DHCP setting that points devices at a "captive portal API". The program answers that API at /captive-api (for example https://<address>/captive-api) with "this network is not captive" and the page's address. Two cautions: it does not make phones open the captions page by themselves, and the standard (RFC 8910/8908) requires HTTPS with a certificate the devices trust, so a plain http:// setting or the program's self-signed certificate is ignored. Only set it up if the venue already uses option 114 and can provide a trusted certificate. It has not been tested on real devices.

Ports and addresses

  • By default the server listens on port 80, so the audience address needs no port number, for example http://192.168.1.10/. If something else is using port 80, or the operating system does not allow it, the server tells you and uses port 8080 instead; the audience address then ends in :8080. On Linux, port 80 needs permission (sudo setcap 'cap_net_bind_service=+ep' ./open-caption) unless you use the systemd file, which grants it.
  • You can choose ports yourself with --http-addr :8081, or in config.yaml.
  • HTTPS is optional. Plain http:// works on every device without warnings and is the recommended audience address. A self-signed HTTPS address makes every device show a security warning. Turn HTTPS on only if you can install a certificate your devices trust. If the venue owns a domain name, the program can get and renew a trusted certificate by itself; see the trusted HTTPS certificate guide (docs/https-certificate-guide.md).

Security

  • The audience page can only read. It cannot change the show or reach the setup and operator pages.
  • Setup and operator each require their own password (kept in config.yaml only as digests, a one-way hash, so the passwords cannot be read back from it; the file is also created readable only by you). An optional viewer password (in Settings) lets a second device, such as a stage manager's tablet, open the Follow page (/follow; the operator and admin passwords open it too) and watch the show without being able to send anything. Give the operator password to the operator, not the admin password. Passwords can be changed from Settings in Setup.
  • On the computer that runs the program, Setup and the operator page open without a password when the address starts with localhost, 127.0.0.1 or [::1] (the person at that computer is trusted as the admin). Other computers, and any request that has been relayed by a proxy, still sign in with a password. Set access.local_auto_login: false in config.yaml if other people can log in to this computer.
  • Anyone who can reach the server can open the Setup and operator sign-in pages, and over plain http:// the passwords travel across the WiFi unencrypted. On a shared guest WiFi that means a curious audience member could capture a password and take control of the captions. Reduce the risk, in this order:
    1. Limit which computers may open them. In config.yaml: 
      access:
  admin_allow: [localhost]            # Setup only on the captioning computer itself
  operator_allow: [192.168.1.50]      # the operator's computer (or a network such as 192.168.1.0/24)
      Entries can be localhost, private (home/office address ranges), a single address, or a network like 192.168.1.0/24. The default for admin_allow is [localhost] (Setup opens only on the captioning computer); an empty list means any computer, and the program warns about it. operator_allow is empty by default (any computer). An address in admin_allow may also use the operator page. Instead of editing the file you can change all of these in Setup under Settings → Access; the change applies at once, and Setup refuses a list that would shut out the computer you are using. After editing the file by hand, restart the program; a bad entry stops the program with a message rather than allowing everyone.
    2. Put the operator on a wired or separate network that audience devices cannot join, or give the captions network a WPA2 password.
    3. Use HTTPS (https.enabled in config.yaml) if you can give devices a certificate they trust; a self-signed one makes every device show a warning, and an unencrypted audience address is simpler.
  • A website, or another service on the same computer, cannot make a browser change the show behind your back: requests that did not come from the program's own pages are refused.
  • The program is meant for a private network. Do not expose it to the internet.

Installing and starting

  1. Get the program. Download the release for your computer from the repository's Releases page and unpack it (or build it yourself: see the build guides in the source repository's docs folder). Put it in a folder you will keep, for example Documents/open-caption.
  2. First start. Run it: double-click it on Windows, or in a terminal run ./open-caption (macOS/Linux). The program is not code-signed, so the first run may need a click: on macOS right-click → Open (or Open Anyway in System Settings → Privacy & Security), on Windows More info → Run anyway in the SmartScreen window.
  3. Note the passwords. The first time, the program prints the admin and operator passwords and where config.yaml is. They stay in that file.
  4. The setup page opens in your browser. If it does not, open http://localhost/admin (or http://localhost:8080/admin if the console says it used port 8080).
  5. Choose where data lives (optional). By default, shows and settings are in your user configuration folder (macOS ~/Library/Application Support/open-caption, Linux ~/.config/open-caption, Windows %AppData%\open-caption). To keep everything in a folder you choose, start with --data <folder>. Always use the same folder.

Useful options: --data <folder>, --http-addr :8080, --https-addr :443, --no-browser, --log-file <file>, --log-level debug|info|warn|error, --version. Every option: open-caption --help, the manual page docs/open-caption.1 (English only), or docs/configuration-reference.md.

If config.yaml has a mistake (a misspelled setting, a number out of range, a bad address), the program lists every problem with its line or setting name and stops; fix the file and start again. (A file marked config_version newer than the program understands is the exception: unknown settings are ignored with a warning, so you can go back to an older program.)

Setting up a show

Open the setup page and follow the six steps along the top (a seventh, Report, is for after the show). The Help button explains each one.

  1. Shows. Create a show (or the sample show, to try things out).
  2. Show file. Paste the show file or drop in a .txt or .md file. Each line becomes one caption. Fix anything listed in the Problems tab beside the editor; click one to jump to its line. Save.
  3. Images. Upload the pictures the show file uses (PNG, JPG, GIF or WebP, ideally under 1 MB each).
  4. Look. Choose colors, font and text size. The defaults (white on black, large) are best for most people. Two readability fonts are built in: a dyslexia-friendly one (OpenDyslexic) and a high-legibility one (Atkinson Hyperlegible, designed for low vision). Individual audience members can also pick either for their own device from the small Aa control.
  5. Test. Run a private rehearsal: you press Space as the operator would, and see the audience screen next to it. Nothing reaches the audience.
  6. Share. Check the readiness list, print the QR sign, and press Open the Run page.

Working on a show is not the same as making it the active show. Work on this show only chooses which show Setup is editing (its name is in the header). The show the audience gets, the active one (marked ACTIVE on the Shows step, and shown in the header by the Active pill, amber in standby and red on air), changes only when you press Open the Run page on that show's Share step. A show that is on air is replaced only after Setup asks.

Opening the operator page loads the show in standby: the audience sees the venue's standby screen (a logo and a message, set once under Settings → Audience screen) and nothing of the show, so you can prepare, rehearse and check the operator page quietly. When you are ready, press Space (the button says START) on the operator page to put the show on air. Go to standby… takes it off again without losing its place.

Writing the show file

Whoever prepares the show file does not need to read the rest of this guide: Preparing a show file covers the job from script to finished file, including editing it in your own program, and Getting started walks through the six steps of Setup.

A show file is plain text. The short version:

<!-- Comments like this are never shown. -->
[loop: 10s]
[image: welcome.png | 15s]
Welcome! Please silence your phones.
[/loop]

[section: Act 1, Scene 1]
[note: lights come up slowly]
[clear]
(A garden gate creaks open.)
MARGARET: You're late, Edwin.
EDWIN: The *train* was late.

[song: The Tea Song]
MARGARET: Oh, the kettle sings its song,
EDWIN: Whistling all day long
[/song]
~ Tea for two, and two for tea ~

[fullscreen: **INTERMISSION**]
  • One line = one caption = one press of Space. You decide where to break long speeches.
  • Speaker names in capitals followed by a colon are shown above the line.
  • Stage directions in (parentheses) are shown in italics.
  • Lyrics between ♪ notes, in italics: start a line with ~, or wrap the song in [song]…[/song]. For two singers at the same time (a duet or counterpoint), put their lines between [together] and [/together], or join them with || on one line; both show at once on one press of Space. The editor's ♪, ♫ and 🎵 Song buttons insert these. See the Musicals help topic.
  • Loops (pre-show and intermission) repeat pictures and text until the operator moves on. A loop at the very start of the show file starts when the operator puts the show on air (START).
  • Notes [note: …] and bookmarks [section: …] are for the operator only. [pace: 8s] tells the operator how long the next line usually stays up, and a line starting with # is a heading that works like a bookmark.
  • The Writing a show file help topic lists everything, with examples, and the Cheat sheet tab beside the editor summarizes it.

Show settings (title, look and more)

Everything about a show except its pictures is stored in its show file, including its title and how the captions look, in a [settings] block near the top:

[settings]
title: The Garden Party
font: dyslexic
text size: 120%
speaker names: color
idle message: Captions will begin shortly
[/settings]

The Look step in Setup writes this block for you, and you can edit it by hand. Anything a show file leaves out uses a default: the program has built-in values, config.yaml (its defaults section) can change them for every show on this computer, and each show file overrides both. Ports, passwords, HTTPS and the access lists are not show settings and stay in config.yaml. Because the show file carries its look, copying or exporting the show carries the look too. See the Writing a show file help topic for every setting.

Checking the character names

Click File ▾ → Characters… above the editor to see every name used as a speaker, the most used first, with how many lines each speaks on. It is the quick way to find a misspelled name: ALCE with one line beside ALICE with forty is marked Did you mean ALICE?. Click a name to go to its first line. A group such as ALICE & BOB: counts for each of its names.

Going back

Each save keeps the version it replaced (the last 50). File ▾ → Earlier versions… above the editor lists them; Load puts one in the editor, and Save makes it current. Compare shows line by line what loading one would change, and a version you give a name to (or Keep for what is saved now) is never forgotten. Export before the show anyway: the earlier versions live in the data folder, not in the export.

Two people editing

If someone else saves a show file while you have it open, the program warns you when you save instead of overwriting their work, and lets you take their version or keep yours.

More than one language

A show can offer captions in several languages. In Setup → Show file, open the language menu at the left of the toolbar and choose ＋ Add a language, keep "Start from a copy of the main show file" ticked, and translate the words. Each language is its own show file with the same lines, commands and blank screens in the same order, so one press of Space shows the same moment in every language. The operator follows the main language only. Audience devices get the language their phone is set to (or the main one) and can switch from the small 🌐 menu, or be given a link ending in ?lang=es. A translation that stops matching the main show file is reported and held back until it is fixed. The sample show includes a Spanish translation to look at. See the Languages help topic.

Changing things during rehearsals and shows

You can edit and re-save a show file while a show is live (for example to fix a typo). The program asks you to type the show's name to be sure, keeps the operator's place by line number, and warns if the number of lines changed.

Running the show

Before the audience arrives

  1. Start the server and open the Operator page; sign in. It should say You are in control.
  2. In Setup → Share press Open the Run page. The show is loaded in standby: the audience sees the venue's standby screen. When you are ready, press Space (START) on the operator page to put the show on air. A pre-show loop, if the show file has one, begins on every screen then.
  3. Open the audience address on your own phone and, if you have one, on the projector. Check the viewer count on the operator page goes up.
  4. Put the QR sign where people can see it.

During the show

  • Space sends the next line (also Right arrow, Page Down, Enter, and most clickers).
  • Backspace undoes the last thing you sent.
  • B blanks the audience screens (hides everything; the same captions return when you press B again). C clears them (erases the captions, so the next line starts on an empty screen). Backspace undoes either.
  • Shift+Q stops an intermission or pre-show loop (blank screen). Space continues.
  • Announcement… puts a one-off notice on every screen ("The show will resume shortly"). Back removes it.
  • Click a line, then confirm, to jump anywhere. / searches the show file.
  • The line with the yellow arrow is next. The green dot marks what is on screen now.

When the show ends

Press Ctrl+C in the program's window (or stop the service). The position is saved. To run the show again from the beginning, use Restart show… on the operator page, or Restart show… in Setup → Share. Either returns the show to standby. How many people used it? When the show reaches its end the banner on the operator page says End of the show. with an Audience report link (Setup's Report step shows the latest one). It counts the different devices that used the audience page while the show was on air, however long each stayed (a phone that dropped off the WiFi and came back counts once), with a graph of the devices over time (showing when the pre-show and intermission loops ran), the busiest moment, the languages and a row for each device; it can be printed or downloaded as a CSV file. Devices are told apart by address and browser type, so it is an estimate. The reports are kept in the reports folder of the data folder.

Day-of checklist

A few days before

  • Rehearse with the real show file and a few real phones on the real network in the real room.
  • Export the show (Setup → Shows → More ▾ → Export) and keep the .zip somewhere safe, such as a USB stick.
  • Confirm the captioning computer's address is reserved and the QR sign shows it.

At the venue, an hour before

  • Power: computer and access point plugged in; computer set to never sleep.
  • Access point on, in place, with the right name; the computer wired to it.
  • Start the program; note the address printed (and in Share).
  • A phone on the audience WiFi can open the address and shows "Captions will begin shortly".
  • Setup → Test: do a quick rehearsal; operator keys work.
  • Projector browser (if used) open on …/?display=projector, full screen.
  • Press START on the operator page. The pre-show loop (if any) is on every screen.
  • Operator sitting where they can see the stage; clicker or keyboard tested.
  • QR sign placed; a volunteer knows the WiFi name and address for people who ask.

After the show

  • Ctrl+C in the program window.
  • Export the show again if you changed anything.

Troubleshooting

Problem What to try
Nobody can open the address Is the phone on the right WiFi (not mobile data)? Does the address include :8080 if the program used that port? Is guest-to-server traffic allowed? Is the computer's firewall allowing the program on private networks? See venue-network-guide.md.
Some devices connect and others do not The access point may be at its device limit. Add a second access point, or move the first into the room.
Captions are late or stall on a few phones Weak signal or a busy channel. Those phones reconnect on their own. Improve access-point placement; use 5 GHz.
Someone missed a line They can scroll the captions up to re-read it; new lines wait behind a Back to live button until they tap it.
A page says "This browser is too old" The device's browser is below what the page needs: about iOS 12 for the audience page, iOS 14.1 / Chrome 87 for Setup and the operator page. Update the device, or use another one.
Screens go dark on phones Phones lock their screens. The page keeps the screen on with the browser's wake lock where it can and, where it cannot (plain HTTP), with a tiny invisible looping video. Anyone who would rather let their phone sleep (a low battery, say) can turn Screen stays on off in the "Aa" panel. Some phones in low-power mode refuse both: the page then shows a tip to switch off Auto-Lock for the evening.
The wrong line was sent Backspace undoes it.
The operator page says another operator is in control Use Take over, if you are the operator.
The computer froze or was restarted mid-show Start the program again. The operator page reconnects, stays signed in and takes control back by itself, the show is where you left it, and audience devices reconnect on their own. A loop restarts from its first item. Backspace can still undo the last few things sent before the restart.
I forgot a password Sign in with the other one and use Settings in Setup, or open config.yaml in the data folder in any text editor.
Something else Setup → Troubleshoot → Download a support bundle; it holds the settings (without passwords) and recent log lines.

Maintenance

  • Backups: Export in Setup → Shows (in a show's More ▾ menu) saves a show (show file, images, look) as a .zip. Import restores it, on this or another computer. You can also copy the whole data folder.
  • Moving to another computer: install the program, import the exported shows, set the new computer's address and, if you want to keep the old passwords, copy config.yaml.
  • Updating the program: stop it (Ctrl+C), replace the program file with the newer one, and start it again with the same --data folder. Do not update right before a show.
  • Reusing a show: Setup → Shows has Rename… and Duplicate…. Duplicating makes a copy of the show file, images and look to adapt for the next run, and leaves the original alone. Rename, Duplicate, Export, Archive and Delete are in the More ▾ menu on each show.
  • Cleaning up: delete shows you no longer need from Setup → Shows. Exported .zip files are your archive.
  • Audience reports: each run of a show leaves its audience report as a file in the reports folder inside the data folder (Setup → Settings → About shows where the data folder is). The newest 30 are kept and older ones are removed automatically. A report lists the devices' network addresses, so delete the reports you do not want to keep (Delete… in Setup's Report step, or the files themselves), any of them or the whole reports folder (it is made again when the next show goes on air); nothing else depends on them, and deleting them does not touch your shows.
  • Logs: Setup → Troubleshoot → the Warnings and errors tab shows what the program has logged lately, filtered by level (it opens on Problems only, warnings and errors); recent log lines are also in the support bundle; add --log-file to keep a file. Each line starts with its level (INFO, WARN, ERROR, or DEBUG). The default info records sign-ins, who took control of the operator page, shows activated and similar events; warn keeps only problems; debug also records every request, which helps when something odd is happening. Set it with log: {level: debug} in config.yaml, --log-level debug, or while the program is running from Setup → Settings → Log detail. If the program was started with --log-level, that flag wins at every start: Setup says so, a change made there lasts only until the next restart, and the start-up log warns when the flag and the file disagree. A log file kept with --log-file starts a new file at 5 MB and keeps three older ones (open-caption.log.1 to .3), so it never fills the disk.
  • Archiving: in Setup → Shows, Archive puts a finished show away (it is kept, listed under "Archived shows", and cannot go on air) and Restore brings it back. Delete removes a show for good.

Operator quick card

Print this and keep it by the operator.

Key Does
Space Send the next line
Backspace Undo the last thing sent
S Skip the next line without sending it (Backspace undoes it)
Shift+Q Stop a loop (blank screen)
B Blank: hide everything, captions come back on unblank
C Clear: erase the captions for a fresh start
/ Search the show file
? Help (keys are paused while it is open)
  • Yellow arrow = next line. Green dot = on screen now.
  • Wrong line? Backspace. Lost your place? Click the line you want, then confirm.
  • Need to say something to the audience? Announcement…
  • Show interrupted? B to blank the screens, Announcement… to explain.