CC Hardware Template

Does anyone know if there is a way to create a template for hardware equipment, were you can name each CC parameter to match the synth/drum machine etc?

I am not sure if you can do so in MPC because I don't have mine at the moment but I do so with my Force by creating a track and then mapping all the CC values and naming them. Save the track and then I load that track into any project and the CC is already mapped and saved.

I’m pretty sure there is, but the MPC usually has you save a Program file. You can choose the midi CC and name them, then save the program.

I’m not in front of mine to verify that you can then load that program into a new project.

I do it often.

Create MIDI program . Route it to your device
PROGRAM EDIT
You have 8 pages of CC parameters to name and configure as your wish .. pencil icon and list of CC numbers
Cons : no way to make a range of control other than 1 to 127
Pro : when you have name your CC for this program they appear with this name in the QLinks "Program" menu
I duplicate the program also inside the project if I want to use to use several midi channels ( e.g for my multitimbral synth . )

Save the program elsewhere .. you will load it easily on any project when you need it .. Just assign it to any track you need, your mappings are saved , as for the Qlinks "Program "page, they will retain your mapping for other project.
just stopped to save that kind of programs apart, I just look for them them in the previous projects "data folder" ... So i'm sure to use the last working version

Calcaire wrote:I do it often.

Create MIDI program . Route it to your device
PROGRAM EDIT
You have 8 pages of CC parameters to name and configure as your wish .. pencil icon and list of CC numbers
Cons : no way to make a range of control other than 1 to 127
Pro : when you have name your CC for this program they appear with this name in the QLinks "Program" menu
I duplicate the program also inside the project if I want to use to use several midi channels ( e.g for my multitimbral synth . )

Save the program elsewhere .. you will load it easily on any project when you need it .. Just assign it to any track you need, your mappings are saved , as for the Qlinks "Program "page, they will retain your mapping for other project.
just stopped to save that kind of programs apart, I just look for them them in the previous projects "data folder" ... So i'm sure to use the last working version

It's been 2 years and this was still immensely helpful. Thank you for your post!

Idk how I created this post but somehow never saw that reply. Very helpful!

Lampdog wrote:HOW, did I miss that EDIT button, after all this time…

That button is key to using it as MIDI controller for external gear. Even more so on the Force because that's how you name the parameters for the MIDI macros.

It took me forever to set up a project temple that had MIDI maps for all my gear. I have synths that got: 16, 32, 8, & 11 channels. It took extra time because I had to label each with the track number so it would more sense when I'm messing with the macros otherwise their would be times when just naming something Cutoff would tell me what it's referring to. So I would put 01-Cutoff. Than I had to do it all over because of the Force MIDI-Learn bug that would reset knob parameters set w MIDI-Learn to value of 0 each time you change the track & came back. So I had to reassign each knob the manual/ tedious way

Glad you finally learned about it.

B-Wise wrote:

Lampdog wrote:HOW, did I miss that EDIT button, after all this time…

That button is key to using it as MIDI controller for external gear. Even more so on the Force because that's how you name the parameters for the MIDI macros.

It took me forever to set up a project temple that had MIDI maps for all my gear. I have synths that got: 16, 32, 8, & 11 channels. It took extra time because I had to label each with the track number so it would more sense when I'm messing with the macros otherwise their would be times when just naming something Cutoff would tell me what it's referring to. So I would put 01-Cutoff. Than I had to do it all over because of the Force MIDI-Learn bug that would reset knob parameters set w MIDI-Learn to value of 0 each time you change the track & came back. So I had to reassign each knob the manual/ tedious way

Glad you finally learned about it.

soooo care to share your external synth programs? is there a way to do the same thing with NRPNs?

It will only make sense if you have any of the same synths that I made them for: RS7000, Proteus-2500, MC707, TR8S.
Do you have any of these?

I don't know anything about NRPN.

B-Wise wrote:It will only make sense if you have any of the same synths that I made them for: RS7000, Proteus-2500, MC707, TR8S.
Do you have any of these?

I don't know anything about NRPN.

Ah, no I was hoping you had some of the same synths I had. Guess I will have to start making some midi programs.

BTW if you do it in the software, you can use more than 8 pages of CCs, not sure what will happen if you create more than 8 pages and open up the program in a standalone though .

When I get time I'll create a thread for project templates on the Force section & hopefully someone here can do it for the MPC, but if the Force MIDI tracks are compatible with the MPC I'll post it here. Do anyone knows?

I wish Akia would give the MPC the Force marcos not including the crossfader one obviously. Then we could really be sharing stuff that's tedious to make.

that 2500 template/program would come handy
(command station over here, i made a sysex Novation SL program for it)