Claude
a2ec4d0d3f
setRundown deep-cloned every rundown a second time on top of the clone
createTransaction already makes - the only two callers that matter for
correctness are the ones passing the live cachedRundown singleton, and
db.data.rundowns[key] is only ever replaced wholesale, never mutated in
place, so aliasing it introduces no corruption path. The other six call
sites already pass a freshly-built object they never touch again, for
which the clone was pure waste.
setRundown now takes ownership of `newData` and stores it by reference,
documented on the function. Verified with a throwaway suite (deleted,
per instructions, once green) covering:
- the reference stored is the exact one passed in, not a copy
- round-trip content correctness is unchanged
- a mutation to the source after setRundown is visible through
getRundown, which is the new contract, not a regression - pinned
explicitly so it reads as intentional
- the fresh-object call sites (duplicate, import, rename, etc.) are
unaffected
- mergeRundown / deleteRundown / not-found still behave correctly
- perf: setRundown on a 1000-entry rundown dropped from ~557us/call to
~5us/call
Real disk I/O could not be exercised in that suite - lowdb's JSONFilePreset
forces an in-memory adapter whenever NODE_ENV=test, which vitest always
sets, independent of this project's own IS_TEST flag. That's fine: this
change only affects which object reference ends up at db.data.rundowns[key],
not persist()'s debounce/write-scheduling logic, which is untouched, so
checking that state directly is equivalent to checking what a real write
would serialize.
Full suite (705 tests), typecheck, and lint all pass on the final diff,
which is 8 lines changed in one file.
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.