Claude
cdde054b14
Reviewing the branch turned up defects, several of them worse than the problems the original commits set out to solve. Destructive: deleting an automation removed its global triggers and only then discovered a rundown event also referenced it. The delete failed, the user cancelled, and their triggers were gone for good. The server reports trigger references before event ones, so this was reachable whenever both existed. Deleted triggers are now recreated when the delete is refused. Silently wrong: a template read the project from disk while writes are debounced by three seconds, so "make some automations, save them as a template" could produce a template without them. Verified by hand: an automation created milliseconds earlier now appears. The demo shipped half a pair. The danger warning set a stage message visible and nothing ever cleared it, so from the first event that hit its danger window the message covered the countdown for the rest of the session. The recipe library ships the clearing counterpart; the demo now does too, and the whole cycle is verified against a running server. Flood control undid itself. resetAutomationLogState ran on every onLoad, and roll mode loads at every event boundary, so the "logging suppressed" notice was re-emitted once per cue: exactly the flooding it exists to prevent. It also wiped the throttle for onLoad and onStop immediately before writing to it. Reset now happens on stop only, outside the early returns that made the first attempt at this a no-op. Trigger reconciliation diffed a mount-time selection against a live prop. Settings are polled, so a trigger created in another tab while the form was open would be deleted by a save that never saw it. It now diffs against the snapshot, and says which triggers a save will remove rather than removing several same-lifecycle triggers silently. Also: a rundowns template no longer carries a phantom empty rundown from makeNewProject; the partial-duplicate endpoint returns the name it actually used, since collisions get renamed; the template flow invalidates the project list rather than relying on a refetch on mount; the last-fired label drops to a one minute cadence instead of holding a 1Hz timer per automation forever; e2e cleanup moved to afterEach so a mid-test failure stops leaking state. The e2e spec has now been run against a real server, green on both the demo project and a blank one, leaving no residue. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LpbLJVVT26tzWkduck1M9H
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.