EasyManua.ls Logo

Miditemp MP 22-W - Page 112

Default Icon
131 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-XMIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
MIDITEMP MP 22-W, MP 22-CD, MP 88-W, MP 88-CD, PMM 88-E, MT 16-X
112
After a Start command, the MULTIPLAYER sticks on the first note of bar one, instead of
After a Start command, the MULTIPLAYER sticks on the first note of bar one, instead ofAfter a Start command, the MULTIPLAYER sticks on the first note of bar one, instead of
After a Start command, the MULTIPLAYER sticks on the first note of bar one, instead of
playing the Song.
playing the Song.playing the Song.
playing the Song.
Problem:
Problem:Problem:
Problem:
The MULTIPLAYER is set to “SYNC: MIDI clock”.
Explanation:
Explanation:Explanation:
Explanation:
You have probably forgotten to set the MULTIPLAYER back to internal synchronisation after recording
a Song via MIDI in external sync. So the MULTIPLAYER waits for some MIDI Clock.
Solution:
Solution:Solution:
Solution:
Set the sync back to “internal” and press Start again.
A MIDI file created on a software sequencer doesn’t play back like it did on the computer.
A MIDI file created on a software sequencer doesn’t play back like it did on the computer.A MIDI file created on a software sequencer doesn’t play back like it did on the computer.
A MIDI file created on a software sequencer doesn’t play back like it did on the computer.
Whole sections or voices are missing, drum and bass parts simply stop after four bars, some of the
Whole sections or voices are missing, drum and bass parts simply stop after four bars, some of theWhole sections or voices are missing, drum and bass parts simply stop after four bars, some of the
Whole sections or voices are missing, drum and bass parts simply stop after four bars, some of the
settings (channel, transpose, velocity, etc.) are being ignored, only the intro of the Song is played, or
settings (channel, transpose, velocity, etc.) are being ignored, only the intro of the Song is played, orsettings (channel, transpose, velocity, etc.) are being ignored, only the intro of the Song is played, or
settings (channel, transpose, velocity, etc.) are being ignored, only the intro of the Song is played, or
the whole Song comes from only one synthesiser, or not at all!
the whole Song comes from only one synthesiser, or not at all!the whole Song comes from only one synthesiser, or not at all!
the whole Song comes from only one synthesiser, or not at all!
Problem:
Problem:Problem:
Problem:
The playback parameters of the software sequencer have not been converted and stored within the
MIDI file.
Explanation:
Explanation:Explanation:
Explanation:
The MULTIPLAYER will only play exactly what is stored within the MIDI file. The “MIDI File Format”
allows the following song data to be saved:
-
Several parallel tracks with any number of events on all 16 MIDI channels
-
Full resolution (e.g. 1/768 Note)
-
All MIDI channel information (Control, Poly/Channel Pressure etc.)
-
SysEx events without handshaking
-
Tempo
-
Time signature
-
(Text events)
The software sequencer will save each event with whichever channel, velocity, pitch, event position,
etc. appears in the Event Editor (i.e. the “original” data).
Sections which seem to be missing are sometimes being played on other MIDI channels, namely the
original channel that they were recorded on in the software. The same is true of the “playback
parameters”. A track which has been transposed there will nevertheless be saved in its original key.
Furthermore, the whole Song must end up as one single pattern, because a Song with lots of
separate patterns cannot be saved as a MIDI file.
Solution:
Solution:Solution:
Solution:
Before saving the Song as a standard MIDI file, you must replace the playback parameters with real,
“hard” events (e.g. “Normalize” and “Fix Quantize” in Creator/Notator, and MIDI channel
calculation using “Process Data” or [Shift-T] in the Editor).
Loops are also playback parameters, and must therefore be replaced by physical copies (in
Creator/Notator: “Segment Copy”, Number of Copies: Loop value / bar count x number of bars).
In Creator/Notator, arrangements of patterns must be merged together into one long pattern using
“Arrange-to-Pattern Copy”. In CUBASE the tracks have to be glued to one complete track, too.
Having done all this, re-save and re-load the Song as a MIDI file into the software sequencer to
check for accuracy.

Table of Contents