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.
Anyone figured how to access an IAA app from Camelot Pro?
Apparently you can via virtual MIDI with the IAA app in the background, however I have tried several different "hookups" and selecting Camelot Midi in the setup, but I can get no interaction from Camelot to anything outside Camelot, but on the same device. Even selected Camelot Pro MIDI as a source in the receiving app.
Comments
I can't tell from what you've said if this is relevant, but ...
Be sure that the two "ends" of the connections match. If you have the target app's named port selected in Camelot Pro, then make sure the target app does not select Camelot Pro. It should have its own MIDI port selected.
Or the other way around...
If you have the target app set to listen to Camelot Pro, then in Camelot Pro do not select the target app as the output destination. Select Camelot Pro's own virtual port (if it has one) as the output.
It's a common mistake to think that you'd set the destination app in the source and the sending app in the target. But that's not the way it works. Basically both ends of the connection have to be to the same port.
Also, of course, be sure that the target app has background audio enabled.
Thanks wim - this is the age (?) old thing with Lumbeat only being IAA, trying to find a way to run it via Camelot...got program changing ok, but trying routing via different channels is a bit tricky.
As the BT pedal can only send on 1 channel, I sorta need to have each of the Lumbeat apps set to a different channel, then re-route midi in on ch 1 to those different channels in Camleot. Otherwise with all of the open they all start playing hahaha! Some pretty interesting polyrhythms going on, but not useful!
But nothing doing! pedal works as a direct source to Lumbeat. but not via Camelot....
AUM to MacOS or Lumbeat to AUv3 would be sooooo useful hahahaha!
Thing is with Camelot, is all you can do is enable virtual midi out in settings, you cannot do so in the song layers....there is no dialogue for determining where it goes...I am guessing it just sends out on all available virtual ports??
Huh. OK then you're doing it right. The target app should be listening to the Camelot Pro virtual port. What apps are you trying to connect to?
I don't have Camelot Pro so this is just going to be a guessing game unless someone who has it sees the thread. I don't get the impression there are many Camelot Pro users active on the forum. You might do a search of forum threads and see if you can identify any that you can try to PM. @sfm has done some videos on Camelot Pro. Maybe he can help.
Thanks wim....it's going out to Lumbeat drum apps. Will see if I cna find those vids....there maybe a nugget of info somewhere in those.
and Italy is still on holiday for another week, so no-one from Audio Modeling will be around either.
Ahh Lumbeats. Been there and have had such problems with their midi implementation more than once. Which apps and what specifically are you trying to do? If you don't mind me asking.
Soft Drummer, Reggae Drummer, Funk Drummer, HipHop Drummer....trying to be able to use all of them for differing songs...As they are IAA I need them all open in the background assigned to different channels. Want to control them using the IK BlueBoard (which can only transmit on a single channel).
So I need to route the Blueboard to the various Lumbeat apps over different MIDI channels which can be done in Camelot via the MIDI channel re-routing tool, however the drum apps are not getting any of that info from Camelot. I can send program changes to each from Camelot to change beats and kits on demand, but the BlueBoard control thing has me stumped!
Hi. If you have AUM or Audiobus, you can use a MIDI monitor to confirm what Camelot Pro is sending. Just load the monitor in a MIDI lane, and route Camelot Pro to it. You can still have the Lumbeats apps listening to Camelot Pro; the monitor will just be in parallel. With that setup, you can compare what Camelot Pro sends by itself, which works, with what you're getting using BlueBoard.
Also, if Camelot Pro does not need to be involved in this BlueBoard/Lumbeats interaction, you could find other apps you could load in AUM that would accept the BlueBoard messages and generate the correct responses.
thanks uncledave, however AUM is not available for MacOS
That's an important missing piece in your description of what you're trying to do. Can you describe how the Mac is involved? Where is Camelot Pro running? What is the Blueboard connected to? Where are the Lumbeats apps running?
All running on the Mac.
See, blueboard is working (confirmed by checking midi monitor in Camelot and as a direct input into the drummer), the drummer is working, Camelot can route to the drummer, confirmed by sending CC0.CC32 and PC messages...BUT for some reason the BB routed through Camelot is not being seen by the drummer.
Don't worry, and thanks for the input....it is simply not going to work. The Lumbeat apps are also showing all sorts minor bugs, not present on the iOS system.
I'm forgetting this and will try other things.
If you hookup via iDAM, I bet you can run the Lumbeats apps on iOS, send midi from Camelot Pro to them, and pipe the audio over to the Mac. That's based on the assumption that the Lumbeats apps just aren't working like they should on the Mac, or the Camelot Pro is having trouble routing to them.
... eh, but that also gives me another thought. I was trying to get midi from a DAW into the standalone Mac version of Koala and there didn't seem to be any way to do that. Then the developer told me about the iAC MIDI Driver, which is made for that purpose. All I had to do was go into Audio Midi Setup's MIDI Studio window and enable it. Voila, I was able to get midi from other apps into Koala.
Might be worth trying with the Lumbeats apps. If that doesn't work then maybe the iDAM solution above would work.
I see. I realize that the Lumbeats are now available on Apple Silicon (news to me). But IAA is an iOS-only protocol, so the MIDI communication between apps will be different on MacOS, and our descriptions of iOS virtual MIDI ports are likely irrevelant.
It sounds like Camelot is simply not relaying its modified MIDI input to its MIDI output, possibly to prevent MIDI loops. Maybe there's a setting or plugin that can enable this?
@wim Do we know anything about MIDI routing on MacOS? Is it similar to iOS CoreMIDI?
Yeah, agree! Trouble is I can get nothing from Audio Modeling (developer) as they are Italian and we know what happens in Italy at this time of the year
I have written to them.
Thanks wim, will have a look at that iAC driver!
TBH, In think if I had to use the iPad in the mix, I'd just run the drum apps standalone on it. Can attach the iPad to a stand or on a tray and interact directly with it.
In this I am trying to do it all in the one device, and to link directly between different songs.
Although an update to a post above, it seems that I can now no longer send the programs change strings to the Lumbeat apps...cannot figure out why this stopped - still looking.
Appreciate yours and uncledaves input though!
Yes - it's called the IAC Driver. It's a component I didn't know anything about until the developer of Koala pointed it out to me. Before enabling that in the MacOS Midi setup app, I couldn't get MIDI to Koala from other apps.
Yeh, after I wrote that I remembered that you had problems with keeping all the Lumbeats apps running and/or seamlessly switching between them on the iPad.
The IAC Driver might help. You should see it grayed out in the MIDI Studio Setup window of the MacOS Audio MIDI setup program. Once enabled, you should see it as a source and destination in other apps.
Thinking further about the channel change thing from the Blueboard, there might be some way to accomplish that and other routing tasks with the super-useful MidiPipe program. There's a bit of a learning curve to it, but it can do all kinds of routings, remapping, and other things. Even as just a troubleshooting tool it's super useful.
oooh yes, that sounds promising. Never heard of it! Will, check it out, thanks
EDIT: had a quick look and while in time I think I could figure it, I was thinking, it is yet another app that needs to be opened and run for a stage session, meaning another possible failure item running live....Might have to wait untilk Italy wakes up again and try and interact with the Camelot developers.
Ultimately I feel the issue is with Camelot not passing on (via it's MIDI out) midi messages that should be going out.
According to their (scant) documentation, I have it set correctly but there may be one small thing that is perhaps out of place, or in the wrong order?? That only they can identify
Just to confirm....I ran a MIDI monitor app on the Mac. Everything connected and enabled was sending/receiving data, EXCEPT Camelot Pro...so there is some issue in it. When I get some response from the developers I will report back.
That's so weird. It's made for that kind of thing.
It'd be nice if it had a manual. I find the line that it's designed to be easy enough to use that a quick start video is all that's needed a huge cop-out, especially for such a costly app.
MainStage is less expensive, more capable, easier to use, and has a fabulous manual. 🤷🏼♂️
Thanks wim, yes I agree it IS made for it.
Perhaps because the receiving apps (in this case Lumbeat), even though "universal", are still essentially IAA, hence Camelot having such issues with it?? Dunno, just hypothesizing.
Re Mainstage, I had thought of it, but was turned off by all the negative "press" re how awkward it was, and glitchy and too complicated for serious live work. I did download and had a look, scratched my head for about an hour (aided by the manual) and just gave up on it hahaha!