Hello Guest

Crazy "bug" ? MMC start/stop

  • 5 Replies
  • 298 Views
*

crony

  • **
  • 85
    • View Profile
Crazy "bug" ? MMC start/stop
« on: July 23, 2018, 04:45:55 PM »
Hi Josef,

I've got a new very tricky one... :D

My ArturiaBeatStep is sending a MMC start and a stop, see 2 Sysex here:
F07F7F0602F7
F07F7F0601F7

But, my midi interface is transmitting:
0602F7
F07F7F

0601F7
F07F7F

So the packets seems hashed in two, with a different order...

I tried my 2 midi interfaces in loop mode, and they both transmitting that way.

At the moment, the workaround is to use MidiFlow to put it the right order, and it works instantly...
I just applied 2 rules :
Remap :
0602F7F07F7F to F07F7F0602F7
and
0601F7F07F7F to F07F7F0601F7

I thought at the beginning the order was not correct, but the Sysex works fine...
I checked that :
https://en.wikipedia.org/wiki/MIDI_Machine_Control#MMC_Message_Format

But it just confirmed that you're doing the job well, and midi interfaces from the 90's are doing something else...
I know it sounds crazy but I guess all midi interfaces with AUM will have this problem !
That would explain a lot of issues (???)

Is there a way you could ad this order also in the responding MMC to AUM ?
I found a workaround by assigning an other CC common to start/stop, but for people who may wonder why MMC from a rock solid midi interface couldn't launch AUM, that could help a bit...

Thanks a lot !

Nicolas

« Last Edit: July 23, 2018, 05:58:36 PM by crony »

*

crony

  • **
  • 85
    • View Profile
Re: Crazy "bug" ? MMC start/stop
« Reply #1 on: July 24, 2018, 12:15:45 PM »
Feel stupid, today it's working perfectly...

*

crony

  • **
  • 85
    • View Profile
Re: Crazy "bug" ? MMC start/stop
« Reply #2 on: July 26, 2018, 05:23:47 AM »
Ok, it came back ! :D
Seems totally coming from my midi interfaces as in bluetooth there's no problem.
Well...I wonder if it could corrupt Link somehow, because after some time, Link connections are crashing also...
« Last Edit: July 26, 2018, 05:25:24 AM by crony »

*

crony

  • **
  • 85
    • View Profile
Re: Crazy "bug" ? MMC start/stop
« Reply #3 on: July 27, 2018, 05:06:48 AM »
Okay, keeping the things weird...
BM3 still answering to MMC even in disorder, but AUM doesn't...

So it seems there are different "orders" accepted by some MMC implementations and some others don't...

I'm trying to setup a rule with StreamByter not to launch MidiFlow...

But Josef, could it be possible to include and allowing receiving MMC in a different order into AUM ?
It seems it's something that happens completely randomly, but seems a standard somehow...

The workaround with a different CC has limitations as AUM has one CC for start/stop, but BM3 has 2 midi actions for start/stop (like MMC)
So it's a bit tricky...

Thanks for considering :)
« Last Edit: July 27, 2018, 05:28:01 AM by crony »

*

crony

  • **
  • 85
    • View Profile
Re: Crazy "bug" ? MMC start/stop
« Reply #4 on: July 27, 2018, 07:18:28 AM »
Tested with midi port of Iconnectivity Audio 4+, same result...

Re: Crazy "bug" ? MMC start/stop
« Reply #5 on: August 22, 2018, 11:09:20 AM »
A note for other readers: this issue has been fixed in the current beta.