Hi Hans. After a pause of a few months, I decided to try the latest (8.40) version of the PI command line, used inside a script with piping in and out.
While, as expected, it didn't really work with a fully-loaded settings preset, i started switching functions off to see at what point it would run normally. But after I switched off all processing functions, I see that the stereotool process still eats between 35% and 100% of the RPI3 CPU. Activating even a couple of functions (AGC + multiband2) immediately raises CPU to > 120% and plays intermittently
I am running it on a Ubuntu 16.04 server installation on an PI 3.
Is there a reason why the command line version may be less efficient than the GUI version?
regards
Christo
|