that's kind of interesting, because if it works on a PC, I'd say it's a performance issue; if you don't see aU (audio underruns) or some osmosdr warnings, then I'd say it's not.
What one does in this situation is both running a process-based cpu usage tool; I recommend "htop" (which is like top, but actually a lot nicer). Do you have another process suddenly consume CPU? Does it look like it's pulseaudio (that would be the implicit audio resampling issue)?
If, what I presume, you only see two python processes consuming 100% each, you will need to dig deeper. There's a tool called "perf" , which, when run as "perf top" as root will let you introspect CPU usage per method, including kernel routines.
Both perf and htop are available as packets for many Linux distributions.
On 01/16/2015 09:27 AM, Andreas Ladanyi wrote:
Yes, i tested this project with the same RTL stick on an "old" dual-core (actually i dont know the exact CPU parameters) notebook and it works perfectly. If i start the project from the console via "python2.7 file.py" i get no warnings.
you never need a throttle block when you have hardware that
limits/defines your real-world sampling rate; in your case, it's your RF
hardware and your sound card.
Aside from things like implicit resampling in the audio card driver
infrastructure, it's absolutely possible that your bananapi is simply
not performant enough to do GUI, signal processing and audio playback at
The question is: Does the same application work sufficiently well on a
fast PC? Do you see any over- or underrun warnings on your console?