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

I don't expect a quick fix for this, but here goes...

I currently use SoundDiver (Emagic, version 3.0.4) to edit most of 
the synths I own, as it is more expedient to click through screens 
on a computer than to menu-surf on a two-line screen.

I previously owned a Proteus 2000 that I traded back for the XL-7. 
For those of you who haven't worked with SoundDiver, the Audity/
Proteus 2000 module is very well designed, and works a charm 
if you're developing a sound library. Patch names for each of the 
factory ROMs are specified if you scan for a particular model 
(Planet Earth Turbo, for example) at setup time. You can request 
all relevant memory locations (multisetups, instrument listings, 
beats, even the LCD display angle!), create and manage patch 
groups on the fly, the whole nine yards--just what anyone who'd 
prefer to program their own sounds would want, right...

I bought the XL-7 because I liked the portability aspect 
(sequencer!) combined with the Xtreme Lead ROM. I've since 
added two additional ROMs (World Expedition and TSCY), and 
travel with the unit on a regular basis. Needless to say, I won't be 
getting rid of this anytime soon (it joins my Waldorf Q kbd and 
MicroWave II module in this respect).

The XL-7 uses a ROM ID unique to itself, such that requesting 
patches vis-a-vis an XL-1 Turbo fails. Scanning it as a Proteus 
2000 (generic family member) works as far as getting patch 
names--but the program stops at (either) beats or riffs.

In other words, the modified memory structure makes it 
impossible to do any serious patch-editing work without having 
to go out and buy a used Proteus 2000 (again), replacing the 
ROMs, and starting from scratch. 

I'm sure this also applies to the Proteus 2500 users as well, and 
would likely apply, similarly, to the new keyboard products as 
listed in the January 2002 E-mu newsletter.

Any ideas? Or should I hold my breath for a Proteus 2500 
adaptation/module? Surely I'm not the only person who's run into 
this problem...?!

Thanks,
Dave Dever

It looks like p2k module is developed by Emagic themselves and it 
would be up to them to update it to include the XL7 ROM.  Since the 
XL7 ROM uses a unique ID, the SD module is unable to access the 
presets no matter machine it is used in.

I'm certain that Emagic's mail filters have already intercepted these 
meesages and will respond soon enough.  If not just email them 
directly about it.

I would do it myself if I had the source code since I have done quite 
a bit of work with SD over the years.


--- In xl7@y..., "rubaiyat_23" <rubaiyat_23@y...> wrote:

> I don't expect a quick fix for this, but here goes...
> 
> I currently use SoundDiver (Emagic, version 3.0.4) to edit most of 
> the synths I own, as it is more expedient to click through screens 
> on a computer than to menu-surf on a two-line screen.
>

in the mean time you can download the XL-7 multiinstrument , that I made,
from Len Sasso's website:     http://www.swiftkick.com/lugenv/other/
under emuxl7.zip.

Kamy

> It looks like p2k module is developed by Emagic themselves and it
> would be up to them to update it to include the XL7 ROM.  Since the
> XL7 ROM uses a unique ID, the SD module is unable to access the
> presets no matter machine it is used in.
> 
> I'm certain that Emagic's mail filters have already intercepted these
> meesages and will respond soon enough.  If not just email them
> directly about it.
> 
> I would do it myself if I had the source code since I have done quite
> a bit of work with SD over the years.
> 
> 
> --- In xl7@y..., "rubaiyat_23" <rubaiyat_23@y...> wrote:
>> I don't expect a quick fix for this, but here goes...
>> 
>> I currently use SoundDiver (Emagic, version 3.0.4) to edit most of
>> the synths I own, as it is more expedient to click through screens
>> on a computer than to menu-surf on a two-line screen.
>> 
>

I'm having a frustrating problem with my new XL-7 (with OS 2.00)  and SoundDiver 3.0.5. I had an XL-1 and never had any problems with SD. When I ask SD to get names, it gets the instrunet lists, but consistently hangs when getting the riff names, saying "Audity/Proteus 2000 did not answer" or something like that. I don't know if it's related, but the XL-7 ROM info also isn't making it to SD. Curiously, the instrument names from the other two ROMS, World Expedition and TCSY, are making it to SD. I've tried adjusting the sysex delay on both the XL-7 and SD with no luck.

Any suggestions?

I think my next attempt will involve taking the extra ROMs out of the XL-7 and seeing what happens.

i tried and it makes exactly the same
i don't have extra roms on it

but : the xl7 is not a proteus 2000 !!!!
it's a proteus 2500
and this is not supported by sound diver
i think it's the cause of your problem
if any1 has managed it to work....

----- Original Message -----
From: "Harry Pinna" <trueshunka@...>
To: <xl7@yahoogroups.com>
Sent: Thursday, July 17, 2003 4:19 AM
Subject: [xl7] XL-7 and SoundDiver


> I'm having a frustrating problem with my new XL-7 (with OS 2.00)  and
SoundDiver 3.0.5. I had an XL-1 and never had any problems with SD. When I
ask SD to get names, it gets the instrunet lists, but consistently hangs
when getting the riff names, saying "Audity/Proteus 2000 did not answer" or
something like that. I don't know if it's related, but the XL-7 ROM info
also isn't making it to SD. Curiously, the instrument names from the other
two ROMS, World Expedition and TCSY, are making it to SD. I've tried
adjusting the sysex delay on both the XL-7 and SD with no luck.
>
> Any suggestions?
>
> I think my next attempt will involve taking the extra ROMs out of the XL-7
and seeing what happens.

>
>
>
> To unsubscribe from this group, send an email to:
> xl7-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

1.  Can you take a look and see what sysex command the software is 
sending to try to get the RIFFS (or whatever is causing the E-Mu to 
hang)?

2.  Does the software have a configuration file for adding dump 
request sysex commands?

I took the liberty of writing E-Magic regarding the problem. 

>> There are some XL-7 users having trouble with the software hanging.
>> Perhaps you can help.
>> 
>> Dr. Steve

> The Proteus2000 module does not yet support the XL-7 due to 
> differences in the SysEx protocol. I can not tell you when a
> version supporting the XL-7 (and the MP-7, PX-7 etc.) will be
> available.

- Jens

Just thought I'd pass this on.

Dr. Steve