new functions for "stop command"

lughsan

Active member
Hello Dimitry, how are you?

I would like to implement the ability to give options to the "stop command" when inserting it into the playlist.
that inserting a "stop command" will automatically add events to the queue.

This is how I insert daily events:
1728163291474.png

The purpose of this is to have the system continue to execute the events but after adding the command.

This option could be added as follows:
1728164732654.png

would work based on the last stop command added.
 
If the stop command was inserted by another event, you can use the "Queue after scheduled tracks" option.
 
We use it directly in the playlist.
1728312586311.png

The idea is that the user stops the playlist, but continues the execution of the following events.
Is the purpose of adding this new feature understandable?
 
The idea is that the user stops the playlist, but continues the execution of the following events.
Is the purpose of adding this new feature understandable?
Not really... If the playlist was stopped by the "stop" command, the events that start after that, will play.
 
Not really... If the playlist was stopped by the "stop" command, the events that start after that, will play.
What I want to achieve is that when I put the "stop" command the next event is not played, it is executed but remains in the queue.

I need that when the playlist is active, the events work like this:
Insert position:
after the playback track (queue)

but when you add the "stop command" to the playlist, the events are automatically executed and queued, but without being played.
 
What I want to achieve is that when I put the "stop" command the next event is not played, it is executed but remains in the queue.
This looks like a very specific use case, I don't think we'll be adding such a feature to the program, I'm sorry. Events can check the playback state and action/skip based on that, but not check for the presence of the "stop" commands in the playlist.
 
Back
Top