Summary
We’re really glad we took a gander at Resonance despite it’s fledgling status. This music player has many delightful touches particularly with its sleek UI. And we think that deliberately excluding tag editing is a good idea. Too many music players get bloated with features that are better served by other types of software.
In our opinion, this music player shows lots of promise. We’ll definitely keep abreast of new releases and will publish an updated review when there’s substantive news to report.
As things stand, Resonance is a massive memory hog. With a small collection of albums loaded, memory usage was reported by the ps_mem utility as a whopping 1.2GB of RAM. That’s the largest memory footprint we’ve seen from a music player. Things get really dire when loading a large collection of music. ps_mem then reports memory usage as 9.1GB of RAM. Do you need evidence? Here it is!
Even Firefox with lots of tabs open looks lean in comparison.
If the memory footprint and the lack of gapless playback can be addressed, we might even start using Resonance regularly.
Website: github.com/nate-xyz/resonance
Support:
Developer: Nathanael
License: GNU General Public License v3.0
Resonance is written mainly in Rust with a splash of Python. Learn Rust with our recommended free books and free tutorials. Learn Python with our recommended free books and free tutorials.
Pages in this article:
Page 1 – Introduction / Installation
Page 2 – In Operation
Page 3 – Summary
I installed Resonance just to verify its memory usage. I got the same. Never seen a music player use 8GB of RAM before!