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

You took the words right out of my mouth, Bruno. 

A few years ago I tried to organize a way to explain E-Mu's uses of pre-defined/hardwired CCs. Maybe this helps in the present discussion: http://launch.groups.yahoo.com/group/xl7/message/21532 

See also: http://launch.groups.yahoo.com/group/xl7/message/21820 as it relates to what Bruno talks about concerning layers.

The idea is that while some CCs are pre-defined, E-Mu's have quite a bit of flexibility. As Bruno points out, using CCs a two step process:

1. Define MidiA -> MidiP globally as specific CCs.
2. Use MidiA --> MidiP in patchcords to do whatever you want them to.

Of course, you are not limited to 16 CCs (or 12 on P2K modules). You can use pre-defined CCs in patchcords to do non-predefined tasks (e.g., mod wheel, pan, volume, expression, etc.). Keep in mind the on/off CCs can also be redefined using patchcords. For example, with Footswitch 1 setup a CC 64 (usually sustain), you could design a preset that shoots layers 3 and 4 up an octave (doubling layers 1 and 2) and turns on (or boosts) some effects.

Steve




--- In xl7@yahoogroups.com, Bruno <brunorc@...> wrote:
>
> 
> To some extent E-mu 2000 line does it as well - IIRC CC#7 & CC#10 are
> always interpreted as Volume & Pan, and you don't have to assign them in
> patchcords. However, CCs are just CCs - messages with sound-agnostic data.
> How particular synth interprets them, depends both on global configuration
> and on preset settings. If you don't define how the synth (globally) or
> patch react to CC #63, what's going to happen if the synth receives it?
> Nothing, I believe.
> 
> E-mu architecture assumes a set of 12 (or 16 - depends on devices)
> controllers, and while their CC numbers are defined globally, they can be
> freely interpreted *per layer*, as well as per preset (see layer/preset
> patchcords). Also, presets in E-mu don't define CCs, but internal
> controllers A-L (or A-P), and you can assign any MIDI CC numbers (at least
> those defined as "open" by standard) to your internal controllers.
>