Skip to content
ARGUS User Manual

Audio

Audio settings control how ARGUS uses your microphone and speakers for PTT, drone stream audio, and alerts. Most audio choices live inside Settings → App → Communications; this page documents every control end-to-end.

Input device

ARGUS uses the browser’s default input device unless you override it.

  • Microphone — the browser device picker is invoked the first time a PTT press is held. Your selection is saved per browser by the media layer; swap it in the browser’s site-permissions page or with the Change microphone control in the PTT drawer.
  • Noise suppression — relies on the browser’s built-in Chrome / Edge noise-suppression pass. It is on by default and follows the browser’s own toggle — there is no ARGUS-side override in the current build. Disable it in chrome://settings if your environment is quiet enough that the suppressor clips voice.
  • Auto-gain — same story: browser default, on by default. Override from the browser.

A mic privacy toggle lives in App settings → Communications:

  • Keep — the mic track stays open between PTT presses; lower latency on first push, some OSes keep the hardware LED lit.
  • Strict — the track is released on every PTT end; the LED turns off immediately but the next press has a short spin-up.

Output device

ARGUS plays every audio source — PTT RX, drone-stream audio, copilot alerts, F-18 master-caution — through the browser’s default output device. Override it by picking a different output in the browser or OS audio control panel; ARGUS follows.

A dedicated output-device picker inside the app is aspirational, to let operators route PTT to a headset and drone audio to a speaker without OS-level fiddling.

Audio ducking (aspirational)

Both ducking behaviours below are on the roadmap and not yet implemented. Today every source plays at full volume and the loudest wins.

  • PTT ducking — when incoming PTT audio arrives, drone-stream audio dims by a configurable percentage for the duration of the transmission, then fades back in. Keeps radio traffic intelligible without losing situational awareness on the video.
  • Alarm ducking — when a copilot alert or master caution fires, all other audio (PTT, drone stream, ambient) is pulled down so the alert is unmistakable. Alarm takes priority over PTT in the duck hierarchy.

Auto-transcription

Auto-transcribe in App settings → Communications routes completed PTT clips through the speech-to-text service. ON sends every release to transcription; OFF requires manual trigger. Transcribed text flows into chat attribution, media search, and the after-action report.

Bundled alert sounds

ARGUS ships five built-in sounds played by the sound service:

  • radio_tx / radio_rx — PTT start beeps.
  • radio_tx_end / radio_rx_end — PTT release beeps.
  • f18_master_caution — master-caution alert.

Per-event mute for these is part of the planned notifications panel and is not available today. Browser autoplay policies can block the first sound until the first user interaction on the page — this is a browser limitation, not an ARGUS setting.

Test mic and test speaker (aspirational)

Dedicated Test mic (live level meter) and Test speaker (plays a short beep) buttons are on the roadmap. Today the quickest way to verify audio is:

  1. Hold PTT in any operation — you should hear radio_tx, see your own avatar glow, and get a TX chip on your row in the Assets tile.
  2. Have a teammate hold PTT toward you — you should hear radio_rx and see their RX chip light up.

If you do not, check the browser’s site-permissions for the ARGUS domain (microphone, autoplay) before touching anything else.