YAMAHA | X G R E A D I N G P A G E

Step 2 Which are the really serious warnings and errors?

There is, of course, a reason for each error or warning message that XG Checker produces. However for actual SMF data production, only a few these will cause fatal problems. So, let's talk about the messages that can indicate serious problems.

Prohibited Control Change
These are control changes which the XG format does not allow, such as CC#84 (portamento control), etc.

No XG System On found in the initiation block
As the message suggests, this indicates that there is no XG On system exclusive message.

Multiple note found
This indicates that multiple note-on messages were found.

ControlChange/NoteOn are too close.
(1/480 tick required)
This indicates that a control change and note-on were found at the same timing. Depending on the type and value of the control change, it can make an important difference whether it occurs before or after the note-on. If the control change and note-on are at the same timing, different sequencers may process the order in different ways, possibly producing an unintended result.

BankSelect(MSB/LSB)/
ProgramChange are too close(1/480 tick required)
This also may cause notes to be played by a voice which you do not intend.

PitchBend is too close to NoteOn.
(1/480 tick required)
Pitch bend and note-on data exist at the same timing. This also can cause unintended consequences during playback.

NRPN MSB/LSB are too close.
(1/480 tick required)
RPN MSB/LSB are too close.
(1/480 tick required)
Both of these can cause unintended consequences during playback.

Empty Text.
A text meta-event with no content (i.e., blank text) was found. Some sequencers may not be able to open the corresponding MIDI file itself.

	Step 2 Which are the really serious warnings and errors?
	There is, of course, a reason for each error or warning message that XG Checker produces. However for actual SMF data production, only a few these will cause fatal problems. So, let's talk about the messages that can indicate serious problems. Prohibited Control Change These are control changes which the XG format does not allow, such as CC#84 (portamento control), etc. No XG System On found in the initiation block As the message suggests, this indicates that there is no XG On system exclusive message. Multiple note found This indicates that multiple note-on messages were found. ControlChange/NoteOn are too close. (1/480 tick required) This indicates that a control change and note-on were found at the same timing. Depending on the type and value of the control change, it can make an important difference whether it occurs before or after the note-on. If the control change and note-on are at the same timing, different sequencers may process the order in different ways, possibly producing an unintended result. BankSelect(MSB/LSB)/ ProgramChange are too close(1/480 tick required) This also may cause notes to be played by a voice which you do not intend. PitchBend is too close to NoteOn. (1/480 tick required) Pitch bend and note-on data exist at the same timing. This also can cause unintended consequences during playback. NRPN MSB/LSB are too close. (1/480 tick required) RPN MSB/LSB are too close. (1/480 tick required) Both of these can cause unintended consequences during playback. Empty Text. A text meta-event with no content (i.e., blank text) was found. Some sequencers may not be able to open the corresponding MIDI file itself.