Skip to content
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

Roll mode offset behaviour #1340

Open
admiralchekov opened this issue Nov 21, 2024 · 1 comment
Open

Roll mode offset behaviour #1340

admiralchekov opened this issue Nov 21, 2024 · 1 comment

Comments

@admiralchekov
Copy link

Hello, I suspect this is actually intended behaviour but I would appreciate some help or changes to allow me to use my old workflow. Perhaps an option to disable offsets?

While in Roll mode If I change the end time of a loaded event to before the beginning of the next event (all events linked start to previous end) the timer starts from the beginning of the next event with the full duration and a negative offset instead of the new start time. I am currently working around this by stopping and restarting roll mode.

For context, the use case is a three hour recording session with a 15 minute break that can be started anytime between 1h 15m and 1h 30m. By default we set the end time of the event before the break to 1h 30m after the start of the recording session but when a break is started before then we manually update the end time of the current event to the time that the break started at.

This is somewhat related to the issue I have opened in the companion module repository: https://github.com/bitfocus/companion-module-getontime-ontime/issues/85
If I press one button to set the end time of the current loaded event to the current time then this will not be an issue. The only reason for the start tine of the break event being in the past is the time it takes to update the time manually.

Thanks in advanced,
Sam

@cpvalente
Copy link
Owner

Hi @admiralchekov , thank you for this
I would like to make sure we are on the same page as what the issue is, would you mind making a small video screengrab showing the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants