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

댓글

댓글 달기

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

다른 글

게임의 사회성에 큰 역할을 하는 음성 채팅: Wwise GME 서비스 시작!

상호작용 요소가 많은 인기 게임의 사운드는 잘 만들어진 게임 자체의 '개별적인 캐릭터'를 뒷받침해줄 뿐만 아니라 더 풍부한 플레이 경험을 제공하고 게임 시스템을 강화하는 데 큰...

8.1.2020 - 작성자: 시몽 아슈비 (Simon Ashby)

Mastering Suite(마스터링 스위트)의 비하인드 스토리: 게임 내 오디오 마스터링

Mastering Suite 는 게임 산업의 크리에이티브와 엔지니어들이 일련의 협력을 통해 얻은 결과입니다. 수년간 PlayStation은 게임 오디오 개발자 커뮤니티와 협력하여...

23.7.2020 - 작성자: 단젤리 솀브리 (DANJELI SCHEMBRI )

UI 설계 관점에서 UI 오디오 접근하기 - 제 1부

어떤 게임에서는 사용자 인터페이스가 플레이어의 전체 경험에 궁극적으로 영향을 거의 미치지 않습니다. 수많은 모바일 게임과 같이 어떤 게임에서는 거의 전체 게임플레이 동안 UI를...

14.10.2020 - 작성자: 조셉 마척(JOSEPH MARCHUK)

Event-Based Packaging(이벤트 기반 패키징)이란?

Event-Based Packaging(이벤트 기반 패키징)이란 무엇일까요? 얼마 전에 Wwise 2019.2 UE4 통합은 Event-Based Packaging(이벤트 기반...

10.8.2021 - 작성자: 판 룬펑 (Fan Runpeng)

노 스트레이트 로드(No Straight Roads)의 음악적 게임 세계 설계하기

안녕하세요, 게임 오디오 여러분들! 저희가 Wwise와 Unreal Engine을 사용해서 '노 스트레이트 로드(No Straight Roads, NSR)'의 극도의 스타일링을...

29.3.2023 - 작성자: Imba Interactive (임바 인터랙티브)

우주의 침묵 속 사운드 | 하드스페이스: 쉽브레이커의 시스템

하드스페이스: 쉽브레이커(Hardspace: Shipbreaker)는 최근 Playstation 5, Xbox Series S/X 및 PC에서 출시된 1인칭 무중력 우주선 해체...

6.1.2025 - 작성자: 벤 맥컬러프 (Ben McCullough)

다른 글

게임의 사회성에 큰 역할을 하는 음성 채팅: Wwise GME 서비스 시작!

상호작용 요소가 많은 인기 게임의 사운드는 잘 만들어진 게임 자체의 '개별적인 캐릭터'를 뒷받침해줄 뿐만 아니라 더 풍부한 플레이 경험을 제공하고 게임 시스템을 강화하는 데 큰...

Mastering Suite(마스터링 스위트)의 비하인드 스토리: 게임 내 오디오 마스터링

Mastering Suite 는 게임 산업의 크리에이티브와 엔지니어들이 일련의 협력을 통해 얻은 결과입니다. 수년간 PlayStation은 게임 오디오 개발자 커뮤니티와 협력하여...

UI 설계 관점에서 UI 오디오 접근하기 - 제 1부

어떤 게임에서는 사용자 인터페이스가 플레이어의 전체 경험에 궁극적으로 영향을 거의 미치지 않습니다. 수많은 모바일 게임과 같이 어떤 게임에서는 거의 전체 게임플레이 동안 UI를...