Memory Usage
Currently radio-active depends on FFplay, an external media player for playback of the media streams. FFplay is a very simple and portable media player using the FFmpeg libraries and the SDL library
The developer is looking to remove that dependency in the future. In the meantime, when measuring memory usage of the program, we need to consider both the memory used by radio-active as well as FFplay.
Here’s a chart showing memory usage for radio-active.
We’ve included other popular software for streaming internet radio. We include both terminal and graphical software. As you can see, radio-active isn’t the lightest in terms of memory usage but it’s certainly no memory hog. As the software runs on the Raspberry Pi series of single-board computers where RAM can be a premium (on some models) it’ll be good to remove the dependency on FFplay.
Pages in this article:
Page 1 – Introduction / Installation
Page 2 – In Operation
Page 3 – Memory Usage
Page 4 – Summary
I have had little luck with radio apps, they seem to be static and crackle for me. I just use by web browser with streema or radiovolna.
There’s no luck involved with radio-active. Installation is very simple, and playback is without static or crackle.
Interesting.
The best source would actually be radio-browser where you can find and connect to streams to test them.
If they work in the browser, they’ll work in the application.
However, I’d go with pyradio – as it’s a far far more user friendly application than this radio.
The software uses that web directory for the stations so just search within the app.
I’ve never had any radio app have ‘static’ or ‘crackle’.
Quite enjoying this. Any way I can get Pulse to work with it for independent volume control?