Yahoo Groups archive

Emu XL-7 & MP-7 User's Group

Index last updated: 2026-04-05 20:33 UTC

Thread

Re: Multi Loading Problems fixed

Re: Multi Loading Problems fixed

2003-07-08 by steve_the_composer

Thanks for giving me the opportunity to get inside the deep structure 
of the Command Station. We bonded. I am now part of the machine.

           Dr. Steve-X     8-)>


-------------------------------------------------------------------
Info follows for others who may want to automate restoring multis.
-------------------------------------------------------------------
CAUTION: If you create a midi sysex file to automatically restore 
multis, the restored multis will replace ones currently in the E-Mu 
memory.  You will not be asked, "Are you sure?"

The bottom line:  Backup, backup, backup!
-------------------------------------------------------------------
Background:
  
OS2.0 allows you to transmit the current multisetup as sysex data.  
You can then save each multi on the storage device of your choice.  
You can restore each multi by (1) sending the sysex data to the E-
Mu's edit buffer and (2) saving the multi in any user location.

Automatic restore:

The E-Mu sysex specifcation has a copy function which will allow you 
(with 11 bytes of data) to copy the edit buffer to a specific memory 
location.

Example:    F0 18 0F 00 55 2C 7F 7F 01 00 F7
            F0 18 0F ID 55 2C ss ss dd dd F7

  F0 18 0F 00 55 2C = E-Mu sysex command to copy muli (ID=00)
     ss	ss 	=  source	 7F 7F	= edit buffer
     dd	dd	=  destination	 01 00 = multi 001
     F7 = EOX (end of midi sysex transmission

For each multi you wish to restore with this command, you will need a 
different sysex command. Change dd dd for other destinations-00 -> 3E 
for locations 000 -> 062.  [sysex digits are in hex, base 16] 

You can append a copy-edit-buffer-to-memory sysex command to a single 
multi.sysex.   As soon as you send the multi + copy command back to 
the E-Mu, it will overwrite whatever is in the specified location 
with the multi you want to restore.

If you have 8 multis in locations 000-003 and 010-013, you can create 
a *.mid file to automatically restore those 8.  You can then create 
new multis in other locations and update your master multi file (or 
create separate files for different multi banks).

If you want more than 1 bank load of multis, you can have several 
banks.  Perhaps you consistently use locations 30-60 for performance 
specific multis.  You can automate a bank to restore just those.

Allow enough time between "playing" sysex dumps from a sequencer (if 
that's your storage device of choice) so the E-Mu doesn't choke on 
the data.

Note 1:  This is just one of many possible solutions.  It is based on 
multis having been stored from the front panel.  It may also be 
possible using sysex to save and restore subsets of the multidata.

Note 2:  In my tests, viewing angle did not appeared to be 
transmitted via the sysex dump.  It does appear to be saved and 
restored with internal/front panel storage.

Hope this helps.

Dr. SyX

PS:  This info is provided "as is" with no warranty about the 
suitability for your particular application. Use these techniques at 
your own risk.  Not responible for typos, daisy chained units that 
may also be set up to the same device ID, etc.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.