Create Ambient Sounds Rw

Hello, I need to know to convert sounds to .wav format, the type of bit channel that is compatible with the game.

 

I only remember these settings that I assume are correct for the conversion of sounds to .wav and that when implemented in the game they are heard: Sampling rate: 44100hz Type: Jumpsuit

 

There has long been a program that converts *.dav files (Sound files that TSC sees) in to a *.wav file.
https://rail-sim.de/forum/filebase/entry/31-dav-audio-decoder/

There is another version that will convert *.wav to *.dav but I have not tried it
https://rail-sim.de/forum/filebase/entry/9119-davdecoder-cli/

 

I understand but my goal is to generate audio in any format and convert it to .wav with the correct settings so that it works in RW.

 

I have no idea what Jumpsuit is as it does not appear when you google for Sampling rate: 44100hz Type: Jumpsuit

 

I Sorry, is Mode: mono sound.

 

Either way I don't think TSC will see a WAV file- most are DAV files

 

And after converting the audio from wav to dav, do I have to create the ambient audio control and sound blueprints in TS's blueprint editor 2?

 

Are the following values correct for converting text to audio .wav format? Program used by Loquendo TTS Director.

 

Result

 

Speaking as someone who has done lots of work on TSC sounds for narrow gauge. TSC will work with .wav files just fine. You just need to make sure that your proxyxml file has .wavs rather than .davs referenced. DavDecoder works both ways - it can decode .davs and can encode .wavs ( although there really is no need to do this). I use a lot of .wavs in my sound sets.
To make / modify sound files I use Audacity which has got lots of capability. For sound files that contain trigger points ( like Chuffs ) you will need a program like CueLister as I have never got the cues in Audacity to work correctly.
Sound file editing is more of an art than science as what you hear in your sound editor sometimes seems less than optimal when heard in game, especially true of cue'd sounds like chuffs. Ambient sounds are a very easy thing to produce as they have no cues etc.
However, unless for personal use sound files downloaded from the internet or modified from those created by others are generally very easy to identify and so intellectual copyright issues really come into play here if you plan on wider release.

 

And yes, you will still need to create a proxyxml files and a dot.bin for the file. I would suggest that rather than starting that from scratch do this. Make your sound and save it as a .wav file. Then simply copy and then edit an existing proxyxml from another ambient Kuju default sound. Its a lot easier. Then SERZ the matching relevant .bin file for your copied proxyxml, edit it to refer to your new proxyxml file name. SERZ it back to a .bin file and bingo. And the little sound placement cone object will stay as the default Kuju one making placement of the sound much easier.

 

I'm lost in that audio blueprint.
I have no idea how the sound is configured to work, rather it is heard on the TSC.
Screenshot of Ambient Audio Control Blueprint:

In this screenshot, the audio mesh and xml of Scenery blueprint removed completed