Yahoo Groups archive

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

Index last updated: 2026-04-29 00:09 UTC

Message

Re: assigning sends/sub-outputs - in the pattern

2011-02-10 by stimresp

> 
>So if you change MidiA from CC74 to CC16 and MidiB from CC71 to CC17, ONLY CC16 and CC17 will affect Cutoff and Resonance, respectively.
> 
> Steve
 

From a quick experiment: the default preset chords usually also map Knob A to Filt Freq via the cords menu. By removing that cord mapping (on each layer), MIDI A will no longer control cutoff, EVEN if cc 74 is assigned to MIDI A in the controllers menu. Incoming cc74 is not by default recognized by the CS (confirmed in the manual - MIDI chart). However, if you re-assign midi A to cc74 and re-establish the relevant cord, then the CS WILL recognize incoming cc74.

CCs 7 and 10 (Vol/Pan), however are by default recognized, so by assigning knob A to cc 7 in the controllers menu works, and the CS will also recognize this incoming cc, independent of any cords.

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...???

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....


  

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
>
> 
> 
> 
> Here is my understanding of the CCs:
> 
> Some midi gear has CCs hard coded such that each CC can be used for one and only one thing. For example CC74 might be Filter Cutoff Frequency and CC71 might be Amount of Filter Resonance and you cannot change that. However, with the P2k synth architecture, to can assign different CCs to different knobs (MidiA -> MidiP on 16-controller systems) and then use those CCs (via MidiA -> MidiP as patchcord sources) to control whatever destinations you want.
> 
> However, since there are some conventions [standardized assignments], such as CC7 = volume, CC10 = pan, CC1 = modwheel, etc. factory designed presets (and third party presets) tend to use those conventions, although you can change them in your own presets, if you want.
> 
> The CCs E-Mu has identified as being hard-coded (CC79 and CC80) are somehow different.
> 
> Patchcord sources include (among others): Pitchwheel [PB], Modwheel [CC1], MidiVol [CC7], MidiPan [CC10], and MidiExpr [CC11] all of which can be routed to whatever destination you choose.
> 
> You could assign CC79 and CC80 to MidiA -> MidiP, but since they are hard-coded as Mix Output and Arp Status respectively, I just always assumned (1) you don't need to use the knobs like that and (2) if you do, in addition to whatever you route those sources to, they will also >always< affect Mix Output and Arp Status, respectively.
> 
> Of course, CC7 seems to always control volume, CC10 seems always to control pan, etc. So the question is, aren't those hard-coded, too? (Does anyone know?)
> 
> As for CC91-96 being labelled as FX depth, I believe thats the convention that emerged from the Midi Manufacturers Association, but on P2K-based synths, you can use them for whatever you want if you assign them as controllers.
> 
> By the way, I think somone may have asked a little while about about resetting controllers. Evidently with CC120 [All SOunds Off], a value of 0 resets all except volume and pan, while a value of 127 resets all.
> 
> Also, having CC74 as "Brightness" [aka Filter Cutoff Frequency] and CC71 as "Timbre/Harmonic Intensity" [aka Filter Resonance] as a convention in P2K-based presets also means compatibility with Roland Sound Canvas based modules. 
> 
> However, while they are hard-coded in Sound Canvas Modules [at least they are in my M-GS64], these are not hard-coded in the E-Mu. So if you change MidiA from CC74 to CC16 and MidiB from CC71 to CC17, ONLY CC16 and CC17 will affect Cutoff and Resonance, respectively. [Actually, now that I think about it, I believe I can change CC assignments in my M-GS64 via sysex commands; so maybe they're not really hard-coded, just "difficult-coded."]
> 
> Steve
> 
> 
> 
> --- In xl7@yahoogroups.com, Bruno <brunorc@> wrote:
> >
> > 2011/2/9 stimresp <stimresp@>:
> > > - Controller 80 is hard-coded to the Arp Status parameter - 0=Off, 1=On, 2=P (preset), 3=M (master)
> > > - Controllers 91-96 for FX depth (but why are there 5 for 2 fx processors)?
> > > -And a few that raise an eybrow - 71 for 'Timbre/Har Inten' , 74 for 'Brightness'
> > 
> > Nice, compliant with XG :-)
> > 
> > But... by "hardcoded" you mean that if I set my A and B controllers
> > (usually mapped to Filter Cutoff and Resonance) to, say, CC 16 & 17, I
> > can control Filter Cutoff BOTH with CC 16 (because of 16 -> A mapping)
> > and 74 (always works)?
> > 
> > Cheers,
> > 
> > Bruno
> >
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.