Crassus
01-15-2002, 09:55 PM
Technically, this should have gone in my last post, but as not to create confusion, I'm making a new thread:
Pitch changing.. what I mean by that is when throttling up and down, MSTS bends the pitch of the engine .wav file up or down to simulate a smooth blend between .wav files..
Now, a few people have mentioned in other posts about a way to increase the volume of the external view sound file is to increase the actual volume OF the sound file in an editor. Now, at first, this seemed to be the obvious answer, and in fact, I tried that before ever reading people's posts on the subject. However, after I had done so, I noticed the pitch bending effect had been lost. I'm also guessing this has something to do with cue points, as the cue points are lost when increasing the volume of the horn as well for looping.
This sucks. :) Is there any way to stop it? What *I'm* guessing is I would have to use a sound editor that actually has the capability of cue points, and thus it would recognize them in the sound file, retaining them. This is all conjecture, so someone tell me if I'm good at guessing these things.
If indeed it's to do with cue points, am I also guessing correctly that the pitch change happens after a cue point, basically letting it complete the sound file, then jumping to the next and begins looping that one?
Pitch changing.. what I mean by that is when throttling up and down, MSTS bends the pitch of the engine .wav file up or down to simulate a smooth blend between .wav files..
Now, a few people have mentioned in other posts about a way to increase the volume of the external view sound file is to increase the actual volume OF the sound file in an editor. Now, at first, this seemed to be the obvious answer, and in fact, I tried that before ever reading people's posts on the subject. However, after I had done so, I noticed the pitch bending effect had been lost. I'm also guessing this has something to do with cue points, as the cue points are lost when increasing the volume of the horn as well for looping.
This sucks. :) Is there any way to stop it? What *I'm* guessing is I would have to use a sound editor that actually has the capability of cue points, and thus it would recognize them in the sound file, retaining them. This is all conjecture, so someone tell me if I'm good at guessing these things.
If indeed it's to do with cue points, am I also guessing correctly that the pitch change happens after a cue point, basically letting it complete the sound file, then jumping to the next and begins looping that one?