3 minutes ago, the incredible smoker said:

Now you know me.

Too cool!

Fun stuff.

Thanks for sharing.

lol : hell machine, indeed this guy looks like a satanist, like the satanist games they make.

Not really christian at least.

On 9/10/2017 at 9:26 PM, jkuehlin said:

A lot of musicians seem to want to avoid the coding, scripting, and programming end. Does anyone else here find the design or logic end of the game world just as much fun and intriguing as playing your instrument? 

It can be very helpful to know how to implement audio when working in games. I have to help prep files and implement them into Unity but I cannot program a full game myself. I can read some code, do some simple Json or XML but I'd never really call myself a coder. But I can work with middleware or certain proprietary programs that certain developers use. 

It gives you as the audio content provider more direct control over how the sounds and/or music behave within the game. It can increase your odds of being able to make your audio vision come to life. 

11 hours ago, nsmadsen said:

It gives you as the audio content provider more direct control over how the sounds and/or music behave within the game. It can increase your odds of being able to make your audio vision come to life. 

I got on a design team a while back (which has since fallen apart). I was basically the idiot in the group with a bunch of fancy audio gear, but it at least helped me realize what I needed to learn. It came down to the lead guy asking me 'can this be done or not', and the answer was always 'let me find out'. And then when it came down to the GDD and triggering dialogue/sfx on certain cues, I really really needed to know more about what I was looking at in order to know what was triggering what in the game.

But since I've spent the last 9 months re-focusing my career into learning Unity and taking as many C# classes as I could find online (Udemy has been amazing), at the last local game-dev meet up, I was able to at least follow questions that were being asked and discussion around the table much better. If anything, I had really felt the need to be able to speak the same language as other developers. Because ultimately, the service industry component of any audio business is understanding someone else vision. I felt terrible holding the other guys back because they had to re-translate every sentence as if they were talking to an air headed drummer lol.

In the meantime, I finally got my new audio facility open (lost the last one two years ago in a nasty fire). Have 3 staff and intern now, getting ready to launch a killer webpage, and  keeping the lights on with a steady stream of commercial music, advertising and broadcast clients while I'm making the transition to games. 

Ps....Nate, and immensely grateful to you and Brian (the Game Sound Con guy) for your pointers a year ago how to get started in this biz...I've followed your guy's recommendations as closely as I can. (Though I haven't touched middleware yet, because I'm still working on getting grounded in the basics for now). Thanks again!

On 9/27/2017 at 12:04 PM, trjh2k2 said:

IMO in order to do sound right in a game, you need either a programmer with some audio knowledge, or an audio person with some game dev knowledge, so that at least one person involved can be the bridge between those two worlds. 

Who gets paid more? The guy who designs it or the guy who implements it?

Lets say between 2 guys both working on the same project...one who has a basic knowledge of audio but thoroughly understands the process of implementing it. The other who has a tremendous knowledge of all things audio (tracking, mixing, editing, design, composition, foley, and dialogue), but has a only a basic knowledge of middleware and not a whole lot more.

If they are BOTH on the same project, who is most likely getting the bigger paycheck?

7 minutes ago, trjh2k2 said:

but what does that have to do with anything?

Your awareness of the demand for certain skillet specializations has enormous impact on your marketing, business strategy, career path, direct competition, and what you can or can't offer a team.

9 minutes ago, trjh2k2 said:

What's more important, the pay scale or the quality of the output? 

Thats like asking what's more important, an ignition or a gas pedal. Both the skill set and the pay scale are necessary parts of a system, and if the engine lacks either it doesn't run. You get zero output if you pay zero dollars.

14 minutes ago, trjh2k2 said:

Ideally, I'd want BOTH of those people on the team, so that they can meet eachother half way, be able to speak the same language, and produce the most appropriate result for the project.

Great. So do I. The original question is which is worth more money.

16 minutes ago, trjh2k2 said:

I guess better way to put it is that there's any number of reasons why one might get paid more than the other, 

Such as?