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

Thanks for posting the XL-7's sysex output. I explain it in the folder where you posted the output. Basically it is a whole bunch of "cancel" messages--I suspect issued from the sysex being too fast.

Also, check out the "about these files" text file for an explanation of the 2010 banks and the 2013 banks.

As I wrote, I did not experience the sysex too fast problem loading the banks into an XL-1 fitted with the CMPSR ROM.  I did confirm that the ROM Instruments seemed to all be set to 000:None. I suspect that's because the ROM ID for the arp pattern in the 2010 files was pointed to non-existent resources (no arp patterns on the CMPSR ROM).

I redid the banks, setting the arp pointers to User arp patterns. On my XL-1, the presets no longer pointed to 000:None.

I'd be curious to know if these versions also get rid of the sysex too fast problem.

Please note: As I have mentioned, the conversions are simply ROM ID substitutions. This creates problems when the source ROM has resources that the destination ROM doesn't. 

For example, if a preset uses an arp pattern not on the destination, the E-Mu will most likely lock up. That's why I set the arp patterns to User arp patterns. However, I suspect there can similar lock ups with presets that uses other non-existent resources.

For some reason 082^3 arp:LowPercRoll points to a non-installed arp pattern and causes a lock up. I am not sure why that didn't get pointed to a User arp pattern. 

Also, since I loaded the banks into a 12-controller box, the Preset Patchcords have non-existent sources (????). I assume that if you load them into a 16-controller box, you shouldn't have that problem.

If you or anyone else discovers more arp presets that lock up, please let me know and I can hand tweak those banks and reload them.

Steve

--- In xl7@yahoogroups.com, "Ricard" <ricard2010@...> wrote:
>
> 
> 
> --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> >
> > I see that I posted a set in 2010. Is that the set you are having problems with? Based on the readme file, I see that I simply changed the ROM ID to point to the P2K Composer ROM--including non-existant arp patterns. Maybe that's causing the sysex-too-fast error. Let me know if those are the files causing a problem for you and I will delete those and try a different conversion.
> 
> Yes, that's the set. Although at the time it seemed that at least someone on the list tested it with success, which is why I think it's strange that I can't get it to work now.
> 
> As I mentioned, it's not just the Sysex: too fast that's the problem; when transferring the file with Bank 0 in it, my XL-7 stores up to patch 37, the patch names are there, etc, but looking at the Instrument assignments, they point to Instrument 0 of the CMPRS ROM which is None (I don't know if that's a true sample, or just a placeholder for "be quiet"). At least one of the Instruments seemed to point to another ROM I have in the machine (the XL-7 I believe) which I thought was strange. All the patches that the machine managed to download were silent, although I have not tried to determine if it's solely because of the Instrument assignments or there's something else in the patch that causes it to not play (i.e. volume set too low, no key range mapped, or whatever).
> 
> My spontaneous guess is that the ROM assignments in the files are wrong, so for each patch downloaded the XL-7 tries to locate it within the sample sets it actually has, which it fails to do, hence the incorrect assignments and ultimate error (because of some bug causing during the search process). I don't know enough about the XL-7 to know if this is even a reasonable thought though.
> 
> Is there anywhere one can see the ROM ID in the menus on the XL-7, or do you have to look in the sysex files for that? I was thinking that perhaps there are different versions of the Composer ROM with different ROM ID's. Normally one wouldn't notice the difference as the patches on the ROM always refer to the actual ROM in question.
> 
> /Ricard
> 
> /Ricard
>