User manual

XGedit95 User Manual Page 52
Problem Files
It should be noted that under certain circumstances XGedit will not show all setup data contained within a
loaded file and/or may not correctly play a midi file. This is usually an indication that the file deviates from
the XG Midi File Authoring Guidelines. Some common errors are described below:-
1) The file is badly structured
If the file contains setup data interspersed with note events XGedit will stop reading data after the
first note event. Hence the majority of edits may not be visible.
2) The file is not XG
Many midi files will have been written for the GS format and contain a GS reset command. In this
case the XG synth would normally switch to TG300B mode before playing the file. XGedit does not
interpret GS commands and will therefore discard GS related events from the file, thus preventing
the synth from switching to TG300B mode. Any remaining GM/XG events will be interpreted but this
will not provide optimal playback of the file (in particular GS bank selections are different to XG and
therefore correct voicing is unlikely)
3) The XG file was written for a different XG synth
Some XG synths provide additional features, voices and effects. If XGedit is in a synth mode which
does not support these features, then their associated edits may not be correctly displayed (XGedit
will attempt to mimic the fallback features of the selected synth).
It should also be noted that the default setup of all XG synths is NOT the same. (In particular the
MU80 defaults for Element Reserves, Effect Parameters and Drum kits are slightly different to those
of the MU50/MU10/DB50/SW60. Consequently if you load a midi file containing an MU80 bulk dump
into XGedit in MU50 mode, you will notice a larger number of edits than shown for XGedit in MU80
mode).
4) Ambiguous Controller Events
If the file contains multiple Controller events positioned on the same midi tick, their ordering cannot
be guaranteed across all sequencers. Additionally XGedit may misinterpret their assignments
(particularly with respect to RPN/NRPN controllers and Data Entry). All controller events should be
spaced at 1/480.
If the author utilises controller events which assume prior initialisation, then XGedit may not interpret
the events correctly (e.g. Omitting Bank Select MSB/LSB prior to a Program change message). All
such controller events should therefor be expressed implicitly and in the correct time order.
15.5 Saving Midi Data
The
registered
version of XGedit allows edited data to be saved to MIDIEX files (.SYX) or standard Midi
files (.MID) in association with normal editor Native saves
MIDIEX files contain raw system exclusive bulks dumps and may be imported into popular sequencers such
as Cakewalk. To save .SYX files the user should select the .SYX format from the standard File Save Dialog.
(note that SYX format saves the complete state of the synth. Hence they should only be used where there
are a large number of edits or layered parts which require sysex. For all other purposes Midi files should be
used)
Standard Midi files are more useful and can be read by almost all sequencers. To save .MID files the user
should select the .MID format from the standard File Save Dialog.
The contents of the saved midi file are determined by the controls in the Master Module (Refer to the
Master Module section for a description of each control)
15.5.1 Saving Merged Midi Data
If the user has merged a midi file into XGedit, then the saved midi file will also contain the merged song
data. The setup data will be saved to the first few bars and assigned to the appropriate song tracks (based
on midi channel number). The song data will be repositioned with respect to the setup data such that a gap
of at least 200ms is left between end of setup and the first note on event (as recommended in the XG
authoring guidelines).