It is far from perfect, but I spend some time since some aspects was old or missed.
Also started to get down some thoughts of how Pmusic actually works.
This could be a lot more...How does it work?
It is no secret that Pmusic acts slower than many players. This because it is built of slow libraries (Bash, ffmpeg and gtkdialog). This gives some challenges when it comes to gui solutions and speed. One thing to mention is that Pmusic is strictly playlist-based, which means you can only play a song added to playlist. You can not start a song from ie. the 'Music-Source' field, bookmarks or from the album list in 'Track-info'. The song must be added to the playlist before played.
Keeping us strictly to the playlist-based model, we can manage huge music-collection in a snappy way. As there are many options combined to the slower playlist, the Music-Source list is simple and fast. Here you can render 20000 items in a blink of an eye. The best workflow is therefor to do as much as possible in the Music-Source list.
In contrast to many new players that focus on audio-streaming and the cloud, Pmusic offers options to build up you local collection. This includes storing lyrics and albumart found on the web, as well as grabbing tracks from your favorite radio-stations.
Pmusic offers a wide range of track info for the playing song. By default this info is not built in the main gui as known in other great players. One of the main targets of Pmusic is to be an easy player, and many (most?) users want the player to ... yepp... play. The track info is therefor separated from the rest in an unique module. Still easy reachable, - only one click away. Also, the track info module can be embedded into the main gui as done in the 'Wings' frontend.
any thoughts?
Sigmund