Dmitry, it appears there is a problem when running the "fadeout" command followed by "next".
At 7:59:55 fadeout 5000
[fades current playlist track x OK then stops]
At 8:00:00 next
starts the playlist again but track X repeats.
The reason why we have a next command in there is to make sure the playlist continues if there happens to be no event at 8:00:00. If there is a scheduled event at 8:00:00 it works fine. But often the event has to be dis-enabled depending on the content and this requires the "next" command to ensure continuation of the playlist music. Modifying "next"so it plays track X+1 would work....however....
Wouldn't it be more elegant to have a new "fade" command option that did NOT STOP the playlist? It is dangerous if someone removes an event and there is still a fadeout command in there, as RB will stop and stay stopped and the silence detector will never activate.
We are using latest version of RB. I hope this is a feasible bugfix.