
A cross-platform java application for decoding, monitoring, recording and streaming trunked mobile and related radio protocols using Software Defined Radios (SDR). Website:
A cross-platform java application for decoding, monitoring, recording and streaming trunked mobile and related radio protocols using Software Defined Radios (SDR).
📖 Read the sdrtrunk User Manual
New to sdrtrunk? Start with the Getting Started guide, then use the User Manual and How-To Guides to set up tuners, playlists, aliases and streaming.
Figure 1: sdrtrunk decoding a P25 Phase 1 simulcast trunked radio system
All release versions of sdrtrunk are available from the releases tab.
The nightly release contains current builds of the software for all supported operating systems. This version of the software may contain bugs and may not run correctly. However, it let's you preview the most recent changes and fixes before the next software release. Always backup your playlist(s) before you use the nightly builds. Note: the nightly release is updated each time code changes are committed to the code base, so it's not really 'nightly' as much as it is 'current'.
Releases are built and published automatically by the Release GitHub workflow whenever a version tag is pushed to the repository.
The version is taken from the tag, so there is no version number to update in the code. Create and push a tag
with a leading v, following the naming convention described in gradle.properties (e.g. v0.6.2-alpha-1,
v0.6.2-beta-1 or v0.6.2):
git tag v0.6.2-beta-1
git push origin v0.6.2-beta-1
Builds made from an untagged commit get a version like 0.6.2-beta-1-14-g4626d567 (14 commits after the
v0.6.2-beta-1 tag, at commit 4626d567), with -dirty appended when there are uncommitted changes.
The workflow then:
Version <version> with auto-generated release notes (a "What's Changed" list of
the PRs merged since the previous version tag), and attaches the six zip
files plus a SHA256SUMS checksum file.If the workflow fails part way through, fix the problem and re-run it from the Actions tab. It resumes from the draft release left behind. It won't modify a release that has already been published. To rebuild a published release, delete the release and the tag on GitHub, then push the tag again.