WorldAudio Limitations

WorldAudio Limitations

Important limitations of the WorldAudio emitter management system and why they exist.

AVPro Incompatibility

The WorldAudio system only works with Unity-based video players (e.g., Unity VideoPlayer, VRC Unity Video Player). It does not work with AVPro Video Player or other third-party video players.

Why: WorldAudio manages AudioSource components directly. AVPro bypasses Unity's audio pipeline and outputs audio through its own system, making it invisible to WorldAudio.

Workaround: Use Unity-based video players. For AVPro, use a separate audio source component on the same GameObject and configure it manually. See WorldAudio Limits Reference for details.

AudioSources Cannot Be Directly Controlled

Once an AudioSource is registered with WorldAudio, you should not control it directly from your code. WorldAudio manages play/pause/culling state based on importance and privacy.

Why: WorldAudio calculates importance scores and decides which AudioSources should be active. Directly setting AudioSource.Play() or AudioSource.Stop() conflicts with WorldAudio's management.

Workaround: Use AudioSourceStateController (on the same GameObject) to control play/pause/stop. For manual control, do not register the AudioSource with WorldAudio. See WorldAudio Limits Reference for details.

Platform Audio Limits

VRChat imposes platform limits on active audio sources. See WorldAudio Limits Reference for the full table and how WorldAudio manages these limits.

See Also

• WorldAudio Limits Reference — technical reference for all limits
• WorldAudio-Subsystem — full system details
• WorldAudioController — controller settings
• OccludedEmitter — per-emitter lifecycle