The DijonStock Digital Home Recording Support Forum

I'm taking a chance here, anyone know how to translate or convert the AW16G SysEx command for the Play button on the fly so that Reaper can identify it as a normal CC message? Reaper cannot 'listen' for SysEx.

art

Okay, MidiOx can do this apparently, but I'm struggling with the mapping tool.

Nope , its a Sysex message and not a CC.

_________________
THE MUSIC IS DOWN IN HERE
____________________________________________________

Good judgment comes from experience, and a lot of that comes from bad judgment.

Dang.

Really? Can handle CC's but not sysex, that strikes me as odd. So... you want the G to start reaper, any problem with having reaper start the G to achieve the same end (assuming reaper can send sysex). Can't remember if you're using a midi patchbay but the motu gizmo that Geno and I have will handle basic transport controls from the device. You may run into a brick wall using midiox to control reaper. Using XP, only the active window seems to have a voice ie. midiox can not start sonar from the same computer.

According to the G's midi implimentation chart , sysex is neither transmitted or recognised. But note one says bulk dumps are allowed. I do know MMC is allowed.

_________________
THE MUSIC IS DOWN IN HERE
____________________________________________________

Good judgment comes from experience, and a lot of that comes from bad judgment.

Yeah, I goofed around with the Data Mapping tool in MidiOx and I am able to convert CC to SysEx, this starts the G no problem. The other way around though is not supported.

You do have an option to capture a 'Start' MMC and translate that to CC, but the Yamaha 'Start' is not recognized??? You do not have a custom field to Capture SysEx in HEX, but you DO have a custom field to Send SysEx translation.

Seems like an oversight to me in the MidiOx design?

PS Mr Bill, you are right about the brickwall. Still like to solve this one anyway.

Just I know it was said...page 207 of the manual has the transport hexes for the G.

The midi imp chart (p.211) has "o" under both transmit and receive. I frequently stop and start the G using sysex messages. I'm a little fuzzy as to what the *1 means in the remarks column, all I know is sysex and the G work together smashingly.

By the way thanks Geno for the previous post on how to read imp charts.

Really , the way I understand it MMC is sysex or a form there of.

_________________
THE MUSIC IS DOWN IN HERE
____________________________________________________

Good judgment comes from experience, and a lot of that comes from bad judgment.

Trust me Geno, we're really pushing the outter limits of my midiocracy. I enter a transport hex code in the sysex event window of sonar (OK I'm paraphrasing a bit) and the G responds appropriately. Are MMC and sysex one and the same, at least for the G?

Technically MMC is sysex. In hex it is written in a sysex format. It identifies , queries , handshakes and shares a midi message with the other device and it responds. These actions alone are by definition sysex communication. Probably more correct to say that MMC is a special form of sysex as is a bulk dump request.

If it quacks , swims and has a shotgun armed following , it must be a duck.

_________________
THE MUSIC IS DOWN IN HERE
____________________________________________________

Good judgment comes from experience, and a lot of that comes from bad judgment.

Midi machine control commands are indeed a special kind of sysex. Found this on wiki:

An MMC message (that is sent to, or generated by, an MMC device) is:

F0 7F deviceID 06 command F7

The third byte is the Device ID.
The fifth byte is the command:
01 Stop
02 Play
03 Deferred Play
04 Fast Forward
05 Rewind
06 Record Strobe (Punch In)
07 Record Exit (Punch out)
08 Record Ready
09 Pause
0A Eject
0F MMC Reset
40 Write
44 Locate/Go to

Or get sequencer that can send MMC?

Orc