Debugging controlling MPC Live II with Sysex/MMC

Hey all,
I'm trying to control the transport on my MPC Live II with MMC Sysex commands. I'm generating the messages by catching CCs and replacing with Sysex, using a 'Mozaic' script (https://ruismaker.com/mozaic/) as the controller (Keylab Essential MK3) doesn't send MMC.

I can confirm that the Sysex is being generated successfully and received by the MPC:


This is displayed on a Windows MIDI monitor on a parallel stream, it's not printed on the MPC MIDI log but the MIDI input alert flashes when this signal is sent -- leads me to believe that it's being received.

(I got the Sysex data from this thread: viewtopic.php?t=186979)

I have checked the 'receive MMC' command on the MPC and the correct inputs are assigned to receive control information.

Can anyone suggest any more strings to pull on in debugging this? AFAIK everything is set up and working correctly apart from the actual behaviour of the MPC.

Thanks,
Oscar

Unfortunately MMC receive has been broken on the MPC since version 2.14 and is still yet to be fixed.

Guess that explains that then

Thanks

For future visitors trying to do this kind of thing, there's more info and Mozaic script being discussed here:

https://forum.audiob.us/discussion/6165 ... aic#latest

Oscar South wrote:For future visitors trying to do this kind of thing, there's more info and Mozaic script being discussed here:

https://forum.audiob.us/discussion/6165 ... aic#latest

Cool....

I don't think what you had would of worked any how.

You had ..

F0 04 7F 7F 06 02 F7 (for play)

The '04' should not be there for a MMC command.

MMC messages need to start with a F0 followed by 7F.

The correct format would be:
F0 7F 7F 06 02 F7 (for play)

HTH

submo wrote:

Oscar South wrote:For future visitors trying to do this kind of thing, there's more info and Mozaic script being discussed here:

https://forum.audiob.us/discussion/6165 ... aic#latest

Cool....

I don't think what you had would of worked any how.

You had ..

F0 04 7F 7F 06 02 F7 (for play)

The '04' should not be there for a MMC command.

MMC messages need to start with a F0 followed by 7F.

The correct format would be:
F0 7F 7F 06 02 F7 (for play)

HTH

I had gotten these from this thread:
viewtopic.php?t=186979

But I think you may be right -- I checked what data my old MPD32 sends from it's MMC pads and these are the messages:




Not sure where the 04 value came from for the purposes of that thread (they seem to have gotten their device working) but the AKAI device doesn't send it.

Oscar South wrote:Not sure where the 04 value came from for the purposes of that thread (they seem to have gotten their device working) but the AKAI device doesn't send it.

I think those numbers where being used to configure pedals, rather than actual midi bytes being sent. I think some pedals did require a message length parameter at the beginning in their configuration for sending a sysex messages, with the 04 being the length of data bytes. This is not needed for standard MMC, which as you've shown should start F0 7F.

You could try rolling back to 2.13 if you really need MMC, and don't need Stems.

It also might be worth reporting this to Akai too if this bug is affecting you also.

submo wrote:

Oscar South wrote:Not sure where the 04 value came from for the purposes of that thread (they seem to have gotten their device working) but the AKAI device doesn't send it.

I think those numbers where being used to configure pedals, rather than actual midi bytes being sent. I think some pedals did require a message length parameter at the beginning in their configuration for sending a sysex messages, with the 04 being the length of data bytes. This is not needed for standard MMC, which as you've shown should start F0 7F.

You could try rolling back to 2.13 if you really need MMC, and don't need Stems.

It also might be worth reporting this to Akai too if this bug is affecting you also.

That's definitely it. The Mozaic function for Sysex also requires a data length param to be sent, but it's sent as a separate parameter so it's more distinct.

submo wrote:Unfortunately MMC receive has been broken on the MPC since version 2.14 and is still yet to be fixed.

Does anyone know if this has been fixed and/or if 3.0 has the problem?

Lil ill wrote:

submo wrote:Unfortunately MMC receive has been broken on the MPC since version 2.14 and is still yet to be fixed.

Does anyone know if this has been fixed and/or if 3.0 has the problem?

Been working for a while on MPC3.X

Lil ill wrote:

submo wrote:Unfortunately MMC receive has been broken on the MPC since version 2.14 and is still yet to be fixed.

Does anyone know if this has been fixed and/or if 3.0 has the problem?

MPC3 can receive MMC properly.

Does anyone know how to map mmc for the "play from start" button on the mpc one +???

Nobody I can find anywhere out there seems to know..

I've been trying to map a nektar pacer footboard pedal to it for a few days now and have everything working but that one button.

Chris collins wrote:Does anyone know how to map mmc for the "play from start" button on the mpc one +???

Nobody I can find anywhere out there seems to know..

I've been trying to map a nektar pacer footboard pedal to it for a few days now and have everything working but that one button.

The Play Start button is actually a combination of two messages: a Locate to Start message
F0 7F 00 06 44 06 01 00 00 00 00 F7
followed by a Play message
F0 7F 7F 06 02 F7.

Elijah wrote:

Chris collins wrote:Does anyone know how to map mmc for the "play from start" button on the mpc one +???

Nobody I can find anywhere out there seems to know..

I've been trying to map a nektar pacer footboard pedal to it for a few days now and have everything working but that one button.

The Play Start button is actually a combination of two messages: a Locate to Start message
F0 7F 00 06 44 06 01 00 00 00 00 F7
followed by a Play message
F0 7F 7F 06 02 F7.

My memory is a bit blurry from when testing this. But I'm pretty sure I also needed to send a Stop command as the first message for the Locate to function. So "Stop, Locate, Play".
But please post the verdict if you get it working with only Locate and Play.

horisonten wrote:My memory is a bit blurry from when testing this. But I'm pretty sure I also needed to send a Stop command as the first message for the Locate to function. So "Stop, Locate, Play".
But please post the verdict if you get it working with only Locate and Play.

You're right. To simulate the PlayStart button while playback is already running, it seems necessary to send "Stop, Locate, Play".

"Locate, Play" only works when the sequence is stopped.