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

# Troubleshoot the Audio Manager

> Fix common Audio Manager problems: the camera doesn't switch, switches on bleed, ping-pongs between presenters or never holds a 2-shot.

Each section starts from what you see in the studio. Start with the trigger list on the Audio triggers page: its status lights and alerts point at most of these causes. See [Watch triggers on air](https://docs.visualradioassist.live/audio-manager/during-a-show.md) for what each state means.

## The page says the Audio Manager is not installed or offline

**Audio Manager is not installed** means no Audio Manager has ever connected to this studio. Install and start it, see [Set up the Audio Manager](https://docs.visualradioassist.live/audio-manager/set-up.md).

**Audio Manager is offline** means the app was connected but stopped reporting. The alert shows the last contact. Make sure the app is running on the studio machine and the machine has a working network connection. The Audio Manager reconnects by itself when the connection is back. Changes you save while it is offline take effect once it reconnects.

## A trigger shows Unavailable

The audio device of the trigger is disconnected from the studio machine. Reconnect it. On Windows, the Audio Manager finds an unplugged Windows audio device again when it comes back. For an ASIO device, or when the trigger stays unavailable, click **Reload devices** at **Settings → Studio → Audio**. If the device got a new name or channel layout, pick the input again in the trigger.

## The camera doesn't switch when the presenter talks

* **The trigger is disabled.** Turn on **Enabled** in the trigger.
* **The threshold is too high.** Watch the meter while the presenter talks. [Calibrate](https://docs.visualradioassist.live/audio-manager/thresholds-and-calibration.md#calibrate-a-trigger) the trigger, or lower the threshold.
* **The input is gated.** For an input with **Post processing** off, the noise gate decides, not the threshold. Check its **Open** level.
* **A higher priority trigger is active.** Another mic that picks up sound keeps the camera. Check which row is **LIVE**.
* **The gating signal is off.** Audio switching is paused. Switch the toggle in the header back on.
* **Nothing matches.** The trigger has only commands with conditions and no **Default**. Add a command without conditions.
* **Camera Assist did not confirm the cut.** A cut to a camera angle that is not confirmed in time is cancelled and the studio goes to the fallback. Check the camera in [Cameras](https://docs.visualradioassist.live/cameras.md).

## The camera switches on bleed or background noise

A mic that hears another presenter, a monitor speaker or music fires its own trigger. The Audio Manager listens for speech, so music and hum fire less often. That does not solve bleed from another presenter's voice.

* Calibrate the trigger. If calibration warns that the gap is under 12 dB, level alone can't tell talk from bleed on this mic. Fix the gain staging at the console, or wire the channel to console tally.
* Make sure the trigger is not set to fire instantly: **Attack trigger** off, with an **Attack hold time** of around 500 ms.
* Check the **Trigger type**. A mic set to **Music** or **Programmed action tone** reacts to level alone.
* For an unprocessed mic, turn off **Post processing** and pick the right **Mic preset**.

## The camera ping-pongs between presenters

* Add a [trigger group](https://docs.visualradioassist.live/audio-manager/trigger-groups.md) for the mics that talk together, so a conversation cuts to a 2-shot.
* Raise the studio **Talk time**, or turn on **Talk time override** for the trigger that releases too fast.
* Tune the [Smart Director](https://docs.visualradioassist.live/audio-manager/studio-audio-settings.md#smart-director), like a higher **Anti-flip-flop guard**.

## A conversation never gets a 2-shot

The Smart Director only acts when the studio has trigger groups. Create a [trigger group](https://docs.visualradioassist.live/audio-manager/trigger-groups.md) with the triggers of the mics that talk together and give it a 2-shot as **Combo command**. A studio that moved from the previous Audio Manager starts without trigger groups.

## A command never plays

The editor marks it **This command will never play**. A command without conditions sits above it and always matches first. Move the conditional command higher.

## A trigger can't be saved

* **This angle no longer exists** - The camera angle was deleted. Pick a new angle.
* **Add new** is disabled - Your license limit for audio triggers is reached.
* For a trigger group, the editor names what is missing, like **Enter a group name to save** or **Add at least 2 triggers to save**.

## Still not working

Open the [activation history](https://docs.visualradioassist.live/audio-manager/during-a-show.md#look-back-in-the-activation-history) to see which trigger had the camera and when. Contact support with the studio name, the time of the problem and the triggers involved.

## Related

* [Thresholds and calibration](https://docs.visualradioassist.live/audio-manager/thresholds-and-calibration.md)
* [Audio triggers](https://docs.visualradioassist.live/audio-manager/audio-triggers.md)
* [Studio audio settings](https://docs.visualradioassist.live/audio-manager/studio-audio-settings.md)


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