Anyone manage to setup Akai MPD232 ?

[Karifi]

Has anybody managed to setup MPD232 to work as a mix contoller?  I have been trying all paths I have found reading all possible tips found from the web. MPD has own template for Sonar and it has been selected. 

Have tried ACT, have tried generic mode, learning, but not able to get Sonar learn the slider or pot movements. Managed to set in the mixed view (or how it is called) one by one the volume  and pan pots to he remote controlled, but the settings are then stored in current project but not usable as a template. 

Has anyone managed to do this?  

 

[gregdei]

Did you find a solution meanwhile?

[Byron Dickens]

 

This is a two-year-old one post wonder.

[steve-a]

Old question here perhaps but still relevant if like me you recently got an MPD232 and want to  use it with CbB.

What worked for me is to start with the Cubase preset rather than the Sonar preset on the MPD232, and in CbB start with the Akai MPK49 preset on an ACT MIDI Controller. You'll need the Akai MPD232 Editor to save a new preset on the MPD232, and will need to save learnt controls to a new controller preset in CbB.

Here's more detail if needed:

First use the Akai MPD232 Editor, with the MPD232 connected as a MIDI input and output device, to set up a new preset:

1. On the MPD232, load the Cubase preset.
2. In the Editor, use File - Load from Hardware to get the active preset config into the Editor.
3. Edit any settings that you'd like to fine-tune (perhaps the channel 1-8 buttons). The Cubase preset Pad Bank A mappings are nicely set to MIDI Channel 10 notes and worked fine for me without changes, and the Control Bank A channel 1-8 rotaries (pan) and sliders (volume) are nicely mapped to MIDI Channels 1-8.
4. In the Editor, use File - Save As to save the changes under a new preset name. I tried Cakewalk as a first choice but it only accepts 7 characters max so CbB works well.
5. Use File - Send to Hardware to store the new preset on the MPD232, either directly to RAM or to an unused preset slot (I used 15).
6. Select your new preset in the MPD232 if you picked a preset number to save it.

Next in Cakewalk, set up a matching ACT MIDI Controller:

1. In Edit - Preferences - MIDI - Control Surfaces, add a new ACT MIDI Controller with the MPD232 as its input.
2. Configure the ACT Controller via Utilities - ACT MIDI Controller 1 (or via the Controller/Surface panel). Pick a preset to start from (Akai MPK49 worked for me), then immediately overtype the preset name with Akai MPD232 and press Save (icon button) (so any changes you save later affect your new preset and don't accidently modify your starter preset).
3. Check the Enable box in Active Controller Technology, and press the ACT button to activate Learn Mode. In Rotaries Mode options, select Multi Channel. In Control Group options, select Track.
4. For each controller on the MPD232 in turn, use the control, then press the corresponding lower parameter box in the configuration panel to learn the setting. I found this a bit erratic and fiddly, but with patience eventually managed to learn each control. I also hit Save often to make sure learnt stuff got stored!
5. Open the Options tab and select Main in the Control Group.  Overwrite Buttons 1 to 3 with new names STOP, PLAY and REC respectively to match the MPD232 buttons, and pick the corresponding Cakewalk action in the dropdown selector. If their Exclude this button from ACT is checked, then uncheck it to allow them to be learnt. For each one in turn, use the button to learn it. First few times around I kept trying to do this from the Controllers tab, but suspect it always failed to learn because the starter preset Options settings had their Exclude this button from ACT checked!
6. Save the preset!

When all parameters are learnt and the preset saved, Cakewalk controllers using the Akai MPD232 preset you created should now react to the MPD232 physical controls when its CbB (or whatever you called it) preset is loaded, and its pads should now trigger kit-mapped notes on a MIDI track with MPD232 - Channel 10 as its input.

Looking at the MIDI out data from various MPD232 presets using MIDI-OX (highly recommended) was what really helped  - seeing the MIDI channels change when the sliders were moved showed that its Cubase preset was closest to what I was after. Not sure what that Sonar preset does, but no longer bothered!

There may well be other ways, and very likely more refinements possible in the preset configs, but this got me up and running with the MPD232 in CbB so hopefully can help someone else - it's great using it once they're matched up!

 

[steve-a]

Thanks @pwalpwal - been appreciating the forum for a while without registering so thought it about time I gave something back ?

[azslow3]

Sorry to say, but "ACT MIDI Controller" part is misleading... "ACT" button, "Active Controller Technology" group and "Exclude from ACT" in the options tab have absolutely nothing to do with MIDI learning the controller, BTW most users will want transport buttons "excluded", to use them as transport buttons when playing soft synths or working with FXes. Historically "ACT" has several different meanings in Cakewalk, mentioned options are related to "following context" and "dynamic plug-in mapping".

From MPD232 pictures, it has encoders (knobs can be turned endless). For controlling DAW, so for the bank used with "ACT MIDI Controller", it is better to configure them as Inc/Dec2 (and set corresponding option in "ACT MIDI Controller" by Ctrl+Clicking corresponding cells). Banks for MIDI learn inside soft synths better set to finite (not all plug-ins understand encoders and recorded MIDI can have strange results otherwise). All switches to be used for DAW controlling ("ACT MIDI Controller" supports 8 in total, but "Generic" and "AZ" Controllers have no limit) better set to CC Momentary, pads to Note without After-touch. All controls used for DAW must have different CC to avoid troubles, on separate from performance controls channel (to avoid clashes). Controls for using with plug-ins can use standard CC (to use without learning) and "unassigned" CCs to learn (CC numbers are described on midi.org and many other Internet resources).

Learning own device (reading the documentation for the device and related software) and learning software in question (in this case Cakewalk documentation, Control Surfaces section) is a good way to make a device work as desired. Randomly selecting/clicking sometimes works, but the result is random....

[steve-a]

Thanks @azslow3 for the additional insights and suggestions - much appreciated. Sorry if anything I wrote was/is misleading, and happy to be shown better ways - and yes, fully agree, given the time it takes, nothing beats deep learning of relevant topics to get things working to best advantage. But also happy that after following those steps at least I can actually use the MPD232 with CbB now instead of it just looking nice for the last couple of weeks since I got it...

Edited April 3, 2022 by steve-a
added missing word

[azslow3]

Somehow thinking that configuring a controller for a DAW is "intuitive" and can be achieved without reading the documentation is common. That was also my approach at the beginning. And I was so frustrated from the result of configuring "ACT MIDI Controller", that I have started to write my own ("AZ Controller")... Later I have learned that existing in Cakewalk instrumentation is not bad and can fulfill many wishes, once learned ?

BTW I have written in depth documentation about "ACT MIDI Controller" (interleaved with tutorial how to achieve the same in "AZ Controller", but that can be skipped):
https://www.azslow.com/index.php/topic,107.0.html

[Byron Dickens]

8 hours ago, azslow3 said:

Somehow thinking that configuring a controller for a DAW is "intuitive" and can be achieved without reading the documentation is common.

??????

+1000

RTFM, people!

[steve-a]

Cheers all and much appreciated, especially your guide link @azslow3 - very nicely done. Away now to RTFM for a while... ?

Edited April 4, 2022 by steve-a