Post by Killswitch on Feb 9, 2005 12:23:07 GMT -5
It seems that massaging sounds into working with OFP can be troublesome. Instead of adding to a thread discussing script issues, I thought I might post this here to show you how I do it. I hope it will be of use and help!
First, you need some tools:
Vorbis tools: vorbis-tools (1.0.1) Command line tool to decode/encode/analyse OGG files oggdec, oggenc
OFPEC Editor's Depot sound tools - grab the "WSS File Decoding/Encoding Utils" wssdec, wsscod
For "repairing" WAV files, I use Audacity.
Installation
The quickest way is to copy the Vorbis tools and WSS tools to C:\WINDOWS since that folder is already in the default windows %PATH%. On my machine, I put those command line tools into D:\Program\bin and added that path to the Windows XP %PATH% variable.
With that done, I can now use the tools from the XP command line window (cmd.exe)
Workflow
In short, I do the following:
1) Make a working copy of all the sound files
2) Convert the .ogg:s to .wav
3) Convert the .wav:s to .wss
4) Delete the copies of the .wavs
5) Decode the new wss files back into wav
6) Play the decoded wav:s to see that they are OK
7) Some usually aren't so I load the original .wavs into a sound editor program and export them back to wavs again
8) Repeat #3-6 for the "fixed" wavs
In detail
1) Start+Run, type in "cmd.exe" and open the "DOS" prompt.
2) Change working directory to the unpacked addon:
3) Make a temporary work folder and copy the sound files into it. Do this using the normal windows file explorer
4) Convert all .ogg:s to .wav:
5) Convert all .wav:s to .wss:
6) Delete all .wav:s again (Remember to work with the temporary backup folder here so you don't lose the original wavs)
7) Now, convert the .wss files back into wav:s in order to test them
8) Load the new wav:s into your favourite sound player and listen to them all
9) Hopefully, most of them will come out ok, but there's usually a few that will sound like static or be of 0 kB in size.
10) Find the original of the non-working .wav and load it into your sound editor program (Audacity here)
11) Listen to them to see that they actually were ok from the beginning ;D
12) You might want to convert them into 16-bit mono, 22.050 Hz which seems to strike a nice balance between size and sound quality.
13) In Audacity, there's a "Export to WAV..." menu choice that I use to save the "fixed" wav. I save this into the previously mentioned work/backup folder.
14) Repeat #10-13 for all the broken .wav:s
15) Hop back to the command line and wsscod them again. After that, delete them again and wssdec them back to wavs. Hopefully they will come out alright this time.
In the end, you should end up with a working all-wss collection of the original set of sound files.
Command line? What's that? I want a GUI that does everything for me
Tell you what... find the box that your computer came in and put it back in there.
Sell it and get a Mac in transparent pink or some other colour that suits you. Then forget about OFP and play Sims or something.
Real men use real tools to get the job done.
Girlie-men use GUI tools.
(KS ducks for cover ;D )
Ok, on a more serious note, I think there's a more GUI-oriented workflow possible. In another thread, raedor mentioned the possibility to drag&drop sound files ontop of the coders/encoders so I'm sure one can do all this without having to use the scary command line.
EDIT: rephrased the 16 bit/22 kHz sound format recommendation. Other sample formats are quite possible to use. 16bit/22kHz/mono is nice for file size/quality.
First, you need some tools:
Vorbis tools: vorbis-tools (1.0.1) Command line tool to decode/encode/analyse OGG files oggdec, oggenc
OFPEC Editor's Depot sound tools - grab the "WSS File Decoding/Encoding Utils" wssdec, wsscod
For "repairing" WAV files, I use Audacity.
Installation
The quickest way is to copy the Vorbis tools and WSS tools to C:\WINDOWS since that folder is already in the default windows %PATH%. On my machine, I put those command line tools into D:\Program\bin and added that path to the Windows XP %PATH% variable.
With that done, I can now use the tools from the XP command line window (cmd.exe)
Workflow
In short, I do the following:
1) Make a working copy of all the sound files
2) Convert the .ogg:s to .wav
3) Convert the .wav:s to .wss
4) Delete the copies of the .wavs
5) Decode the new wss files back into wav
6) Play the decoded wav:s to see that they are OK
7) Some usually aren't so I load the original .wavs into a sound editor program and export them back to wavs again
8) Repeat #3-6 for the "fixed" wavs
In detail
1) Start+Run, type in "cmd.exe" and open the "DOS" prompt.
2) Change working directory to the unpacked addon:
>C:
C:\> cd <path to OFP>
C:\...\...Flashoint\> cd <path to MCAR mod folder>
C:\...\...Addons\> cd myaddon_sounds3) Make a temporary work folder and copy the sound files into it. Do this using the normal windows file explorer
4) Convert all .ogg:s to .wav:
for %i in (*.ogg) do oggdec %i5) Convert all .wav:s to .wss:
for %i in (*.wav) do wsscod %i6) Delete all .wav:s again (Remember to work with the temporary backup folder here so you don't lose the original wavs)
del *.wav7) Now, convert the .wss files back into wav:s in order to test them
for %i in (*.wss) do wssdec %i8) Load the new wav:s into your favourite sound player and listen to them all
9) Hopefully, most of them will come out ok, but there's usually a few that will sound like static or be of 0 kB in size.
10) Find the original of the non-working .wav and load it into your sound editor program (Audacity here)
11) Listen to them to see that they actually were ok from the beginning ;D
12) You might want to convert them into 16-bit mono, 22.050 Hz which seems to strike a nice balance between size and sound quality.
13) In Audacity, there's a "Export to WAV..." menu choice that I use to save the "fixed" wav. I save this into the previously mentioned work/backup folder.
14) Repeat #10-13 for all the broken .wav:s
15) Hop back to the command line and wsscod them again. After that, delete them again and wssdec them back to wavs. Hopefully they will come out alright this time.
In the end, you should end up with a working all-wss collection of the original set of sound files.
Command line? What's that? I want a GUI that does everything for me
Tell you what... find the box that your computer came in and put it back in there.
Sell it and get a Mac in transparent pink or some other colour that suits you. Then forget about OFP and play Sims or something.
Real men use real tools to get the job done.
Girlie-men use GUI tools.
(KS ducks for cover ;D )
Ok, on a more serious note, I think there's a more GUI-oriented workflow possible. In another thread, raedor mentioned the possibility to drag&drop sound files ontop of the coders/encoders so I'm sure one can do all this without having to use the scary command line.
EDIT: rephrased the 16 bit/22 kHz sound format recommendation. Other sample formats are quite possible to use. 16bit/22kHz/mono is nice for file size/quality.
