jcoles

Yes. I might have moved too early on this. In Ollie's github repo (following the link from SourceForge), it shows the latest commit was 8 months ago! Your code gives me the same errors, such as "invalid use of incomplete type ‘class CPaOut’". So something has changed. I'll wait for the dust to settle. I'm not a pro developer. I may be doing something wrong. It would be helpful if the readme could include up-to-date building instructions. Thanks.

Have the dependencies or build instructions changed for your code at https://github.com/Drm-tools/dream ? The qmake then make process that worked for r1548 from SourceForge now produces errors regarding src/sound/drm_portaudio.cpp .

Since I have Hamlib 4.5.5, I restored the 'const' where PrintHamlibModelList is defined. Let's be more specific. Code is precise. People would need to know exact changes to specific lines in specific files. I have worked out the following required changes: change src/util/Hamlib.cpp line 344 CHamlib::PrintHamlibModelList(struct rig_caps *caps, void *data) to CHamlib::PrintHamlibModelList(const struct rig_caps *caps, void *data) change src/util/Hamlib.h line 116 static int PrintHamlibModelList(struct...

Since I have Hamlib 4.5.5, I restored the 'const' where PrintHamlibModelList is defined. Can you please be more specific. Code is precise. People would need to know exact changes to specific lines in specific files. Thanks.

How do you get GQRX and Dream connected to the AirspyHF at the same time? Or, are you just piping the output from GRQX to Dream?

How do you get GQRX and Dream connected to the AirspyHF at the same time? Or, are you just piping the output from GRQX to AirspyHF?

It's interesting that SoapySDR devices like my AirspyHF can be accessed as the signal input, but I see no way to actually tune the SDR from Dream. How can I use this?

I don't understand. You're referring me to a posting from February that mentions the exact problem that I have. There's no solution there that I can see. Has Dream 2.2 been stuttering since February? It's unusable with the stuttering. Why even put it up? It seemed to have stopped. When? Yesterday's build fixed the Input Spectrum and Input PSD plots, but the stuttering remains. By the way, it's confusing that your updated files on SourceForge have the same name as previously. Why not add a numeric...