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 Mac
Program change in Addictive Synth - MIDI Designer Q&A

Program change in Addictive Synth

+1 vote
asked Jan 24, 2014 in How does MIDI Designer work with X? by otters78 (140 points)

1 Answer

+1 vote
I've noticed that some iOS synths including addictive synth don't respond to program changes because of the way they do patches, they should really combine bank changes in those senerios but for some reason they don't.

The problem is I guess is that there is no limit to the amount of paches you can select for example in addictive synth and others you can save unlimited amount of user patches.
answered Jan 25, 2014 by midicode (1,480 points)
That is a pain!

I have the same problem when using MIDIbridge, the synth won't take on the program change, it bugs the hell out of me!

So, does that mean I can only iOS synths that have the traditional 1-127 patch number?
I'm saying these synths that allow users to save patches don't normally respond to program changes. Some synths even allow you to create new banks that you can save patches in , there's no limit to how many patches you can save so its kind of difficult for synth developers to deal with them using program change.

The only way to solve the issue is to convince VirSyn to put some mechanism in addictive synth where you can assign a patch to a programme change value.
not sure that I'm following, but do you need to send the bank change before every program change? That's what "send current value" is for, along with send multiple midi messages (google that).
Send current value allows a bank select and a program change combo? I did wonder once how a super control can send its value as well, Thanks.

If a synth doesn't respond to program change there's nothing we can do except make a request to the synth developers to implement the feature in some way.

Program change and bank select are two separate things. There's no need to keep sending bank select every time you send a program change unless you want to select a different bank of sounds.
Sorry I wasn't clear, and that there's not better documentation on this.

Send current value makes a knob sends its current value INSTEAD of the supercontrol value.

This way you can have a super of a bank change and program change knobs. The bank change knob is set to "send current value" so it sends out its current value instead of being modified by the supercontrol.

This way you can set the bank change knob to a value you want and then send bank-program changes that work.

Hope that was clear.
Yeah Dan that's how I thought it worked , just thought you was teaching me something new. Sorry about that.
MIDI Designer is designed to be pretty transparent: even though we wrote it, we're kind of discovering it again as users.

The only thing that's a bit weird about this discussion is that at times you seem to be talking about having "supercontrols send own values" to be on. Is that correct?
I've never been able to get a SuperControl to send its value, the only time I mentioned super control was in response to you?
It's an option in config. That said, we recommend not using it, generally.
Ok , Thanks.
...