Author Topic: 53 problem with schedule starting based on priority  (Read 1072 times)

Offline Centauri61032

  • Newbie
  • *
  • Posts: 44
    • View Profile
53 problem with schedule starting based on priority
« on: December 08, 2018, 03:37:58 PM »
I loaded 53 to check the name corruption issue, and my show didn't start.
I have one playlist running 24/7 with just music.
And my show starts at 4:30 with a higher priority.
Up through 51, the higher priority show would kick off at 4:30.
On version 53, it did not. The lower priority 24/7 playlist kept going.



Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: 53 problem with schedule starting based on priority
« Reply #1 on: December 08, 2018, 05:35:52 PM »
There is a quirk there. I will push out 54 with the fix once I test it with my show.


Sent from my iPhone using Tapatalk

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: 53 problem with schedule starting based on priority
« Reply #2 on: December 08, 2018, 11:25:24 PM »
54 is up


Sent from my iPhone using Tapatalk

Offline mmais

  • Full Member
  • ***
  • Posts: 212
    • View Profile
Re: 53 problem with schedule starting based on priority
« Reply #3 on: December 09, 2018, 05:23:38 AM »
54 is up

Just tried to download 7:30 AM & says Failed-No File
Mike


Offline Centauri61032

  • Newbie
  • *
  • Posts: 44
    • View Profile
Re: 53 problem with schedule starting based on priority
« Reply #4 on: December 09, 2018, 09:22:03 AM »
Well, 54 is a no go.
It runs for a while. Then just suddenly disappears.
Log attached, hopefully

Offline Centauri61032

  • Newbie
  • *
  • Posts: 44
    • View Profile
Re: 53 problem with schedule starting based on priority
« Reply #5 on: December 10, 2018, 03:43:42 PM »
OK, so far, 55 is doing great.
I have had it running for about 10 hours now.
No file name corruptions. No crashes.
And the schedule kicked off based on priority as it should.
Kudos to Keith!