Gonzalo José Carracedo Carballal

I agree that for some scenarios having the main LCD show the demod frequency makes sense. Still, there are several reasons why I'd like to keep the current display: 1....

Indeed, that's the expected behavior. Profiles are just a way to store source configurations that are used frequently. That configuration should be saved in and restored from `~/.suscan/config/uiconfig.xml`. If it's...

I experienced that as well. Probably a LimeSDR Mini bug: the device is rejecting 20 Msps and for some reason falls back to 100 Ksps (only happens with LimeSDR mini...

CubicSDR also reports problem with this module https://github.com/cjcliffe/CubicSDR/issues/716

Just looked into it, and I don't think it will help. Their problem was related to a streaming sample rate setting, while ours has to do with an improper sample...

I've just made a little experiment. SoapySDR's Lime module reports only 2 allowed sample rates (100ksps and 65 Msps). If this is right, LimeSDR Mini would be unusable for streaming...

I think the best approach here will be to keep the supported sample rate list in the device object and for SDR devices to provide a combo box (keeping the...

I have just added the aforementioned combobox. Pull from the following branches: * sigutils: feature/performance-improvements * suscan: feature/performance-improvements * SuWidgets: feature/ux-improvements * SigDigger: feature/ux-improvements Compile and tell me what you...

The true reason is that, for some SDRs, forcing a value that is not theoretically supported, makes it deliver samples at some random rate while reporting an absolutely different rate,...

I totally agree with you. The problem is that the user is going to see something broken that I can't / don't want to fix. The only thing I can...