peterbmarks
commented
1 year ago I think I'm seeing the same thing but it makes the miri soapy driver unusable in clients including CubicSDR. Here's what SoapySDRUtil shows just loading before even receiving:
SoapySDRUtil --make=driver=miri ######################################################
Soapy SDR -- the SDR abstraction library
######################################################
Make device driver=miri Using device #0: Mirics MSi2500 default (e.g. VTX3D card) driver=miri hardware=miri _mirisdr_alloc_async_buffers Lost samples! 82 01 00 00 00 90 00 00 40 7e 22 fb 0e fc db 4f Lost samples! Lost samples! OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOLost samples!
I have a couple of clone sdrplay devices which I have been testing. I have noticed a few things with this driver verses the sdrplay driver. With a USB2 connection it works with both drivers, however, the soapymiri driver seems to lose samples, where as, the sdrplay driver does not. Plugged into a usb3 port things are better, this driver might lose a couple of samples when it starts the stream but then comes good. I changed cables etc to try and isolate what is going on. Im using CubicSDR as my reference app.