SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp
description
Transcript of SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp
![Page 1: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/1.jpg)
SAFE AND SOUNDRisk Free Audio Development
GDC San Francisco 2009, Audio Boot Camp
Tomas Neumann – Senior Audio Programmer
![Page 2: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/2.jpg)
Introduction
Tomas Neumann: Safe and Sound / GDC09
GamesFarCry (2004)Crysis (2007)Crysis Warhead (2008)Crysis Wars (2008)
Studios Frankfurt, GermanyBudapest, Kiev, Sofia, SeoulCrytek UK
Tomas NeumannSenior Audio Programmer in R&D since 2005Tomas(at)crytek(dot)com
![Page 3: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/3.jpg)
Audio In Game Development : Everywhere
Tomas Neumann: Safe and Sound / GDC09
• Pre-Production• Implementation• Music / Dialogue• Milestones• Reviews• Technical settings• Alpha / Beta / Gold• Demo• Patches
People outside of Audio– Might have wrong
impression– Fear what they dont
know– Influence your work
![Page 4: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/4.jpg)
Risk Free Audio Development ?
Tomas Neumann: Safe and Sound / GDC09
• Stability– Fewer crashes– Fewer show-stoppers
• Efficiency– Fast turn around– Fast bug fixes– Safe bug fixes
• Earns trust– Reduce their fear– Prove Audio is low risk
• Quality– Better Audio in final
product
![Page 5: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/5.jpg)
Risk Free Audio Development ? YES PLZ!!
Tomas Neumann: Safe and Sound / GDC09
• How to achieve?– Not done in a day– Not a single task– Baby steps
• „Never-ending story“– Ongoing development– Ongoing effort– Ongoing improvements– You will never succeed!
This talk:• I will not tell you how to improve 1000
details!• HOPE
![Page 6: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/6.jpg)
1.Limit access2.Inform others3.Divide and Conquer4.Do not put things where they don‘t
belong5.Prepare for content-locks6.Find your own bugs7.A bug is your friend8.Keep track of changes9.Exploit automation10.Data-mine for gold
General Strategies To Follow
Tomas Neumann: Safe and Sound / GDC09
![Page 7: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/7.jpg)
1) “Limit Access“
Tomas Neumann: Safe and Sound / GDC09
• Use abstract, data-driven sounds
• Use high level parameters
• Minimize external interface and behaviour – (Code & Audio)
Cost: – More work– More responsibilty– More bugs
Benefit: – More creativity
(internal)– Faster implementation– Less coders help
needed
![Page 8: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/8.jpg)
2) “Inform Others“
Tomas Neumann: Safe and Sound / GDC09
Write what others don‘t know.
• Internal communication– Forum / Mail– Wiki
• Show work early and often– No embarressment– See Jason‘s „Fail early“
• Code: – Optional debug messages
Cost: – More communication– Extra code
Benefit: – Better transparency– Help others– People know:
• you actually work(!)• what is WIP and
what is new
![Page 9: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/9.jpg)
2) “Inform Others“ 2
Tomas Neumann: Safe and Sound / GDC09
![Page 10: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/10.jpg)
3) “Divide And Conquer“
Tomas Neumann: Safe and Sound / GDC09
Avoid unclear responsibilities or overlapping tasks
• Sound Designer– Source (raw) asset
creation– Asset specification
• (Automatic) build process– Build (cooked) asset
• Other areas:– Audio implementation / Code– Localization / post-processing
Cost: – Extra working steps
Benefit: – Easier to resolve issues– Modular and structured
work habbits
![Page 11: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/11.jpg)
4) “Do Not Put Things Where They Don‘t Belong“
Tomas Neumann: Safe and Sound / GDC09
• Code– Avoid hard-coding audio
specification and references
– Serialize from external database (xml, sql)
• Audio– Clean up audio asset
Cost: – Coding effort– Well organized SDs
Benefit: – Independence from
code– Quicker iteration
(immune to code-lock!)– More control (stripping)
![Page 12: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/12.jpg)
5) “Prepare for code/content-locks“
Tomas Neumann: Safe and Sound / GDC09
They are coming, wether you want or not on milestones, demos, or randomly.
They will block your progress!
• Be prepared for downtime– Reserve work to do in
between.– Inform if no audio bug
was blocking
Cost: – Administrative
overhead– More communication
Benefit: – Balanced work load– Increase trust if audio
was non-blocking– Steady progress despite
milestones
![Page 13: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/13.jpg)
6) “Find Your Own Bugs“
Tomas Neumann: Safe and Sound / GDC09
Dont expect: • QA to know what is
broken• Producers to know how
important or risky a fix is
• Train QA• Add bugs by yourself
– Add to bug tracker, even if you are about to fix it
• Increase bug priority– Non-critical but annoying
(known shippable in Beta)
Cost: – Extensive play tests– Scanning through game
logs Benefit:
– You know the game better– More fixed bugs = better
shipped audio– Increase bug fix rate– Decrease fix time– Helpful statistics– Happy producer = more
trust
![Page 14: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/14.jpg)
7) “A Bug Is Your Friend“
Tomas Neumann: Safe and Sound / GDC09
• Document problems– Write about it : What?
Why?– Add to bug tracker, even
if you are about to fix it• Code
– Use assert()– Log: Output warning– Catch function call
results– Create test cases
• Inhouse & middleware
Cost: – Admit your mistakes– Overcome one‘s weaker
self Benefit:
– Increased awarness (team, QA)
– Faster fix-rate • Done it before• Searchable mail• Producer‘s trust
![Page 15: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/15.jpg)
8) “Keep Track Of Changes“
Tomas Neumann: Safe and Sound / GDC09
Why was a decision made 2 years ago?
What was agreed on in that meeting?
Dialogue integration specialist: „btw, today is my last day!“
• Preserve knowledge• Offer it to new team
members• Write what you know
Cost: – Documentation effort– Write down the obvious
Benefit: – Surprise-proof– Database of experience– Evaluate and rate old
decisions
![Page 16: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/16.jpg)
9) “Exploit Automation“
Tomas Neumann: Safe and Sound / GDC09
• Automatic Build on several platforms– Code (compilation errors)– Audio (integrity errors)
• Automatic test run– Stability tests – Mail filtered logs of
warnings• Statistics
– Performances graph• Show impact of changes
– Finalize compression settings
Cost: – Extra hardware– Build / Audio engineer
Benefit: – Frees worker‘s PC– Honest verification– Stability– Performance– Short down time
![Page 17: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/17.jpg)
10) “Data-mine for Gold“
Tomas Neumann: Safe and Sound / GDC09
0
500
1.000
1.500
2.000
2.500
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33
Times Played Times Played on a Channel
Statistics help you to find the bang for the buck
• Graphs• Lists• Pictures
![Page 18: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/18.jpg)
Conclusion
Audio Development– safer – more stable– more efficient– more trustworthy– increase quality
You have to work on it – every single day!
But it is FUN!
Tomas Neumann: Safe and Sound / GDC09
![Page 19: SAFE AND SOUND Risk Free Audio Development GDC San Francisco 2009, Audio Boot Camp](https://reader036.fdocuments.us/reader036/viewer/2022070423/568167e1550346895ddd4392/html5/thumbnails/19.jpg)
Tomas Neumann: Safe and Sound / GDC09 – Tomas(at)crytek(dot)comAll pictures created by Crytek
Thank youThank youPlease rate!Please rate!
Ask questions!Ask questions!
KKTHXBYE
We are hiring! Visit us at our booths #226 WH, #5940 NH