In Wwise, a sound only reaches the system as its own audio object when it has a 3D position, full spatialization, and a free object slot. Miss any of those, and it goes into the channel mix instead.
That last condition is the one worth sitting with. Object status in a game is granted per sound, per moment, by a runtime that is also servicing gunfire, footsteps, and dialogue, and it can be revoked while the sound is still playing.
None of which resembles the certainty of a pan sequence baked into object metadata in a music session, where the move you drew is the move that ships. Interactive audio does not work that way, and the gap catches out plenty of people crossing over from records.
FMOD starts from the other end. Every event is two-dimensional until you add a spatializer, and once you do, the spatializer handles positioning from game engine coordinates. Nothing about that pipeline is expecting a curve you drew against a bar line.
This is the part that trips up music-trained designers. In a session, position is a property of time. In a game, position is a property of geometry, recalculated every frame from where the listener and the emitter happen to be standing. Distance is its own layer on top, with attenuation curves setting how volume falls away as the gap widens.
Listener with Automation does something adjacent, placing audio along predefined paths relative to the player or camera rather than a world object. Both give you authored movement that survives contact with a running game.
The important detail is what the game knows about it, which is nothing. The engine is completely unaware of this movement, and Wwise is not moving actors or game objects to produce it. The motion exists purely inside the audio system.
FMOD has no direct equivalent. Designers reach for API-level work to get something similar, which is a different kind of job from drawing a shape and hearing it loop.
So authored rhythmic movement is possible. It just gets authored in the middleware, from a path in the Position Editor, rather than arriving as a lane you exported from somewhere else.
When the available slots are gone, Wwise falls back to first-in, first-out prioritization. Something has to lose object status, and the rule deciding which is not aesthetic.
FMOD handles the squeeze differently but lands in a similar place. You can create as many object panning processes as you like, though each platform has a flexible limit on how many are actually processed. Past that point, FMOD virtualizes the least significant sounds and mixes them through the traditional channel path instead.
The playback end has widened considerably, which raises the stakes. Every iOS device from the iPhone XS onward, running iOS 14.6 or newer, supports Dolby Atmos for gaming through stereo headphones or the device speakers. A spatial idea that used to be a console-only concern now reaches phones, on hardware where the object budget is tightest.
Spread is worth watching for a related reason. Set it to zero, and a multichannel source collapses to mono, which quietly removes the spatial benefit you were routing it through the object pipeline to get.
All of this shapes how spatial movement gets authored inside middleware. A pattern that only reads as an object needs to still function when the engine demotes it mid-scene, because on a busy frame that decision belongs to the runtime rather than to you.
That last condition is the one worth sitting with. Object status in a game is granted per sound, per moment, by a runtime that is also servicing gunfire, footsteps, and dialogue, and it can be revoked while the sound is still playing.
None of which resembles the certainty of a pan sequence baked into object metadata in a music session, where the move you drew is the move that ships. Interactive audio does not work that way, and the gap catches out plenty of people crossing over from records.
Position comes from the game, not from your session
The default case in Wwise is a 3D positioned emitter. Its position updates through SDK calls that report the emitter's world coordinates, so the pan is recalculated as the object moves. There is an option to hold the initial position for the length of the sound, which is about as static as it gets.FMOD starts from the other end. Every event is two-dimensional until you add a spatializer, and once you do, the spatializer handles positioning from game engine coordinates. Nothing about that pipeline is expecting a curve you drew against a bar line.
This is the part that trips up music-trained designers. In a session, position is a property of time. In a game, position is a property of geometry, recalculated every frame from where the listener and the emitter happen to be standing. Distance is its own layer on top, with attenuation curves setting how volume falls away as the gap widens.
Wwise will author movement in its own editor
There is real middle ground, and Wwise is where you find it. Emitter with Automation, which replaced the old 3D user-defined mode, lets a sound follow pre-designed paths around its emitter during playback. You draw those paths in the Position Editor, and you can design more than one for the same sound.Listener with Automation does something adjacent, placing audio along predefined paths relative to the player or camera rather than a world object. Both give you authored movement that survives contact with a running game.
The important detail is what the game knows about it, which is nothing. The engine is completely unaware of this movement, and Wwise is not moving actors or game objects to produce it. The motion exists purely inside the audio system.
FMOD has no direct equivalent. Designers reach for API-level work to get something similar, which is a different kind of job from drawing a shape and hearing it loop.
So authored rhythmic movement is possible. It just gets authored in the middleware, from a path in the Position Editor, rather than arriving as a lane you exported from somewhere else.
Objects run out, and the fallback is a channel mix
Wwise routes objects through a bus you deliberately set up. You create an audio bus as a child of the master audio bus, set its configuration to Audio Objects, and route sounds from the actor-mixer hierarchy into it. Sounds that travel that path keep their metadata, position and spread included, all the way to the endpoint.When the available slots are gone, Wwise falls back to first-in, first-out prioritization. Something has to lose object status, and the rule deciding which is not aesthetic.
FMOD handles the squeeze differently but lands in a similar place. You can create as many object panning processes as you like, though each platform has a flexible limit on how many are actually processed. Past that point, FMOD virtualizes the least significant sounds and mixes them through the traditional channel path instead.
The playback end has widened considerably, which raises the stakes. Every iOS device from the iPhone XS onward, running iOS 14.6 or newer, supports Dolby Atmos for gaming through stereo headphones or the device speakers. A spatial idea that used to be a console-only concern now reaches phones, on hardware where the object budget is tightest.
Spread is worth watching for a related reason. Set it to zero, and a multichannel source collapses to mono, which quietly removes the spatial benefit you were routing it through the object pipeline to get.
All of this shapes how spatial movement gets authored inside middleware. A pattern that only reads as an object needs to still function when the engine demotes it mid-scene, because on a busy frame that decision belongs to the runtime rather than to you.
