Problem iPad softsynths?

Question

Using MIDI Designer  Pro 1.6.2, iPad 4, IOS 7.1, iSem 1.0.2, iMini (latest version)

So I've built a couple of (what I consider killer for my use) layouts for Arturia's iMini and iSem. Well, layout-wise, at least, they're killer for me and the way I intend to use them.

Then comes time to actually assign the MIDI CC info to the layouts, and that's where I'm running into problems. Nothing responds. Check Config and everything is set to either iSem or iMini (per layout and MIDI channel)

I've hooked up a Korg Nano Kontrol to my Mac and assigned the knobs and sliders via the Korg Kontrol Editor for each of the four scenes, reassigning defaults for each of the knobs, sliders, buttons. Good to go.

Then I went into Arturia's iSem and launched MIDI learn based on the Nano Kontrol, which seemed to work. Until I went into MIDI Designer, setup the MIDI CC numbers, and alas, no joy. Then went back to iSem only to find it would delete the CC numbers I assigned it once I assigned them in MIDI Designer, leaving blanks.

As a quick attempt to see if I'm going crazy or not, I tried assigning the CCs manually in Magellan, and all seemed good in a new layout. WTF?

So I guess what I'm asking here is, are there some iPad softsynths that just have software issues like this (Arturia iMini and iSem) and others that don't have the problem? Haven't tried Thor, Sunrizer, Z3TA, Cassini, Mitosynth, Nave, and others yet, but is there a a known issue list somewhere of iPad synths that have issues with this type of thing?

Many thanks for ANY insights here!

Comments

The real question for me is, does the same thing happen with the Korg if you just switch to the home screen or another app that's NOT MD? The reason this is so important is that we're still trying to figure out if it's an MD problem or just a problem. Glad to help in either case, but in one case we won't sleep and in another we'll sleep pretty well ;)

---

OK, just got home and tested it with an Arturia MiniLab. Went to Midi Learn in Sunrizer, set Effects Send to CC 72, then got out of Midi Learn. Next turned the physical knob at CC 72 (which should have turned Effects Send, right?). Alas, it moves the OSC 1 Width (which is set to CC 75 in Sunrizer). Switch back into Midi Learn in Sunrizer, and it still shows Effects Send at 72. So then I exit Sunrizer by Quitting it (swipping up) and relaunching it. Now the Effects Send is blanked out again.

Weird. This is also the problem I was having with iSem, where it just keeps loosing all my Midi Learn settings. So it looks like it wasn't MD after all, just need to look for another way around all this.

---

The coincidence between Sunrizer and other apps is too weird and very suspect.

Try weird stuff like entering settings, saving settings (if there is such a thing), etc. Many of those things might trigger a save... Also make sure to exit to the home screen first before killing the App, as it might cause a  save whereas just killing the App might not. Etc. etc. Hand your iPad to a 3-year-old and see if they can get it to work. When all is said and done, we'll figure it out and then they'll be able to fix it from our awesome bug report ;)

---

I tried everything last night, and still the problems persist, both with Sunrizer and with iSem. Pulling my hair out, leading to heavilly drinking in frustration... It's not MD's fault, Dan, and I realize that, it's these soft synths that don't seem to be holding the Midi Learn, which is a complete drag. Just thought this morning about deleting each synth and re-installing it to see if that cures it. Went to both Sunrizer's and Arturia's forums and noticed that neither actually answered anyone's questions (which is certainly a testament to you and your commitment to MD). I'll let you know what I discover soon.

Thanks again for all your help in this mess, Dan!

---

Sorry to hear that their forums aren't really doing much. Tech support becomes a box people check off, without actually reading anything. We've noticed that the default in 2014 is to have awesome questions, no answers and little discussion. But there are exceptions!

Anyway, yeah, whatever you do, diagnosing problems should be a slow and methodical process. Drinking cannot help you diagnose better, but some other things might help you think outside of the box, especially if you're in CA or CO or WA... HOWEVER, I don't have any brilliant suggestions about getting them to save MIDI learn.

On the support front, though, I'd suggest emailing the devs, calling them out (respectfully) on Twitter, etc. They might answer some channels way better than others. Oftentimes it's just a failure to have a good alert system.

Thank you for your interest and passion. Oftentimes, though, we are diagnosing a situation that we could sidestep, use something else, etc. And those solutions only come when we walk away from the problem.

Good luck!