The activation worked because the audience was not only watching a game. They were changing the game audio live, hearing their own performance inside the build within moments.
For Gamescom, I wanted to create something that showed game audio as a process rather than a finished reel. The result was a live dubbing station built around Trials of Randoom, a project from GoGo Games Interactive and Teion Games for which I had worked on sound and music.
Players could record character lines, hear those recordings inserted into the game and immediately understand what VO integration actually feels like from inside production.
That made the activation useful on two levels: it was entertaining for the audience and technically honest about how voice moves from microphone to game.
The Goal Was Participation, Not a Demo Reel
Most event showcases ask people to watch.
This one asked them to perform.
Participants dubbed Deivy’s frightened lines, grunts and Randoom’s evil laugh, then heard themselves inside the game. That changed the relationship with the project because the audience stopped being passive for a moment and became part of the production.
The activation worked because the result was immediate.
Record.
Replace.
Trigger.
Hear it in context.
That loop is much more memorable than explaining VO implementation on a slide.
The Game Needed to Support Fast Replacement
The technical setup only works if the project structure is prepared for it.
VO events need predictable names, clear file relationships and a way to replace content without rebuilding the entire game every time someone records a line.
FMOD is useful here because its project structure is built around events, assets and runtime behavior. The FMOD Studio Concepts documentation explains the relationship between events, parameters, banks and audio assets.
The live station simplified the normal production pipeline, but the same basic logic remained: the game called an event, and the event needed the correct media.
Pro Tools Handled Fast Recording and Bounce
The recording side needed to be almost invisible to the participant.
A performance came in, the file was captured, edited enough to be usable and bounced directly into the folder structure FMOD expected.
That avoided unnecessary file movement and made the replacement process fast enough for an event environment.
The technical principle is useful beyond the activation.
If a pipeline has a predictable destination, naming convention and export process, the team can reduce the number of manual steps between recording and implementation.
Live Update Made the Process Feel Immediate
FMOD’s live-development workflow is especially useful when the game and authoring environment can communicate while the build is running.
For the activation, that meant audio changes could be heard quickly enough that the audience experienced the cause and effect directly.
This matters because technical audio can otherwise feel abstract to people outside the discipline.
A parameter diagram is one thing.
Hearing your own evil laugh suddenly come from a character is another.
The second one explains the pipeline much faster.
Event Design Needs a Short Feedback Loop
An activation at a convention has very different constraints from a studio session.
People are waiting.
The environment is noisy.
The participant does not know the tools.
Any technical step that takes too long breaks the experience.
That means the workflow needs to prioritize speed and reliability over perfect editing.
The recording only needs to be clean enough for the point to land.
The goal is not to finish a commercial VO take.
It is to show the relationship between performance and implementation.
The Experience Also Showed Why VO Is More Than Recording
Players often think voice production ends when the actor says the line.
The station made the next stage visible.
The line needs to be recorded, edited, named, placed in the correct project structure and triggered in the right context.
On a real project, that chain becomes much larger when there are hundreds or thousands of lines, multiple actors and localization.
The activation compressed that pipeline into a few moments.
That made the craft easier to understand.
Gamescom Was the Right Context for the Experiment
Gamescom events bring developers, players, service providers and production teams into the same environment, which makes interactive demonstrations especially useful. The gamescom LATAM programs include industry, business and public-facing activities that create room for this kind of crossover between production and audience. The official programs page provides current context for the event ecosystem.
The station was not a formal workshop.
It was closer to a tiny production experience hidden inside an event activation.
That is why it worked.
The Best Marketing Element Was the Production Itself
The activation did not need a separate explanation of why game audio matters.
The participant heard the result.
Their voice changed the character.
The game suddenly felt more personal because they had contributed something to it.
That kind of interaction can create stronger memory than another branded giveaway because the experience is tied to the project itself.
The production process becomes the marketing idea.
There Were Technical Risks Too
Live systems fail in public.
That is part of the job.
Recording environments are noisy. Files can be named incorrectly. The wrong asset can replace the wrong line. A connection can fail. Latency can make a simple experience feel broken.
The setup therefore needed a narrow, controlled scope.
Only a small set of lines.
A repeatable recording path.
A known FMOD project structure.
The more variables you remove, the more reliable the experience becomes.
The Activation Was Also a Pipeline Test
One of the interesting things about building event experiments is that they expose production friction very quickly.
If replacing one line requires several manual steps, the activation becomes slow.
If naming is inconsistent, mistakes appear immediately.
If the event structure is unclear, debugging takes too long.
That makes the experiment a useful test of how clean the underlying audio pipeline really is.
A good event activation benefits from the same things a good production does: clear structure and predictable handoffs.
What I Would Preserve in Another Version
The core idea is strong because the participant understands the result instantly.
If I built another version, I would keep the experience short, preserve the immediate record-to-build loop and make the technical layer even less visible to the audience.
The audience should experience the magic.
The production team should handle the complexity.
That is true for game development too.
The Larger Lesson
Interactive audio demonstrations work when they let people change something meaningful and hear the consequence immediately.
The technology is there to support that loop.
Not to become the attraction by itself.
For a deeper look at middleware, Why I Use Audio Middleware in Game Development explains the broader role of FMOD and Wwise. For event preparation, Gamescom LATAM: How to Prepare for Meetings, Pitches and Networking covers another side of the event experience.
Next Step
If you are designing an interactive activation around a game, start with the shortest possible loop between audience action and in-game consequence. Then build the technology around that moment.
Explore Flutu’s work or send us the activation idea if you want to combine VO, middleware and live interaction around a playable experience.
