Helix SMPTE compatible?

[wilkinsi]

Since MIDI over USB is set to ON, MIDI PC Send and Receive are both set to MIDI + USB; I expected the Command set to MMC Play for the designated footswitch would send an MMC command via USB into my DAW. I have already set the DAW to receive sync from the Helix via USB. This means I may have to risk spending £260 on a USB/MIDI interface. My DAW has an SMPTE-Z plugin, allowing me to send an SMPTE signal through an audio interface's analog out. Is Helix compatible with SMPTE?

[Digital_Igloo]

There's no MTC or SMPTE in Helix, as there's no HH:MM:SS:FF timeline with which to reference. Sync is limited MIDI Clock (Tx and Rx), which is par for the course in even the highest end effects processors.

[rd2rk]

Might be helpful to name your DAW. Mine, Sonar Platinum, is not compatible with mmc, although older versions were.

[wilkinsi]

My bad. I was thinking of two things at the same time.

 

I first of all would like to get MOTU Digital Performer to respond to MMC PLAY and STOP from Helix. I then wish to send SMPTE from DP9 to my Roland VS recorder. However, since neither my MOTU 8D or 112D have any analog outputs whatsoever (they're digital only), I was thinking of using Helix as an interface to carry the SMPTE signal from DP9 onto the VS recorder. MOTU say their SMPTE-Z plugin inserted on a mono track and routed to an analog output of any connected interface will work.

 

HELIX > MMC via USB > MAC/DP9 > SMPTE-Z > USB > HELIX analog out > VS Recorder SMPTE input.

 

Hope that makes better sense.

[rd2rk]

Assuming that you have already configured dp9 to recognize the helix as both audio and midi device, look in dp9's configuration pages for a way to enable mmc. If you can't find it, try their support/FAQs/forum.

[wilkinsi]

I already found and checked the "enable MMC" box in DP9. I may have to try MIDI CC or CC toggle instead. I am still in contact with MOTU Tech Support regarding this matter.

[wilkinsi]

As a general rule, is MMC transmitted through the Helix USB OUT?

 

If the answer is no, then I need to get myself a USB/MIDI interface.

 

If the answer is yes, then I'm not sure why this isn't working.

[rd2rk]

Do you have a MIDI monitor? If you're on a PC, get MIDIOX (it's free). There's something for MAC, but I don't know what it's called. There's also a VST MIDI Monitor. Once you have a monitor, see EXACTLY what the Helix is sending, that way you can tell the MOTU guys YES it's sending and exactly WHAT it's sending.

[rd2rk]

And YES, MMC is sent from the Helix over USB.

[wilkinsi]

Yep - MIDI monitor in DP9 shows MIDI input from Helix is always ch16, even if I change it on Helix.

[rd2rk]

When I got my Helix, I was looking through the Templates and found the DAW REMOTE (MMC). This is what the "START" message looks like in MIDIOX -

 

SYSX: 240 127 127 6 2 247

 

When it did nothing in SONAR, I went looking around for info on how MMC works. I found this:

 

"Sysex messages do not support MIDI channel numbers, so the model and unit number are necessary in order to target a specific synth in a MIDI chain that contains multiple synths from the same manufacturer."

 

And this:

 

"MMC Message Format[edit]

An MMC message is either an MMC command (Sub-ID#1=06) or an MMC response (Sub-ID#1=07). As a SysEx message it is formatted (all numbers hexadecimal):

F0 7F <Device-ID> <06|07> [<Sub-ID#2> [<parameters>]] F7
Device-ID: MMC device's ID#; value 00-7F (7F = all devices); AKA "channel number"
Sub-ID#1: 06 = command
  Sub-ID#2:
  01 Stop
  02 Play
  03 Deferred Play (play after no longer busy)
  04 Fast Forward
  05 Rewind
  06 Record Strobe (AKA [[Punch in/out|Punch In]])
  07 Record Exit (AKA [[Punch out (music)|Punch out]])
  08 Record Pause
  09 Pause (pause playback)
  0A Eject (disengage media container from MMC device)
  0B Chase
  0D MMC Reset (to default/startup state)
  40 Write (AKA Record Ready, AKA Arm Tracks)
    parameters: <length1> 4F <length2> <track-bitmap-bytes>
  44 Goto (AKA Locate)
    parameters: <length>=06 01 <hours> <minutes> <seconds> <frames> <subframes>
  47 Shuttle
    parameters: <length>=03 <sh> <sm> <sl> (MIDI Standard Speed codes)
Sub-ID#1: 07 = response
  Sub-ID#2: response state
  parameters: values detailing response state"

 

----------------------------------------------Looks like Greek to me!

 

I tried contacting L6 support about using this template, but I got the impression that they didn't want to get into it.

 

I wound up using CC#s to control the transport in Ableton and the built-in ACT controller functions (which use CC#s) in SONAR.

 

I suggest you look for similar functions in DP9.

 

If someone from L6 knows how to use the DAW REMOTE (MMC) template, I hope they'll chime in here.......

[wilkinsi]

I tried the MMC template in Reaper and it worked. But Reaper doesn't make it easy or obvious to carry out other tasks.