xSchedule Crash

[Centauri61032]

Hey all.
I am also having trouble with the schedule locking up. it is not actually crashing, just locking up when it changes steps. Unfortunately I'm not at home right now so I can't provide any logs are screenshots. But what my wife has noticed is on the right side of the x schedule screen, the step that is supposed to be playing suddenly has a unprintable character in the line. she says the character just looks like an open box. But if she stops and restarts x schedule, it will go ahead and start running and that step may very possibly work again without the special character. She has double check that the file names and everything are correct. but the schedule is occasionally locking up, and when it does lock up this strange character is appearing in the name of the step that is supposed to be running.
I went back to a previous version for now, but will install the new version tomorrow when I get back home and see what happens. Then I can send some logs if needed. Just didn't know if this anomaly was of any help in fixing it.

[keithsw1111]

Post you xschedule file and your xschedule log file.


Sent from my iPhone using Tapatalk

[Centauri61032]

OK, the requested files are attached here. Along with a screen shot while schedule is frozen, showing the step with the strange character in the name.
Again, this is a freeze, not a crash. I can just 'x' out of xSchedule and restart it. Also, the freeze is random. It will happen on any song.
I also have a screen shot of the same song as above, not frozen, without the special character in the name.

ADDITIONAL INFO...  I just tried running this schedule on a totally different computer. Basically, the computer that I use for creating sequences. (Not connected to the lights.) After about 40 minutes, it also froze with the exact same symptom. So whatever my issue is, it is not isolated to this one machine.

[ttn2207]

2018.48 Crashed last night - At the end of the show, lights turned off then received the crash screen.  I downloaded .49 just now and will let you know how things go.  Here is the log file/crash report from last night.

[ttn2207]

Just did a quick test with .49.  It appears to be an issue with the "Stop All" Command.  I have a "Final Sequence" that just has the all the lights on.  At the end of 1 minute, the lights turn off and then I run "Stop All" to ensure that no other playlist kicks back in.

If I take this command out, the "Final" playlist runs, and then it goes back and plays the playlist that was playing.  If I put the command back in, I get the crash (log file/crash report attached). 

Pressing the "Stop All" button at the bottom of the screen does NOT result in a crash.

I am going to let it run tonight without the "Stop All" command to ensure that it runs as expected and will report back tomorrow.

[ttn2207]

Without the “Stop All” command, everything ran nice a smooth.


Sent from my iPhone using Tapatalk

[keithsw1111]

Interesting. That would explain some crashes I have been seeing. Didn’t consider that a playlist could become invalid during a step.


Sent from my iPhone using Tapatalk

[nmiller0113]

Just did a quick test with .49.  It appears to be an issue with the "Stop All" Command.  I have a "Final Sequence" that just has the all the lights on.  At the end of 1 minute, the lights turn off and then I run "Stop All" to ensure that no other playlist kicks back in.

If I take this command out, the "Final" playlist runs, and then it goes back and plays the playlist that was playing.  If I put the command back in, I get the crash (log file/crash report attached). 

Pressing the "Stop All" button at the bottom of the screen does NOT result in a crash.

I am going to let it run tonight without the "Stop All" command to ensure that it runs as expected and will report back tomorrow.

I'm just curious, why do you need the stop all?  If you set the last sequence / step in a playlist to "play only once" then it does the same thing.  I'm probably misunderstanding your issue or reasons

[ttn2207]

Interesting. That would explain some crashes I have been seeing. Didn’t consider that a playlist could become invalid during a step.


Sent from my iPhone using Tapatalk

I did not have a chance last night, but I would like to test other “commands” to see if it is just the “stop all” command or if it is all of them.




Sent from my iPhone using Tapatalk

[ttn2207]

Just did a quick test with .49.  It appears to be an issue with the "Stop All" Command.  I have a "Final Sequence" that just has the all the lights on.  At the end of 1 minute, the lights turn off and then I run "Stop All" to ensure that no other playlist kicks back in.

If I take this command out, the "Final" playlist runs, and then it goes back and plays the playlist that was playing.  If I put the command back in, I get the crash (log file/crash report attached). 

Pressing the "Stop All" button at the bottom of the screen does NOT result in a crash.

I am going to let it run tonight without the "Stop All" command to ensure that it runs as expected and will report back tomorrow.

I'm just curious, why do you need the stop all?  If you set the last sequence / step in a playlist to "play only once" then it does the same thing.  I'm probably misunderstanding your issue or reasons

I only do the “show” at certain times one night a week.  The “show” is only about 15 minutes long (I am striving for the old church Christmas Pageant).  The rest of the time, the rest of the week, I have an all lights on show playing with some songs, which continually loop from 4-9.  I then have a “final” sequence play at 8:59 that has a higher priority than the one than the normal sequence.   This “final” sequence slowly dims the lights until they are off.

In testing, I found that the “normal” show would sometimes go over my 9:00 shut off time.  So I created the “final” sequence of the night.  If I play this final sequence, it ends and if there was a little bit “normal” show left, then it would go back to play that then end.

By adding the stop all command, it allowed me to ensure that all lights were off right at 9.

It is no longer the “end of the world” if the show does not end right at 9pm (which coincided with my daughters bed time - floodlights on cutouts shines into her bedroom), it is just a “left over” from days gone by and since my neighbors have gotten used to the lights being off at 9, I am trying to make sure they are, but again - not the end of the world if I run a couple of minutes over.


Sent from my iPhone using Tapatalk

[keithsw1111]

Interesting. That would explain some crashes I have been seeing. Didn’t consider that a playlist could become invalid during a step.


Sent from my iPhone using Tapatalk

I did not have a chance last night, but I would like to test other “commands” to see if it is just the “stop all” command or if it is all of them.




Sent from my iPhone using Tapatalk

It should just be the stop commands.


Sent from my iPhone using Tapatalk

[Centauri61032]

Hey Keith...
I have some more 'observations' about the issue I am having with the scheduler locking up...

I just happened to be sitting at my computer while the schedule was playing my offline songs. I had the xSchedule window open, as well as the web interface HOME page. The home page was of course showing the song playing, next to play, etc.

Suddenly, when the next song started playing, the web interface screen went just about all but blank. It had the green 'Player Status' bar at the top, but nothing below. But the song was still playing.

I switched to the xSchedule screen. I had a green bar on the song that was playing. But the NEXT song to play (yellow bar) had that strange unprintable character in it.

I looked at the log file, and there were some  "[WARN] Frame interval greater than 200% of what it should have been [50] 183 " (and other numbers than 183) messages.  The current song was still playing.

I went back to the web interface, and switched to the 'Playlist section. I found the song with the unprintable character in the title, and clicked 'play'. It started playing. I went back to the Home screen, and it was displaying normally again.

At that point, the schedule continued on it's merry way. 

One other thing...  On the xSchedule screen, the song with the strange character still showed the strange character. But when it came back around, it did play normally. In the web interface, the title was correct (without the character). But in the Schedule screen, that song title did NOT turn green. Even though it was playing fine.

I had no problems with any of this in v 2017.44.  I have gone back as far as 2018.43, and still have this issue. If there is another earlier version in between you would like me to try, let me know.

Thanks!! -Ray

[ttn2207]

Looks like it is just the “Stop All” command that is causing the crash.  The “Stop” commands, specifically the ones to stop certain playlists, appear to just “pause” the specified playlist.   In testing these, the specified playlist appear to only pause.  After my “final” sequence plays, it goes back to the “filler” sequences that I had attempted to stop.


Sent from my iPhone using Tapatalk

[ttn2207]

Keith - should I add this to the bug list?


Sent from my iPhone using Tapatalk

[keithsw1111]

No ... i think i fixed this for .50