Lumin T2 burn in time?

Hey @tah800, I actually think the lumin app is pretty good once you get used to it.  I especially like the pop up menu from any song on the playlist or the browse window to search for a song, album, or artist.   Sometimes you hear a song you like and want to see what other albums or songs does the artist have, or sometimes you might like to see if there are other covers of a particular song.   I think that's a great feature and it saves a lot of time.  I'm talking about using Tidal here.  This feature doesn't apply to Spotify.

The one thing I don't like which I already mentioned in this post is the 'shuffle/random' feature.  It is just poorly implemented.  Hey @thingswelike, are there any chance that you guys are going to fix the 'random' play feature?  Thanks.

I'll pass on your thoughts to the team.

@xcool What is it about the 'random' play that you don't like? That's the first time I've heard it criticised.
Can you describe a test that would be repeatable by the support team?

HI @thingswelike, I’m cutting and pasting from my earlier post in this thread on the ’shuffle’ feature. Thanks!

For testing, just play a list of songs and turn on shuffle mode, and see if you can hear a song repeated before the current playlist is finished. I’m a software engineer myself, so I would say just look at the code, and see how the shuffle feature is implemented. If the logic does not keep a list of already played songs, then randomly picking the next song can possibly pick a song that’s already been played. My preferred logic for this feature is to first randomize all the songs and create a playlist in this randomized order and play from start to finish. If new songs are added to the playlist while it is still playing, then I would say re-randomize all the songs that haven’t been played plus the newly added songs.

Anyway, this is my original post on this issue. Thanks again!

"BTW, I have another comment about the Lumin App. It’s about the implementation of the "shuffle/random" feature of the playlist.

First of all, when the shuffle feature is turned on, the current playlist is still displayed in the original insertion order, and I noticed that some songs can possible be selected more than once before the playlist is finished. Also, you have no idea what the next song will be ahead of time. It seems to me that the shuffle implementation picks the next song randomly when the current song is finished, therefore it is possible that a song can be played more than once. Am I correct with my observation?

I’m comparing your implementation against something like the Cambridge Audio app. In the Cambridge implementation, when shuffle feature is turned on, the current playlist gets randomized and displayed in this new randomized order. You know exactly what the next song will be, and also the same song will not be played more than once before all the songs in the playlist have been played."

Thanks for the update - I'll forward this to the relevant team members.

@xcool I've heard back from the team that shuffle will already avoid repeating any tracks.
My simple tests show this to be the case.

Note that this gets reset if you tap any track or modify the playlist though. So perhaps you've noticed repeating because you've been trying to treat it like the Cambridge app and manually select tracks during playback.

My initial thought is that we don't want to randomise the actual list, but you are welcome to email us with a feature request and it will get reviewed by the full team.