Local recordings

Local recordings are an optional desktop-app feature. They are off by default and unavailable in the browser console. Follow your community’s recording policy and obtain any required authorization or consent before enabling them.

​

Choose a recording mode

Open Help → Desktop App settings… and choose either or both: Set Maximum storage (MB) and Retention (days), then select Save recording settings. The two modes work independently.

​

Record a session

1. Enable Allow session recording (start manually) and save the setting.
2. Select ● REC session in the toolbar, or Start session in Help → Local recordings….
3. Check the recording status for confirmation or an error.
4. Select ■ Stop REC or Stop and save session when finished.
5. Open the local recordings library to play the completed session.

Sessions include silence between transmissions and stop at a maximum of 8 hours. A stopped or interrupted session does not automatically resume on the next sign-in or launch.

​

Replay a transmission

Open Help → Local recordings… to review completed clips and sessions. Select Play and use the playback controls to pause or resume. Reload refreshes the library; an active file may not appear until it finishes. When a transmission in the activity log has a matching local clip, its row also has Play/Pause controls. A transmission split into several clips can have separate numbered play buttons. Completed clips without a matching event appear as Recorded RX or Recorded TX entries. Full sessions are available only in the library. Starting a new transmission stops local replay. Starting replay also ends an active transmission; do not use playback while holding PTT for live traffic.

​

Delete recordings

• Use a recording’s Delete… control to delete that completed item after confirmation.
• Use Delete all recordings… to stop an active session and remove managed recordings for the current console address’s origin.
• Clearing the activity log is not deletion: use the library to remove the audio files.

​

Storage and retention

Old completed recordings can be removed early to stay within storage/count limits. Retention is not a guarantee that a file will remain for the full number of days. Playing and active files can leave too little room for new capture; check any storage error rather than assuming recording continues. Running clips and a session at the same time can save the same traffic twice and use more space.

​

What is saved and who can access it

The app saves accepted radio audio received by this console and its own granted transmit audio. It does not record all server channels, unrelated microphone input, other applications, system audio, or traffic missed while closed or offline. A local TX clip is not proof that another user received the transmission. Files stay on the computer and are not uploaded to a server recording archive by this feature. Different dispatch logins using the same OS profile and console origin share that recording storage. Logging out stops capture but does not delete completed files or reset your opt-in preferences. Treat saved audio as sensitive local data. It is not encrypted or tamper-proof evidence storage. Protect the computer and follow your community’s rules for retention and sharing.

​

If recording reports an error

Read the status in app settings or the library. A skipped-chunk warning means some audio was dropped; it does not necessarily mean capture stopped. A disk, quota, timing, or capture error can stop recording early. Update the desktop app, check storage and the selected modes, and verify a short test recording. Interrupted recordings may be recovered on reopening, but crashes or power loss can lose queued audio. Report repeated errors to staff with the exact message and app version, without sharing sensitive recordings publicly.