Collection Size Playback Order Chronological Order Random Offset

[spark zealot]

Version 25.4.0-988ed8db-docker-amd64

This has been happening for a while but before Multiple Mode: Collection Size was involved I was using what seemed like a unintended edge case of Multiple Mode: 0 that seemed to do the same thing, and figured best not complain about unintended edge case behavior. However now that there is a this multiple mode, there's this strange issue where if I want a collection to play in Chronological or Season/Episode order, it sometimes seems to decide to play in order, but from some arbitrary index instead.

This happens inconsistently. In the documentary channel I posted you can see that some of the schedule items are in correct order, others aren't. It's occured to me before that maybe this is due to bad metadata but the cases I've checked have not had this issue. Both the dates and season/ep order appear correct, playout just isn't doing that. It's not even a consistent index offset as far as I can tell

[stone jasper]

I would check the schedule itself for the random start point option

[spark zealot]

Ok, so Random Start Point means "random start point per schedule item"? I was under the impression it meant take a playout and start as if it had been going for a random amount of time, so the order is consistent but when reset it gives the appearance of randomness

[stone jasper]

Yes it randomizes the start point of each collection