Specifications
converter 1.5
2000 - 2005 urr Sound Technologies Inc.
18
file listing of the converter package
The following is a listing of all the files included in the converter source zip archive, and their relationship
with the main program file. Files noted as required need to be in the same directory (folder) as the
converter program file (
c.exe
) in order for it to operate properly. Files noted as optional are not needed
for proper operation of converter, but are highly recommended to be kept together.
file description dependancy
c.exe
converter program file (executable) required
c.cfg
converter system configuration file required
hardware.cfg
soundcard interface settings required
*.cdt
converter data files required
*.urr
converter data files required
default.set
default program file loaded when converter is initially run required
empty.set
‘blank slate’ / reset converter to default settings recommended
cmanual.pdf
manual for converter (this document) optional
autoexec.bat
a basic autoexec.bat file which can be used for a bootable
floppy disk installation of converter
optional
lastset.set
‘revert to previous’ setting file optional
m-opslib.set
preset : midi input processor operations library optional
gpmixcut.set
preset : gameport input as midi mixer / mute (cut) optional
dltrig*.set
presets : audio to midi trigger program files optional
cbootdsk.zip
archive with self-extracting converter bootable floppy image not needed
There are three external files used by converter which serve different purposes – all three of these must
be located in the same directory (folder) as the executable file (c.exe). The first file,
hardware.cfg
, is a
text file which holds the individual computer-specific hardware settings for the soundcard used. The file
default.set
is the base program file which is read from when converter is initially run, and updated
(written to) when converter is quit. The final file, called
c.cfg
, is read from at run-time and written to on
exit, and is used to store other computer-specific hardware settings adjustable from within converter. In
this way, programmed converter configurations (
.set
files) can be interchanged with other users, while
machine-specific settings remain tied to the particular machine on which converter is being used. At the
same time,
c.cfg
and
default.set
provide something akin to a ‘battery-backed memory’ so that
the last converter session, with all its settings, is automatically re-loaded and ready to be used the next
time converter is run.
types of parameter settings saved exclusively in c.cfg
•
display settings (vertical retrace, animation settings, oscilloscope settings, scrolling text window
status, midi input processor view mode, etc.)
•
input device settings (joystick axis channel calibrations, mouse axis speed)