TCP based SoapySDR remoting, no clever protocols, just a TCP/IP byte stream.
Note: currently developed and tested on Debian stable only.. ports welcome (see below!)
Because I've tried SoapyRemote, and it always has streaming errors due to network underrun/audio overrun,
which is daft when I have a solid 80Mbits/sec (10Mbytes/sec) from the source device to my laptop (measured
using a simple
I've also tried USB/IP, which is a total loss for anything faster than keyboards.
I've tried a network audio solution TRX, which looks good with RTP for networking, but sadly due to having to switch between user and kernel mode for every UDP packet at 500Hz+ thrashes my wee source device to kernel panic & death =(
By using the same approach as simple TCP/IP network protocols, use the capabilities of the underlying
TCP/IP stack which is reliable, efficiently and implemented in the kernel so I don't have problems
due to process/thread thrashing. Atop this, use
stdio to manage buffering and data segmentation
(less code for me to write), and finally, don't aim for stupid low latency, choose buffer sies that
provide ~250msecs delay, this again reduces thrashing on the source device (which is tiny =)).
You will need
Then it's the usual CMake incantations (on both source and target devices!):
cmake -B build
cmake --build build
cd build; make install
After which you should be able to check the driver is installed with
SoapySDRUtil --info and run
the server (on the device where your SDR is attached)
So it's not working first time? You can get significant details by setting the SoapySDR log level in the environment:
<VALUE>is one of:
ERROR, WARNING, NOTICE, INFO (def), DEBUG, TRACE
Feel free to raise issues for discussion or problems or features, better yet: submit PRs to fix my poor code please!