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.
Loopy Pro Questions
This discussion has been closed.
Comments
I always get that kind of offset, mentioned it in the Loopy Beta Slack channel. I’m not 100% certain but I seem to recall that over a long period of time you could actually tell the loops going out of sync.
Like I said, in my case i get this offset consistently. I usually move it back to 0 cos it doesn’t feel right and also cos it gives me TOC! 🤪
This post caught my eye because quite a while back I was working with a project that used AUM/Mozaic/Xequence2, and I had to add a pre-Delay of about 25ms (I can't remember all the details now, sorry) to wait for a signal. Perhaps it was relevant. I can try to look back at my notes and see what was happening then. Sorry if my post is irrelevant.
So I'm starting to get into this part to control some external hardware. Have a couple questions regarding this:
1) if you have a widget on multiple pages that is assigned the same cc value, is it possible to have the widget update between pages? Here's an example of it not updating. Fader 1 is assigned to the same midi channel and cc on 2 pages
2) in the above video, my end goal is to have the knobs above change what they control depending on which fader (track) is selected on the bottom. Anyway to accomplish this without having 20 pages?
Is everyone else using a controller keyboard? Because it’s impossible to play the on screen keys and tap on a donut to quickly capture something right?
I don’t understand how people are using AUv3 instruments and LP? I mean, the synth is totally in the way! What if I want to mess with a certain parameter while I’m playing the on-screen keys and record what I’m doing?
With record quantization you can have as much time as you need between tapping on a loop and playing on the keyboard. Say, for instance you have a master clock length of four bars. With count-in quantization set to Master, you only need to tap the loop somewhere within that four measures and it'll not start recording until the top of the cycle. If Count Out Quantization is also set to master, it'll automatically stop after four bars. That's just one of many ways you can set it up. You can also do custom count-in and out, for instance.
I find that with most apps, if maximized, I can still get to any controls I need to when the keyboard isn't maximized. Of course on a phone, that gets challenging - as it does in any host.
When I need to, I break out my NanoKEY Studio for a quick Bluetooth hookup. A midi controller of some kind is something anyone making music on iOS pretty much needs, IMO. But more often than not I can find a screen arrangement that works OK, at least on my iPad. ymmv.
All MIDI Processor means is that it can both send and receive MIDI. MIDI Instrument means it could be used as something that can generate MIDI without receiving it.
Not exactly. MIDI Processor means it can send and/or receive MIDI but not audio. MIDI Instrument means it can make sound as well as send and/or receive MIDI.
A processor in a MIDI strip can be controlled from an external control and can also control other apps.
No, it isn't always a Synth AU. It's any app that can (optionally) produce audio, and (optionally) can respond to and/or produce MIDI.
(Just to twist your brain a little, for instance StreamByter, which is MIDI only and produces no audio, can be slotted into a MIDI slot as either an instrument or midi processor, an instrument slot as an instrument (producing no audio but receiving and sending MIDI), but not as an audio effect. Loopy can be loaded as all those in addition to being loaded as an FX.)
The distinction is only in the host. If you load the Instrument AU in a MIDI channel in AUM you won't have anywhere to route the audio.
Having fun imagining the mind-tilt this post is probably triggering in you right now.
A challenger has arrived.....
Apple has created mind-bending confusion by their AU plugin types, with their overlapping characteristics, and made it so much more confusing by their horrible developer documentation. Hell, there's not even a succinct and updated reference to all the different four letter type codes, and explanation of their functionalities.
For instance kAudioUnitType_MIDIProcessor (aumi) doesn't have one word of explanation when you follow the link here: https://developer.apple.com/documentation/audiotoolbox/1584142-audio_unit_types/kaudiounittype_musicdevice.
Oh, and you also can't change a plugin type after the fact without breaking every project that uses the plugin. This is why some plugins have more than one type.
Thanks.. Did not see it…
👍🏼 I hope you find it useful as an example. There's some good ideas from @espiegel123 that I implemented in there. I wouldn't have figured that one out without his insight.
FWIW, I put Drambo as an audio source when I want to use it as a MIDI controller. That way, each of its tracks can be routed to another instrument.
If I load it as a MIDI AU, then it only has a single track.
It only has a single track with the default template that loads, but you can add additional tracks, each with a different output channel if you like.
Thanks! That’s a very handy tip!
Ok, this makes sense. Thanks @wim, as always ,for your articulate and kind response
Hi--I'm re-posting a question I asked in a Koala thread as it seems to maybe be a Loopy issue.
I’m trying to use koala in loopy pro — loading any sample via “import audio” in koala (even short 1 shots) gives me an error msg - “Operation couldn’t be completed OSStatus error -10875)
The sample appears to load on the pad then the error message happens when I tap the pad.
2017 iPad, IOS 15.1. Loopy pro 1.0.2
(After asking this in the Koala thread it was suggested I try "import audio" in Koala AU in a different host. I did and it works fine in AUM)
Any ideas?
Update -- I tried rebooting my iPad and now am simply get "the AU has crashed" message
Koala does seem less stable in Loopy than in AUM and it may be a Koala issue. See if there are Koala crash logs in the Analytics section of Settings on your device and send copies to both @elf_audio and @Michael
There was another AU that seemed less stable in Loopy than AUM and the developer determined that their AU needed an update and that solved the problem.
@espiegel123 Thanks--I found crash logs and will send
Apologies for not reading through this fine long book, but could anyone please point me in the direction of a menu etc for connecting either my Arturia Keystep (wired) or NanoKey Studio (wireless). I swear I did this a couple of weeks ago, but now back and jumping on the LP train I cannot find the right buffet car etc.
Go to the mixer and tap the + button. Choose Add Midi.
If you haven't looked through it, the manual has a lot of good information in it and is available from Loopy Pro's Help menu.
For the NanoKEY Studio, go to Settings > Bluetooth. Or, there's a Bluetooth icon at the top-right of the Add MIDI screen.
This is like if back when audiobus was released there was one forum post “audiobus released” and one forum post “audiobus problems” and and that’s it.
If specific questions don’t get their own posts, then what’s the point of a forum?
https://forum.loopyapp.com/
That’s the real place for Loopy questions.
Or join the Discord
Do you have a question? No one is going to prevent you from asking a question. Did you read the opening post of the topic? The reason I started it was because it simplifies the task of collecting common questions that they can more easily be tracked and used as a basis for topics on the wiki. Sometimes it is more efficient to have a few threads rather than a zillion.
Thank you!