Probably I’ll develop as a plug-in as I
have the radio interface available. Once working I could
then make it a standalone program but that’s quite a lot of
One reason for DAB+ is I then have the
classes available for future work, also I can listen to Jazz
FM (UK) and also play DAB+ when we get good Tropo.
Currently using a nice 100 to 600MHz log
periodic, am only ~8 km from the transmitter.
could you include that in console?? or will it be an extra
app like qt dab?!?
QT-DAB does work, drives the Airspy
correctly. My birthday present from me to me in October
will be my own DAB+ receiver app 😊
look for qt dab ... soft from jan
lots of hardware included (rtl dongle, sdrplay, lime,
pluto etc etc) ... he even works on receive via dab and
retransmit on analog fm stereo (if you use a pluto) ...
then you can receive your favourite dab station on any
normal fm radio in your house (retransmitting not finished
jan is now on holiday but will be back in a few weeks
(mid of july?!?)
greetz sigi dg9bfc
Am 30.06.2021 um 10:18 schrieb Simon
I’m just running the Windows kit,
haven’t built it or even looked at the code.
Simon Brown, G4ELI
[Edited Message Follows]
On Wed, Jun 30, 2021 at 08:22 AM, Simon Brown wrote:
Welle.io is not bad but uses a lot of CPU and I don’t
think it drives my Airspy R2 correctly.
It depends. If it is built to use FFTW, then yes. The
CPU-load in my case is around 17%.
But if I build Welle-IO
using Kiss-FFT and
compiled using fast-calls
the CPU drops to only
Edit: the Airspy problem
is proably related to how Welle-IO
handles SoapySDR. Not
very good IMHO.