New sound engine question or two.

[Panzertard]

LWR, not RWR I hope? We're talking about BS here, right?

[sobek]

LWR, not RWR I hope? We're talking about BS here, right?

 

What else is there? ;)

[CAT_101st]

You know what I am just so use to posting in here I forgot I was talking about FC2. The BS sounds are perfict for me.

[Vympel]

Dear guys,

we definetely can't please all the people al the time ;)

That's what Sounds/sdef/.sdef is for.

It's much easier to tweak corresponding sdef-files instead of the samples.

 

Can I tweak this file to make the Vikhr launch a little louder and the flare release audible in the cockpit?

[c0ff]

Sounds/sdef/.sdef is the documentation for all Sounds/sdef/*.sdef files.

It should not be edited.

All other .sdef files are editable and are settings for respective game sounds.

[Woots]

I think the only way is to completely remove 3 wav files in DCS Blackshark\Sounds\Effects folder:

 

EngineTV3117.wav

Enginetv3117inL.wav

Enginetv3117inR.wav

 

 

I went ahead and removed them. Takes away all the white noise and you're left with the thump thump thump of the rotors. Kinda soothing actually. It all boils down to personal preference.

[funkee]

I went ahead and removed them. Takes away all the white noise and you're left with the thump thump thump of the rotors

 

Cuz you need to use modded RotorKA50Dyn.wav file. Sounds cool to me. I've uploaded it for you :P

http://www.speedyshare.com/files/22528889/RotorKA50Dyn.wav

Edited May 19, 2010 by funkee

[Frederf]

I may have missed the peculiarities of the bug conversation but I removed the mentioned files and was not happy with the results. So far I just wanted to change the balance between the blade sounds and the Vikhr/flare launches. It's still a bit out of whack but my autoexec.cfg reads: sound.cockpit_world_volume = -12 sound.cockpit_world_lowpass = 4000 And I'm happy enough with it.

[Nate--IRL--]

You could try adding "Gain = 2.0" (Choose a value to suit) to both Flare.sdef and MissileLaunch.sdef.

 

Nate

Edited May 19, 2010 by Nate--IRL--

[Frederf]

I'll give it a shot. I think it's the low-pass filter mainly since there isn't much bass in those sounds compared to the rotors.

[Nate--IRL--]

I have interchanged those two files. Is this this way how it should be done?

 

To be honest I did the same, along with editing the autoexec.cfg to increase external sounds, but I'm not totally happy with it. The reason is that now Rotors when stressed/loaded, in cockpit, sounds correct, but in external views and sound from your wingman is wrong (ie Stressed/loaded Rotors play unstressed/unloaded sound)

 

What is really needed are sdef files (RotorKa50In.sdef & RotorKa50DynIn.sdef) for the engine sounds in cockpit, in order to correct and control better what is heard in cockpit.

 

Nate

[sweinhart3]

I added this line in my cfg file and now I can hear flare ejection and outside damage. Its not loud but you can hear it.

sound.cockpit_world_volume = 25

[Nate--IRL--]

I did some more flying yesterday, and I noticed that the rotor stroke sound increases a lot with speed. The bass shaker was doing its work. Overall, the in-cockpit sound enviroment is a lot more natural than before. I'm liking it very much.

Although the two files mentioned above are still interchanged in my installation, have not time for tests! I'm wondering how would it sound without that alteration, I did it right after patching because I read this thread before having time to patch.

 

Simply play the two wav files in windows media player. The Default RotorKa50Dyn.wav will have more bass than RotorKa50.wav

 

Remember that:-

RotorKa50Dyn.wav is played in external views for loaded rotors and RotorKa50.wav is played for unloaded rotors (This is correct and Normal)

RotorKa50.wav is mistakenly played in cockpit for loaded rotors and there is no sound for Unloaded rotors.

 

By fixing the Cockpit sound, the external view sounds are now incorrect. This to me is a fair compromise.

 

Nate

[funkee]

I think the best compromise would be to remake some sounds since they dont fit with the new sound engine and there are too many problems for too many users.

 

Additionaly we should get abbility to adjust the volume of more cockpit sounds, especially aircraft engines.

Edited May 22, 2010 by funkee

[Nate--IRL--]

Funkee you can adjust the engine sounds in cockpit by editing the *.sdef files.

 

sdef names for cockpit sounds have "In" suffix.

 

The ones you need: "APUIn", "APUBeginIn", "EngineTV3117InL", "EngineTV3117InR", "Gun2A42In", "Gun2A42LowIn"

 

By adding the line "gain = 1.0" you can control the volume of those particular sounds (1.0 is normal volume, higher or lower numbers = increased or decreased volume)

 

For example I have added "gain = 0.3" to "APUIn.sdef", "APUBeginIn.sdef" in order to quieten the APU sound in cockpit.

 

Nate

[martinistripes]

I've been in the back of choppers dispensing flares plenty of times. Scares the sh*t out of you if you're not ready for it! Loud and bright. Seen a few guys just about jump out their seat! :lol:

 

But with a pilots helmet on... couldn't say.

[Tangolima600]

Anyone notice, or maybe it's just me, but when starting up the number two engine after #1 is running idle, it sounds like the sound just starts over again, the same quiet as #1 spools up as opposed for the running #1 engine and hearing another layer of noise spooling up.... kind of hard to explain but hopefully someone will catch on what I'm saying.

[Nate--IRL--]

Anyone notice, or maybe it's just me, but when starting up the number two engine after #1 is running idle, it sounds like the sound just starts over again, the same quiet as #1 spools up as opposed for the running #1 engine and hearing another layer of noise spooling up.... kind of hard to explain but hopefully someone will catch on what I'm saying.

 

Yep, I've noticed that too. It's almost like a single wav file being used for engine spoolup that stops abruptly and replayed from the start, when starting to spool the 2nd engine.

 

However looking at the sdef and effect files, this doesn't seem to be how it is implemented. If I were to guess, it seems that EngineTV3117.wav is being used as the spoolup sound, but not as the main engine sound in cockpit.

 

Engine sounds in cockpit are provided by enginetv3117inl.sdef & enginetv3117inr.sdef, and the external (filtered) enginetv3117.sdef. There is no separate specific spoolup sound, though it does sound like a separate sound is used.

 

There is a broken sdef enginetv3117in.sdef that refers to a wav file that doesn't exist (not sure if this is by design)

 

I'll dig around later to pinpoint the issue.

 

Nate

[martinistripes]

Anyone notice, or maybe it's just me, but when starting up the number two engine after #1 is running idle, it sounds like the sound just starts over again, the same quiet as #1 spools up as opposed for the running #1 engine and hearing another layer of noise spooling up.... kind of hard to explain but hopefully someone will catch on what I'm saying.

 

Yeh, I hate this. I was going to mention it a day or to ago in 'problems and bugs' forum, but was certain I'd already seen it mentioned somewhere. No doubt ED are on to it. It's quite obvious. The only guys that won't notice are the ones who start hot.

 

Still, this bug is better than the previous bug. :)

[Nate--IRL--]

OK this is a weird bug but I think I've isolated it. I have temporarily deleted enginetv3117.wav in order to only hear enginetv3117inl.wav & enginetv3117inr.wav in cockpit.

 

Starting up (Left engine First - APU on Rotor brake off).............

Start Left engine - enginetv3117inl.wav is played, tempo and volume increased, to match left engine power.

 

Start Right engine - enginetv3117inr.wav is played, tempo and volume increased, to match right engine power.

enginetv3117inl.wav is reset and then played, tempo and volume increased, to match right engine power.

 

 

Starting up (Right engine First - APU on Rotor brake off).............

Start Right engine - enginetv3117inr.wav AND enginetv3117inl.wav are played, tempo up and volume increased, to match right engine power.

 

Starting Left engine - No new sounds played.

 

Edit:- When I tested this, the enginetv3117inl.wav used was a renamed BulletHit.wav to easily differentiate it from enginetv3117inr.wav

 

So, it seems the right engine determines the in-cockpit engine sounds for both engines. It's a bug alright.

 

Nate

Edited June 16, 2010 by Nate--IRL--

[martinistripes]

+1 to you sir. Have I seen you over at subsim by any chance?

[Nate--IRL--]

+1 to you sir. Have I seen you over at subsim by any chance?

 

It's been ages since i've been there, but I do try to key the flight sim section up to speed on the Latest from ED........ which reminds me.......

 

Nate

[SuDepp]

....would be great if we all post our sound related hardware!

 

I mean, an onboard soundchip and a weak 2.1 will bring a quiet different immersion to you, then a dedicated soundcard with a upmarket headset.

 

Thats extrem important especially when tweaking the lowpass setting and to compare our different settings......

 

Just my thoughts ;)

 

Greets

S@uDepp

[mobias]

....would be great if we all post our sound related hardware!

 

I mean, an onboard soundchip and a weak 2.1 will bring a quiet different immersion to you, then a dedicated soundcard with a upmarket headset.

 

Thats extrem important especially when tweaking the lowpass setting and to compare our different settings......

 

Just my thoughts ;)

 

Greets

S@uDepp

------------------------------------------

I'm not so sure dude- I thought I just read in here somewhere that since they implemented 1.0.2. the sound is all coded as software, to run on CPU's Core2 or something like that [if you have a dual or above CPU], therefore, that sounds to me like its now bypassing all our soundcards! :( I'd agree what's important is what's pumping out the sound, in my situation i'm blessed with the sweet sennheiser PC 350's...compliments of my wifey. :music_walkman:

[Nate--IRL--]

I suspect that's completly wrong, but someone more knowledgeable should give us a better explanation.

 

The CPU handles all of the sound processing now, calculating Doppler shift, speed of sound, ect, which is then sent to the sound card to output. The reason for the CPU doing this job is compatibility, there is no need to support specific API's just for sound processing, as it is all done in software now.

 

Nate