Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
User avatar
By SimonInAustralia Tue Oct 21, 2014 2:18 pm
Almost Lazy wrote:so whats the point of saving them as a mapping & not being able to load them??

Find it, where you saved it, in the browser list on the left of the window, double click on it, it loads into the current Project.


Almost Lazy wrote:so your saying to make the mapping work i need to save the program, not the mapping.. then load that up into a sequence template to load each time i start a new song?

Save it, and load it when you want to use it, or create a template with them already assigned to tracks, and use that.

It is not a MIDI Controller mapping, it is part of the MIDI Program.

Rename the MIDI Program so that it identifies which synth it works with.
By Almost Lazy Tue Oct 21, 2014 2:24 pm
correction.. midi shows up in the program list yes, but not in the program window on the mixer page.. they stay as tracks...
still no info on importing the Midi Control files...

no automation on midi tracks..( i refuse to call them programs cos really they aint) they hold no data ..

seriously.. someone know how to load midi controller map to a midi track? :lol: :worthy: :hmmm: :WTF: :!:
By Almost Lazy Tue Oct 21, 2014 2:32 pm
SimonInAustralia wrote:
Almost Lazy wrote:so whats the point of saving them as a mapping & not being able to load them??

Find it, where you saved it, in the browser list on the left of the window, double click on it, it loads into the current Project.


Almost Lazy wrote:so your saying to make the mapping work i need to save the program, not the mapping.. then load that up into a sequence template to load each time i start a new song?

Save it, and load it when you want to use it, or create a template with them already assigned to tracks, and use that.

It is not a MIDI Controller mapping, it is part of the MIDI Program.

Rename the MIDI Program so that it identifies which synth it works with.



so whats the point of midi controller page.. ? DAW or something..?
honestly im still lost on no automation on a midi track.. what they think everybody writes with a pencil these days???

all my browser list folders are sample short cuts.. dragging the file from finder doesnt work.. im bored with this bull shit.. im just gonna record live tweaks to the synth patterns that somehow the Ren can record.. :popcorn:
User avatar
By SimonInAustralia Tue Oct 21, 2014 2:36 pm
MIDI Programs show up as a Program in the Track section in the Main Mode screen. They are programs, they hold the QLink assignments.

You don't load a MIDI Controller Map to a MIDI Track, you load a MIDI Program. You can double click on them in the MPC browser window, or drag them into the Project list area, or onto the pads, in Main Mode, to load them.

MIDI Controller Mode is for controlling external software/devices directly from the controller, working as a MIDI controller, it is separate to normal MPC sequencer operation.

You can control MIDI track automation with QLinks. Have you tried assigned a CC number to a Qlink, then recording that MIDI CC in from your external MIDI device, to see if it then shows up in the automation lane?

Good luck with it, you have to work with what is available, until they improve it.
User avatar
By fdodds Tue Oct 21, 2014 11:11 pm
Yeah, you definitely can automate midi values. I automated portamento controls on a melody i was sequencing just last week.

As SimonInAustralia says, you automate midi values using the q-links within midi programs (same way you automate pitch, pan, volume levels on drum programs). You've been able to do what you want to the whole time...

Midi control mode is mostly intended for users who want to map their mpc to features in a DAW (if they are using plugin mode, or routing virtual outs to a DAW), it's definitely not meant for controlling external synths, that would be a nightmare.
User avatar
By SimonInAustralia Wed Oct 22, 2014 12:02 am
fdodds wrote:As SimonInAustralia says, you automate midi values using the q-links within midi programs (same way you automate pitch, pan, volume levels on drum programs). You've been able to do what you want to the whole time...

I think he would prefer to have it record in the CC movements being sent from the external keyboard, rather than having to work out what the CC numbers are and do it on the QLinks.

It should be able to record incoming external CC messages in the same way as assigned QLinks, but he will just have to use the QLinks until they sort that out, if they do.

External MIDI doesn't really seem to be a priority for them, as I suppose most people are working ITB these days with plugins, rather than external MIDI devices.
By Almost Lazy Wed Oct 22, 2014 8:33 am
appreciate you assistance fellas!
so i was a little trippin on the recording of the cc, even on the qlinks.. cos ya need record pressed, not the automation trigger.. that shit is so inconsistent! Programmers need their background to include us oldskool MPC heads.. as for ITB production.. thats fine but buy maschine cos it has fuk all midi.. still trippin on why all those ports if the software aint gonna hold up to it...
they might as well left off the Phono connections as well..

anyway i how this is a wake up call to them & maybe for any budding musos out there instead of sampling gurus..

Akai shld give me a job... ill keep them respecting their roots while they play catch up with NI..
in this industry, ya loose us ya lost us forever..