std::runtime_errors thrown for incorrect settings

[Stefan-Olt]

Hello,
I wanted to use soapyMiri with gr-osmosdr, but I noticed one issue: gr-osmosdr sets the bandwidth to 3/4 of the sample rate by default, which causes soapyMiri to throw an exception. I could fix that by hard-coding a value, but wouldn't it better rather than throwing exceptions, just choose the closest allowed value?
Best regards,
Stefan

[ericek111]

Just to be sure, are you trying to use this driver through Soapy with gr-osmosdr?

I'm asking, because there used to be support for libmirisdr in gr-osmosdr, but they've removed it (it was broken anyway, fixed here if you're interested for some reason: https://gist.github.com/ericek111/4e59b94ecfc20a182c2bb1c3fab5fa42 ).

[nmaster2042]

I just made test with Gqrx SoapySDR support in gr-osmosdr, and I get same issue.

I already saw this one with other hardware.

It's because Gqrx doesn't automatically chose the correct BW.

If I enter BW corresponding by hand, I get device working.