Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Opening Gadget app makes my MIDI keyboard stop working
I am sorry to contribute another Gadget thread, but I hope that this one is different enough to at least be interesting.
I am currently using a Yamaha SY99 synth as a MIDI controller, connected via MIDI DIN to an iConnectAudio4+ which is connected to my iPad. The strangest issue is happening to me - if I turn on my SY99, and then open the Gadget app on my iPad, it somehow seems to "disable" MIDI on my SY99. The SY99 not only stops sending MIDI to the iPad - it also stops making sound on its own! If, after opening Gadget, I hard-restart the SY99, then MIDI functionality returns. Further, if I am holding a chord on the SY99 while I open Gadget, the MIDI notes hang for a second, and then cease. It is as if opening up Gadget sends a "permanent" MIDI Panic message to the SY99, silencing it until I restart it.
If I first open Gadget, THEN turn on the SY99, then all is well. But obviously, there is some problem here.
Does this sound like a problem with Gadget itself, or with my iConnect interface, or with the SY99? I am going to do some further troubleshooting when I get home, but there are many variables here to test. No other app causes this problem (including other Korg apps Module/iM1, as well as other DAW/host apps AUM and GarageBand).
Comments
I wonder if turning off the NanoKEY and NanoKONTROL native mode settings for Gadget (in Other Settings) would have any effect? Maybe Gadget is sending some Sysex meant to discover or set up their controllers that is crashing the SY99. It's an easy thing to try at any rate.
Otherwise my next guess would be some kind of a MIDI loop.
Hah - good catch! That did it. I didn't even know that that was a setting, so I never would have looked there.
Thanks - I was getting nervous, as I'm planning on using this setup as my live rig. Feel much better now.
Mm mm. Pretty bad that Korg would be munging up other hardware with their proprietary gunk.
@wim I think that in order for the nanoKEY native modes to work, there has to be two-way communication. For example, when you change the scales in Gadget, the Scale Guide and Easy Scale notes change. So Gadget controls the controller. And also I believe that when you select a new Gadget, the nanoKEYS sees that and then remaps the cc's in the nanoKEY so that all the Gadgets work in similar ways. This is complicated, so I don't think Korg is going to change any of this.
I suppose it is the same for the nanoKONTROL.
But it's an easy fix for people to simply turn off native mode if they are having issues with another controller.
I'm surprised that @dtaki had the native modes turned on by default. That wasn't the case for me, but if Korg does that, they should stop.
@Reid Sure, I understand there needs to be sysex going back and forth between Gadget and the nanoKEYs in order to recognize and set them up. The thing is, that process can and should be done in a way that doesn't crash other devices.
I agree they're not likely to care about that, but they should. MIDI is like a networking protocol, lots of devices can be in the network and can see traffic whether it's intended for them or not. You can't have one bad player crashing other devices sitting on the network. Sure it's an easy workaround to turn that off, but it shouldn't have to be done.
Moot point. Even if the OP or someone else brought it up with Korg, I seriously doubt it would be worth the time.
I should mention that I also occasionally use a Korg Microkey61 (mk1) - although it has not been connected the last few times I opened Gadget. It seems likely that the first time I connected it and opened Gadget, that setting turned on, and subsequent times that I opened the app simply remembered that setting. This, of course, is assuming that the app views the Microkey in a similar light (MIDI-wise) as the Nanokey.