Mass Effect Composer Jack Wall on the Tools Behind the Franchise's Score
Mass Effect composer Jack Wall tells TechRadar Gaming that game visuals drive his writing and that Wwise improved the Mass Effect 2 score.
According to TechRadar Gaming, Jack Wall, who composed music for the first two Mass Effect games, has described the tools he used to build their soundtracks. In an interview with the outlet, Wall said his inspiration comes mostly from the game's visuals, which he described as an abundance of material that shapes how he writes.
Wall told TechRadar that for Mass Effect 2 he used Wwise, short for Wave Works Interactive Sound Engine, to place the score inside the game. He called that approach far superior to the method used for the first title, according to the outlet's report.
TechRadar describes Wall's account as a look at what makes the franchise's music stand out. The interview focuses on the creative process and the technical choices behind it, rather than on any new game announcement.
The outlet presents Wall's comments as his own recollections of working on the series. The report does not include additional details from BioWare or from other members of the development teams.
Background
Mass Effect is a science fiction role-playing series developed by BioWare. The first game arrived in 2007, and the second followed in 2010, building on a story that let players shape outcomes through dialogue and decisions. Its music became part of its identity, with themes that recur across the games and help signal tone during both quiet exploration and high-tension combat.
Game soundtracks differ from film scores in one important way. A film is fixed in time, so the composer knows exactly when each cue will play. A game has no fixed timeline. Players might linger in a location, fight an unexpected enemy or wander off, so the music has to respond to what is happening on screen. Developers have long handled this through interactive or adaptive music, which switches or layers tracks as conditions change.
Wwise is audio middleware made by Audiokinetic, a company whose software is used across the games industry. Middleware sits between a composer's material and the game engine. It lets sound teams define how music and effects transition, blend and react to gameplay states without rewriting code for each change. Many studios use it because it gives composers and sound designers direct control over timing and mixing.
Interactive scoring has grown more sophisticated over time, and it now shapes how many players experience a game's soundtrack as much as the notes themselves. Tools like Wwise are one reason a composer's intent can survive the journey from studio recording to the living, shifting world of a game.
Why it matters
Wall's comments point to a part of game development that players rarely see. A soundtrack can sound lovely on an album and still feel disconnected in play if transitions are abrupt or cues repeat too often. How a score is implemented can therefore matter as much as how it is written, and the tools that connect the two are part of the creative work.
The interview also shows how composers and engineers depend on each other. When a composer credits a specific piece of software for a leap in quality, it suggests that the technology is not a neutral background detail. It shapes what is possible musically, from how smoothly a theme returns to how carefully the mix responds to a battle or a quiet moment.
For fans, the remarks offer a clearer sense of why the Mass Effect music feels the way it does. Wall's emphasis on visuals as a source of inspiration also reminds listeners that game music is often written in response to art, environments and character design, not just to abstract musical ideas.
More broadly, the story reflects a long-running argument in gaming about the status of composers and sound teams. Their work is central to atmosphere and emotion, yet it is often discussed less than graphics or gameplay. Interviews that explain the craft help bring that work into view.
What to watch
The main open question is how much of Wall's account will be confirmed or expanded. The TechRadar interview is the only source in this report, so readers should look for fuller accounts from BioWare, from Audiokinetic or from other people who worked on the series.
It will also be worth watching whether more composers discuss their tools in public. Detailed talk about middleware, implementation and workflow is still less common than discussion of melodies and albums, and more of it would help players understand how interactive scores are built.
Fans may also look for any future releases, re-releases or anniversary coverage that revisit the franchise's music. Any such coverage would show whether the soundtrack's implementation still holds up as technology changes.
Finally, watch how the broader games industry describes its audio tools. Clear explanations of how a score moves with a player could become a more regular part of developer interviews.
Viewpoints
Commentary from our columns: three angles on this story.
The Builder the engineer's view
Most players will never open a sound engine, but the choice to use Wwise is a design decision with real consequences. Middleware like this turns a composer's cues into a set of rules: when a track should start, how it should fade, which layers should rise during a fight and which should drop away when the player returns to exploration. Getting those rules right takes close collaboration between the music team and the engineers who wire everything together.
What stands out in Wall's account is the implication that the implementation, not just the composition, made a difference from one game to the next. That is an engineering lesson as much as a creative one. Every hook a composer gets from the engine is a question someone had to answer in advance, such as how many states the system tracks and how much memory the audio can use.
Developers working on their own projects should take note. Adaptive music looks effortless when it works, and that is exactly why it is hard to build. Teams that plan the audio pipeline early, test transitions under real gameplay conditions and treat the sound engine as a creative collaborator tend to avoid the seams that break immersion. The Mass Effect experience is a reminder that good tools matter most when they serve the people making the art.
The User what changes for people who use it
For someone sitting down to play, the change is simple to describe even if the machinery behind it is not. The music should feel like it belongs to the moment. A tense exploration sequence should not jolt into a fight, and a calm scene should not cut off abruptly when the player walks through a door. When interactive scoring works well, people often stop noticing it at all, and they just feel that the game is responding to them.
That is why Wall's remarks about implementation are worth paying attention to. Players do not experience a soundtrack as a list of tracks. They experience it as a series of small decisions made by the game, and the tools that govern those decisions shape how the story lands. A theme that returns at the right point can carry more emotional weight than the same melody heard on a loop.
Whether you are a longtime fan or a newcomer, the practical takeaway is to listen more closely. Notice how the score shifts when you change locations or when a conversation turns serious. Those transitions are part of the game's craft, and understanding them can make a replay feel fresh. The next time a piece of music seems to know exactly what you need, there is probably a lot of careful planning behind it.
The Optimist the hopeful reading
There is something encouraging in a composer saying that the visuals of a game feed directly into the music he writes. It suggests a healthy creative loop, where artists across disciplines inspire one another rather than working in isolated lanes. A world built with care gives musicians something to respond to, and the result can be a score that feels rooted in the place it describes.
The hopeful reading of this interview is that craft still matters in an industry that often rushes forward. Wall's focus on tools and implementation shows that composers and engineers continue to refine how music lives inside games. Each improvement in how a score responds to a player is a small step toward soundtracks that feel more alive and more personal.
It is also a good reminder for newer creators. Learning the tools of interactive audio is not a dry technical exercise but a way to give your ideas a life beyond the page. If the next generation of game composers takes Wall's example seriously, studying both the art and the systems behind it, the future of game music could be richer than the past.