SDR++ is a cross-platform and open source SDR software with the aim of being bloat free and simple to use.
#sdrpp
(libera.chat) NO LONGER ACTIVE, JOIN DISCORD INSTEADNightly builds contain the very latest features and bugfixes. They are usually just stable as normal releases but are available basically minutes to hours after a change has been pushed to the code.
You can download them here. It'll redirect you to the latest nightly on GitHub, scroll down to "Artifacts" and click on the version for your OS.
GitHub currently requires an account for the files to be downloadable so make sure you are logged in.
Download the latest release from the Releases page and extract to the directory of your choice.
To create a desktop shortcut, rightclick the exe and select Send to -> Desktop (create shortcut)
, then, rename the shortcut on the desktop to whatever you want.
Download the latest release from the Releases page and extract to the directory of your choice.
Then, use apt to install it:
sudo apt install path/to/the/sdrpp_debian_amd64.deb
IMPORTANT: You must install the drivers for your SDR. Follow instructions from your manufacturer as to how to do this on your particular distro.
Install from source following the instructions below.
WARNING: The sdrpp-git AUR package is no longer official, it is not recommended to use it.
There are currently no existing packages for other distributions, for these systems you'll have to build from source.
Download the app bundle from the latest nightly build
There are currently no BSD packages, refer to Building on Linux / BSD for instructions on building from source.
The preferred IDE is VS Code in order to have similar development experience across platforms and to build with CMake using the command line.
C:/Program Files/PothosSDR
)C:/Program Files (x86)/RtAudio/
)After this, install the following dependencies using vcpkg:
You are probably going to build in 64 bit so make sure vcpkg installs the correct versions using .\vcpkg.exe install <package>:x64-windows
IMPORTANT: Replace <vcpkg install directory>
with vcpkg's install directory.
mkdir build
cd build
cmake .. "-DCMAKE_TOOLCHAIN_FILE=<vcpkg install directory>/scripts/buildsystems/vcpkg.cmake" -G "Visual Studio 16 2019"
cmake --build . --config Release
./create_root.bat
This will create the root_dev
directory that will be used to save the configs of sdrpp and the modules.
You will next need to edit the root_dev/config.json
file to point to the modules that were built. If the file is missing in your folder run the application once and it will create one with default value -- see later on how to run the application.
From the top directory, you can simply run:
./build/Release/sdrpp.exe -r root_dev -c
Or, if you wish to run from the build directory e.g. build/Release
and adapt the relative path to the root_dev
folder:
./sdrpp.exe -r ../../root_dev -c
The optional -c
argument is for keeping the console active in order to see the error messages.
Because all the paths are relative, for the rest of the command line instructions we are going to assume you are running from the top directory using the former command.
As mentioned previously you need to edit root_dev/config.json
to add the modules that were built. From the default configuration file you need to add the paths in the modules
section. Add to this list all the modules you wish to use.
...
"modules": [
"./build/radio/Release/radio.dll",
"./build/recorder/Release/recorder.dll",
"./build/rtl_tcp_source/Release/rtl_tcp_source.dll",
"./build/audio_sink/Release/audio_sink.dll"
]
...
You also need to change the location of the resource and module directories, for development, I recommend:
...
"modulesDirectory": "root_dev/modules",
...
"resourcesDirectory": "root_dev/res",
...
Remember that these paths will be relative to the run directory.
If you choose to run SDR++ for development, you do not need this step.
First, copy over the exe and DLLs from build/Release/
to root_dev
.
Next you need to copy over all the modules that were compiled. To do so, copy the DLL file of the module (located in its build folder given below) to the root_dev/modules
directory and other DLLs (that do not have the exact name of the module) to the root_dev
directory.
The modules built will be some of the following (Repeat the instructions above for all you wish to use):
build/radio/Release/
build/recorder/Release/
build/rtl_tcp_source/Release/
build/spyserver_source/Release/
build/airspyhf_source/Release/
build/plutosdr_source/Release/
build/audio_sink/Release/
Depending on which module you want to build, you will need to install some additional dependencies. Please refer to the module list table further down in this readme for the names, dependencies and build options of each module.
The build options are then passed to the cmake command as such cmake .. -DOPTION_NAME_HERE=ON -DANOTHER_OPTION_HERE=OFF
etc...
Next install dependencies based on the modules you wish to build (See previous step)
Note: make sure you're using GCC 8 or later as older versions do not have std::filesystem
built-in.
replace <N>
with the number of threads you wish to use to build
mkdir build
cd build
cmake ..
make -j<N>
sh ./create_root.sh
If you wish to install SDR++, skip to the next step
First run SDR++ from the build directory to generate a default config file
./sdrpp -r ../root_dev/
Then, you will need to edit the root_dev/config.json
file to point to the modules that were built. Here is an example of what it should look like:
...
"modules": [
"./build/radio/radio.so",
"./build/recorder/recorder.so",
"./build/rtl_tcp_source/rtl_tcp_source.so",
"./build/audio_sink/audio_sink.so"
]
...
Note: You can generate this list automatically by running find . | grep '\.so' | sed 's/^/"/' | sed 's/$/",/' | sed '/sdrpp_core.so/d'
in the build directory.
You also need to change the location of the resource and module directories, for development, I recommend:
...
"modulesDirectory": "./root_dev/modules",
...
"resourcesDirectory": "./root_dev/res",
...
Remember that these paths will be relative to the run directory.
Of course, remember to add entries for all modules that were built and that you wish to use.
Next, from the top directory, you can simply run:
./build/sdrpp -r root_dev
Or, if you wish to run from the build directory, you will need to correct the directories in the config.json file, and then run:
./sdrpp -r ../root_dev
To install SDR++, run the following command in your build
folder:
sudo make install
Warning: This is not for the faint of heart and the instructions are mostly untested. It is recommended to use the nightly builds instead.
The dependencies are exactly the same as for linux, see that section for the core dependencies as well as the module list for the per-module dependencies. You will need to install the dependencies using Homebrew.
Make sure to install portaudio as it'll be needed later.
An example install command would be:
brew install libusb fftw glfw airspy airspyhf portaudio hackrf rtl-sdr libbladerf codec2 zstd
pip3 install mako
You will need to install volk from source. Follow the instructions on their repository. On M1 there are a few more manipulations needed.
You will need a few special cmake argument on top of the linux ones. You will need to enable the portaudio sink modules -DOPT_BUILD_PORTAUDIO_SINK=ON -DOPT_BUILD_NEW_PORTAUDIO_SINK=ON
and disable the usual rtaudio sink -DOPT_BUILD_AUDIO_SINK=OFF
as well as the option to tell SDR++ that it will run as a MacOS bundle -DUSE_BUNDLE_DEFAULTS=ON
. On MacOS versions older than Catalina (10.15), you will also need to use the internal std::filesystem as the OS can't provide it -DOPT_OVERRIDE_STD_FILESYSTEM=ON
.
Here is an example of build commands that will build almost all modules at the time of writing. You can always check the CI scripts for the latest arguments just in case but this should work. From the top of the SDRPlusPlus directory:
mkdir build
cd build
cmake .. -DOPT_BUILD_SOAPY_SOURCE=OFF -DOPT_BUILD_BLADERF_SOURCE=ON -DOPT_BUILD_AUDIO_SOURCE=OFF -DOPT_BUILD_AUDIO_SINK=OFF -DOPT_BUILD_PORTAUDIO_SINK=ON -DOPT_BUILD_NEW_PORTAUDIO_SINK=ON -DOPT_BUILD_M17_DECODER=ON -DUSE_BUNDLE_DEFAULTS=ON -DCMAKE_BUILD_TYPE=Release
make -j<N>
From the top of the SDRPlusPlus directory:
sh make_macos_bundle.sh ./build ./SDR++.app
This will create a SDR++.app
bundle that you can instal like any other MacOS app by dragging it into Applications.
Not all modules are built by default. I decided to disable the build of those with large libraries, libraries that can't be installed through the package manager (or pothos) and those that are still in beta. Modules in beta are still included in releases for the most part but not enabled in SDR++ (need to be instantiated).
Name | Stage | Dependencies | Option | Built by default | Built in Release | Enabled in SDR++ by default |
---|---|---|---|---|---|---|
airspy_source | Working | libairspy | OPT_BUILD_AIRSPY_SOURCE | ✅ | ✅ | ✅ |
airspyhf_source | Working | libairspyhf | OPT_BUILD_AIRSPYHF_SOURCE | ✅ | ✅ | ✅ |
audio_source | Working | rtaudio | OPT_BUILD_AUDIO_SOURCE | ✅ | ✅ | ✅ |
bladerf_source | Working | libbladeRF | OPT_BUILD_BLADERF_SOURCE | ⛔ | ✅ (not Debian Buster) | ✅ |
file_source | Working | - | OPT_BUILD_FILE_SOURCE | ✅ | ✅ | ✅ |
fobossdr_source | Working | libfobos | OPT_BUILD_FOBOSSDR_SOURCE | ✅ | ✅ | ✅ |
hackrf_source | Working | libhackrf | OPT_BUILD_HACKRF_SOURCE | ✅ | ✅ | ✅ |
harogic_source | Beta | htra_api | OPT_BUILD_HAROGIC_SOURCE | ⛔ | ⛔ | ✅ |
hermes_source | Beta | - | OPT_BUILD_HERMES_SOURCE | ✅ | ✅ | ✅ |
kcsdr_source | Unfinished | libkcsdr | OPT_BUILD_KCSDR_SOURCE | ⛔ | ⛔ | ⛔ |
limesdr_source | Working | liblimesuite | OPT_BUILD_LIMESDR_SOURCE | ⛔ | ✅ | ✅ |
network_source | Beta | - | OPT_BUILD_NETWORK_SOURCE | ✅ | ✅ | ✅ |
perseus_source | Beta | libperseus-sdr | OPT_BUILD_PERSEUS_SOURCE | ⛔ | ✅ | ✅ |
plutosdr_source | Working | libiio, libad9361 | OPT_BUILD_PLUTOSDR_SOURCE | ✅ | ✅ | ✅ |
rfnm_source | Beta | librfnm | OPT_BUILD_RFNM_SOURCE | ⛔ | ✅ | ✅ |
rfspace_source | Working | - | OPT_BUILD_RFSPACE_SOURCE | ✅ | ✅ | ✅ |
rtl_sdr_source | Working | librtlsdr | OPT_BUILD_RTL_SDR_SOURCE | ✅ | ✅ | ✅ |
rtl_tcp_source | Working | - | OPT_BUILD_RTL_TCP_SOURCE | ✅ | ✅ | ✅ |
sdrplay_source | Working | SDRplay API | OPT_BUILD_SDRPLAY_SOURCE | ⛔ | ✅ | ✅ |
sdrpp_server_source | Working | - | OPT_BUILD_SDRPP_SERVER_SOURCE | ✅ | ✅ | ✅ |
soapy_source | Deprecated | soapysdr | OPT_BUILD_SOAPY_SOURCE | ⛔ | ⛔ | ⛔ |
spectran_source | Unfinished | RTSA Suite | OPT_BUILD_SPECTRAN_SOURCE | ⛔ | ⛔ | ⛔ |
spectran_http_source | Beta | - | OPT_BUILD_SPECTRAN_HTTP_SOURCE | ✅ | ✅ | ✅ |
spyserver_source | Working | - | OPT_BUILD_SPYSERVER_SOURCE | ✅ | ✅ | ✅ |
usrp_source | Beta | libuhd | OPT_BUILD_USRP_SOURCE | ⛔ | ⛔ | ✅ |
Name | Stage | Dependencies | Option | Built by default | Built in Release | Enabled in SDR++ by default |
---|---|---|---|---|---|---|
android_audio_sink | Working | - | OPT_BUILD_ANDROID_AUDIO_SINK | ⛔ | ✅ | ✅ (Android only) |
audio_sink | Working | rtaudio | OPT_BUILD_AUDIO_SINK | ✅ | ✅ | ✅ |
network_sink | Working | - | OPT_BUILD_NETWORK_SINK | ✅ | ✅ | ✅ |
new_portaudio_sink | Working | portaudio | OPT_BUILD_NEW_PORTAUDIO_SINK | ⛔ | ✅ | ⛔ |
portaudio_sink | Working | portaudio | OPT_BUILD_PORTAUDIO_SINK | ⛔ | ✅ | ⛔ |
Name | Stage | Dependencies | Option | Built by default | Built in Release | Enabled in SDR++ by default |
---|---|---|---|---|---|---|
atv_decoder | Unfinished | - | OPT_BUILD_ATV_DECODER | ⛔ | ⛔ | ⛔ |
dab_decoder | Unfinished | - | OPT_BUILD_DAB_DECODER | ⛔ | ⛔ | ⛔ |
falcon9_decoder | Unfinished | ffplay | OPT_BUILD_FALCON9_DECODER | ⛔ | ⛔ | ⛔ |
kgsstv_decoder | Unfinished | - | OPT_BUILD_KGSSTV_DECODER | ⛔ | ⛔ | ⛔ |
m17_decoder | Working | - | OPT_BUILD_M17_DECODER | ⛔ | ✅ | ⛔ |
meteor_demodulator | Working | - | OPT_BUILD_METEOR_DEMODULATOR | ✅ | ✅ | ⛔ |
pager_decoder | Unfinished | - | OPT_BUILD_PAGER_DECODER | ⛔ | ⛔ | ⛔ |
radio | Working | - | OPT_BUILD_RADIO | ✅ | ✅ | ✅ |
weather_sat_decoder | Unfinished | - | OPT_BUILD_WEATHER_SAT_DECODER | ⛔ | ⛔ | ⛔ |
Name | Stage | Dependencies | Option | Built by default | Built in Release | Enabled in SDR++ by default |
---|---|---|---|---|---|---|
discord_integration | Working | - | OPT_BUILD_DISCORD_PRESENCE | ✅ | ✅ | ⛔ |
frequency_manager | Working | - | OPT_BUILD_FREQUENCY_MANAGER | ✅ | ✅ | ✅ |
iq_exporter | Working | - | OPT_BUILD_IQ_EXPORTER | ✅ | ✅ | ⛔ |
recorder | Working | - | OPT_BUILD_RECORDER | ✅ | ✅ | ✅ |
rigctl_client | Unfinished | - | OPT_BUILD_RIGCTL_CLIENT | ✅ | ✅ | ⛔ |
rigctl_server | Working | - | OPT_BUILD_RIGCTL_SERVER | ✅ | ✅ | ✅ |
scanner | Beta | - | OPT_BUILD_SCANNER | ✅ | ✅ | ⛔ |
scheduler | Unfinished | - | OPT_BUILD_SCHEDULER | ⛔ | ⛔ | ⛔ |
First, please make sure you're running the latest automated build. If your issue is linked to a bug it is likely that is has already been fixed in later releases
This is a bug in 1.0.0 that was fixed in 1.0.1
In some cases, if a crash happened while the config was being saved, the config file would be corrupted and SDR++ would refuse to start because of it.
This has now been fixed. If a config file is corrupted it'll just reset it to its default state.
You likely installed the soapysdr-module-all
package on Ubuntu/Debian. If not it's still a SoapySDR bug caused by multiple soapy modules coming in conflict. Uninstall anything related to SoapySDR then install soapysdr itself and only the soapy modules you actually need.
If the module was included in a later update, it's not enabled in the config. The easiest way to fix this is just to delete the config.json
file and let SDR++ recreate it (you will lose your setting relating to the main UI like VFO colors, zoom level and theme).
The best option however is to edit the config file to add an instance of the module you wish to have enabled (see the Module List).
This is a bug recently introduced by libusb1.4 To solve, this, simply downgrade to libusb1.3
If you also have the SoapySDR module enabled, this is a bug in libhackrf. It's caused by libhackrf not checking if it's already initialized.
The solution until a fixed libhackrf version is released is to disable the soapy_source module from SDR++. For this, go into the "Module Manager" menu and click the -
button next to the row with "soapy_source". After that, restart SDR++.
If you still have an issue, please open an issue about it or ask on the discord. I'll try to respond as quickly as I can. Please avoid trying to contact me on every platform imaginable thinking I'll respond faster though...
Feel free to submit band plans via the GitHub issue tracker. For code changes, please create a feature request instead.