> ## Documentation Index
> Fetch the complete documentation index at: https://docs.visualradioassist.live/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the names from the glossary at https://docs.visualradioassist.live/glossary: Audio Manager (two words), command (never commando), on air and off air (never live) for programs and studios, and server apps for the VRA apps installed in the studio.
> Say which app an answer applies to, like VRA Cloud, the Core or the Output Player, and the version when the page names one.
> Only give settings, values and steps that are in these docs. Never invent one. If the docs don't cover it, say so.
> When the docs don't answer the question, send the user to Visual Radio Assist support at https://cloud.visualradioassist.live/support.

# Watch triggers on air

> See which Audio Manager trigger has the camera during a show, meter every mic, pause audio switching and scrub back through 30 days of history.

During a show the **Audio triggers** page tells you which mic has the camera and why the picture is where it is. You don't need to change anything here to run a show. This page explains what you see.

## The trigger list during a show

Each trigger is a row with a status light. The light turns red while the trigger is on air.

* **LIVE** - The trigger is active and has the camera. A red bar runs across the top of its editor.
* **UNAVAILABLE** - The audio device of this trigger is disconnected. The trigger can't fire.
* **DISABLED** - The trigger is turned off. The row is dimmed.

Rows also show the angle the trigger cuts to, the device and channel it listens to, and badges for settings that change how it behaves: **P80** for a priority other than 50, **Pre-shot**, and **Alt 3** for three alternative angles.

At the bottom of the list, **Fallback active** shows while the studio [fallback](https://docs.visualradioassist.live/audio-manager/fallback.md) is on air.

## Meter every mic

Switch the header to **Live metering** to see every trigger as a channel strip:

* A meter from -96 to +12 dB, green up to -18, yellow up to -6, red above. A held peak marks the loudest moment and a clip light shows at -0.5 dB.
* The threshold as a fader on the meter, see [Thresholds and calibration](https://docs.visualradioassist.live/audio-manager/thresholds-and-calibration.md#adjust-thresholds-from-the-metering-view).
* **Voice**, an indicator that the mic hears a voice, and **Floor**, the measured background of the mic.
* The angle the trigger cuts to.

Trigger groups show as their own strip, with a bar per member.

## Pause audio switching

When the studio has a [gating signal](https://docs.visualradioassist.live/audio-manager/studio-audio-settings.md#gating-signal), its toggle sits in the header of the Audio triggers page. Switch it off to stop audio switching, for example for a moment where the director takes the cameras by hand. The fallback keeps running. Switch it back on to hand control back to the Audio Manager.

## Recent activity

With no trigger selected, the right side shows **Activity**: the latest activations on a timeline. Use the zoom to show 10 to 60 minutes, and **Full history** to open the activation history.

An open trigger also lists its own last 10 activations, each with how long it was on air.

## Look back in the activation history

**Audio Manager → History** shows which mic held the floor over the last 30 days, on a timeline you can scrub.

* Move by hour with **Earlier** and **Later**, jump to a date with the date picker, or go back to **Now**.
* Filter on **Triggers** and **Types**.
* Zoom from 10 to 60 minutes.
* Switch between **Vertical (lanes)** and **Horizontal (per trigger)**.

A lane is a mic, not a person. The history records which trigger was active, when it started and when it released. It does not record why a camera was chosen.

## Related

* [Audio triggers](https://docs.visualradioassist.live/audio-manager/audio-triggers.md)
* [Troubleshoot the Audio Manager](https://docs.visualradioassist.live/audio-manager/troubleshooting.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.