Windows Command another request

[ItsMeBobO]

While the topic of Windows command is going,  I would like to submit another request which may be helpful.      Currently the windows commands may only be executed the moment the sequence starts playing.     In addition to IF the command should be executed,  can we specify WHEN to execute it?   And if this is considered, could there be more than a single command run?     Many of us are using the command to track when songs start playing and to trigger changes on signs, RDS transmitters,  Tv monitors,  and web pages reporting which song is currently playing.   It would be nice to send messages to external devices in the middle of a sequence so it can coordinate other messages.   Example:   When the audio declares "Its Christmas",  having a cmd send a message which can tell a Tv monitor to display the words "Its Christmas"  to incorporate it into the show. 

It would also be useful to run a command some number of seconds before the end of a playing sequence.     This trigger can be used to prepare external software to transition to the next sequence.  

Edited July 3, 2020 by ItsMeBobO
typo

[k6ccc]

Yea, I can see some advanced uses for something like that.  Something like Windows command 1, 2, & 3 with each having options for when to run such as a) start of song, b) x seconds after start of song, c) x number of seconds before end of song, or d) at the end of the song.  In reality, options c & d could be eliminated if it's too much trouble because we CAN do the math...

 

[ItsMeBobO]

You are right     b)  specify second,   would cover a) and  c) & d)      if the knowledge of when to run is completely stored in the sequence.            

But.... if you were using a shared command which was set to 5 seconds before the end.. it would work for any song.      This would mean the knowledge of when to run relative to the start or end would have to be stored with the command in cmdmap.lcm

Edited July 4, 2020 by ItsMeBobO