Article Development[edit]

Still missing: meaning for code 8

Supposedly existent: Rehearse mode, reverse play, loop mode, shuttle/jog, chase, mute channels.

> Is it possible to use MMC to query devices for their current status such as
> armed tracks, locate points, etc ?

Supposedly it is. Where 0x01 is stop and 0x02 is play, there still are commands

 0x40 (write)
 0x41 (masked write)
 0x46 (search)
 0x42 (read)
 0X4c (move)

which supposedly can read/write fields such as

 TIME_STANDARD         0X45
 MCTALLY               0X48
 REC_MODE              0X4C
 REC_STATUS            0X4D
 TRACK_REC_STATUS      0X4E
 TRACK_REC_READY       0X4F
 GLOBAL_MONITOR        0X50
 RECORD_MONITOR        0X51

If anyone has managed to get these to work on any device, documentation about that would be welcomed.

Identity Request Section[edit]

I am removing the Identity Request section, since it is not an MMC message. It is not even a Real Time SysEx message. It is a Non Real Time Universal SysEx message. If it is included in Wikipedia, it should have its own section in an article about those SysEx messages. I did not check whether the removed section's info is correct. DocRuby (talk) 01:11, 5 July 2013 (UTC)[reply]

Identity Request[edit]

Query an MMC device to find out its identity. Identity Request message (note that this is equal to a 'stop' message):

F0 7E channel 06 01 F7

The reply is device/manufacturer specific. For example, a tape recorder will return the following System Exclusive message:

F0, 7E, channel, 06 02 ID fc1 fc2 fn1 fn2 v1 v2 v3 v4 F7

parameters:

ID - Device's ID 
fc1 fc2  - Device's family code 
fn1 fn2  - Device's family number 
v1 v2 v3 v4 - Software Version