MPC Live Midi implementation list/SysEx messages

Did you check that when you send « PLAY START » from an external controller as two SasEx :
F0 7F 00 06 44 06 01 00 00 00 00 F7
F0 7F 7F 06 03 F7
It starts playing not from 1.1.0 but from 1.1.198 ?
I can’t understand the cause, but my Live works like this.
I use XSonic AIRSTEP as the controller.

Does anyone know what the Manufacturer ID and Device ID are for sending SysEx messages or how to get them?

I'm trying to get my Live 2 set up with an M-Vave Chocolate Bluetooth controller. It can send SysEx messages, but none seem to register with the MPC. I've confirmed CC messages are received (though I haven't yet been able to get a CC to do anything), and have Receive MMC on. I'm brand new with MIDI programming so I'm sure it's user error.

I'm also trying to connect the m-vave chocolate bluetooth pedal to my mpc one+. It receives midi messages, but the sysex codes don't seem to be correct. Did you manage to solve the problem? Any suggestions?

The MPC doesn't seem to have a sysex implementation per se. It doesn't record to sysex messages, and the only ones it responds to are MMC messages which are a subset of the universal system exclusive messages. But that's broken in the latest version,

https://github.com/TheKikGen/MPC-LiveXp ... ode-how-to

Did play around with this a little when I was testing iamforce.
Need to sort SSH out on 2.15 and have another play.

Shame I can't address pads 17 onwards while still on bank A but still useful

eLuSiVeMiTe wrote:https://github.com/TheKikGen/MPC-LiveXplore/wiki/MPC-and-Force-global-midi-mapping-in-standalone-mode-how-to

Did play around with this a little when I was testing iamforce.
Need to sort SSH out on 2.15 and have another play.

Shame I can't address pads 17 onwards while still on bank A but still useful

If these work on a 'final' MPC2 release with critical bugs fixed, I might go down this road myself. There isn't a working version of the OS though which isn't years out of date and missing other core functionality (I think the last fully working version is 2.8, unless it has other issues that write off that release too).

I appreciate everyones dedication to figuring these things out. i was able to get the standard controls working, but still trying to figure out the sysex messages to switch between different sequences. the + and - buttons would be ideal to map to my morningstar. does anyone have any idea how to do that? Ive been stuck on this for daaaays and im not programmer so i dont even know where to start. from what ive read theres no way to dump info from the standalone mode so i cant figure it out, Honestly i have no idea how anyone even figured out how to control the play etc buttons in the first place.

So I recently messed with the new MPC3 beta and it seems like the reason the sysex information is broken in 2.14 and 2.15 is because the commands have changed for the new software. for example, my start/stop commands no longer work. but rec and reset are fine. Hopefully this helps someone else down the line. I submitted a form to Akai about this issue as well.

Shimsh wrote:I appreciate everyones dedication to figuring these things out. i was able to get the standard controls working, but still trying to figure out the sysex messages to switch between different sequences. the + and - buttons would be ideal to map to my morningstar. does anyone have any idea how to do that? Ive been stuck on this for daaaays and im not programmer so i dont even know where to start. from what ive read theres no way to dump info from the standalone mode so i cant figure it out, Honestly i have no idea how anyone even figured out how to control the play etc buttons in the first place.

You can change sequences using program change, not SysEx. Check the settings under Prefs > MIDI/Sync > Program Change.

Shimsh wrote:So I recently messed with the new MPC3 beta and it seems like the reason the sysex information is broken in 2.14 and 2.15 is because the commands have changed for the new software. for example, my start/stop commands no longer work. but rec and reset are fine. Hopefully this helps someone else down the line. I submitted a form to Akai about this issue as well.

My previously working MMC and sysex commands from 2.13 are all working again in 3.4beta without any modifications -- in case that's useful info.

@Elija, the idea of sysex messages is to start play and rec by extern devices. Yes, it is possible to switch sequence by a program message, but while playing it waits until the current sequence is completed. With sysex you can send a program change AND a play AnD a from start message so it imediately switches sequence on request instead of after currently playing sequence finished
So it is very, very annoying that after update 2.15 my MPC has become useless for live performance.
Everybody does of course the best work they can do at Akai, but this is really a very, very bad choice to not fix this in 2.15.1
And, NO, I am not going to version 3.
I chose MPC to not have the problems with updates I had with my iPad. But it seems that we are back at unusable stuff by some board taking decisions on commercial purposes, instead of quality

Elijah wrote:

Shimsh wrote:I appreciate everyones dedication to figuring these things out. i was able to get the standard controls working, but still trying to figure out the sysex messages to switch between different sequences. the + and - buttons would be ideal to map to my morningstar. does anyone have any idea how to do that? Ive been stuck on this for daaaays and im not programmer so i dont even know where to start. from what ive read theres no way to dump info from the standalone mode so i cant figure it out, Honestly i have no idea how anyone even figured out how to control the play etc buttons in the first place.

You can change sequences using program change, not SysEx. Check the settings under Prefs > MIDI/Sync > Program Change.

the idea of sysex messages is to start play and rec by extern devices. Yes, it is possible to switch sequence by a program message, but while playing it waits until the current sequence is completed. With sysex you can send a program change AND a play AnD a from start message so it imediately switches sequence on request instead of after currently playing sequence finished
So it is very, very annoying that after update 2.15 my MPC has become useless for live performance.
Everybody does of course the best work they can do at Akai, but this is really a very, very bad choice to not fix this in 2.15.1
And, NO, I am not going to version 3.
I chose MPC to not have the problems with updates I had with my iPad. But it seems that we are back at unusable stuff by some board taking decisions on commercial purposes, instead of quality

[email protected] wrote:

Elijah wrote:You can change sequences using program change, not SysEx. Check the settings under Prefs > MIDI/Sync > Program Change.

the idea of sysex messages is to start play and rec by extern devices. Yes, it is possible to switch sequence by a program message, but while playing it waits until the current sequence is completed. With sysex you can send a program change AND a play AnD a from start message so it imediately switches sequence on request instead of after currently playing sequence finished
So it is very, very annoying that after update 2.15 my MPC has become useless for live performance.
Everybody does of course the best work they can do at Akai, but this is really a very, very bad choice to not fix this in 2.15.1
And, NO, I am not going to version 3.
I chose MPC to not have the problems with updates I had with my iPad. But it seems that we are back at unusable stuff by some board taking decisions on commercial purposes, instead of quality

Even if MPC2's MMC receiving functionality is restored, it is still not possible to switch scenes seamlessly in the middle of a bar. Sending messages like MMC Stop, Program Change (Scene Change), and MMC Play will cause the playback head to return to the beginning when the scene is changed.
If possible, try MPC3, as it has working MMC receiving functionality.

This thread has been super helpful for setting up my MC6 to control the MPC. Thank you all for the information here!

I can play, rec, stop+reset, sequence change with PC scroll.
One thing I can't figure out is if there is a way to send a stop all samples (like double tapping the stop key on the MPC)?
I have tried sending multiple stop messages on a single tap. One after another or with a delay between. Is there a different message I could send instead? If anyone has any insight or ideas I would love to hear!

Hey, all, found this thread that seems to address some similar issues I’m running into with my new Line 6 FBV Express MKII.

I’m hoping to use my FBV as a transport control for my MPC Live with overdub, play, stop, and play from start buttons. I’m getting pretty close but not all the way there.

To start, I ran into some operating system issues, but found another thread that let me know I had to downgrade to firmware 2.13 (from 2.15) in order to support incoming MMC messages.

So now that im on the correct firmware, I’m able get the standard MMC messages from the FBV to work (record, play, play/stop, stop) which is ok, but I’d really love to get ‘overdub’ and ‘play from start’.

What’s extra frustrating is I am able to get all the buttons to work as intended via mapping/midi learning when I either use the MPC DAW alone or along with the MPC in controller mode. It’s when I use the MPC in standalone mode the way I normally do, though, that I cannot map/learn those functions.

Anyone has any insight? Is it possible to translate the available sys ex messages that some are using to into Midi CC I can program into the FBV?

Thanks in advance for any help.

-JV

Reference Pics
1. https://drive.google.com/file/d/1y_mQnXi3elf_gZeI6P-jFQutohFAI-Z2
2. https://drive.google.com/file/d/12PS-n93CMbmihF2z8fxe5CHjoEQazJ6T