--
You received this message because you are subscribed to the Google Groups "ka9q-radio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ka9q-radio+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ka9q-radio/CADO0QiYikbMyTTt%3DoknCxDwYFwHT7B4GtdRP9tiz_1O9CtfGgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Weird. I'm traveling and will look at it when I can. It's running
on my Pi-5.
That's what I'd suggest. A mismatched #if/#endif would show up
quickly during compilation anywhere if it were real.
Hi Rob,
i try to install it this weekend.
What OS do you like to have on the pi5? Raspian without GUI?
thanks, Holger
Well, technically you *can* run other software on the Pi5 at the same time, but there's little resources left. In particular, if you use a lot of memory you will probably worsen the cache hit ratios badly enough for the FFT threads inside ka9q-radio that they will no longer run in real time. This can also happen if you run ka9q-web (locally or on another system) with the default spectral option of "zoom all the way out". This causes the spectrum pseudo-demod thread inside ka9q-radio to calculate power levels for every one of 32.4 million complex FFT bins, and that cache contention also keeps the FFT threads from running in real time.
Although the Pi is a nifty little computer, it should not be seen as a CPU engine but as something best suited for embedded applications. ka9q-radio runs best on x86-64 systems with enough cycles (and cache) to provide a good margin for its real time operations.
Phil
To view this discussion on the web visit https://groups.google.com/d/msgid/ka9q-radio/fc7049e4-6e7c-4b8a-a380-3f872f309f00n%40googlegroups.com.