Event Scheduler : Inverse Waiting Options to insert the event XXminutes earlier than scheduled if it's possible

Altec

Active member
Hi Dmitriy,

There is this very useful option in the Event Scheduler :

1768476142186.png


Could it possible to add the same option but to allow Scheduler launching the event earlier and define an amount of Seconds or minute where the Sheduled event could be allowed to start earlier.

Example :

You configured an event to start at 9:11am and you don't want to cut the Song actually playing, the song end is at 9:10:40 and to avoid the next song to be launched, it could be useful to allow sheduler to insert the Event at 9:10:40 by an option like screened in my post.

ex : "Maximum time set for starting the task earlier"

Best

Altec
 
I think the event start time is sufficient on its own.

If your goal is to start an event at 9:11 AM and you allow it to start 20 seconds earlier, it's best to schedule the event for 9:10:40 AM.

You're including your grace period in the event start time.
The wait time option is useful for suppressing or forcing the start of your event.
This way, your event can start within a timeframe that seems acceptable to you (or be suppressed after a certain delay).
 
You configured an event to start at 9:11am and you don't want to cut the Song actually playing, the song end is at 9:10:40 and to avoid the next song to be launched, it could be useful to allow sheduler to insert the Event at 9:10:40 by an option like screened in my post.

ex : "Maximum time set for starting the task earlier"

Best

Altec
I asked for this some time ago, and was told it was considered for the next version. A practical use for this would be to make sweepers work even better. There are 2 possibilities.
1. Sweepers finish earlier because the time for cross fades were not taken in to consideration, allowing the next song to start early. This can and has happened with multiple sweepers used before.
2. Sweepers could be discarded if they turn out not to be necessary.

Thanks for mentioning this.
 
You configured an event to start at 9:11am and you don't want to cut the Song actually playing, the song end is at 9:10:40 and to avoid the next song to be launched, it could be useful to allow sheduler to insert the Event at 9:10:40 by an option like screened in my post.
This is what will actually happen if you enable this option. This will wait for the current song to end, and once it ends, the event will play. You can also adjust the start time to make an event start earlier, if this is acceptable.
 
I asked for this some time ago, and was told it was considered for the next version. A practical use for this would be to make sweepers work even better. There are 2 possibilities.
1. Sweepers finish earlier because the time for cross fades were not taken in to consideration, allowing the next song to start early. This can and has happened with multiple sweepers used before.
2. Sweepers could be discarded if they turn out not to be necessary.
What was asked in the original post seems to be different (and it's already how the software works), about the sweepers,
1. Crossfading is taken into account, as well as custom start/end markers and other things. If you have a specific case when a sweeper is not properly calculated, can you please provide more details?
2. The sweepers are discarded if it's determined that a sweeper is not needed, or no suitable sweeper is found. If a sweeper is inserted, it means it's needed, and there's no need to discard it later as it's in its place.
 
Back
Top