denny 6dc1f0fdcb #2742 Calls View with database support
Tab page size preference (50, 100, 250, 500; default 500) next to the paging controls.
Calls tab call type search filter.
- Type filter (group, patch, private, telephone, other) in the Calls search bar, applied when selected.
- CallType provides the SQL condition on the stored identifier forms, using the same rules as the Type column.
#2742 Calls tab default column order puts protocol, system, site and channel at the end.
#2742 Call type test.
#2742 Calls tab shows the call type: group, patch, private or telephone.
- CallType is derived from the stored TO and FROM identifier forms, so existing calls have a type without a schema
  change.  Telephone interconnect calls (telephone number TO or FROM) show as Telephone.
- Calls tab: Type column.
#2742 Patch group calls store their patched talkgroups so a talkgroup search finds the calls it was patched into.
- Schema version 2 adds the patched_talkgroups table (call id, talkgroup, fully qualified address), deleted with
  the call.  Existing version 1 databases are upgraded automatically at startup.
- The call manager captures the patched talkgroups (they can change during the call); transfers copy them.
- TO searches by talkgroup value or talkgroup alias match the patch group and its patched talkgroups, in the
  database and for live calls.
- Calls tab: Patched column lists the patched talkgroups with their current aliases.
#2742 Calls tab replays recordings through the audio channels.
- Replay uses the sdrtrunk audio output and channels instead of a separate JavaFX media player: an idle channel
  (left first), otherwise the left (or mono) channel, which drops the live call it is playing.  Live calls aren't
  assigned to a replaying channel and queued calls play after the replay.
- RecordingReader decodes MP3 (LAME decoder; MPEG-2/2.5 frame size fix) and WAVE recordings to 8 kHz audio.
- ReplaySource supports pause, seek and stop; the Calls player keeps its controls and auto-play next.
- Playback events and the Calls tab Playing column show replays (history icon); the audio panel shows REPLAY.
- Playing row channel edge is drawn as a background layer so the row's cells stay aligned with other rows.
- HikariCP and MariaDB driver logging limited to INFO.
- javafx.media removed from the runtime image modules.
#2742 Calls tab shows which calls are playing on each audio channel.
- Audio segments have a unique id, which the call manager uses as the call key.
- Audio channels report the call they start and stop playing; the audio playback manager publishes these as
  ChannelPlayback events (re-wired when the output device changes) with a snapshot for late listeners.
- Calls tab: Playing column with a LEFT/RIGHT/MONO chip and a channel-colored row tint and edge for calls that are
  playing.  Calls reloaded from the database keep their call key so a call that ended but is still playing stays
  marked.
- Audio panel channel tags use the same colors (left/mono blue, right orange).
#2742 Replace AudioRecordingManager with CallManager and CallRecorder.
- CallManager (new call package) is the single audio segment listener for calls.  It manages each call's
  life-cycle: creates and updates the call record, saves it to the call database and broadcasts it to call
  listeners (Calls tab, future external subscribers).
- CallRecorder (record package) holds the streaming recording logic and file naming.  The call manager creates one
  CallRecorder.Recording per call, which fills in the recording details of the call record.
- DatabaseManager remains storage only.  No behavior change.
#2742 Record all calls by default; delete duplicate and Do Not Monitor calls after a retention period.
- Record preferences: 'Record all calls' (default on).  When off, only calls with an alias record option are
  recorded, as before.
- Duplicate calls are no longer discarded immediately.  Duplicate calls, and Do Not Monitor calls that no alias marked
  for recording, are deleted with their recordings after a configurable retention period (30 minutes to 7 days, or
  never; default 1 hour) set in the Call Database preferences.  Calls store whether an alias requested recording.
- The duplicate call 'Recording' suppression switch is replaced by a note pointing to the retention setting.
- Age-off runs every 5 minutes.
#2742 Calls store the alias list name and look up TO/FROM aliases from the current alias list.
- The calls table no longer stores TO/FROM alias names.  It stores the alias list name, the TO/FROM identifier
  forms and the fully qualified (roaming) addresses, and the Calls tab looks up the aliases in the current alias
  list when it displays a call, so historical calls show the latest alias values.
- AliasList lookups by protocol, value and fully qualified address, sharing the identifier matching rules.
- TO and FROM search fields drop down a filtering list of talkgroup or radio aliases.  Selecting an alias filters by
  the alias's alias list and its talkgroup/radio values, ranges and fully qualified identifiers.  Typed text still
  matches the identifier.  The alias search field is replaced by a talker alias search.
#2742 Call database, Calls tab, call audio age-off and talkgroup hold.
- Call database: built-in H2 (application 'db' folder) by default, with optional MariaDB or PostgreSQL.  The
  sdrtrunk schema and tables are installed and versioned automatically.  Engine differences are isolated in
  IDatabaseDialect implementations and call storage behind ICallRepository.
- Switching databases asks whether to transfer the existing calls and, when the target schema already has
  sdrtrunk calls, whether to append, clear, or create a separately named schema.
- Every call gets a database row when it starts, updated as identifiers change and when the call completes.
- Call recordings are written while the call is in progress (streaming MP3/WAVE), so the recording file and its
  name are stored with the call from the start.  MP3 ID3 metadata is rewritten in reserved space at the end.
- Calls tab after Now Playing: search by talkgroup, radio, alias, protocol, system and date range, live
  duration of calls in progress, built-in recording player with auto-play, context menu to hold a talkgroup.
- Call Database preferences: database selection, test connection, and age-off rules (age and total size),
  each deleting the call and recording or only the recording.  The status bar recordings meter uses the size
  rule limit when enabled.
- Talkgroup hold: Hold button on each audio channel steers the held talkgroup (and patch groups that include
  it) to that channel, keeps other calls off it, plays it even when do-not-monitor, with an optional idle
  auto-release in Playback preferences.
2026-11-21 07:48:36 -05:00
2017-08-28 19:51:13 -04:00

Gradle Build Nightly Release Latest Release Downloads License Discord support-google_groups-blue

sdrtrunk

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.

sdrtrunk primary application window decoding a P25 trunked radio system Figure 1: sdrtrunk decoding a P25 Phase 1 simulcast trunked radio system

Download the Latest Release

All release versions of sdrtrunk are available from the releases tab.

  • (alpha) These versions are under development feature previews and likely to contain bugs and unexpected behavior.
  • (beta) These versions are currently being tested for bugs and functionality prior to final release.
  • (final) These versions have been tested and are the current release version.

Download Nightly Software Build

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'.

Minimum System Requirements

  • Operating System: Windows (32 or 64-bit), Linux (32 or 64-bit) or Mac (64-bit, 12.x or higher)
  • CPU: 4-core
  • RAM: 8GB or more (preferred). Depending on usage, 4GB may be sufficient.

Creating a Release (Maintainers)

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:

  • Verifies that the version the build derives from git matches the tag and fails if it does not.
  • Builds and tests the code, then creates the release zips for Linux, Mac and Windows (x86-64 and aarch64).
  • Creates a GitHub release titled 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.
  • Marks tags containing a dash (alpha and beta versions) as pre-releases. Tags without a dash become full releases.

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.

Description
No description provided
Readme GPL-3.0 50 MiB
NXDN-625 Latest
2026-06-25 09:56:10 -04:00
Languages
Java 99.7%
CSS 0.3%