Closed bflorat closed 9 years ago
Commented by bflorat on 6 Aug 2013 19:21 UTC What we could do is to shuffle among all tracks minus all track played since a given time (like 6 mounths or one year) from history. If remaining tracks number is too low, we shuffle among all tracks minus tracks selected in first step.
Commented by Duncan on 11 Aug 2013 10:06 UTC I was referring to tracks queued in a single session. If for example there are 20 tracks, instead of playing all tracks one after another, it will play 3/4, then select an already played track, rather than playing an unplayed track.
Is there a way of hiding a track/making it unavailable once it has played as far as the programme is concerned so it will be skipped to avoid this problem?
Commented by bflorat on 26 Mar 2014 20:55 UTC Done in upcoming 1.10.7 for global shuffle function : in addition to shuffling tracks, we now keep tracks played recently (150 days) apart given than we still have a minimum of 200 files in the queue.
UT written.
Reported by Duncan on 30 Jul 2013 15:32 UTC I raised a previous ticket a while ago in which I mentioned the "randomisation factor" being an issue. On further thought, the tracks selected are very much ok in terms of randomness (no multiple instances of the same track, artists vary etc.)
It seems that the problem is really with Jajuk repeating songs that have already played from the play queue BEFORE the rest of the songs have played.
Is this fairly simple to smooth out?