Claude
8551c161f1
Review of the run history feature turned up four defects, all in the code that feature introduced. - Runs were dated with a time of day rather than a wall clock instant. `clock` and `rundown.actualStart` are millis since midnight, so every run in the history list rendered as 1 January 1970, and getLatestRun ordered runs incorrectly across days: a run at 09:00 today sorted below one at 20:00 last week, so the "last run" chip and /runs/latest could return an older run. Runs now take `_startEpoch`, the instant the show began, and the type documents the invariant. - A stop arriving with no run open is ignored. Loading a project stops playback and reinitialises reporting in the same tick, and the trailing stop was attributing the previous project's event to the new one. - Run summaries counted planned events from the loaded rundown rather than the rundown the run belongs to, so switching rundowns mid-run gave the summary a denominator from a different rundown. A run whose rundown has since been deleted now keeps its last known count instead of dropping to zero. - Recovery of runs left open by a crash only closed the first one. Any others stayed dangling forever: permanently shown as ongoing and never eligible as the latest run. Also replaces the raw ISO default run label with a readable local date and time, and adds a batching upsertRuns to the store so recovery writes the sidecar once rather than racing one write per run. Each fix has a regression test, verified to fail without the change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019nr3FbLbM8gB8Jm771YgTV
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.