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

Great stuff. It's all coming clear now.

Cheers!


--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
>
> From you experiemtn, it sounds like you are developing a good understanding of the relationship between incoming and internally generated CCs and patchcords. See comments below.
> 
> --- In xl7@yahoogroups.com, "stimresp" <stimresp@> wrote:
> 
> [snip]
> 
> > So, if a cc is not by default recognized by the CS, you need to assign that CC to a knob and further map that to a cord to tell that CC what to do...???
> 
> In a word, yes. That's the price of flexibility--it is a two stepped process: 
> (1) Under Controllers, assign a CC number to a definable patchcord source if it is not pre-programmed (mainly Midi A->MidiP and Footswitches) or you don't want to use the default CC numbers and then (2) use that source to do whatever you want in the patchcords. 
> 
> Let me add something that you may already: If MidiA is defined as CC 74, then i't doesn't matter if the CC vales are coming from the knob marked MidiA or through an externally connected source.
> 
> One of the things that helped me understand my E-Mu is when I started thinking of it in terms of separate systems. For example, the 4x4 knobs are midi controllers--just as if they were externally connected. Here's another example, if you use the 16 buttons as note triggers to latch arps on and off, think of them as midi controllers--just as if they were externally connected.  
> 
> > Is there a more direct way? What if I want to map an incoming cc to, say LFO rate? MIDI CCs are not modulation sources in the matrix....
> 
> To me this is more direct than having to use sysex commands to map CCs to specific modulation sources as in some other gear. I am trying to think of more direct approaches--such as gear that has a table of CC and you can assign a function to each CC, or the converse, gear that has a table of functions and you can assign a CC (or several CCs, I suppose) to each. I suppose if I had gear like that and I didn't have to use sysex commands to change the assignments, I'd make use of it.
> 
> I guess I am so happy that I have midi knobs and buttons built into a box with a synth engine with virtual patchcords and a sequencer to boot, that it never dawned on me befor now that it could be simpler (such as with the use of direct CC mapping). I don't know why the OS dosn't have CC numbers as sources, but I am gonna take a guess. Maybe if it did, you'd only be able to use that function to map externally generated midi; you couldn't use the knobs, for example, without assigning them to CCs. That's just a guess, and I am also guessing that because these boxes were designed as all-in-one sound work stations stations with built-in controllers (as opposed to sound modules dependent on external controllers), the developers wanted to maximize the flexibility of the built-in controllers. If I am right, that would seem to dictate the use of the two-step process over a direct map. Again, I am just thinking out loud here. You raised an interesting topic.
>