Receiving Sysex Value Changes

0 votes
asked Jun 10, 2015 in User Support, Resolved by helkiro (120 points)
recategorized May 17, 2016 by MIDI Designer Team (Dan)
Hi there, thanks for checking out MD12.

The question is whether the Juno actually sends back the same messages as it gets. In MD's log, what  do you see? Is there incoming sysex from the Juno?

Perhaps you have to set something on the Juno itself?
As I said, the message send from the Juno are the same.

The messages appear on the MD Log and I had used the learn function to get the sysex correct on the sliders.
Sorry I missed that. I'll have to check if there are any issues with receiving sysex in 1.7, but there are none that I know of. I'll be back.... thanks for your patience.
Hi there: there are no known issues in 1.7 sending or receiving sysex. What's your sysex string look like? What does the log look like?
The sysex property are set to: 41 10 00 00 3A 12 10 00 20 07 V 78
Checksum None and 1 Byte in Value

For the log, will need to get this later.
any checksum? does that 78 vary when the sysex comes in?
Tested again today and I could see that the end value was changing. Turned that the 78 was a checksum (Roland), but the keyboard still interpret the message with a fixed value.

Removing the 78 from the property and selecting the checksum as Roland solved the problem.

Thanks for the help!
How ridiculous that the checksum is just totally ignored by the actual MIDI target that needs it! Anyway...

Glad we got you solved!

If you dig the App and feel so inclined, please leave a nice review in the App Store.

Thanks!
Dan

Dan Rosenstark
Author & CEO

1 Answer

0 votes

Hi helkiro,

in the moment I do the same for ROLAND FA-Synths, I only have problebms with the Overdrive in Rotary-Effects, but I think, the problem would be solved!

Candy

answered Aug 15, 2015 by candy (250 points)
...