What is "sound" programming?
Posted 03 January 2012 - 08:11 AM
Like why is there a separate section for sound and audio specific programming if it can fall easily into a broad general programming category?
Programming with sounds is not really a thesis that any other kind of programming, such as graphics, would be special in and of itself.
In the end it's really no difference putting sounds into your game or putting images, etc. It's all data, and it's barely anything critical or specific with audio than with any other asset of information.
Or am I wrong here?
Posted 03 January 2012 - 10:38 AM
On the face of it, audio seems pretty simple, but in practice it's a different beast.
Unlike most other things, it's real-time stuff (we're talking 0.02ms stuff here, as oposed to video's 17ms; and nobody cares if you miss a frame here or there, but audio must be flawless), and you have to deal with latencies and all sort of fun stuff like that.
Again, it looks simple and the concepts are pretty easy, but for some reason it always ends up being tricky. Thus, most people end up using libraries like FMOD, and *still* end up having issues here and there.
Posted 03 January 2012 - 02:35 PM
Posted 03 January 2012 - 05:47 PM
Audio plays a key role in game development just like it plays a key role in motion pictures. Two important human senses are vision and hearing. In itself, it would seem inappropriate to exclude a category specific to audio. There are as many interesting DSP algorithms for audio as their are algorithms for graphics. If you've played any recent games, you will undoubtedly have heard sound damping, doppler shifting, reverberations, low/high pass filters, etc. Those experiences would not be possible without somebody putting in the effort to create the real-time filters to generate those effects.
Posted 03 January 2012 - 08:23 PM
Posted 04 January 2012 - 06:58 AM
There also aren't too many "generic" questions you can ask about audio programming (apart from synthesis) - asking things like "I keep getting audio underruns with my custom mixer running on ps3 spe, any ideas what could go wrong" are rather domain specific..
Posted 04 January 2012 - 01:55 PM
Are you just trolling?
Posted 06 February 2012 - 10:13 PM
As has been pointed out, ' sound programming' can be some of the most intensivige game coding someone can do...
I like to lump "sound programming" into 3 broad (sometimes overlapping) categories.
1) Sound Implementation programmer. This sounds like what you probalby think of. That's the programmer (often an intern ;0) whose job is to sprinkle the code with calls like "PlaySound(SNDTag, Parameters); through the game. (it can be quite a bit more than that, of course). Sound Implementation is usually, but not always, pretty straightforward
2) Sound Engine/Tool programmer. These programmers write the high-level sound engines that perform things like real-time streaming, data file parsing, etc. That requires pretty good knowledge of real-time and system programming. They may need to write entire (friendly and robust) User interfaces that a sound designer or composer will use when creating content. They are the essential link between content and code in content-driven audio development systems.
3) low-level audio signal processing programmer. These programmers typically need to know assembly language like the back of their hands as well as the complex mathematics behind the processing of audio. FFTs, DFT's, MLTs, IIR, FIR filters, data compression/decompression algorithms. That's pretty heavy stuff. And there's a ton of stuff going on out there. People do entire PhD dissertations on things like physical modelling of sound, real-time analysis of music, or environmental modeling..
So there's a lot of "meaty" stuff in game audio programming-- way more so than it may seem on the surface. Video game music and sound design still need a lot of specialized code to make it work
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users