Snap, Crackle, Pop....

[Clipper]

Anyone have experience with aircraft sound files making crackling and popping noises? I downloaded some Comets Hagar found, and they came with a seperate sound folder. I installed correctly, but I'm getting some really annoying static sounds. I tried downloading the file a second time, same results. Any diagnostic feedback would be greatly appreciated, as the planes and panels are phenomenal. It would be a pity not to be able to utilize the actual Comet sound file. Thanks.

[jordonj]

Take a look at your event viewer...sometimes that can tell you something...

Do you get this with anything else?

[Papa9571]

Guys....

I have downloaded the Comet sound file from Dave Maltby's site and find your systems do not have a problem. Several of the sound files were recorded incorrectly resulting in overmodulation. This causes the snaps, crackles, and pops you are hearing.

The problems are especially noticable on the sound files for the outside of the aircraft.

The solution is to find a copy of the Avon Engine sound files that are recorded correctly.

[Hagar]

Clipper. After your comments on this I downloaded the Comet sound file to check it out. I don't know if your problem is with internal or external sound. I noticed a definite glitch (rough transition) when you increase/reduce power settings in Cockpit view but only with large throttle movements. I didn't notice anything much wrong with the external sound from Spot view. This could be due to my antiquated sound card or a bug in the sound files or Sound.cfg. As I mentioned earlier, I know very little about FS sound so can't suggest a way over it.

[Clipper]

Jordon, I do see this problem from time to time with other files, but it's rare. Elaborate on the event viewer please.
Papa9571, my search commences. If you run into any let me know.
Thanks for the quick resposes.

[commoner]

Clipper have you tried just opening each sound file? I downloaded them and played one at a time they sound just fine. Maybe it's not the actual files that are the problem..commoner.

PS Mind you what sounds ok to me might sound cr*p to others

[Hagar]

It might be a simple case of tweaking Sound.cfg. That's if you know how to do it of course. I don't mind admitting that I have no idea & leave that to the experts.

[Clipper]

Commoner, that's interesting. What would the procedure be to install them seperately, as opposed to the way I dit it previously as a "common folder"? By the way, the problem is very obvious, to the point the sound is tottaly unplayable.
Hagar, The only thing I know how to tweak is not file related.  ;) Thanks anyway

[Hagar]

This package is set up using the old FSFS Converter principle with the sound in a special folder & Sound.cfg of each variation aliased to it. This is done mainly for convenience & to keep the size of your FS9\Aircraft folder down. You can install that sound package separately by pasting all the WAV files + Sound.cfg into the sound folder of the individual aircraft you wish to use it. Overwrite the existing Sound.cfg when prompted. This shouldn't make any difference.

[Papa9571]

You are welcome Clipper.

The event viewer that Jordan mentions is a log file of everything your computer does. It logs system events, security events, and application events.

To ge to it, if you are running XP, is to right click on My computer.., This will bring up a window that has several choices. You want to click on the Manage choice. That will bring up a window that looks lkike this.





From here you select the event viewer and look at the files located there. These files will tell you what is going on with you system. The only events you should be concerned with is the events that have red circle with an X inside, and you should only be concerned with those if your system is acting strangely.?

The easiest way to see if the sound file is not correct is to run each sound file through windows Media player and have the display set to bars and waves: oscilliscope.

Watch the line that appear there as the sound is playing. If the tops or bottoms are squared off, that file was recorded incorrectly and will probably sound bad during playback. That is the cause of 99% of sound problems. Its like turning your 200 watt stereo system  up to full volume  and listening to the nasty sound coming out of your 100 watt speakers .

I hope thats clearer than mud.

[commoner]

....as I said do they sound ok individually?..if they do then it's probably like Hagar says..the sound.cfg...but I wouldn't know what to tweak .... :-/

[Clipper]

Hagar, I'll try it when I get home this evening. Many thanks...
Papa, Thanks for familiarizing me with the event viewer. I'm sure it'll come in handy! I will test each sound file this evening.
Commoner, I'll do as Hagar suggests and install individually. Didn't you indicate previously that you tried them seperately and all was fine?

[Hagar]

Might I suggest you have a look through the SimV Sound section for Avon or similar jet sound packages & compare them. If you have more than one version of the Comet (4A, 4B, 4C etc.) you could install different sound packages to each of them.

http://www.simviation.com/fssounds.htm

PS. I think by individually Commoner meant playing them in Media Player by double-clicking on the WAV files. Look for any breaks at the beginning or end of the recordings. This sometimes causes these problems.

[Clipper]

Hagar, you're the light in my darkness!
All you guys, your enthusiasm in helping me is appreciated I only hope that one day I can return the same.

[Hagar]

I just opened Sound.cfg of that package to check it out. I couldn't help spotting this.

[FLTSIM]
product_code=FSIM

[SOUND_ENGINE]
number_of_engines=3

It seemed logical to me to try changing the number of engines to 4 like this.

[FLTSIM]
product_code=FSIM

[SOUND_ENGINE]
number_of_engines=4

Please bear in mind that I have no idea what I'm talking about but it seems to make it smoother on my system. :-/

PS. Installing panels or sound packages separately or aliasing to them should make no difference. The FS9 default b777_300 Sound.cfg is aliased to the b737_400 sound like this.

[fltsim]
alias=B737_400\sound

The default b747_400 is also aliased to the 737_400 sound. This seems to disprove my previous theory about number of engines.