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.
[SOLVED] Nanokey Studio lost connection with Korg Electribe Wave on iPhone
Anybody else has Nanokey Studio connection lost with Korg Electribe Wave on iPhone (7 Plus here)?
This is only with native NKS mode enabled in settings: I start playing with keys and knobs and connection is lost after 30 seconds max, I need to power off/on NKS and connect it to app to make it work again. 100 % reproductible.
When native mode is disabled, there are no issues, midi learn works well too.
Never had any issue with NKS in all other apps including Gadget native NKS mode.
Comments
I just had a 10 minute play on my iPhone 7s and it was fine. First time I tried the NKS with KEW. Super fun!
Batteries maybe? Or close all apps and reboot?
I recall having the same problem on my iPhone 6 with Gadget, but it worked fine with GarageBand. Never did figure it out, on iPhone SE and iPad 2017 model no issues. Hope you can crack it, it was super annoying
Are you connecting directly in KEW, or through the BLE Midi app? I was connecting directly in the app, and had no other apps running. No other bluetooth (headphones, speaker, etc.) either.
This happens only when connecting directly in the app, and while moving automapped knobs, not while playing keys to be more precise. No other apps are running.
Again, this is only in native NKS mode:
BTW, native mode doesn’t seem to add anything over regular midi learn not native mode: it’s then possible to use NKS banks to permanently assign controls to everything including mixer faders, and as synth assignments will follow in app selected synth, disabling native mode and make custom mapping seems to be the way to go with KEW/NKS combo. I will report my native mode issue to Korg however.
Well, all I can say is I’m having no trouble whatsoever with native mode. There must be some difference, and it’s always helpful to developers if that can be identified. Did you try rebooting? What iOS version are you on?
Have you got a 7 or 7 Plus? Yes I’ve rebooted, use iOS 12.1, I’ve reinstalled KEW, changed NKS batteries, tried on internal speaker and headphones, try with enabled/disabled background audio, network midi, disable auto-lock options, and that changed nothing. When I turn a knob in NKS native mode BT connection is lost (NKS even not visible anymore in settings) in less than 5 seconds, the app is frozen for a few seconds I can’t move or play anything in KEW screen, and strangely NKS led is still steadily blue... never happened before, always have been perfectly stable with all other apps or even over BT midi/audio gear.
I love how you can scroll through drum pad samples with the #1 knob in native mode. That is super handy.
Good to know thanks, this gives some motivation to report my issue to Korg. I can’t use native mode long enough to discover all its features
Like Gadget, KEW works flawlessly with GarageBand as IAA input with midi clock or with Xequence. And in app controls and effects/automation capabilities seems pretty deep. Sounds really good and contemporary, nice to have in the palette!! NKS support is nice to have even if I’ve got the issue I know Korg is efficient at fixing things even if that usually take some time. Black Friday price was also a pretty good deal! I always like to experiment new apps, this is also what I like with iOS, even if one semi-complaint here is KEW workflow which is very different from my usual workflows so I’ll need to learn that. And I find keyboard and controls a bit small even on iPhone 7 Plus. Strangely I use Gadget/most other iOS apps mostly with 7 Plus touchscreen and I was feeling using NKS with KEW like an almost immediate necessity, as everything is a bit too tiny. Must be better on iPad for this app.
I have an iPhone 7. No matter what I do I can’t make it act up. It’s going to be difficult for Korg to address unless they can reproduce it. Hopefully maybe some others here will make the attempt.
Dumb question maybe but I have to ask ... have you checked the App Store to be sure you’re using the latest version of KEW?
... humm. And now that I think of it, I remember upgrading the firmware of the NanoKEY at one point. I wonder if that’s possibly making the difference?
Hey you!!... clever guy!!
thanks you!!!
Works much better no more issues with 1.07 update from 1.05!!
Everything is here:
https://www.korg.com/us/support/download/product/0/551/#software
Download system updater connect your NKS via usb and hold oct- and sustain buttons while powering on, 4 upper drum pads should be steadily enlightened.
Then run system updater. I had to uncheck all boxes to being able to make the update on Windows:
Thanks again @wim, you made my day
You should check that your NKS is updated too!!
Edit: took me something like 10 minutes for writing this post, and NKS/KEW connection still going strong!!
I really agree, very good implementation
Cool beans!
MF keyboard is ideal to use with KEW on iPhone:
Audiobus preset 'KEW MF': http://preset.audiob.us/Wp4NaUkWYxEVKJX
Thanks very much for this - very useful.
@Janosax Hmm I remember updating it once, next time I think of it gonna have to check it out and see, there’s probably been an update since I did it last. Thanks! Always forget stuff like this lol..
You’re welcome!!
Yes me too! All my software is always updated, but for hardware I tend to forget/avoid as sometimes that can leads to issues, rule being if that works and firmware update don’t adds features or fix things you encounter, try to avoid it: don’t break something that works well, especially true for motherboard bios. In this case that was useful.