Originally posted on: 10 May '12 - 18:51
I was positive I didn't have duplicated playlist entries, but I tried your suggestion anyway. Still 2,169 entries, still around 76 hours. I haven't disabled Random Play since I reloaded my "modules" playlist and my Library file list hasn't changed since before that. The longest amount of time it's been since a track has been played has been 44 days (not counting the 71 files that have never
been played in the 44 days my Library kept track of these files, which is a mix of files old and new I might add).
I'm willing to admit that I'm wrong about the "xmplay" playlist file not tracking files, as after examining the file itself and doing a bit of testing with 37 files, it didn't
start repeating files (as far as I could tell) until it was completely out of files to play. The only thing I didn't try was rebooting after advancing a few files, as that's the only clear difference between my testing situation and my "everyday use" situation. So maybe it's all in my head... I can't say I have
gone through all 2,169 files yet, since I just updated recently here. So maybe those "44 days since last played" and "never played" statuses are just carried-over artifacts from v220.127.116.11...
Of course, it would still be nice if, when loading from the Library, there was a way for the music player to take into consideration the last time some files were played compared to others. Like for example, auto-tagging files played in the last 7 days as "played", rather than keeping specific dates handy in the Library list or playlist files. This would probably only be helpful to people to rapidly swap around their playlists a lot (like I occasionally do), though, so I'm probably in the minority here...
Thanks for your response, by the way! It really got me paying closer attention to the mechanics of the program and its local playlist file, which got me thinking. I'll get back to you on the randomness thing after I've played through 76 hours-worth of music. Which will probably take a couple weeks, knowing me. By the end of that period, I'll hopely not see any number higher than around "14 days" on my Library, though. But we'll see!
*makes a note to use another media player if he has a sudden urge to listen to an entirely different playlist, for now*
Originally posted on on: 28 May '12 - 09:54
Alright. That last idea of mine... I'm not sure actually panned out like I thought it would. The longest "last played" on my Module library was indeed about 20 days or so (I stupidly emptied my library before I checked), but it still seemed like I was getting a number of repeats after playing the entire playlist, despite having only maybe one or two duplicate songs (with different file names)... So! I'm doing this instead:
I have a playlist of 1,630 files amounting to 48 hours of music. I'm going to use this for my revised test, in which I've emptied my Library completely and turned off auto-scan for my MP3 folders, but enabled
"Add to Library on play". This will be a sure-fire way to see just how random this randomizer really is.
Wish me luck.
Welp... It's been eight days, and my Library reflects that exactly. 1,630/1,630 files have been played and, to the best if my knowledge, I did not detect a single duplicate that wasn't a duplicated file in and of itself.
My apologies, Ian. Your coding is indeed very, very good and the randomization in the newest BETA version (linked above) is most definitely very random. Kudos!