Image of small orchestra

PQMusic – minimalistic audio player

Memory Usage

The chart below shows memory usage for a whole gamut of open source music players.

Memory usage chart for a wide range of open source music players including PQMusic

Remember that some of the music players are terminal based. We’re showing terminal and graphical players.

Compared to other players, it’s fair to conclude that PQMusic is a lean graphical music player. That’s one of the many virtues of writing software in Python rather than using bloated frameworks such as Electron.

Next page: Page 4 – Summary

Pages in this article:
Page 1 – Introduction / Installation
Page 2 – In Operation
Page 3 – Memory Usage
Page 4 – Summary

Notify of

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Newest Most Voted
Inline Feedbacks
View all comments
Deepak Chopra
Deepak Chopra
1 year ago

Thanks, I like DeaDBeeF

1 year ago

Much software development seems to be fairly pointless.
We have small players already. DeaDBeeF plays anything, Audacious is nicer on KDE, QMMP is cute, Strawberry is great for opening a folder> opens in new playlist… and many others.

We have amazing features – looking at Guayadeque, which is now dying – but which has the MOST convenient Lyrics (autosearch, click to search, click to open search in browser – copy paste and save text to the track), as well as a superb playlists functionality, superb filtering and Smartplay, and many features lacking in most new players.

Why aren’t NEW players interested to bring forward the best functions? Maybe New developers are just too lazy to research before they design…

1 year ago
Reply to  Ben

Ben, you make some interesting points. Linux is very strong in some areas (such as music players) and yet very weak in many other software genres. Points to bear in mind:

– Open source developers have no obligation to include things like filtering and smartplay or other features some people deem important. Many projects start out with a developer wanting a music player that meets their needs, which obviously won’t necessarily accord with others.
– Define best functions? Someone may want gapless playback or refined playlists, someone else wants things like an equalizer. Adding everything under the sun is likely to result in a bloated program with tons of bugs. It’s much harder to maintain complex software particularly for a sole developer.
– Some features are harder to code than others. Many open source developers are coding in their spare time, they are going to focus on what is important to them
– Some developers take donations, they may be willing to add features that some users want if there’s a financial incentive to do so. Unfortunately, so many people leech, never helping financially with any open source project (or even in some other way). When you look at a project’s GitHub many music players code is written almost exclusively by a single person.
– A developer writes a program for different reasons e.g. they may write a music player to help them learn a new language or toolkit.
– You say Guayadeque is dying. I’ve never tried that one. Assuming it’s open source, there’s nothing to stop anyone from forking the project and carrying on with the project.