Timeline for Shuffle in music players
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2019 at 10:26 | vote | accept | Juha Untinen | ||
| Jul 30, 2019 at 12:00 | history | protected | user53019 | ||
| Jul 30, 2019 at 10:33 | comment | added | Lie Ryan | Here is a more visual representation of why simply shuffling a playlist fails the human's "looks random" test. Also known as Texas sharpshooter fallacy. | |
| Aug 21, 2018 at 3:00 | history | tweeted | twitter.com/StackSoftEng/status/1031737812410949634 | ||
| Jul 25, 2018 at 13:09 | answer | added | Ryathal | timeline score: 14 | |
| Jul 25, 2018 at 13:01 | answer | added | Ewan | timeline score: 3 | |
| Jul 25, 2018 at 12:35 | comment | added | Neil | Oddly, a computer is better equipped to determine randomness of a series than a human being. It seems what we really want is "pseudo-random" shuffles. | |
| Jul 25, 2018 at 12:10 | comment | added | Useless | Implementing shuffle correctly is, indeed, pretty trivial. Implementing shuffle that "feels randomish" to people isn't, because a random shuffle will randomly repeat sub-sequences on different plays, or randomly select clusters of songs from the same album. The listener, noticing these patterns, will attribute them to a "bad" shuffle because people are rubbish at reasoning about coincidences. | |
| Jul 25, 2018 at 11:45 | review | Close votes | |||
| Jul 30, 2018 at 3:05 | |||||
| Jul 25, 2018 at 11:31 | comment | added | Juha Untinen | I checked that one too, but in that the use case is far more specific, ie. playing a similar version (eg. various live performances of the same song) of the same song only after a certain amount of other songs have played inbetween. | |
| Jul 25, 2018 at 11:29 | comment | added | gnat | Possible duplicate of I'd like to write an "ultimate shuffle" algorithm to sort my mp3 collection | |
| Jul 25, 2018 at 11:27 | history | asked | Juha Untinen | CC BY-SA 4.0 |