## Midi CC Standard Map for scope ?

Scope and XITE Development

Original topic on PlanetZ: https://forums.scopeusers.com/viewtopic.php?t=15596

####

Posted: Mon Mar 28, 2005 5:15 pm
by spacef
Hi all,
I am updating many devices of mine with various controllers.
I would like to share with you the assignment of one of my biggest synth, "DXD", because all other spacef devices use the same map when possible. Making it a standard ? it is up to you.
Advantages of a common standard for Scope :
- It includes default midi assignement (GM?) such as 74 for LP Cutoff, 71 for resonance, 5 for portamento etc. Of course, sometimes it doesn't make sense to assign "10" to pan, so I use it on all devices to control the static LowCut/Bass Cut (Static/FInal Hipass) of all my synths.
- it may alllow users to make a preset for their controllers, and this preset will be valid on all devices. This is the case in particular for the ADSR group of Amp& Filters Enveloppes. This one should be the same on all devices. Same for the Pitch Env and additional prameters (A/D slopes etc).
- Some controls are "buttons". Through all devices, they will corespond to buttons too (a button in one device is a button in another device).
- DXD is big and includes 4 oscillators, 5 filters (the fifth is dual) and 3 envelopes (AMP, Filter, Pitch), an oscillator mix section etc etc. So the exact same assignment can be re-used to fit a synth with less controls.
- Assignement by groups : you can see colors, or look in the "list by groups" and focus on the FM section. It includes 20 controls for that oscillator : now, if you re-assign parameters of that group to control, for ex, noise oscillator, and save a preset, it means that one memory/prest of your hardware controller can be re-assgned to other parts of the synth, simply by changing a preset of the Midi Controller Bank of the device. It means 100 % hardware control is possible.
Always unassigned : CC 32 (Noah bank Select) and 64 (Sustain pedal) are never assigned in any of my devices. They can be used by users as unassigned midi controllers if needed. I also ropose that those 2 controllers be never assigned in any synth as a default rule.
With a smaller synth, it simply makes more unassigned (or undefined) controllers.
You can read more by having a look to this page. I will also post the AN-Osc assignement map very soon, so it will be more obvious for you to see what i mean by comparing the two lists.
For the moment it is spacef only, but i wanted to share it with you, because I think it can only benefit everybody, developpers and especially users.
I think it also saves a lot of presets/memory of the hardware controllers.
I will try to make a standard map, but for the moment I am finsihing a few other devices on the same "map".
Have a look here for the map (an-osc map will follow):
http://www.spacef.com/PRODUCTS/BB/midiccDXD.htm
(ps the "common midi controller group is not shown here" because i didn't finsih that html page yet. It will also include the map of "remapped CC" from the DXD Midi Controller presets)
I may use CC 118 for Noise resonance so you can add this one to the list).
Post or mail me question if you wish (but i will not answer any SDK related questions here. sorry).
In any case, see you.
Mehdi