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.
Comments
It actually affects MIDI clock, not just notes, so no AUv3 MIDI app needs to be involved. I get the problem with AUM sending clock or notes from its built in keyboard, for example.
@ghostclub Thanks for testing and contacting Apple. I’m away from my hardware till Monday, will try Apple then if nothing interferes with my plans.
Sounds like there's a similar problem in MacOS Sonoma. So maybe a fix is on the way...
Fingers crossed, but if I can get onto Apple Support tomorrow I will - it would help if people are letting them know it affects iPadOS as well (presumably iOS too, but I’ve not checked).
Fwiw, the macOS and iOS/iPadOS teams are totally different. I wouldn’t assume that a bug the MacOS team knows about is known to the others.
It may be useful reporting the problem to Nektar as well, seeing as they're already in touch with Apple and can ask for the issue to be reported to the iOS/iPadOS team.
I won't have time to do that this week unfortunately - took long enough reporting the issue to Apple. Painful...
This defo looks like an update issue as my up to date air 3 won’t output to my sq1 but my old pro 1 that’s still on 15.xx will…
Thanks, Chris. Everything is pointing in this direction.
Cool, I’ve just done a report on the page linked above as well… 🤘👍🙏🙌🤞
Good grief. Just got off the phone to Apple Support, at 14.40, having started by message at 11.36, and been through three different people…
They have similar reports from others, my case has been attached, and it will require an OS update to fix. So it’s iPadOS 17, and it’s sit back and wait time.
Thank you to everyone who’s reported issues, hopefully we’re getting through to them.
I’m off for lie down in a darkened room.
Well done mate, doing the work of angels 🙌
The sad thing is that the people I dealt with (one via Messages, two on the phone) were really trying to be helpful, but didn’t really get the MIDI thing. I guess because there aren’t that many of us yet trying to work with MIDI in this way, and front line staff can’t know everything. The third person looked the issue up, saw there were other reports and added my case to the list. If the first bod could have done that, we’d all have been a couple of hours better off. But, in fairness, I did eventually end up with someone who could do something sensible, and there’s no way to make a helpdesk perfect. I’ve had worse results.
Thanks @bygjohn, it sounds like you got through to someone more competent than I did eventually! Great that it's on the radar already and multiple people have made reports.
I do have the reported iOS 17 problems with the Korg SQ-1 on my iPad 9 (no M1 CPU). I can receive MIDI from the SQ-1 via USB and sequence notes or sync apps like AudioBus or LoopyPro with the clock, but the other direction - sending MIDI from the iPad to the SQ-1 - is virtually dead. And this although the two output ports of the SQ-1 do show up in the apps.
Tried to upgrade to iOS 17.3.1 - still the same problem.
Drat. Haven’t tried 17.3.1 yet (notification only just came through), but obviously we’ll have to cross our collective fingers for a 17.4 breakthrough.
So I ended up reporting the issue to Nektar and they responsed almost immediately:
"Yes, we are aware of the problem. I thought that the support page also mentioned iOS but it looks like I was mistaken. I will ask for that page to be updated.
"In any case, the problem has been reported to Apple. The issue occurs with a few MIDI interfaces for Nektar and other brands. A few weeks ago, I was told that our contacts at Apple said the problem would be fixed in updates to MacOS and iOS. However, updates for both of those OSs have been released since then, so I'm not sure when the problem will be addressed."
Great customer support from Nektar but unfortunately no timeline for when Apple will fix this yet. Here's hoping it'll be fixed for 17.4 in March...
🤞 I emailed Nektar a while back, too. It’s good that they’re updating their page to include iOS.
The final Apple support person I spoke to confirmed that while iOS and MacOS development is separate, common frameworks like CoreMIDI etc will be sharing the same code base, hence it’s affecting both platforms. Which I guess is actually a bonus, as it means the problem is affecting more users, so more likely to get sorted.
17.4 update: it doesn’t fix the problem.
And, entirely predictably…
17.4.1 still doesn’t fix it.
Following this, thanks for reporting!
Great news, I think! 17.5.1 seems to have fixed this issue.
I’ve only had a 5-minute test, hence my slight hesitation, and I’ve not tested my NTS-1 yet. But MIDI clock seems to go to the right ports on my Nektar MIDIflex, and clock and notes go to my SQ-1 properly now.
I’d do a small and embarrassing dance of joy if I wasn’t currently knackered!
If anything still seems to be broken when I get the chance for more testing I’ll report back.