G.3. Procedure

In order import audio from an existing Wings system, proceed as follows:

G.3.1. Create Rivendell Groups

In RDAdmin->ManageGroups, create a Group to correspond to each Wings Tab value that exists in the library to be imported, and an additional group to catch any Wings entries that may not have a valid Group. When creating these groups, it is essential that a default cart number range be configured for each group that is large enough to accomodate all anticipated imports.

G.3.2. Locate the 'Wings' Database and Audio Files

These can be mounted from a remote system if needs be. Read-only access is adequate, as the script does not modify these items in any way.

G.3.3. Verify Available Disk Space

Verify that enough disk space is available in the '/var/snd/' directory to accomodate the audio to be imported. You should have at least the amount of space currently occupied by the Wings ATX files, plus 5 percent additional.

G.3.4. Invoke Script

Start up the script, as described in Section G.2, “Usage”. The script will print progress reports as it proceeds, or notify you of error conditions as required.

G.3.5. Clean Up

If desired, use RDAdmin->ManageGroups to rename the single-letter import groups to more intuitive names.

Note on Audio Processing

Wings Filter does not alter or reencode the audio sample data in any way, and thus does *not* incurr any generation or transcoding loss of quality. At the same time, this means that the incoming audio will be brought into Rivendell *exactly* as it exists in the Wings system, with all parameters (e.g. sample rate, bit rate, level, etc) unaltered. If you need to alter one or more of these parameters as part of the import process, we suggest you use the RDImport script instead.