Transmitting Archived/New Data To The - Roland EM-50 Owner's Manual

Owner's Manual
7. Wait until the display tells you Comi lete, then
stop the seguencer.
8. Save your new seguencer song to floppy or hard
disk.
Try to save it under a clear name (example: UserProg
EM 2/4/99). That way, you know exactly which file
you need to transfer back to the EM-50/30 at a later
stage.
9. To leave the MIDI mode, press [CANCEL] several
times until the "MIDI" message is displayed, then use
MENU A Y, followed by [ENTER] to select another
mode.
Transmitting archived/new data to the
EM-50/30
Transferring your dumped settings back to the
EM-50/30 is relatively easy and requires no special
actions on your Creative Keyboard. Do note, however,
that the settings you transfer back to the EM-50/30
will overwrite the current settings in that memory
area (Custom Styles, User Programs or Song).
1. Connect the EM-50/30's MIDI IN port to the
seguencer's MIDI OUT port.
MIDI OUT (or "IN" connector of
the MIDI/Joystick cable)
MIDI IN
RH DNA
2. Stop Arranger (or Song) playback on the EM-50/30
and dump the settings and dump the internal settings
you do not wish to lose to the seguencer (see page
55).
3. Start the seguencer and load the file you wish to
transfer to the EM-50/30.
For best results, set the seguencer's playback tempo to
a value between J = 100—120.
4, Start playback on your sequencer.
As soon as the first data arrive, the display indicates
the following:
trn Pee
T dm tmb ut
CST 222 "s
SYS means that the EM-50/30 is receiving SysEx mes-
sages (that are only understood by the EM-50 or
EM-30). The display will also inform you about the
data type being received: Custom Styles (for all 8
memories; CST), User Programs (for all 64 memories;
USP) or a song (SNG).
5. Wait until the Come let- message appears, then
stop playback on your sequencer.
6. Try out your freshly loaded settings to see if they
work as expected.
Possible error messages during the reception of
Bulk data
As SysEx data are rather delicate data (the slightest
data error will make the entire bulk unusable), the
may be situations where receiving these data does not
work out as planned. Here are the error messages that
could be displayed. Note that you need to switch off
the EM-50/30 and try again if one of these messages is
displayed.
File Err—These data are probably not for the
EM-50/30 because it cannot read them.
CSum Err—Checksum error. The checksum does not
correspond to the data contained in the SysEx string.
This probably only happens when someone has tam-
pered with the data on a computer, etc.
ID Err—Wrong Model ID. Every instrument has a
Model ID that says "I am an EM-50 or EM-30". This
ID number is also included in SysEx data (and then
means "this is only for an EM-50 or EM-30"). If the
EM-50/30 received Bulk data for, say, a JX-305 ("this
is only for a JX-305"), the EM-50/30 would respond
with "but I am an EM-50/EM-30", and would turn
down the data.
Long Sys—The SysEx string is too long and cannot be
received. Again, this is only likely to occur when
someone programmed the SysEx data by hand (which
is perfectly possible, by the way). This message should
not appear for data you dumped from the EM-50/30
itself (see page 55).
Addr Err—Wrong SysEx address. Every parameter of
a SysEx string has an address that informs the receiver
about its nature (e.g. "I am the Cutoff parameter...").
This error message means that the EM-50/30 received
an address that does not exist.
Rx Fault—The reception doesn't seem to work
according to plan. Check the cable connections, or use
another MIDI cable.
Flsh Err—Flash Memory Error. There is a problem
with the Flash ROM memory which is used by the
Custom Music Styles. Contact your Roland dealer, or
local distributor.
OvRunErr—Framing error/Buffer overrun. The
SysEx data were transmitted too fast for the EM-50/
30. Slow down the playback tempo of your "song" and
try again.
56