Closed guruofquality closed 8 years ago
I would say we should go ahead and pull the async version to master; there's no downside in performance that I've found; the problems seem to have just evaporated.
The async work is now merged into master and I did some cleanup as well.
Excellent; thanks -- with this update it's much more stable on SoapyRemote than rtl_tcp.
rtl_tcp constantly crashed on my Pi with the slightest interruption, could barely handle 2Mhz and I was never able to re-load until I restarted the Pi..
Referencing this issue: https://github.com/pothosware/SoapyRemote/issues/9 I noticed that a FM demod demo was extremely choppy and causing audio underflows. This didnt happen with the RTL support from SoapyOsmo. I couldn't find anything obviously wrong with the use of the sync api or the conversion code.
So I switched to the async api on this branch and the problem went away: https://github.com/pothosware/SoapyRTLSDR/commits/async_stream
I suspect a bug in the sync API, and I wonder if anyone else is seeing a similar issue. Although the sync API is more fitting here, if its going to have issues, the async_stream branch needs some cleanup and can be merged.