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
Message
XL-7 and SoundDiver
2001-12-29 by rubaiyat_23
Attachments
- No local attachments were found for this message.