https://bugs.kde.org/show_bug.cgi?id=428833
--- Comment #6 from Nate Graham <n...@kde.org> --- (In reply to Matthieu Gallien from comment #4) > Thanks for your feedback. > > I have a quite different opinion. I think that a music player is dedicated > to manage the playlist. That should show what tracks have been played and > will be played next. > > This is one thing I regret from Amarok (i.e. the smart playlists). What I've discovered over time is that there are two general usage models for a music player: 1. Add the music you want to play to a global playlist explicitly ----------------------------------------------------------------- With this model, you have to explicitly add the music you want to play to a semi-temporary global playlist. This model is well-suited to people who like to create mixes and listen to lots of songs from different albums. The downside to this model is that it requires an extra step to actually play any music; you can't just say "Play this thing I'm looking at"; you have to explicitly put that thing in the global playlist, which means you always have to do some state management. So it's a bit more annoying for people who have simple use cases like "sequentially play these albums from this artist" or "Randomly play songs in my whole collection" As a result, music players which emphasize this style tend to eventually find a way to support more lightweight play modes where you can use the browsing views directly to play music and hide or disable the global playlist until needed. 2. Use the navigation/browsing views as a de facto global playlist ------------------------------------------------------------------ With this model, you navigate to what you want to play and click play right there, and then the player plays that music as well as the rest of the music that's currently visible in the view. This model is well-suited to people who tend to listen to whole albums of music in sequential order. The downsides to this model are that it becomes unclear what will play next if you navigate somewhere else, and it's hard to create a temporary curated list of music to play without creating an explicit saved playlist, which is a heavyweight interaction. For these reasons, music players which emphasize this style tend to eventually gain a "global playlist" feature anyway, even if they make it semi-hidden by default so that interacting with it is optional. ====== Elisa is a #1 music player, which explains why we periodically get complaints from people who want simpler, more lightweight methods of playing their music. I think implementing the proposal here would help a lot. You could then hide the global playlist and use the browse views exclusively, with a playlist of music being implicitly created, but hidden from view until you actually need it. -- You are receiving this mail because: You are watching all bug changes.
