Claude
f806244586
Adds a teleprompter at /teleprompter which builds its script from the rundown rather than from an uploaded file, so the read follows the show. The script comes from a text custom field chosen per view, and the whole rundown renders as one continuous document with a heading per segment. That is how broadcast prompters work: the operator scrolls to the right section as the show moves, so a hard cut on every event change would take the tail of the line the talent is still reading. Following the loaded event is a soft jump which releases when the user scrolls by hand, the same interaction the operator view already uses. Controls are local, and match the convention shared by prompter software: space to run, arrows for speed and nudge, home to rewind, F to flip. That convention doubles as the hardware protocol, since foot pedals and hand controllers are USB HID devices emitting these keystrokes, so they work with no setup. Space is claimed back from the navigation menu for the lifetime of the view via a small store, since the router renders the menu generically for presets and a prop would not reach it. Scrolling uses native scrollTop on an overflow container, with the animation frame loop as its only writer. Position is kept as a float in a ref: at readable speeds the per frame movement is well under a pixel, so rounding every frame would stall the scroll, and holding it in state would re-render the document sixty times a second. Scroll anchoring and smooth scroll behaviour are both disabled because each would be a second writer. Notable details: - flip applies to the view root, so a beam splitter inverts the scroll direction along with the text - content padding is derived from the viewport height, not a percentage, which resolves against width and would strand the first line - image custom fields are refused even when typed into the URL - script text is rendered as a text node, never as markup Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cb8RVPNQ2ETPJxdy4b8CHf
Download the latest release
- Download for Windows
- Download for macOS (Apple Silicon)
- Download for macOS (Intel)
- Download AppImage for Linux (Intel / AMD 64-bit)
- Download AppImage for Linux (ARM 64-bit, Raspberry Pi 4+)
- Download AppImage for Linux (ARM 32-bit, older Raspberry Pi)
... or
- Get from Docker hub
- Install from NPM
- Install from Homebrew
Need help?
We do our best to have most topics covered by the documentation. However, if your question is not covered, you are welcome to fill in a bug report in an issue, ask a question in GitHub discussions or hop in the discord server for a chat.
Using Ontime?
Let us know! Ontime improves from the collaboration with its users. We would like to understand how you use Ontime and appreciate your feedback.
Ontime
Ontime is a browser-based application that manages event rundowns, scheduling, and cueing.
With Ontime, you can plan, track your schedule, manage automation and cross-department show information all in one place.
Ontime is made by entertainment and broadcast engineers and used by
- Conference organisers
- Touring shows and receiving venues
- Broadcasters and streamers
- Theatres and opera houses
- Houses of worship
Main features
- Multiplatform: Available as a Cloud service and for Windows, macOS, Linux, or self-hosted via Docker.
- In any device: Ontime is available to any device with a browser, eg: tablets, mobile phones, laptops, signage, media servers...
- Team Collaboration: Dedicated views for directors, operators, backstage, and signage.
- Real-Time Updates: Manage and communicate runtime delays effortlessly.
- Automatable: Ontime can be fully or partially controlled by an operator, or run standalone with the system clock
- Flexible Integrations: Use one of the APIs provided (OSC, HTTP, Websocket) or the available Companion module to integrate into your workflow (vMix, disguise, Qlab, OBS)
... and a lot more ...
For live environments
Ontime is designed for use in live environments.
This guides the application into being flexible and efficiently integrating into different workflows.
For teams
All information added in Ontime is shared with the production team and other software / hardware in your workflow.
Ontime also improves team collaboration with dedicated views for cuesheets and operators, and for public and production
signage.
Simple infrastructure
All the data is distributed over the network, making its distribution and infrastructure flexible and cheap.
With the availability of the docker image, you can also leverage IT infrastructure to make Ontime available online for
your team and clients.
Ontime is made by video engineers and entertainment technicians.
Using Ontime
Getting started
The easiest way to start with Ontime is by leveraging our Cloud service.
This will give you immediate access to running instances of Ontime which are available to share with anyone with an internet connection.
Alternatively, you can run Ontime locally for free by downloading the latest release for your platform or using the docker image, available at Docker Hub
Once installed and running, any device that shares the same network as Ontime will have access to Ontime.
More information is available in our docs
Continued development
Ontime is under active development. We continue adding and improving features in collaboration with users.
Have an idea? Reach out via email or open an issue
Issues
We use Github's issue tracking for bug reporting and feature requests.
Found a bug? Open an issue.
Contributing
Looking to contribute? All types of help are appreciated, from coding to testing and feature specification.
If you are a developer and would like to contribute with code, please open an issue to discuss before opening a Pull Request.
Information about the project setup can be found in the development documentation
Links
License
This project is licensed under the terms of the GNU GPL v3
Sponsor
You can help the development of this project or say thank you with a one time donation.
See the terms of donations.