Seify
Rust SDR hardware abstraction for applications that want one API over multiple radio backends.
What Seify Provides
A clear path towards a great Rust SDR driver ecosystem.
- One API for probing, opening, configuring, and streaming from SDR devices.
- Typed devices when an application wants a concrete backend.
- Type-erased devices when an application wants runtime driver selection.
- Capability-oriented channel APIs, so backends expose the controls they support.
- Feature-gated drivers, so each binary only includes the SDR backends it needs.
- SoapySDR support for broad hardware coverage and native Rust drivers where available.
The native Rust drivers are still experimental. For production use and the widest set of stable hardware integrations, prefer the SoapySDR backend.
Features
The default feature set is soapy.
Enable drivers explicitly in Cargo.toml or on the command line:
Available features:
| Feature | Driver argument | Notes |
|---|---|---|
dummy |
driver=dummy |
Driver for unit tests. |
soapy |
driver=soapy |
SoapySDR backend. Enabled by default. Requires SoapySDR system libraries. |
aaronia_http |
driver=aaronia_http |
Aaronia HTTP backend. |
bladerf1 |
driver=bladerf |
bladeRF 1 backend. |
hackrfone |
driver=hackrfone |
HackRF One backend. |
hydrasdr |
driver=hydrasdr |
HydraSDR backend. |
rtlsdr |
driver=rtlsdr |
RTL-SDR backend. |
Use the generic API with an argument string to select a backend at runtime:
Additional driver-specific arguments can be passed in the same string:
Example
use Complex32;
use DynDevice;