From script to stage, in one project.
Sténtor brings together script preparation, translations, accessible versions, audio description, screens, audience smartphones and live show control. This page describes the available features and the recommended workflow.
Before entering the venue. Always test the project using the same computers, screens, devices and network that will be used during the performance.
Availability
Sténtor is available in beta for macOS and Windows. The two applications share the same workflow but use the native technologies of their respective platforms. A Tauri-based Linux version is in development and is not yet publicly available.
| Area | Availability |
|---|---|
| macOS | Native app built with Xcode, Swift and SwiftUI. Universal build for Apple silicon and Intel Macs, compatible with macOS Monterey 12.4 and later. |
| Windows | Native app built with C#, .NET 8, WinUI 3 and XAML. Compatible with Windows 10 version 1809 (build 17763) and later, including Windows 11; builds for x86, x64 and ARM64. |
| Linux | Tauri-based desktop version in development. It is not yet available as a public release. |
| Licence | Sténtor requires licence activation. Licences are issued free of charge; free access is guaranteed and is an integral part of the Sténtor project. |
Recommended workflow
From preparation to the stage and the audience.
- Create or open a .stn project
- Complete the production details and import the script
- Check cues, characters, languages and audio descriptions
- Configure screens, audience access, connectivity and surveys
- Test the system with the venue network and devices
- Use Live Control during the performance
1. Projects and archive
Projects is the starting point. Here you can create a project, open an existing file and find recent work. A Sténtor project contains all the materials and settings required for a production.
- Create new projects and open .stn archives exported from other workstations.
- Keep scripts, languages, characters, audio descriptions, screens, audience access and surveys together.
- Use demonstration projects for technical tests without confusing them with the real archive.
2. Production
Production contains the show's general information and makes the project easy to identify during rehearsals, performances and transfers between workstations. Enter at least a title and company, then review the options available for that production.
Show identity
Title, company and production details make projects and versions clearly distinguishable.
Shared configuration
Project choices are stored with the script and reused in the other sections.
3. Importing text
Import turns a script or subtitle file into editable cues. Supported workflows include Word, TXT, SRT, WebVTT, CSV and JSON; individual options may depend on the installed build.
Before importing
Choose the text language and use the preview, when available, to check how lines will be separated.
After importing
Check speakers, stage directions, line types, scenes and script order before starting translation work.
4. Text and cues
Text is used to correct and organise the script. You can select a cue, edit its content, assign its character and line type, split or merge it, and check the result in the preview.
| Element | Function |
|---|---|
| Cue list | Browse, search and select cues quickly. |
| Line type | Distinguishes dialogue, titles, stage directions, notes, audio descriptions and material that is not projected. |
| Cue style | Applies a local exception when a cue needs different formatting from the general style. |
| Preview | Shows how the text will appear at the output and flags possible readability problems. |
| Undo | Undoes recent changes to the text and script structure. |
5. Languages and translations
The interface language is independent of the project languages. In Languages, choose the versions needed for the show; in Text, keep the original, translations and accessible variants aligned to the same cue sequence.
- Configure production languages once and reuse them for text, screens and audience access.
- Accessible variants, identified by the + symbol, remain linked to their base language.
- Check every version on its actual output before the performance.
6. Audio description
Audio description is an independent layer of the project. You can prepare recorded descriptions or text for live delivery, link them to the correct point in the show and make them available to audience devices when the setup supports it.
Use in the venue. Check audio preloading, volume, headphones, network stability and playback confirmations before the audience arrives.
7. Timeline
The timeline provides a map of the performance. It helps you read cue order, the current position, sections, rehearsal timings and text density.
Orientation
The operator can see the current position and which blocks are coming next.
Timing and rehearsals
Recorded timings help preparation but do not replace manual live control.
8. Live Control
Live Control is the operating console for the performance. It clearly shows the current and next cue, keeps output status visible and brings together the controls needed during the live show.
| Control | Use |
|---|---|
| Previous / next | Manual control of the current cue, with the next cue always visible. |
| Pause | Pauses operational progression without changing prepared content. |
| Blackout | Immediately blacks out public displays; this control remains independent of Pause. |
| Audio description | Shows the status of the channel, descriptions and devices receiving audio. |
| End show | Explicitly ends the live session and opens the survey choice. |
9. Screens
Screens configures the outputs used in the venue. For each screen, check its content, language, style, size, contrast and preview, then verify the result on the actual display or projector.
Projection
Each output can be configured for surtitles, translation, easy-to-read language or other text content.
Visual check
Preview, status, blackout and styling help prevent errors before text is displayed.
10. Audience
Audience prepares what spectators see on their own devices. Configure the welcome screen, available content, page appearance and access by address or QR code.
- Choose whether to provide surtitles, translation, audio description or several modes together.
- Customise access instructions, logo, theme, text and the options available to spectators.
- Open the QR code with at least one real smartphone and check readability, language and synchronisation.
11. Ending the show and surveys
The survey does not appear simply because the last cue has been reached. When you select End show, Sténtor asks whether you want to display it to connected spectators. You can end without a survey or open the final screen inviting them to respond.
Immediate survey
Displayed on connected devices only after the operator confirms it.
Deferred survey
Can be shared by link or QR code and remain available for the period set by the production.
12. Connectivity
Connectivity shows the status of the local service, the addresses to use and connected devices. The Sténtor computer, screens and smartphones must be able to communicate over the same local network.
Before an audience test. Check that computers, screens and smartphones are on the correct network, that the QR code opens the right page and that firewalls or hotspots do not block local communication.
13. Settings
Settings contains general app preferences and options affecting workstation behaviour. Show-specific configurations remain in the project.
- Global settings apply to the application and workstation.
- Project settings travel with the show and remain in the production file.
- After a significant change, reopen previews and verify outputs before returning to Live Control.
14. Files and export
The .stn file stores the project and allows it to be moved, archived or reopened on another compatible workstation. Always keep a separate copy before rehearsals or substantial changes.
- Import a script or subtitles
- Check structure, characters, languages and cues
- Save the .stn project
- Export materials for rehearsal, translation, archiving or research
15. macOS, Windows and Linux
The macOS and Windows versions are separate applications built with native technologies, but share the same project structure, terminology and workflow. The Linux version will use Tauri to bring the same working environment to a third desktop platform.
macOS
Xcode · Swift · SwiftUI
macOS 12.4+
Apple silicon and Intel
Windows
C# · .NET 8 · WinUI 3 · XAML
Windows 10 1809+ and Windows 11
x86 · x64 · ARM64 · runtime included
Linux Coming soon
Tauri
In development
Public release not yet available
16. Troubleshooting
| Problem | First check |
|---|---|
| The phone does not open the QR code | Check that the phone and computer are on the same network and that the local service is running. |
| The text does not advance | Check Live Control status, whether Pause is active and the selected cue. |
| The screen remains black | Turn off Blackout and check which output is assigned to the screen. |
| The survey does not appear | Use End show and explicitly confirm that you want to display it. |
17. Research and development
Research and development contains observations, feedback and experimental tools used to improve Sténtor through tests and real use. It is not required to run a performance.
Consent and context. Enable surveys and feedback collection only when they are useful, disclosed and compatible with the production conditions.
Check the project, configure the outputs and test Live Control on the venue's actual network.