AKAI MPK mini Plus MIDI Remote Script

I hove made a MIDI Remote Script for AKAI MPK mini Plus.
I will share for you🤗️
You can download from my GitHub repo “/flyinghog88/cubase-midi-remote”.
Please read akai/mpkmini_plus/README carefully.

*This post is second time. Becouse my account was suddenly deleted.
*I can not post links, yet. Please post link for my GitHub repo as reply.

Just been looking at this for a compact keyboard controller. I see there’s a script for the original mini in Cubase 13 already. Did you adapt it? Couldn’t find a script for the plus at Akai.

I also couldn’t find an official script for the mini Plus, so I created my own by referencing the mini mk3 script available in Cubase 13 and using Steinberg’s official documentation. (Since I’m a professional programmer, this is my area of expertise.)

Sounds good! Thank you for sharing.
So your Plus script has all the functionality of the non-Plus factory script?
I don’t have the thing yet but knowing compatibility is there is key. Looks like a nice size to keep permanently in front. My current big thing too often gets pushed out of the way.

i have looked at your script and I’m not sure how to edit it. I know I should edit out the japanse language and the MAC os lines. I assume with / / ? I did as you said and looked at my midi port names for the mini plus. They are
AKAI MPK MINI P for both my in and outs. can you please assist me in editing this? I can not seem to edit on your page directly. Is it ok to use something like notepad and save with the appropriate extension? When I drop into notepad, the colored text becauase black. I’m not sure if this is important. i will be happy to buy you a cup of coffee to figure this out. Thanks you so much in advance.
DJ DUDE

This script cannot be used with the non-Plus version. While Cubase 13 includes standard scripts for the mini MK2 and mini MK3, there was no script for the mini Play.

The size is perfect, and it has more than enough features, so I’m very satisfied with it. In photos, it looks deep, but in reality, it doesn’t take up much space. I initially bought the mini MK3, but the number of keys was too few for my needs, so I switched to the mini Plus.

Of course!

I can update the script for you, but I need more information about your environment.

Windows or macOS?

The port name seems to be truncated, so please try expanding the window to see the full name.

You can’t edit the script directly on the GitHub page. Download it by clicking the green “<> Code” button and selecting “Download ZIP,” then edit it with a text editor. When saving, do not change the file name, extension, or folder structure. The colors are just for readability on GitHub and are not relevant. In a text editor, everything will appear in black.

I would love to have coffee with you, but since I live in Tokyo, that coffee might be quite expensive! (laughs)

Thank you

Os is windows 11 pro
I don’t have the version number currently because I’m not at home for almost another 24 hours.

It seems as if cubase 13 pro for windows has a character limitation on that port names. I use (or trying to use) a new connectivity mioXL It has the same character limit as cubase or so it seems.

Tokyo, how interesting. I have a flight attendant friend who flys all over Asia including Tokyo , Singapore, Malaysia, etc. he has said Tokyo is VERY expensive. At least I know I could hit up a vending machine for whatever type of coffee you like! Ha!

Thank you for procedure with GitHub. I will try when I get home.

An aside, I’m not sure what the native windows port name would be. I didn’t think to look in device manager. If we knew that, you might be able to homogenize the port your script looks for.

So kind of you to help. Seems like I’m always trying to figure out new stuff with Cubase. Unfortunately I have a bunch of gear (new or new to me) to kearn and not enough downtime. I certainly appreciate you taking your time away from your project to help!

Otsukaresamadeshita

@djdude
I see…

If we can determine whether Cubase is abbreviating the original port name or if that’s the actual port name, we can take appropriate action.
I also want to complete this script to support Windows, so I’d appreciate your cooperation.
Please let me know once you can confirm the port name.

This port name is used to identify the connected device. Ideally, we could use the Vendor ID and Product ID obtained through MIDI System Exclusive Messages, but since I couldn’t find the ID information for the mini Plus online, we have to rely on the port name for identification.

Maybe I should contact AKAI…

Japan has experienced significant yen depreciation recently (1.5 times compared to a few years ago), making it quite affordable for inbound tourists.:+1:
On the other hand, for us Japanese, overseas travel has become incredibly expensive.:cold_sweat:

Hi, you may want to try sending the sysex to your controller so you can have its info. You can use this: F0 7E 7F 06 01 F7

@m.c
Thank you. I tried that, but I didn’t get any response…

Wait… was that before I resolved the port name issue?
I’ll try it again…

@m.c
I did it!
Although I couldn’t see the response in Cubase’s MIDI Monitor even after disabling the filter, I was able to capture it with another MIDI Monitor!

@djdude
So, I have updated the script.
It now identifies by the Product ID, so it should work on both Mac and Windows regardless of the MIDI port name.

Github - Cubase 13 MIDI Remote Scripts
Click the “<> Code” (green button) → “Download ZIP”.

Great :+1:

I have to guess that the id response is just too special message and consumed by Cubase upon receive for use in its own id recognition function.