-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live performance & theatre #165
Comments
Hey @sagerian, apologies it took me a while to get back to you. I wanted to have a good read since there are lots to unpack First of all, thank you for your message and for getting involved. I have been developing ontime in collaboration with people like you and being able to do some feature testing and validaton of workflows is a great contribution. Onto your points
Do I understand correctly that actual start / end would be a record of when did the operator started the running event and actual end when the playback moved away from this event? (which would mean that duration is a factor of the two).
Thank you again for getting involved. It would be great to talk about your workflow and how could the app help you in the theater. Lets continue the conversation and maybe make some issues from here, feel also free to reach out at [email protected] |
Just adding a bit more context to this - around the start and end of an act, there is a lot going on for the stage manager. On a large production there could be dozens or even close to a hundred people who all need to do something at exactly the right second, in completely different rooms, floor levels, sometimes different buildings. Even a simple performance there's a lot to do. The workload then is 100x higher than at any other point in the performance and you rarely have enough people. If you did, 90% of them would spend the next hour doing nothing at all. Even when it goes smoothly I often just glance at my watch at the start and memorise the time, then start my timer a minute (or five minutes) later and scribble it in my notepad. It's obviously not accurate enough. When things aren't going smoothly, eg a broken leg, sometimes I just have to run the show without a timer for the act. If it could just start automatically that would be so much better. |
Hi @abhibeckert , thank you for getting involved. great to get some feedback. I would suggest that perhaps one of the integrations could be used to start the time? so that it could be triggered by lighting / sound. |
Hey Apologies back for the slow reply. I've been flat out at work but I have also implemented a proof of concept system across our current site which shows potential.
Yeah, basically the functionality I would love to see is the ability to look at the scheduled times versus their actual times. For us this would mean we can keep an eye on particular acts if they're starting to drag etc.
The next event start, or it might be a stop or pause or some other input. In an ideal world this could be exported or saved as a text file
I appreciate roll mode adds an extra layer of complexity. It feels like a good litmus test. Does it need an end? |
Hi @sagerian and @abhibeckert The current specification is something like:
The data contained would look like
Along with a list of your events, and the report of their playback, eg: for a single event
The data would relate to the last time something happened in an event. Meaning that if you were to run the same timer a few times, you would only see stats for the last run Could you please share some thoughts? @sagerian Some other things you mention:
We have a few requests along this lines and we have paved the way to make it happen in v2. However I am unconfident on the details. Perhaps you can help?
As for start only, could you take a look at a similar thread #59 (comment) |
Most of the improvements here have been implemented over time. The missing part, which we called event reporter, doesnt seem to have received enough community interest to be considered worth it by us working with Ontime I am happy to reconsider a implementation as described above if this changes Meanwhile I will close this issue |
Hi,
I'm a tech for a touring live show and I've been looking around for a timing system.
I just wanted to make myself know around here. I can't write any code beyond some simple Applescript but I may be able to contribute to this project in other ways. I'd like to see this project succeed because I feel it can bring a tremendous amount to the table.
Ontime has a number of great features that I would use on other shows, however it doesn't quite work for my current show. Ontime clearly shows a lot of potential.
I would like to be able to reduce the workload for staff (SM mainly) by automatically recording when Act 1, Interval, and Act 2 start/end. This information could be used to automatically populate the post show report template. In my situation qlab could easily send an OSC signal to ontime to start the timers.
Currently we use a hacky method of timing the interval with midi time code (MTC). QLab starts a MTC cue at 00:00:00 and stops after 20 minutes. The timecode starts along with the cue that is fired as the intermission starts so it's perfectly accurate for our purposes.
I've written a script that auto opens timecode window allowing front of house and other staff to see the time if they are within arms reach of the QLab MacBook. I would love a way for SM, FOH, Venue staff to easily see the interval timer on their phone (or apple watch?) instead.
I've been playing with the cuesheet display and I'd like to see some more columns
General features that would be nice
Bit of a ramble here happy to clarify if there's interest.
Thanks
The text was updated successfully, but these errors were encountered: