Yamaha MU80 User Manual download pdf (Page 50)

XGedit95 User Manual Page 50

The File | Merge Midi menu item performs the following:-

Provides Midi Input File Selection

A standard file select dialog box is opened allowing the user to select the Midi input file. The file

must have the .MID extension and must contain either a type 0 or type 1 header with associated

midi track data.

Data Loading and Setup Bar interpretation

On closing the file select dialog, the midi file data is loaded into XGedit for processing. The

processing consists of interpreting all setup bar data contained within the file. For the purposes of

this processing, Setup Bar data is considered to consist of all midi events prior to the first note on

event of the song.

XGedit interprets the data listed below. Where relevant an events midi channel is used to

determine which synth part(s) to update.

Since there is no way of determining midi port from a

standard midi file, XGedit cannot update parts 17 to 32 of multi port modules unless they are also

assigned to the first midi port

•

Header information (used to determine output midi save format)

•

Tempo/Time base (used to determine playback/event storage timing and saved to output

files)

•

Time Signature/Key Signature/SMTE offset (saved to output file and used to realign midi

data after appending setup bar)

•

System Exclusive Bulk Dumps (interpreted and used to update display)

•

System Exclusive Parameter Change (interpreted and used to update display)

•

Patch Change/Bank Select (interpreted and used to update display)

•

Relevant Continuous Controller messages including RPN/NRPN (interpreted and used to

update display)

•

Note On/off (first event used to signify end of setup bar)

Setup Bar stripping

The data interpreted above is stripped from the midi file and stored for use when saving out files.

Any other data that lies within the setup bar and is not interpreted is discarded; this includes text

events, markers, pitch bend, modulation and aftertouch controller data, any unrecognised Sysex

(including SW60XG mixer) and all channel mode messages)

Any tracks left empty after setup data stripping are discarded

All data after and including the first note on/off event is preserved and used for saving out midi

files.

XGedit will not recognise sysex for the QS300 user voices available on the MU10/SW60/DB50

and will therefore strip them from an imported midi file. To prevent this ensure any such voice

sysex is placed after the first note on event (a dummy note on event with a velocity of zero may

be used if desired)

Display Update and Synth Refresh

The interpreted data is used to update the status of the editor and refresh the attached synth

(such that the editor and synth remain consistent). Any parameters contained within the merged

midi file override existing parameters in the editor; all other editor parameters remain intact

Midi File save/play preparation

The loaded midi song data is prepared for playing using XGedits midi play feature and processed

1 2 ... 45 46 47 48 49 50 51 52 53 54 55 ... 61 62

Comments to this Manuals

No comments

Yamaha MU80 User Manual Page 50

Comments to this Manuals

Related products and manuals for Power generators Yamaha MU80