Modified Wav File Not Playing Back (in MSTS/OR)

Official support for: acondigital.com
meeshu
KVRer
Topic Starter
2 posts since 20 Feb, 2022

Post Sun Feb 20, 2022 1:51 am

Running Acoustica version 7.3.22 under Windows 7 64 bit.

Tried a simple modification of a wav file by reducing a couple of frequency components using Equalize 2. On saving the modified wav file, a message box appeared from Acoustica that stated something about the file being clipped -

"Clipping occurred during encoding. Please use a floating point rendering format or limit the signal to 0 dBFS".

Not quite sure what this message was all about but I ignored that message for now.

Tried "playing" the modified wav file back under Open Rails (train simulator), but I couldn't hear the modified wav sound at all!?

Note that the original wav file is for the external engine sound for locomotives.

It might help to have both MSTS (Microsoft Train Simulator) and OR (Open Rails) installed so that the (modified) wav file can be "played back" by adjusting locomotive throttle to full. The wav file is for maximum locomotive throttle engine sound.

Both the original and the modified wav files played back fine under Acoustica and for other audio editors also! So this suggests that Open Rails doesn't like something about the modified wav file which appears to prevent the wav file from being played, or maybe being played at some much higher frequency and or maybe played at much reduced volume??

This question was asked at Trainsim forum but I'm not expecting much help, at this stage, as this issue may be something beyond their knowledge(?)

x_GE_run8_orig.zip
x_GE_run8_acoustica.zip

The two wav files have been attached (zipped). First file is the original wav file, the second wav file is the Acoustica modified file.

Maybe a comparison between the two files can determine what might be causing playback issues under Open Rails?

Thanks for all constructive comments.
You do not have the required permissions to view the files attached to this post.

meeshu
KVRer
Topic Starter
2 posts since 20 Feb, 2022

Post Tue Feb 22, 2022 7:07 pm

After extensive searches on the internet and after some experimentation, it appears that Acoustica saves wav files with the unusual header - RIFFdÓ . . WAVEJUNK.

This is not the usual type of wav file where the usual wav file has the header - RIFF . Ó . . WAVEfmt .

Apparently some audio editors, like Acoustica, save wav files with this unusual wav file header (RIFFdÓ . . WAVEJUNK)!? Why? This is not clear!?

It appears that MSTS and OR can ONLY read wav files with the usual wav file header (RIFF . Ó . . WAVEfmt ).

In order to get MSTS and OR to read wav files saved with the unusual header RIFFdÓ . . WAVEJUNK, the wav files have to be opened in OTHER audio editors that save wav files in the usual format (wav files with the header - RIFF . Ó . . WAVEfmt ). The wav is then selected and then re-saved, this time with the usual wav file header of RIFF . Ó . . WAVEfmt !

This is just a workaround, and is a bit inconvenient and time consuming if processing a lot of files.

Why can't Acoustica save wav files with the usual format of - RIFF . Ó . . WAVEfmt !?

User avatar
stian
KVRian
1299 posts since 1 Jan, 2005 from Norway

Post Wed Feb 23, 2022 1:57 am

Hi!
meeshu wrote: Sun Feb 20, 2022 1:51 am "Clipping occurred during encoding. Please use a floating point rendering format or limit the signal to 0 dBFS".
This message is just a warning that the audio is too loud and will be clipped when converting to PCM when saving.
meeshu wrote: Tue Feb 22, 2022 7:07 pm Why can't Acoustica save wav files with the usual format of - RIFF . Ó . . WAVEfmt !?
The JUNK chunk is allowed and the error seems to be in the software you use to load the audio file. We use the JUNK file to reserve space in case the total file size exceeds 4GB, in which case Acoustica switches to the RF64 standard and hence needs to write additional information in the header.

Best,
Stian

Return to “Acon Digital”