menu
 

The Untold Tale of a Technical Sound Designer

커뮤니티와 이벤트 / 사운드 디자인

While I've just released a two-volume collection of my writings on Game Audio from the past 10 years, there's one story that’s not been written until now: the Genesis of the Wwise Project Adventure. You can catch wind of it in the Intro & Outro to Game Audio: Tales of a Technical Sound Designer - Volume 02 where excerpts from the Wwise Project Adventure are reproduced with gracious permission from Audiokinetic. However, that addition is just the tip-of-the-iceberg indicating a relationship that, for me, has catalyzed a career in game audio and given me firm-footing as a technical sound designer. Read on for an untold story of game audio from the perspective of someone who experienced the rise of audio middleware.

Cover_Volumes_Ad_01.png

In 2006 I attended my first GDC. By that time, I had found myself fully enamored with the tools used for integrating audio as a proxy between audio files and game programming. There were a few publically available audio middleware solutions (and a couple you could access through a maze of Non-Disclosure Agreements) but the learning curve was steep, documentation was scarce, and comprehension was slow-moving. Hours spent parsing commented code in disparate .xml files across demo projects or highlighting potentially relevant scripts buried within the pages of audio SDK’s had exposed me to skeletal framework and potential, but nothing approaching a full-circle understanding of the manipulation of sound interactively. So I went to the Game Developers Conference to help fill in the blanks between the knowledge I was able to glean from relationships and experience.

Little did I know that I was standing at ground zero for a revolution in game audio integration.

I don't remember much fanfare indicating the coming renaissance. If I had heard about the announcement of a new audio middleware tool in advance of the conference, I can’t remember. As many first-year attendees to GDC will attest: you’re lucky to get out with your sanity intact due to the heaping-helpings of raw knowledge being spooned out of every presentations honey pot. The buzz in those first-years was that Audiokinetic had created the Italian sports car of game audio middleware; a fast-moving and well-tooled audio pipeline solution (and in the beginning, it was priced to match!). But with a free-to-download authoring application and documentation that illustrated the benefits and strategies available within it’s (lovingly?) monochromatic-grey interface it quickly became the perfect training ground for the creative expression of interactive sound.

I chalk this feeling up to what I call the 360-degree strategy that Audiokinetic has employed since the inception of Wwise. From the beginning, everything within the Authoring Application was established in a way that allowed for the creation, auditioning, profiling, and iteration of systems to play back audio in a fully audition-able manner. Writing about Wwise in 2010 as part of the first installment of the Audio Implementation Greats Series (available in Game Audio: Tales of a Technical Sound Designer - Volume 01) I said “The ability to mock up every aspect of the engines, within the provided Soundcaster, brings the Wwise toolset further into a full prototype simulation outside of the game engine.” Everything from Parameter-controlled Blends, States, Switches and RTPCs could be manipulated on-the-fly before ever making it into a game. In 2006 Wwise emerged as a fully-formed implementation toolset and playground for a burgeoning technical sound designer such as myself and it would only get better from there.

I watched as Audiokinetic drove the game audio middleware industry and game developers associated with audio to achieve greater things. It wasn't long before other audio tools stepped-up their game with comparative features, things like: Interactive Music Systems, Extensible Mixing Architectures, Built-in Localization, and Game Profiling. However, without the comprehensive design infrastructure to support these additions, they often felt bolted-on, clunky, and poorly implemented without regard for authoring in what ended up feeling like a punishing pipeline of brutality. I spent the first 7 years of my career as a freelancer, and during that time had the opportunity to use, misuse, and ship with the best and worst that game audio tools had to offer (“To All The Audio Toolsets I've Loved Before…” - Volume 02)...trust me, I’ve muscled through some rough workflows and suffered at the obliquely referenced functionality of some primitive tools to get the job done. Ultimately, I ended up using Wwise across several projects during my formative years and the paradigm opened my eyes wide to the potential of audio tools.

Soaking in the Wwise methodology allowed me to harness the potential of interactive sound in a way that feels creative and empowering.

Spines_01.png

It was during this maelstrom of game audio tool technical submersion that I was approached by the folks at Audiokinetic to help streamline some of their early documentation. I would help combine, update, and focus two documents: Wwise Fundamentals & The Wwise Approach into the currently existing Wwise Fundamentals document. While I had been posting thoughts on implementation, authored a series for DesigningSound.org called Audio Implementation Greats, and began writing for Game Developer Magazine as part of their monthly Aural Fixations column (all of which is available in Volume 01) , I had never waded into technical documentation. This opportunity served as a perfect springboard where I was able to begin to understand the differences between the stream-of-consciousness writing I had been doing and the requirements of a detailed explanatory document. This work would eventually lead to the creation of the Wwise Project Adventure.

One of the greatest things to come out of my career in game audio are the friends and colleagues I’ve been able to meet along the way. These relationships are especially critical when collaborating on a project or helping to realize someone's vision. So when Simon Ashby at Audiokinetic asked me to wade into the deep-waters of technical documentation and create “a document that will make a new Wwise user up and running in a really short period of time” and help “to create a 'full' project where you can see the relationship between the Wwise project and how it's setup in code,” I felt that there was a level of trust as a result of our previous interactions. This proved to be incredibly important as the scope of the project unfolded over the next months to encompass the massive 300 page document that became the Wwise Project Adventure.

Truly a collaboration of the highest-order, by the end of the creation of version 1.0 we would pull in many of the folks at Audiokinetic, the content creation team at Bay Area Sound, an editor, translation, and a team of proofreading Beta-testers to help solidify and sharpen the resource. An absolute labor of love, the Wwise Project Adventure shifts between abstract game audio narrative (sketching out the forthcoming chapter’s material) and step-by-step technical implementation in three languages (English, Japanese, Chinese). Coupled with the provided fully-implemented Wwise Project, the goal was to give someone new to Wwise multiple ways to digest the educational content, either by reading through, working through, or exploring the already finished Wwise project. The approach that Simon and the team at Audiokinetic initiated with the Wwise Project Adventure also feeds into the 360-degree strategy I mentioned earlier, in that the overarching goal was to further extend the loop of learning that begins the first time you start working with Wwise and continues as your experience with the Authoring Application and methodology deepens.

At every step in the process working with Audiokinetic, I have been met with true creatives and individuals who are invested in, not only the success of Wwise but, the success of game audio professionals and creatives working with interactive audio. Each member of the team exudes a passion and commitment to their craft and it has been a joy coming to know many of them through work, collaboration, and a visit to their office in Montreal during the MIGS conference in 2014. It’s no wonder that I have felt creatively empowered through the use of Wwise over the years with this team of unique and talented individuals driving the next generation of game audio.

I’d like to carry forward and augment thanks to the original group who helped launch the Wwise Project Adventure: Simon Ashby, Etienne Caron, and Bernard Rodrigue from Audiokinetic. Editor Judy Lapalme. Continuity experts: Hrishikesh Dani, Luca Fusi, Jack Menhorn, Roel Sanchez, Michael Taylor, and Rob Bridgett along with Robert Mollon and additional staff at Audiokinetic during the interim years. It was with their help that the document was elevated from frantic scratchings and verbose insanity into a sharpened axe of implementation tutelage. My deepest thanks.

So, here I find myself at a milestone in my career with the release of this two-volume collection of writings, surveying the game audio landscape spread out behind me and reflecting on the components that have comprised my experiences as a technical sound designer. Audiokinetic and Wwise have contributed to a fundamental appreciation of interactive audio, technical sound design, and game audio in a way that I continue to be deeply thankful for. I look forward to the years to come, the challenges and successes, and the people in the community who continue to inspire me. All the best in your future endeavours!

Game Audio: Tales of a Technical Sound Desgner Volume 01 & Volume 02 is self-published and available in Softcover - Color or Black & White print-on-demand editions or digitally (PDF) via Blurb.

  

Subscribe

Damian Kastbauer

Software Product Manager

Audiokinetic

Damian Kastbauer

Software Product Manager

Audiokinetic

Atari 2600/ NES channeled through> C64 SID chip Blue Monday game child purple mountain majesty feasted on guitar noise during 90's shoegaze invasion culminating in two-tiered pedal board with never enough digits to turn all the knobs. Constant fascination with dark art of implementation leads to articles diving into unknown technical sound design as attempt to share discussions through game audio podcasts and now the two-volume book series Game Audio: Tales of a Technical Sound Designer. Community to the core, noise for life, respect the vibrations.

Lost Chocolate Lab

 @DamianKastbauer

댓글

댓글 달기

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

다른 글

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

이 글에서는 UI 디자이너*의 관점에서 UI 오디오에 접근하는 방식을 보여드리려고 합니다. 이를 통해 심미적으로나 기능적으로 화합적인 UI를 제작하는 데에 도움이 되었으면 합니다....

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

가상 현실을 위한 훌륭한 잔향 제작하기

이 시리즈에서는 과거, 현재, 그리고 새로운 잔향 기술을 집중적으로 살펴보고 몰입적 공간적 관점에서 이 기술을 검토해봅니다. 이전 글에서 저희는 왜 가상 현실에서 몰입적인 잔향을...

17.2.2021 - 작성자: 브누아 알라리 (BENOIT ALARY)

고전적 잔향 방법의 몰입적 잠재성 살펴보기

이전 글인 VR에서 몰입형 잔향의 도전 과제에서는 가상 현실에서 몰입형 잔향을 성취하기가 힘든 이유를 알아보았습니다. 이 시리즈에서는 과거, 현재, 그리고 새로운 잔향 기술을...

23.2.2021 - 작성자: 브누아 알라리 (BENOIT ALARY)

zerocrossing의 SpectralMultiEffect

SpectralMultiEffect는 Wwise용 플러그인입니다. 이 플러그인은 게임에서 상호작용성을 향상시키기 위해 제작되었으며 사운드 디자이너가 실험해보고 오디오를 변화시킬 수...

9.2.2022 - 작성자: 하비에르 아르시니에가스(Javier Arciniegas)

Wwise로 도플러 효과 제작하기

도플러(Doppler) 효과는 음파를 기준으로 관찰자가 움직임에 따라 파동의 주파수가 변하는 것입니다. 이 물리적인 현상은 모든 종류의 파동 전달에서 일어나며 음파도 예외가...

30.3.2022 - 작성자: 쒸 웨이 (Xu Wei, 徐巍)

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

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

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

다른 글

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

이 글에서는 UI 디자이너*의 관점에서 UI 오디오에 접근하는 방식을 보여드리려고 합니다. 이를 통해 심미적으로나 기능적으로 화합적인 UI를 제작하는 데에 도움이 되었으면 합니다....

가상 현실을 위한 훌륭한 잔향 제작하기

이 시리즈에서는 과거, 현재, 그리고 새로운 잔향 기술을 집중적으로 살펴보고 몰입적 공간적 관점에서 이 기술을 검토해봅니다. 이전 글에서 저희는 왜 가상 현실에서 몰입적인 잔향을...

고전적 잔향 방법의 몰입적 잠재성 살펴보기

이전 글인 VR에서 몰입형 잔향의 도전 과제에서는 가상 현실에서 몰입형 잔향을 성취하기가 힘든 이유를 알아보았습니다. 이 시리즈에서는 과거, 현재, 그리고 새로운 잔향 기술을...