This document explains the process of converting recorded master .wav files to the proper format for use on Intervoice systems using the Sound Forge Batch Converter.
Batch Converter overview
The Sound Forge software creates standard .wav files, although other information is embedded in the header of these files, such as recorder name, loudness level, and script text. Before these master files can be placed on a runtime InterSoft IQTalk or VoiceXML system, they must be converted into the Intervoice runtime format:
- For InterSoft IQTalk systems, the compressed runtime format must be 32 KBps (8 KHz, 4-bit) ADPCM .ivc.
- For VoiceXML systems, the compressed runtime format must be 64 KBps (8 KHz, 8-bit) A-law/µ-law .wav.
You can convert all of the master files to the proper Intervoice runtime format in a single step using the Batch Converter 5.0. However, before you perform this step, you must configure the batch script (Sound Forge 5 through 7) or batch job (Sound Forge 8) to perform the required processing and conversion steps in the correct order. Once you create and install the batch script or batch job file on the Batch Converter, you can use it again whenever you need to convert a group of master .wav files to the compressed InterSoft IQTalk (.ivc) or VoiceXML (.wav) runtime format.
Example batch file overview
Intervoice provides an example batch file to simplify the initial creation for the conversion process. They are:
- INTV Example Batch Script V7 (for Sound Forge 8) INTV Example Batch Script V7 (-20dB) u-Law.bj.
- IVB Example Batch Script V6.0 (for Sound Forge 5 through 7) IVBExampleBatchScriptV6.bcs.
The example batch files completely predefine the plug-in steps required to convert Intervoice master files into InterSoft or VoiceXML runtime files. They perform these processes:
- DC offset removal
- Silence trimming
- Equalization
- Volume normalization
- Resampling to 8 KHz
- Format conversion to ADPCM .ivc or m-law/A-law .wav format and insertion of Intervoice headers.
Note The script or batch file must contain all of these steps to correctly convert the master files to runtime files.
The DC offset removal, Silence trimming, and Resample steps are basic Intervoice format operations. These operations should never be modified in the batch file to be used for master-to-runtime conversions. They are critical for the correct conversion from .wav files to the InterSoft or VoiceXML runtime format. Changing these preset steps could affect audio quality or make the runtime files unusable.
The Equalization, Volume Normalization, and Format conversion steps can be modified or tailored to a particular recording talent’s voice or to a particular application. If you make any changes to the batch file, you should never change the order of the instructions.
Modifying the batch file
The Intervoice example batch files are examples. Many of the plug-in steps are standard and are required in any Intervoice master-to-runtime conversion script. You do not need to change these standard steps for any master-to-runtime conversion job. However, there are several steps that can be changed to customize the master files for a specific runtime application.
The most common changes made to the examples are:
- Speed — All runtime messages need to be in 24Kbit (or 32K or 64Kbit) format.
- Encoding — All runtime messages need to be in A-law (or m-law) format.
- Volume level — All messages are too soft (or too loud).
- Equalization — All messages sound too tinny (or too much bass).
To change these parameters in the batch file, edit the parameters of the appropriate plug-in in the example file using the Batch Converter plug-in chain editor. Once you have changed a plug-in or file format, save the new plug-in under a new name, and then save the modified file under a new name. You should not make changes to the original example batch file. The new name should reflect the changes made from the example batch file; for example, 24K A-law –15dB volume 3dB 2000Hz treble boost for Mary batch file.
After you modify the batch file, you can test some of the runtime files produced by the script on an actual system, played through a telephone handset. Intervoice recommends “actual system” testing of runtime message files to verify actual usage conditions. You can play the messages through the high-fidelity speakers of a PC sound system, but they will sound different than the same messages played through a telephone handset. In some cases, messages that sound fine played on a PC will sound muddy or tinny through a telephone handset. Alternatively, messages that sound bad on the PC will sound fine through a handset.
If the runtime messages are not satisfactory (for example, too loud or too tinny), modify the batch file, and save it with a new name in the Batch Converter program. Then rerun the conversion process using the new script on the original master messages. You should be able to fix any audio problem with the Batch Converter, except for incorrectly spoken messages, so you should rarely have to re-record master files. Always be sure to keep a copy of the master messages, so you can create new runtime messages with different characteristics at any time.
Converting .ivc files to m.### format (InterSoft systems)
For InterSoft IQTalk systems, the Batch Converter produces message files with an .ivc extension. This extension is important for Windows to recognize the message files as Intervoice format files, but the InterSoft runtime system does not recognize messages with an .ivc extension. To convert the .ivc files to m.### files (such as m.500), use the CRVoice2 utility.
The CRVoice2 utility converts all .ivc files in a specific directory to the m.###. You can specify for CRVoice2 to either make copies of the .ivc files and convert them to the m.### format, or to replace the .ivc files with the equivalent m.### files.
[an error occurred while processing this directive]