FAQ
VoluBridge full FAQ
A detailed reference for setup, latency behavior, supported outputs, trial limits, and license terms.
Basics
Basics
What does VoluBridge do?
VoluBridge provides a controllable virtual output and low-latency bridge for HDMI displays, DisplayPort monitors, USB DACs, and other Mac outputs where the standard macOS volume keys may not work as expected.
Why does it need a driver?
VoluBridge needs a CoreAudio virtual driver so macOS can see it as a volume-controllable output and so audio can be bridged to the real external device.
Does the app need to stay open for audio to work?
The core audio bridge runs at the CoreAudio driver level. After setup, everyday audio output does not require keeping VoluBridge.app open. The app is the management screen for output selection, EQ, VU meters, FFT display, RT diagnostics, and driver tools.
Which outputs are supported?
VoluBridge is intended for outputs recognized by macOS, including HDMI, DisplayPort, USB DACs, and built-in audio. Behavior can vary by device and connection path, so the 14-day trial is the best way to check your own setup.
Audio / Latency
Audio and latency
Is latency really zero?
It does not mean physical device or OS scheduling latency disappears. VoluBridge is designed so the virtual path does not add meaningful extra waiting time compared with direct hardware output.
Why use timestamp sync instead of FIFO buffering?
In a FIFO model, increasing buffer stock for stability moves playback farther away from the current sound, so added latency depends on the amount of queued audio. VoluBridgeRT aligns Producer schedule and Render output time around a fixed target.
Will sound drift later during long sessions?
VoluBridge is not designed as a simple FIFO path that stores audio in order and plays it back later. It passes audio to the physical device according to the output timeline, avoiding a structure where delay builds up over time. Actual behavior depends on the output device and setup, but the goal is external audio that remains natural during long sessions.
How is it different from typical virtual audio?
Typical virtual audio often receives audio from apps, stores it in a buffer, and sends it onward in order. VoluBridge is built for everyday external output, prioritizing a bridge that follows physical-output timing without stockpiling a large audio queue.
Does VoluBridge change sound quality?
With Optimizer off, VoluBridge can be used without intentional sound shaping. With Optimizer on, EQ, presets, and SoftClipper can adjust the output for monitors, headphones, meetings, or daily listening.
Can noise occur when launching another app while music is playing?
When audio is already playing in YouTube or Spotify, launching another app may cause brief noise. For example, Cubase or Parallels Desktop may request low latency, and the buffer update interval can change as VoluBridge follows that request. This may trigger an internal re-snap. After the snap has settled, the state becomes stable and noise is less likely to occur under the same conditions.
Can it be used for games, video, or meetings?
VoluBridge is designed for low-latency use, so it is intended to feel natural for video, meetings, games, and music production. Actual feel depends on the device and app.
Operation
Operation and compatibility
Can it work with USB DACs?
If macOS recognizes the DAC as an output device, it is intended to be selectable as a VoluBridge output. Device-specific behavior can vary, so test it in your normal setup.
How is this different from DDC control?
DDC tools control display hardware features from the outside. VoluBridge works with the CoreAudio signal path, so it does not depend on whether a monitor supports DDC volume control.
What happens after sleep or monitor reconnect?
VoluBridge is designed to follow output disconnects, reconnects, and sleep/wake changes. Depending on the environment, output reselection or re-snap may occur.
Can the start of a sound be cut off in power-saving mode?
If a monitor, DAC, dock, or other output device wakes from a power-saving or standby state, the first instant of audio may be missed. This is usually caused by the output device needing time to wake or prepare its buffer, and it can be noticeable with notification sounds or short effects after silence. If it happens often, review the monitor or DAC power-saving, sleep, or auto-standby settings.
Which devices and apps have been tested?
Current checks include M1 MacBook Air, Mac Studio M4 Max, ASUS PG42UQ, MacBook Air built-in audio, RME UFX, Roland Fantom 08, Cubase, Parallels Desktop, Spotify, and YouTube. The list is expected to grow.
License
Trial and license
Is there a trial?
Yes. VoluBridge includes a 14-day trial so you can test it with your own monitors, DACs, and apps before purchasing.
What happens after the trial ends?
After the trial ends, license activation is required. VoluBridge audio output is not available through the virtual path until the license is activated.
What is the price and license type?
VoluBridge is a $49 one-time purchase. For personal use, the purchaser can use it on up to 3 Macs they use. Business, team, or shared-device use requires one license per user.
How many Macs can I use?
For personal use, one license covers up to 3 Macs used by the purchaser. If you activate on a fourth or later Mac, an older activation that has not been used recently is automatically replaced.
Can businesses or teams use it?
Business, team, or shared-device use requires one license per user. One license cannot be shared by multiple users.
Can family members or coworkers use my license?
One license can be used on up to 3 Macs used by the purchaser. If a family member, coworker, or team member uses VoluBridge, that user needs their own license.
Troubleshooting
Troubleshooting
What should I check if there is no sound?
Check that macOS output is set to VoluBridge, that the real output device is selected inside VoluBridge, and that the target device is visible to macOS.
My device does not appear as an output.
Reconnect the device and confirm that it appears in macOS Sound settings. With USB hubs or docks, recognition can vary by connection path.
What should I do if noise continues?
Try reselecting the output device, restarting the affected app, and checking sample-rate settings. Brief noise immediately after launching a low-latency app may settle after re-snap completes.
What should I try first when behavior still feels wrong?
First use Reset to Defaults in VoluBridge general settings, then select the output device again. If the issue remains, restart your Mac so CoreAudio, the driver, and the external device connection state are rebuilt.
Next