MIDI Devices

34
MIDI devices
The code has to end with </MidiDevices>, otherwise it is
incomplete and cannot be imported.
The value of the variable “DeviceNode Name” is the name
of the device given in the Installed Devices List.
Object classes have unique IDs, which are important in
case you want to merge XML files (see below).
Editing the device setup XML files directly
It is possible to “merge” XML files, e.g. in these cases:
• You have created a panel for a device and now want to
add the patch banks from another patch name script.
• You have created a MIDI Device from a patch name
script. Then you want to add a panel, but new parameters
appear only in one channel node and not across all 16
channels, because the default setup during import is set
to individual channels.
The general approach is:
• Generate two device setups that differ mainly in one aspect
(e.g. patch bank details).
• Compare the two files.
• Create a combination of the two device setups.
For example, what you would have to do for the second
case is the following:
1. Open the original device (without identical channels),
note down the patch banks and their structure, and export
the device setup.
2. Create a new device with 16 identical channels, re-
build the main patch bank structure and export the device
setup.
This leaves you with two files, so that you can copy the patch banks from
the original file into the new file.
3. Compare the files and copy all original patch bank
contents into the new file. Take care that you use the
unique IDs from the new file, not the ones from the old file.
Panel XML files
Panels are saved as an XML file of their own, with a name
consisting of:
<device name><unique combination of letters and num-
bers>.xml
To save the panel file, you need to leave the Panel Editor,
at which point you will be asked if you want to save the
panel file.
Ö Note that the panel file can’t be saved under another
name.
Excerpt from a panel XML File
The device name is given in the first row.
Bitmaps are included with the tag <resources>, in this ex-
ample the Bitmap “virus LOGO.bmp”.
Controls have their own tags <control class>. Templates
are encoded in sections that are tagged with <template>.