Hey.
Mega noob question here!!!
Is the parameter number the cc number?
Trying to make my first control surface for the E1 and would just like to know if i am right in my assumption!
Kalle
Yes. If that is what you want it to be. You will also need to select CC (I presume 7 bit) as the message type and the midi values or their range. If you haven’t, I highly recommend reading the online documentation for the editor. Pretty straightforward if you are just mapping cc numbers and values to controls (fader, toggle or list are the most common types). Also, good to download some user presets to see how other people do it. That is how I learned the basics. Don’t forget to set the midi channel to match what your device is listening on. Good luck.
1 Like
Thx for the answer 
yeah i am looking thru other presets and so on i was just a bit confused if i had to change cc in the json or the parameter was the actual cc number
Parameter Numbers are unique within their message type. Keep that in mind.
Parameter Number 7 as message type Virtual is not the same as parameter Number 7 as CC.
SOME RULES OF THUMB FOR PARAMETER MAINTENANCE
If a message type is CC or NRPN , then it IS the same as the CC or NRPN number.
Try to avoid giving the same parameter number for different types, in the end it will confuse you. It’s not always avoidable though.
Typically for SysEx parameters, try to give it an identifier number that is to be used in the sysEx message itself. If you do that properly (through a lua function you then call in the sysEx), you only have to edit the sysEx data once, and then copy it to all other sysEx controls. Much easier than writing all different sysEx sequences.
By the way always use a lua function for other semi-static variables that are often used in SysEx data, such as a MIDI channel number or Device Number. It is very frustrating to have typed in a hundred SysEx data strings, then decide to change the MIDI channel of the synth, only to discover you need to change all hundred SysEx strings by hand one by one…
Typically for Virtual parameters, you can number it whatever you want. Just make sure you find a way to remember the numbering logic you applied, so you can still understand your logic if you look at your preset some years later. I usually write down the logic I applied to my parameter ranges as lua comments on the first lines.
Last but not least, if you forget what numbers you already consumed, use the lua statement:
parameterMap.print()
1 Like