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.
USB hub seems to work but doesn’t (Digitakt)
Hi,
I’m using an Apple original usb-c adapter with a usb hub to connect various devices: Digitakt, zedi audio interface and a keyboard. The usb hub is just a regular one I had around, it’s powered (although that doesn’t seem as relevant with usb-c). I’m on a 2018 iPad Pro with iOS 15.
Here’s the thing:
When connected to the hub, the Digitakt is recognized as a midi device by the iPad (AUM, Zenebats, wherever) but it doesn’t send or receive midi. Now, if I connect it DIRECTLY to the iPad adapter , no hub, it works as expected. The zero audio interface works with the hub.
To me this doesn’t make sense. As it’s long as it’s recognized it should work… right?.
Is this hub thing a thing?. Just trial an error?.
Wonder if someone has encountered this kind of situation and can shed some light.
Cheers!
Comments
How about connecting the hub direct to the iPad’s USB-C port with the appropriate cable? Bypass the Apple adapter.
@tahiche. What if you connect only the Digitakt through the hub; remove the audio interface. I'm wondering if the Digitakt has some audio capability that conflicts with the interface.
Sounds unrelated but does iOS 15 support multiple audio interfaces?
No, it doesn’t. Only one shows up, the latest one. If I want the Zedi10 I have to power it after the Digitakt.
But I’ve put the Digitakt in usb midi mode, just in case.
The hub has one of the old mini-usb connections, I’d need a usb mini to usb-c which I don’t have and it’d probably cost the same as a new usb hub.
I pretty sure I tried it aswell. But as I said before, the Digitakt is in “only midi” mode, plus the Zedi10 has no midi, so there shouldn’t be a conflict there.
I actually talked about what might be a similar case here . A usb-to-midi device that showed up in AUM but was unresponsive, which is pretty much the same as happening with the Digitakt.
What baffles me is that the device (Digitakt) shows like connected. It’s probably “advertised” by the hub but then makes no further connection.
Btw I also tested with a Voicelive3 connected to the same hub and this one did receive midi… weird.
It's weird indeed. The only help I can give you is that I've mostly used Bluetooth MIDI dongles with my Digitakt because I try to avoid cables whenever i can.
I had a similar problem yesterday, now I think about it.
My OP-Z was plugged straight onto my iPad with a USB-C to USB-C cable, and worked perfectly as an audio interface. But the midi would’t show up at all.
Maybe this is an iOS 15 problem?
It sounds like, even though the Digitakt is in USB MIDI only mode, it is being dropped by iPadOS in favor of the audio interface. After all, the Digitakt is only one device, supporting both audio and MIDI, and that's the device seen by iPadOS. Configuring it to send only MIDI doesn't change its USB interface; it only limits the data to be transferred.
This makes sense, but I’m not convinced. Here’s some points where the “single audio interface” theory doesn’t add up:
@mistercharlie i didn’t try this same setup before iOS15 so I can’t tell. Did your issue with the OP-Z only happen in iOS15?. It’s a tough one to blame on the iOS since it seems to be somehow related to the hub… and you have no hub.., 🙃
@tahiche Yes, only on iOS 15. I shall check it again now to see if it has magically fixed itself.
@tahiche . A USB hub (not those monster docks) is a pretty simple device, buffering and forwarding messages. It has no idea of their contents. Computers with multiple USB ports already incorporate docks, so they're everywhere.
Have you power-cycled the Digitakt since turning off its audio interface? I assume you have, but that might be necessary for it to configure its USB interface as MIDI only.
What happens if you connect the Digitakt after the audio interface? Does it block the audio interface, even though it's MIDI-only? That would imply that iPadOS is somehow recognizing its audio capability.
The fact that the Voicelive3 interface works differently may only show that its USB interface is implemented differently.
Certainly, iPadOS 15 may have introduced a bug in handling these multi-function interfaces. Sometimes working code is updated by someone who doesn't understand the full scope of its functionality.
Not sure if this is helpful but I have a similar set up and it’s working as expected. The only difference is I’m on an iPad Air 3 with lightning connector and OS15. I connect the MOTU4 and the digitakt through this cheapo powered hub (the only one they had at the computer store near my place—shop local!). The last device to connect (or power) is recognized as the audio interface, but the digitakt and any other MIDI device remains active as source and destination, no matter the order they’re plugged/unplugged.
To eliminate weak links maybe you can try with another hub?
Yes, I’m gonna try with another hub, will have to wait till next week.
And I’ll try the cheapo usb-to-midi thing again, I’m suspecting it’s the same issue.
Indeed the fact that the Voicelive3 works fine is a mistery.
Thank u all for your comments and help 🙏