Could I ask those responsible for recording the voices for v5 to try and get the words and phrases sounding brisk and realistically clipped? I say this because in v4 there are one or two pedestrian sounding voices which say things one (pause) word (pause) at (pause) a (pause) time. This not only doesn't sound very realistic but takes up time. I appreciate that all those providing the voices are doing it voluntarily and we users are grateful for that but a quality product deserves quality in every area. :( Iain Smith

Could I ask those responsible for recording the voices for v5 to try and get the words and phrases sounding brisk and realistically clipped? I say this because in v4 there are one or two pedestrian sounding voices which say things one (pause) word (pause) at (pause) a (pause) time. This not only doesn't sound very realistic but takes up time. I appreciate that all those providing the voices are doing it voluntarily and we users are grateful for that but a quality product deserves quality in every area. :( Iain Smith

Wouldn't that "one (pause) word (pause) at (pause) a (pause) time" be a result of joining the recordings into one "sentence"? I went through the folders and found hundreds of wav files. Each of them holding a piece, for example "Turn right heading 125" would actually mean that "turn.wav", "right.wav", "heading.wav", "1.wav", "2.wav" and "5.wav" would be taken at that time and played one after another to create single sentence... That's where the (pause) appears as the system needs to close previous wav, clear allocated memory and open another wav file to play it... I might be mistaken 'cause I'm no expert in this field but that's how I would think it works...David.

Wouldn't that "one (pause) word (pause) at (pause) a (pause) time" be a result of joining the recordings into one "sentence"? I went through the folders and found hundreds of wav files. Each of them holding a piece, for example "Turn right heading 125" would actually mean that "turn.wav", "right.wav", "heading.wav", "1.wav", "2.wav" and "5.wav" would be taken at that time and played one after another to create single sentence... That's where the (pause) appears as the system needs to close previous wav, clear allocated memory and open another wav file to play it... I might be mistaken 'cause I'm no expert in this field but that's how I would think it works...David.

it's a balancing act. no one is going to record 12000 wavs, which what it would be, if i had a wav for 010, 015, 020, 025..., climb fl240, climb fl250, climb fl260..., descend 8000, descend 7000, ...we all agree that dead air at the front and back of the wavs are problematic. we have learned a lot in 10 years. will it be perfect, probably not. will it be better, that is what we are striving for.

Pick one controller or pilot. Adjust the speed slider just a bit to the right from the recommended left position. See if your PC can handle that. If you get clipping or performance stutters set it back to basic.The other thing is to insure you have enough ram to allow catenation of the wav files. If you are getting page swapping then your physical ram might be two low. Your OS and version of FS will affect this, as well as your ram. Your CPU clock speed needs to be high as well since multiple cores are not used well in FS.Make sure you are not using an on-board audio system as that can drain performance.

Pick one controller or pilot. Adjust the speed slider just a bit to the right from the recommended left position. See if your PC can handle that. If you get clipping or performance stutters set it back to basic.The other thing is to insure you have enough ram to allow catenation of the wav files. If you are getting page swapping then your physical ram might be two low. Your OS and version of FS will affect this, as well as your ram. Your CPU clock speed needs to be high as well since multiple cores are not used well in FS.Make sure you are not using an on-board audio system as that can drain performance.

Thanks Ron. I have 2GB of PC6400 DDR2 RAM which should be enough for FS9 and I have a separate sound card.I'm convinced this is not a computer problem but a matter of different styles between controllers. Some have recorded the words or phrases more briskly than others and sound more convincing as a result.Iain Smith

The stock FSX ATC voices are superb IMHO...how did they do it?

The stock FSX ATC voices are superb IMHO...how did they do it?

there was a blog post about how they did it a while ago. they have a significant larger budget than i do. but we will keep trying to do better...jd

The stock FSX ATC voices are superb IMHO...how did they do it?

Can a smaller gap between words do the trick? Or having pre-recorded some complete phrases? For example, instead of having wavs for "line", "up", "and" and "wait" and then joining them, why not having a single wav for "line up and wait"? (it's only an example)Best regards from Colombia,Luis Miguel

The stock FSX ATC voices are superb IMHO...how did they do it?

Like JD said it's a matter of time and budget. It takes studio quality recording conditions, countless hours of optimizing the files and tweaking the engine that is used to combine and output the voice. Also the voice library, i.e. number of phrases is significantly larger with the MS ATC.Try doing that with tens of volunteers from all around the world!

Many of your examples are single waves. One such is "taxi into position and hold".Also try increasing the speed sliders for each voice but that can cause problems so just try a few.

Can a smaller gap between words do the trick? Or having pre-recorded some complete phrases? For example, instead of having wavs for "line", "up", "and" and "wait" and then joining them, why not having a single wav for "line up and wait"? (it's only an example)Best regards from Colombia,Luis Miguel

The stock FSX ATC voices are superb IMHO...how did they do it?

Can a smaller gap between words do the trick? Or having pre-recorded some complete phrases? For example, instead of having wavs for "line", "up", "and" and "wait" and then joining them, why not having a single wav for "line up and wait"? (it's only an example)Best regards from Colombia,Luis Miguel

Many of your examples are single waves. One such is "taxi into position and hold".Also try increasing the speed sliders for each voice but that can cause problems so just try a few.

All my voice sliders are over to the left which is the fastest I believe.Iain Smith

JD.would it be possible to a list of volunteers to record the voices? More voices= more realistic experience. IMO

Can a smaller gap between words do the trick? Or having pre-recorded some complete phrases? For example, instead of having wavs for "line", "up", "and" and "wait" and then joining them, why not having a single wav for "line up and wait"? (it's only an example)Best regards from Colombia,Luis Miguel

line up and wait is a single phrase.taxi into position and hold is a single phrasefly heading is a single phrasedescend and maintain, climb and maintain, cross 40 miles, etcif you want to see what is recorded as single words, and what is recorded as a phrase, start viewing the .txt files in \script\controllerscripts and \script\pilotscriptsi only broke phrases apart when it was necessary.

JD.would it be possible to a list of volunteers to record the voices? More voices= more realistic experience. IMO

i hope everyone that posts here about the wavs, will be the first in line to volunteer to record. typically not every volunteer is accepted due to poor quality of their recording, their speech characteristics (too slow, too mellow, etc).i'm not able to compensate these volunteers as handsomly as microsoft, but i do give you a copy of v5 if we use your voice set.not bad for 3-5 hours of work.jd