About crossfading, I think there should be an option to select how user wants to do it - time based or dB.
This is good news. And I agree with giving options. Its always good for users to make their own choices.
From DJSOFT: Or it should just skip events? From DJSTU:I would suggest that each event have a "life" to exist after its original intended time to play. Add in a box that has variables like if this event is unable to play/activate within x minutes of its posted event time, then its to be deleted.
I've been thinking further about this. I have given the impression that each event should have a "life" given to it. But I think a better way of handling it would be to do this (once again giving users options):
(1) The event has "NO Time to Live", therefore stays and subsequently plays (but only on hitting resume RB). This could be more than one event.
(2) The event has a "Time to Live" nominated in minutes after its designated scheduled time, therefore either stays or goes due to time lapse (remaining events play only on hitting resume RB). This could be more than one event.
(3) The event has a "MUST play", regardless of RB status. That is, if RB is in stop mode for instance, then the event happens regardless. It could be a command happening outside the Playlist, therefore the Playlist would not start but the event happens, or it could be an instruction affecting the mode of the Playlist. This could be more than one event.