Goodwinmcd wrote:OrionG wrote:Heyyo.
So I have all these working on my morningstar mc6 2 along with the mpclive in standalone:
PLAY: 4 127 127 6 2
STOP: 4 127 127 6 1
RESET: 11 127 0 6 68 6 1 0 0 0 0 0
RECORD: 4 127 127 6 6
DEFERRED PLAY: 4 127 127 6 3
Any chance anyone has figured out the sysex for overdub in stand alone mode?
Same for looper.
One thing to note, in controller mode you can indeed assign midi cc to control the looper but i think we're all here for standalone mode control.
I know this is old but this confused me.
Does 4 127 (4F?) Correspond to any standard midi messages? It doesn't look it.... So MPC just created their own Midi implementation?
Trying to integrate a UMI3 foot switch with it but you can only program standard messages (Note on, CC, PC, MMC, etc). Really frustrating.
(2 years later, for anyone having trouble understanding this thread)
Most MIDI gear responds to MMC messages, that is MIDI messages for Play, Stop, Record.
The MPC appears to completely ignore them, and because of this we've had to resort to using Sysex
Sysex is standard MIDI, giving the ability to talk directly to equipment, each manufacturer defines exactly how these are used.
Ideally they should document them for users, but many don't.
Sysex is usually expressed in hexadecimal, rather decimal like the above.
Sysex commands start with the byte F0, then the message in a number of bytes, ending with F7.
Using hexadecimal the full sysex messages are:
play
F0 04 7F 7F 06 02 F7
stop
F0 04 7F 7F 06 01 F7
deferred play
F0 04 7F 7F 06 03 F7
record
F0 04 7F 7F 06 06 F7
reset
F0 0a 7F 00 06 44 06 01 00 00 00 00 F7
MIDI Solutions has two devices you can program to convert MMC Play, Stop & Record into Sysex
Event Processor or Foot Controller. There is software to program them, & all sysex is in hexadecimal.
Visit their site for more information
https://midisolutions.com/prodevp.htmhttps://midisolutions.com/prodfsw.htmHopefully this helps