Synchronizing Subcontrol messages

0 votes
asked Oct 19, 2014 in User Support, Resolved by elkbeat (1,120 points)
recategorized May 17, 2016 by MIDI Designer Team (Dan)
they should always send in the same order. Hmmm... I'll check and confirm this empirically, but it should be working correctly. Are you sure the order is not getting changed somewhere later in the message transmission?
Can you try the following? Turn on Send On Release in the sub control knobs.
@Ezb, yes it was the first test I performed. It doesn't change the result indeed.
@ admin I'm checking output messages using MD log. I assume it to be accurate.
@ all I tested it strongly and this is what I get...
I created three subknobs (MSB, LSB, PC) and one superknob, all having 128 ticks. The superknob doesn't send midi msg.
Then I tested this set rotating superknob...
If I rotate it using finger, sometimes (2 out of 10 times) I got midi message coming out in different order (PC, MSB,LSB for example instead of the expected MSB, LSB, PC). If I use momentary step buttons to control the superknob, the messages are ok (MSB, LSB, PC) all the time. So I can say with momentary buttons the subcontrol messages are synchronized. Instead if I use finger it is not synchronized all the time, so you can not rely on it. I checked it in many different situation and I think it is something to investigate on.

1 Answer

+1 vote
 
Best answer
No.  The midi log does not always show messages in the correct order.

Testing midi designer output on an external midi monitor is the best approach to take for debugging/testing your templates.

Midi log is still a useful companion for mostly anything else.

The items in a super control are always sent in the order they appear like you expected. You can change the sending order at anytime anyway.
answered Oct 20, 2014 by midicode (1,480 points)
selected May 17, 2016 by MIDI Designer Team (Dan)
thank you midicode, good to know. I will test it with external device and let you know.
Thanks midicode for moving this discussion forward
MIDI Log is now fixed in latest beta of MD 2.0. Thanks!
...