Wayward Strand's Voiceover Pipeline | Part 3

게임 오디오

This article is part 3 of Maize's 3-part series on the voiceover pipeline of Wayward Strand. You can read the first part here, and the second part here.

Playing the wavs through Wwise:

In some ways, this was quite straightforward, because Wwise has a great implementation for playing external audio files, and once we’d figured out how to do this once with Unity’s Wwise plugin, it would work across all of the lines across all scenes. The trickiest thing here was figuring out how to organise the wavs inside the subfolders.

We ended up going for a folder structure of: <day>/<scenename>/<files, named 01.wav through 999.wav> - we could then figure out the path of a particular wav in a particular scene by knowing the day the scene was in, the scene name, and the special number that we had defined for the recordings for that line. An additional wrinkle was that we had a special folder for ‘shared’ scenes for characters, which required a different folder structure - this one was shared/<character>/<scenename>/<01.wav-999.wav> - so if it was in the ‘shared’ folder, it used that structure, otherwise it used the general day structure.

That special number mentioned just a sequential line index within the scene, but one that we ‘fixed in place’ before printing scripts out/recording sessions, so that if a scene had additional edits or structural changes after recording, the index wouldn’t change even if the scene did. Edits post-recording happened surprisingly often! Whether it was that a scene had logical issues that were only perceptible when QA testing with the VO in there, or line-reads that weren’t exactly right and could be cut without breaking the flow of the scene, or sneaky additions where lines from a few different scenes could be used to create an entirely new scene. Fixing the numbers in place turned out to be an incredibly useful approach that meant we could be fixing bugs and improving scenes after the VO was recorded, right up until release.

Bugs:

So what VO bugs can there be?

Wrong line or take

To fix this, I would open the relevant notation sheet, and Pro Tools file, and go digging for the correct line. This would need to be re-edited through the Pro Tools and RX presents. Sometimes the notation was the source of the mistake, and the described line didn’t exist. There’s so much to concentrate on during recording, things get missed!

Line not sliced correctly, leading to scene going out of sync

Woops! A line of dialogue wasn’t sliced properly, so now every line after it has the wrong number, and the characters are saying each other's words! Jason made a tool that scraped through all the scenes, and see if there was more or less wav files in their folders, than was expected. So I was able to go through these pretty systematically, and fix them. But, sometimes the scene would sync up again by the end, because of an additional miss-slice, and so the scene would be found through manual QA, and not any of our automated tools.

The first step is always to open the notation sheets, and check there first. They’re the source of truth! But, I didn’t always then have to open Pro Tools. I got to the point where if all the right words were there, just not in the right clips, I’d skip Pro Tools and use Audacity to slice/combine instead.

Words missed

When you don’t speak Danish, and when you’re slicing through 100 lines a minute, it’s easy to miss-slice. Or it could be because a character was coughing, speaking gibberish, or making some other nonsensical sounds that were mistaken for dialogue. This would lead me back into Pro Tools, to go looking for where this missing word went. OR, in the case where a word was never said, I would either look through the scripts to find another instance of that word, or I’d go into the Ink/script file in the game and change the line there.

So, the tools I was using to fix VO bugs were:

  • Our notation spreadsheets
  • Pro Tools sessions
  • Audacity for simple stuff
  • Ink for script fixes

We didn’t have many bugs! In fact the person who made the most mistakes in the editing process was me, Maize! Look, we all have our specialties... I had some stats on what percentage of scenes had bugs. I think out of the hundreds of scenes, maybe 5% of them had some small fix needed? Thankfully we had budgeted for implementation time, which ended up being half automated, so I was able to pivot to bugs which we hadn’t predicted.

The End

The end of the process was scene direction. Jason, as well as Aspen Forster, Susan Dang, and Marigold Barlet would do scene direction using the timeline feature of Unity, as well as a totally custom suite of tools made by Jason, with assistance from Russell Dilley and Thomas Ingram. This was an additional place where VO bugs could be found, for me to fix. As well as any extra pieces of audio cues that may have been missed, and had to quickly be made and implemented.

In the end, recording and getting the VO into the game, was a massive team effort. I just have to remind myself that it IS the equivalent of 18 feature films! Massive!

Maize Wallin

Composer, Sound Designer and Audio Programmer

Maize Wallin

Composer, Sound Designer and Audio Programmer

Victorian College of the Arts (BFA) educated, Melbourne based composer, sound designer, and audio programmer working across indie games and big budget AAA. ​Their focus is in 3D spatialised audio, and dynamic music, using cutting edge techniques to create unique outcomes. Maize lectures consults in Australia and around the world on these topics, and is strongly engaged in the game development community, and in activism and representation within it. Highlights from Maize's extensive folio include God Fall, Receiver 2, Wayward Strand, and Cosmic Express, as well as their solo experimental audio game works.

maizewallin.com

 @MaizeWallin

댓글

댓글 달기

이메일 주소는 공개되지 않습니다.

다른 글

Unity3D에서 사운드 디자이너의 역량 강화하기

최근 몬트리올 국제 게임 서밋(Montréal International Game Summit, MIGS)에서 '사운드 디자이너의 역량 강화하기'라는 제목으로 발표를 한 적이...

6.11.2018 - 작성자: BEATRIX MOERSCH (베아트릭스 모쉬)

이미지 기반 파라미터를 이용한 오픈 월드 앰비언트 디자인

Blend Container는 강력한 시퀀싱 및 믹싱 도구가 될 수 있습니다. 단순히 그것의 기능을 배우는 것이 게임 사운드 디자이너의 생각에 온갖 종류의 새로운 아이디어를...

13.3.2020 - 작성자: 톰 토디아 (TOM TODIA)

'Suspects: Mystery Mansion'의 GME 음성 채팅 시스템

소개 이 블로그 글은 Wildlife Studios의 'Suspects: Mystery Mansion' 게임의 음성 채팅 시스템에 관한 것입니다. 안녕하세요. 저희는 Leo...

24.8.2022 - 작성자: 펠리페 로페스 (Felippe Lopes)

상호작용 음악: '여러분이 직접 선택하는 모험' 스타일의 발라드

2018년 크라우드 펀딩 캠페인을 성공적으로 마친 inXile Entertainment(인엑사일 엔터테인먼트)는 '웨이스트 랜드 3(Wasteland 3)' 게임의 본격적인 제작에...

23.5.2023 - 작성자: Alexander Brandon (알렉산더 브랜드)

무료 Wwise 인디 라이선스 | 최상의 오디오로 인디 개발자에게 힘을 실어줍니다

프로젝트의 비전에 맞는 몰입형 오디오 경험을 만드는 것은 특히 예산이 제한된 인디 개발자에게는 어려울 수 있습니다. 바로 이를 위해 Audiokinetic의 Wwise는 인디...

18.7.2024 - 작성자: Audiokinetic (오디오키네틱)

BPM: 불렛 퍼 미닛(Bullets Per Minute)에서 음악과 게임플레이 동기화하기

어떤 리듬의 FPS를 만들지 결정하기 BPM: 불렛 퍼 미닛(Bullets Per Minute)은 박자에 맞춰 총을 쏘고, 재장전하고, 점프하고, 피하는 리듬 액션 FPS...

11.12.2024 - 작성자: Awe Interactive (어 인터랙티브)

다른 글

Unity3D에서 사운드 디자이너의 역량 강화하기

최근 몬트리올 국제 게임 서밋(Montréal International Game Summit, MIGS)에서 '사운드 디자이너의 역량 강화하기'라는 제목으로 발표를 한 적이...

이미지 기반 파라미터를 이용한 오픈 월드 앰비언트 디자인

Blend Container는 강력한 시퀀싱 및 믹싱 도구가 될 수 있습니다. 단순히 그것의 기능을 배우는 것이 게임 사운드 디자이너의 생각에 온갖 종류의 새로운 아이디어를...

'Suspects: Mystery Mansion'의 GME 음성 채팅 시스템

소개 이 블로그 글은 Wildlife Studios의 'Suspects: Mystery Mansion' 게임의 음성 채팅 시스템에 관한 것입니다. 안녕하세요. 저희는 Leo...