-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support MPK Mini Play #1
Comments
There's something odd about this dump. The content states 0x63 (99 decimal) bytes, but the byte count is only 79 decimal... This is shorter than the configs for Mini MK1 (102 decimal), which has less items to configure, and much shorter than for the Mini MK2 (109 decimal). |
Like I mentioned, I just faked a device by enabling a Midi loop-back with the name 'MPK Mini Play'. If you'd like to help (once you get your hardware), use to connection panel to 'wire' the outgoing Midi from PC to MPK Play so that it also goes to a recorder. Send a program and recorded the SysEx which is actually sent. You should be able to use 'amidi -p XX:2 -r dump.bin'. I suspect that it may be in a couple of different blocks, which would explain the above confusion... Here's some details on the MPK MiniMk2, there's also the script for reading/adjusting the configs: The MPK Play is probably different enough to warrant a new script, hopefully somewhat similar though. |
I think I see why the MPK Play has a smaller config file, it does NOT send Prog and CC messages for the pads. The device doesn't have the extra buttons (CC and Prog) and these items are missing from the configuration editor. This would 'save' 24 bytes: It also has 2 banks of 4 dials, rather than 1 bank of 8. Thought that requires the same amount of config/bytes. |
Santa left you a gift :-)
|
Assuming that the MPK Mini Play behaves similar to other devices.... The python script 'mpk_play.py' can take the configuration settings (miniplay_ram.zip) for the device and change certain parameters - such as the note/sounds/etc. The configuration settings themselves are a SysEx patch and can be directly downloaded to the device:
The dump ('-d') from above is a human readable version of the configuration. Normally you'd use the other command line parameters to change settings and then upload the new configuration to your device.
The settings are stored into the preset (termed 'favourite' by Akai) held in the configuration, this can be changed with the '-p' parameter. If you store a new configuration onto the device, you may have to select that particular 'favourite' again, to load it into current/RAM setting. There is likely a SysEx command for retrieving the configurations (device->PC) and changing which is selected on the device. |
It hung but still ctl-c canceled then found a file... $ amidi -l $ amidi -p hw:2,0,0 -S 'F0 47 00 34 12 00 01 01 F7' -r recall_1.mpdplay |
The file that you posted does not look like the SysEx Config files that I have seen before. The command that you give is for retrieving config from the MPD218: I believe that you want to adjust it with the following ID's
So I think that the retrieve command should be similar to the MPK Mini MK2 command... |
Is this helpful ? $ lsusb $ sudo lsusb -d 09e8:44 -v Bus 001 Device 035: ID 09e8:0044 AKAI Professional M.I. Corp. $ amidi -l $ amidi -p hw:2,0,0 -S 'F0 47 7f 44 66 00 01 01 F7' -r recall_1.play $ hexdump recall_1.play |
Yes, that does help. :-) It shows the same issue as the MPK Mini MK2, in that the 'files' recalled from device have a 0x67 rather than a 0x64. I saw that this needed to be corrected before they would upload. See: It also has a slightly different ID and length count. I have just fixed these in the parser. If you are up for some more experimentation... it would be helpful if you could retrieve all 8 presets from the device.
As above, once the 0x67 is changed to 0x64 it should be possible to change and upload these back to the device
Note: You may need to re-select the preset/favorite on the device (hold 'favorite' button and press pad) to bring the new settings into the RAM of the device... this is needed on the MK2. |
Make and zip all in one place $ mkdir presets $ cd presets/ |
Well the presets are all rather boring ;-) Seems that Akai did not change anything between them - previously I saw that the MPD218 was pre-configured with different settings for different applications (ie. preset 5 for working with MPC Essentials). Were you able to change the preset settings and upload to your device? |
I am working on what I think are missing fonts for WINE due to failure during upgrade to Ubuntu 18.10 Then I can get PLAY editor to run on same system. Favorite 2 has selected different keys and drums but no difference in dumps $ hexdump recall_2.play I can watch with kMidimon when editor gets FAVORITE 2 then FAVORITE 1 with different patches. 22051,45.9564,0:1,,ALSA Port subscribed,131:0,24:0, 183265,381.8130,0:1,,ALSA Port start,131:1,, Just figured how to use kMidimon to get NEW buffer then do Get favs 1 and 2 and save as attached file that shows the parameter and data changing. Also, I had turned on time stamp from when I was working with Roland MIDI clock. kMidimon columns are |
You should look closer... there is a difference between the following. Seems you have changed the key and pad sounds. |
Good eyes ! Next, I plan to decipher why some songs freeze the Akai MPK mini Play. |
I'd still like to know whether my python script can change the settings and whether you can upload the configuration to the device... You kMidimon approach only records data from the device, it might be helpful to see what the editor sends. Although I suspect that we already know everything it does. For the MPK Mini MK2 I experimented a lot with SysEx commands to the device, and was able to figure out a few more 'commands'. The data you posted at the start of this thread suggests that 'we' might be able to read (and set?) the Program/Global memories of the device, this would likely take a lot of experimentation to understand fully. Re stuck notes. The device should be able to respond to 'all notes off' and 'panic' MIDI messages. |
I'll try your script once I can fully grasp how it is built or sent in use. The attached text earlier is bi directional but I agree I should see the request to send or else it is saying source 0:1 data 1 131:1 is all that is needed. What ever that means. |
@mungewell K5 64 Sustain - Behavior Prefer to use CC indicated in the screen and on device. Eventually want the LPD8 knobs to do same as PLAY knobs but no documentation found of what FILTER, RESONANCE REVERB AMT, CHORUS AMT LPD8 and Play send data of attached kmidimon log when editors request PRESET 1 |
You may be interested in this comment from Akai [edit] this is what that page used to say...
|
We already support the MPK Mini and MPK Mini MK2, so why not the Play?
Akai Editor stores the patches in a non-SysEx way, but does send them to the device as SysEx (very similar to the others). The editor uses the Midi name to locate the device, and that can be faked with midiLoop (*).
The text was updated successfully, but these errors were encountered: