Troubleshooting

This page covers common problems you might encounter with Orbit itself, as well as issues in ADM content that Orbit can help you identify.

App issues

Problems with Orbit's operation.

If you don't hear anything during playback:

Check your output device — open the Settings tab and confirm the correct device is selected.
Match monitoring mode to your setup — if you're on headphones, use Binaural; if you're on speakers, use 7.1.4.
Check the master fader — make sure it's not turned all the way down. Option+click to reset to 0 dB.
Clear any mutes — click the Clear button in the Solos & Mutes panel to reset all mute states.
Check macOS volume — verify your system volume is up and Orbit isn't muted in Sound preferences.
Verify the file has audio — some ADM files may contain metadata but no actual audio content.

If objects appear static in the visualizer:

Make sure playback is running — press Space to play.
Scrub to a section with automation — not all ADMs have moving objects, and objects may be static during some sections.
Select an object — click an object in the sidebar to highlight it with a white ring. This makes it easier to track.
Check the file — confirm the ADM actually contains object automation (metadata-only sections won't show movement).

Head tracking requires specific conditions:

Must be in Binaural mode — head tracking is only available when monitoring through headphones.
AirPods must be selected as your output device for AirPods tracking to work.
Camera tracking requires camera permission. If prompted, allow access. You can select which camera to use in Setup → Camera Tracking Settings.
External webcams should appear in the camera dropdown — verify your camera is connected and recognized.
If tracking seems jittery, open Setup → Camera Tracking Settings and adjust the sensitivity sliders.
Recenter after putting on headphones or changing your posture.

Large ADM files take longer to process:

Waveform generation happens after the audio is loaded — this is the slow part for big files.
The cache speeds up future loads — once .orbwave files are written, reopening is much faster.
Close other heavy apps if your system is struggling.

Force a rebuild by deleting the .orbwave file next to your ADM. Orbit will regenerate it on next load.
Check the file modification time — if the ADM was updated, Orbit should detect the change, but deleting the cache is a reliable fallback.

If meters don't reflect what you're hearing:

Switch monitoring modes to see if the issue is mode-specific.
Verify the ADM has content on the channels you're checking — use the Multichannel waveform view to see per-channel activity.
Solo the bed or specific objects to isolate what's contributing to the meter readings.

Performance issues during playback:

Open the Performance HUD (⌘⌥D) and watch for underruns or high render times.
Try a different output device — some audio interfaces handle real-time playback better than others.
Close other CPU-heavy applications to free up system resources.