Talk to other MIDI Designer users about MIDI Designer, iOS MIDI and related topics. Or share layouts, pages, and ideas.

Check out our Facebook Group.

Of course, if you want to send us an email, feel free.

Open problem reports

Summary of user requests

MIDI Designer
Design your perfect MIDI controller for iPad, iPhone, and now on M-powered Macs
Can a supercontrol (knob) be blocked sending cc data? - MIDI Designer Q&A

Can a supercontrol (knob) be blocked sending cc data?

+1 vote
asked Aug 28, 2018 in Basic by gurbz (2,490 points)
edited Aug 28, 2018 by gurbz
Make Similar is a bit confusing, because you the similar control gets both the supercontrols and the subcontrols of the original control. This is sometime useful, sometimes unexpected.
Yeah, noticed that.

I am replacing a lot of controls that were ‘made similar’ and this cleans up the midi data quite nicely. It’s a bit tedious procedure but hey, when’s done its done.

1 Answer

0 votes

Supercontrols do not send any data, they only move subcontrols (unless the option under More / Config / Options - supercontrols send own values is selected - this is a global option)

You can chain multiple layers of supercontrols, but only the final subcontrols actually send midi data out of MD as cc, sysex, etc.

Are you sure that is is not your subcontrol that is sending the cc data?

answered Aug 28, 2018 by jkhiser (16,170 points)
edited Sep 1, 2018 by jkhiser
Yes, the midi log is clear that the data is send. As far as i can tell there is no way to send not cc data except if you turn a control off?
You want the sub control to be display only?  Then change the control output to be something that will not impact anything on your setup.  One possibility is chose sysex, then leave the midi field blank.  This will send F0 00 F7, which nothing should react to.  This reminds me I need to recommend that Dan include some display only fields as a future update.
Thanks, that's an interesting option. I solved it another way: with streambyter plugin. B1 = XX +B (block midi channel2)
The midi log displays now incoming messages (channel2) and send messages (only channel1)
This way I send all the correct CC's on channel 1 and block the other messages on 2 so the system is not overloaded with midi messages.
...