Lights staying on in scheduler...

I'm not sure if this is a bug or a feature.  Basically, what happens is that the lights stay on between sequences until the current sequence uses the channel(s) that is left on when using the scheduler.

Here's how to duplicate the issue.

Create a 10 second silent WAV file.
Create a 5 second silent WAV file (you can have music or what not, but just easier to recreate the issue this way).  I used audacity to do this.

Now, create a sequence using the 10 second WAV file.  Turn on the lights on one of the channels (use channel 1 for now, but it doesn't matter what channel) for the entire 10 seconds.

Save the file as test1.

Next, create another sequence using the 10 second WAV file.  This time, use a different channel (channel 2).  The main thing is to not use the same channel in the test1 file.

Save the file as test2.

Next, go to File->Properties and change the music file to the 5 second file WAV file and save the file.

Now, go to scheduler and put test2 as the first file to play and test1 as the second file to play.

What you will notice is that channel 2 will stay on when the next sequence is played (test1).  This is because we changed the number of seconds of the sequence from 10 to 5 and the last 5 seconds of the sequence had channel 2 on.

I'm not sure if this is a feature or a bug.  I would think that all of the lights would go off once the sequence has completed. 

This happened to me when my son wanted me to shorted the song he was working on.  I apparently cut it a little shorter than was his sequences were.  I was able to resolve the issue by reloading the original music, deleting the extended sequences and then loading back in the shorted music file.

Hopefully this makes sense.
   --Cam--

Pony_God is correct... the "off" event is never sent because it is never reached.  While we can fix this in the code, at the moment it is an "undocumented feature"... consider it a trick to keep your tune to signs lit between songs.

FYI... you can also accomplish this without shortening the WAV file.  The "off" event at the end of the sequence is one of the "default events" that Aurora requires in the sequence and places there automatically.  While you can not delete this event (Aurora will not let you), nor can you scroll past it to see its cell, but you can zoom out far enough to see past it (with some effort).  Once you can see past it you can in fact use the info too to edit the final off event and change it to something else that will hold between songs.