Embedding super control values into midi commands on sub control

Question

REVISED:

I need a byte injected into a SYSEX command, where the value of the byte is provided by a super control.

 

I have tried using a channel changer, but as the value I need is either 50h or 60h, Midi Designer crashes when I try to set the default mid value to 50h. That makes sense though as the value I want is outside the range of 1-16 that a midi channel would use.

A midi command might look like this:

41 00 00 00 1C 12 60 00 20 14 V

But be changed to this

41 00 00 00 1C 12 S 00 20 14 V

S would represent the current value of the super control.

 

Answer 1

Yes you can.

i suppose you are using sysex.

In the sysex message the byte that represents the channel has to entered as "L".

Then use another control as Channel Changer and make this a super of the control that is sending the sysex message

Comments

Awesome suggestion! Ok but isn't the channel changer limited to 00h - 0Fh values, where we need 00h - FFh as a value range. If a channel changer allows a full range of 256 values, you have the solution :)

---

i don't this, never had the need for that many values. You have to try it.

---

Using a channel changer doesn't work, in fact to cut a long story short trying to do so crashes Midi Designer, as I suspect having a have of 60h and 50h on the channel control is out of range of the 1-16 channel number expected.

I think the original feature request still stands, but the architecture of the channel changer injecting its value into subcontrol is a perfect design pattern, we just need to be able to inject the value of a slider, which isn't specifically a channel changer, it's just a provider for a value between 00-FF/

---

I am pretty sure that the channel changer value range can be higher than 16. I don't know if the limit is 128 or more. Till now I've only used this to change the channel byte in sysex messages. Will try it and let you know my results.

---

Guys, please let's remember: "to cut a long story short trying to do so crashes MIDI Designer" doesn't really help us find and fix the bugs. Anything that consistently crashes MIDI Designer is an awesome, replicatable bug and WE NEED TO KNOW ABOUT IT, otherwise we cannot fix it and get you working again.

Channel changer supers are limited to 127, not to 16.

Both of you are kindly invited to get in touch via the in-app mail and get on the Alpha/Beta test team. It's a separate App that gets installed, so you can test as little or as much as you want without affecting your production MIDI Designer (and it's cool to get an Alpha and Beta to  play with, too).

Right now the only values you can inject are channel changers (L)... We've been talking about injecting more values (X, Y, Z, etc.) but it's not a feature yet.

Thanks so much for the enthusiasm and great dialog.

Best!
Dan

---

Well I really have no issue with this.
I can also say that I am using not as a channel changer only. I realized am using it for 2 byte sysex messages that exceed the possible number of ticks available for the controls. For eg I use a second knob to change the second byte of a sysex stream and have access to all the possible values(16384). Very useful!!

---

Yeah, we definitely didn't contemplate multi-byte values. We will when we consider other variables...so for right now it's a suggestion... and a possible bug report for the crash. Thanks!

---

When I get back to my rig I'll write down the scenario that I found which consistently crashed. But it does sound to me like kraftf is doing exactly the same thing that I want to achieve.

@Dan, I'd be honoured to be part of the test program and will be writing a clearer definition of suggested features that I'd find useful in my VG99 layout.

---

Thanks @Chris, please get in touch via in-app mail or use any other method...

---

I've got two pages of controls working now where a channel changer is used to modify a byte in a Sysex cmd. Setting the default value on the changer manually seemed to crash MD. I'll put together an email with a test case and template so you can reproduce.

---

Hi Chris and thanks for this. We've done some initial testing and cannot replicate. If you want to try to whittle down your example to just one page, or even just two controls, that would be great, please. Thanks!

---

I can't replicate this either now. At the time I was doing a fair bit of Make Similar...but then I flicked to using Save Page/Load Page, to duplicate large sets of controls, after which I'd have to set the default value on the Channel Changer to wire it to the alternate signal path that the new page was intended to control.

Please feel free to park it for now. If I come across it again I'll resubmit.

Many thanks for the follow up

---

Well I did replicate this crash.
It happens for me in a Sussex fader. If you change the midi range( min-max) and the default value doesn't get updated to be inside the midi range.  If you try to change it then MD crashes.
Have not tried this with other midi messages.

Answer 2

Yes you can.

i suppose you are using sysex.

In the sysex message the byte that represents the channel has to entered as "L".

Then use another control as Channel Changer and make this a super of the control that is sending the sysex message