Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

B1900 sound problem.

Featured Replies

Hey all,First of all this is a different problem to the one that's already been discussed (clicking turbine).This one is a long pause in the sound when the engines are brought out of a high power state and are winding down to idle and it only happens when in spot view. To hear this sit on the ground and wind the engines up to full. Once there (and stable) pull the power all the way down as if just after touch down (i.e. don't inch it back real slow). As you hear the prop sound get deeper as the rpm drops there should be a pause of at least a couple of seconds, after that the normal sound returns.I've noticed this happens at around the time both the turbine and propeller RPM are dropping below the green bars.Anyone else getting this, if so how do you go about fixing it?CheersDavidP.s. While I'm here and to save cluttering up the forum. PMDG, any chance you can add a 'start cold and dark' function to the 737 Styles Menu when you release the 8/900? Pretty please :)

Bump,Getting lost down the pages.David

Bumped again,Is no-one else having this problem?David

No, but I hear a very obvious 'loop' in one of the sounds when I throttle back to cruise power. I've tried the turboprop sound enhancement for the King Air in the library, but it seemed a little too quiet to me (Not that I known anything about what it sounds like on a 1900's flight deck) so for now I'm sticking with the PMDG sound.The pause in the sound isn't anywhere near the two seconds you talk about, it's just an obvious decrease in the sound level when that particular .wav file loops.BlairCYOW

Hey Blair,Different problem your talking about. I also get the 'looping error' when at cruise power, this problem is a different one. This happens when the engines are winding down from high(ish) power settings to idle and it only occurs in spot plane view. It happens when the RPM of the blades is reducing below the green line and the tone from the blades gets deeper. I've tried it out on a second machine that uses a different sound system and I got it there too.Try this, go into spot view and perform a rejected take off at 60 kts (standard full power take off) but don't use reverse thrust, just brakes. You should get a pause in the sound of the props but will continue to hear the turbine whine.Can you try this and let me know?ThanksDavid

Yes, I get the same thing, but I had never noticed it until I followed your instructions so it's really not much of an issue for me. (If I'm rejecting a takeoff, my mind might be elsewhere :-) )It is odd though.

Hey,I hear it even at lower power setting, e.g. if I'm taxiing from spot view looking at the scenery. The RTO was just the easiest way to demonstrate it. It's not a real big problem, just weird.CheersDavid

I have also noticed this pause after I have just landed and used some reverse thrust to slow the bird down. There is quite a long pause before the engine sound settles and matches engine behavior. I managed to sort the other looping problem out myself, but this could be a sound.cfg config that needs to be adjusted, and that is a little more complex I think. But I might give it a try and see.Philip.

Hey Philip,If you can figure it out will you let us know? I've never done very much with Sound.cfg's myself so any help would be appreciated.CheersDavid

I'd love to know how you fixed the sound looping problem too.BlairCYOW

Bumped (sorry, but I want to fix this),Any news Philip (or PMDG)?CheersDavid

Hi David, sorry - was off-line for the weekend, and did not get around to looking at the sound file. Hopefully PMDG will address all of these issues, but I will try to solve this in the mean time.Philip.

Hey Philip,No worries, it was just getting lost down the pages. AFAIK PMDG haven't said bo-peep about this so far, I don't doubt that they're aware of it though (must be blind if they don't with all these bumps I've been doing :)).I'll probably have to wait for an official fix though, I can't find my sound editor and the one that comes with nero doesn't open the files :-roll.CheersDavid

Lots of B1900 files are badly looped. It either has half of the second pause on the end, or it simply doesn't fit.The files are in the ADPCM compressed format, and you MUST get a program that will read those files and be able to edit them and save them in the same format (although the files can be saved in the ordinary PCM). I did it in the studio on the Steinberg Wavelab, but anyone at home with Cooledit, Wavelab, and any a bit better sound editor could do it. The program must be able to loop-playback the files so that you can hear how it sounds.I corrected all my files, but PMDG informed me that they are not allowed to post those files on their site. And I am also now allowed to send those files to anyone, but, here's a short how-to on editing these files:1) Open the file, and zoom in so much that you can see the wave, so much that on the whole screen you see something like: / / / /2) On the beginning of the file, see that the file begins on the ZERO point. Meaning, the wave is not either up or down, it's in the middle. Yes, it can and must afterwards go up or down, but the start HAS to be on the zero point. Though, remember if it's going up or down after the cut, that's important.3) Go to the end of the file, also zoomed in. Delete any empty space, where you don't see the waveform (that is those half of the second I'm talking about in some files, that most users notice) and then, cut the waveform again, also on the zero point, BUT try to make it so, that if on the beginning it's continuing up, then on the end should be coming from below and of course vice versa. Because logically, waveform usually goes up and down and up and down...(not all the time equally, but pure sinus wave goes up and down in the same speed).4) Now, try playing the file, in the looped mode. Close the eyes and try hearing the cut. If you don't locate it, you're good. Some people hear more, I'm very sensitive (my job is an audio engineer), so I was editing this until it was sounding 100% perfect.Just one little thing: when you soom out, and see already a dark wave, and say it is black every 1-2cm (inches), then you will also want to make the cut that makes the whole wave consistens, meaning if on the beginning it begins with this dark "part", then on the end, you will NOT cut it in the middle of another "dark part". Sorry, if you don't understand this, I really can't explain it better. But I hope that this helps you to change the worst errors!Now, there is nothing more I could explain, it's up to you to play with the cuts, and make them sound better!Enjoy!

Thank you Word Not Allowed for the time and effort you put into your reply. Unfortunately I don't have access to that sort of sound editing program.I really think this should be PMDG's responsibility to fix anyway. I know it's an "express" package, but it's still payware and it seems a bit ridiculous to be searching around for a freeware sound file to replace one I paid for.BlairCYOW

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.