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
If the loop is getting pitched up, something weird is going on…as loopy’s time-stretching doesn’t change pitch.
Can you zip up a set of loops with which you have a problem and post them somewhere to download?
Are all of the loop’s the same sample rate? If loopy mishandled sample rate conversion that could cause a pitch change.
You if you also zip up your project where things have gone wrong, I could take a look and tell you how to fix it and hopefully how to avoid issues in the future. It’s possible there is a bug being triggered and with this example @Michael can address it.
@robosardine : is time-stretching on in your preferences?
@robosardine : worth knowing if you swipe up on a clip, the track overview will show what it thinks the original tempo was and you can change that if loopy guessed wrong
Is it possible to import samples into Loopy straight into tracks on the timeline view?
You can drag/drop from Files to clips but not to the timeline, You need to get the audio into a clip first
It’s worth noting there is a bug in .22 with un-phase locked loops and time stretching – they sound very strange for a little while until the background process has finished. That’s fixed in .23 which I’m about to release
I see. Thanks!
Strange though...
Cheers - I can’t send an example though as I binned the whole lot after the recurrence from the last time I tried it ages ago.
Everything was exactly the same. I had one large file from a jam - cut it to 512 bars in AudioShare - opened it in Auditor - divided it down by halves to 8 bar loops - exported the lot to Files App - binned the ones that didn’t work in AudioShare then dropped them on individually from Sample Crate - so they were all the same size and all from the same stable.
Having said all this - I’ve just been at it again for the past several hours and it all seemed to go ok this time, if I get it again I’ll keep it and send it over.
Time Stretch was on (I’ve switched it off now)
Many thanks 👍
@robosardine : if you do run into issues, save the problem files . Michael is quite active in checking issues out and often the particular files speed up finding a problem.
The scope of Loopy Pro is massive . So, it is expected that things will crop up that haven’t been seen reported… and they can only be addressed if reported.
I had been wondering about the very same thing 😃…. when the clips are loaded on they are each allocated a lane in the sequencer, then you just tap on the timeline and they appear. I need to work out how to actually switch it on so that I can hear it… but that will be for another day.
I’m starting to wonder why I didn’t persevere with this a while back 😏 .. duh!
When you add events to the timeline, pressing play plays the sequence. The letters SEQ appear at the top of the screen when in the donut room. Clicking on SEQ toggles whether the sequencer is on or off.
Sweet. Thanks man.
Not sure if I've missed this, but is there a way to trim samples exactly to beats/bars - like a snap function?
Can you say more about the context?
Indeed: Essentially I'm importing audio I've made in AUM which is say 10 seconds long. I want to trim part of that audio in Loopy pro so that it's exactly 1 bar. I know you can do this in the donut settings but there doesn't seem to be a snap function there and it seems trick to get it exactly right.
Is the audio at the current tempo with the places where you the markers to on precise beat divisions?
There is some snapping when moving the brackets (at least when time-stretching is off) but it is finicky. It seems related to the speed you move your finger at. On the phone there is haptic feedback when crossing beat boundaries.
It would be nice if one could turn on a grid. I think it is on the roadmap (I know it has been requested but haven’t checked to see if it is somewhere on the roadmap/suggestion site)
you can work around it by adding the clip to the sequencer and trimming there (where the snap points are less finicky) and resample into a new loop from there.
Is there a way to export a clip with the color fx/auv3 applied?. I know I can Resample to a new clip but wondering if there’s a faster way that I’m missing.
Resampling is it at the moment or putting it in the sequencer and exporting the sequence
Everything was exactly the same. I had one large file from a jam - cut it to 512 bars in AudioShare - opened it in Auditor - divided it down by halves to 8 bar loops - exported the lot to Files App - binned the ones that didn’t work in AudioShare then dropped them on individually from Sample Crate - so they were all the same size and all from the same stable.
Which I have since discovered was a complete waste of time because I could have done this far quicker and much more efficiently by using the Retrospective Recording feature….. at least I’ve got a lot to look forward to now 🤗
When I open a new project after previously starting with a home made template then saving it to a new name in AUM - it always reverts to the original template name? I open it by pressing on the newly saved name- but it has reverted back even though the new name project has loops in it as they should be?
I take that back partially - some of the loops I thought were saved in column 1 have now vanished 😕
Can you make a screen recording showing the entire process? There may be some critical step triggering this. I can imagine the possibility of tension between AU state-saving and Loopy’s own project saving in some cases… so a video that shows a recipe for the problem might help identify the issue.
When you load an AUM session, it includes the state of the AUv3s as they were when the project was saved. But the AUv3 does not necessarily know the name of its preset. After all, you may have modified the state since loading a preset, so there really is no "current preset". This means that the preset name displayed by the app is essentially meaningless.
Strange - I was attempting to make a screen recording - but now there is no name appearing in the box at all. Shortly after this I also had a crash when having many of the circles loaded - so I had to start again with the whole experiment. Even though I had saved the project in AUM - it had vanished from the list. I think some of the issues might well have arisen from having multiple instances of LP open at the same time using the same preset. Anyway - I am now going to save projects in the app itself which seems a lot more cleaner and reliable. Next time I have a problem like this I will record it there and then so that it’s readily available.
What @uncledave said seems to make sense as well - and I can of course give it an instance name an colour in AUM - though knowing my luck with LP something will go awry before long there as well.
Many thanks
@robosardine : a couple of thoughts, running several instances of Loopy Pro is something that seems to sometimes result in memory faults for some people. I’d make a habit of saving explicitly a little more often than you would otherwise.
When you say it vanished from the list even though you save it in AUM, what is the “it” and what list?
Also, if the AU crashes, it is helpful if you send the log to @Michael . AUv3 crashes create logs these days but might not automatically be sent to devs.
It was the name I had given that particular preset for the saving list in AUM at the time. I opened the preset list to load it - and it/they were gone completely. I think that maybe playing several instances is perhaps more safe than trying to record into several. I had LP open in one lane and another open in another lane. I was trying to record into the first column in LP - save it, then reopen it in the other lane and record into another column with another instrument after opening the saved version there. Probably not the recommended way to go about it, I’m not even sure how much of the problem that was likely to have caused - but probably a fair bit.
I will certainly be making a habit of saving regularly from now on.
I don’t know how to send a log - I’m not sure how to go about it. I’ve turned on ‘share with app developers’ in settings - will this now send crash logs automatically?
I have to say - I’m having a great time with the app now despite any hiccups that I’m having. It has given my creativity a real boost and has my workflow has sped up considerably as well, even though I am just learning the basics still. Quite incredible really. This will be at the centre of things for me from here on in.
Cheers
I am glad to here that this go-round is going better than your introductory one. I feel pretty confident that LP will continue to grow (in both power and reliability).
Here are details about how to find and send crash logs:
https://loopypro.com/manual/#reporting-crashes
It is possible that AUM doesn't save its presets lists frequently. For saving actual data (as opposed to empty templates), I would not use AUM's preset list. I am not sure when AUM does the actually saving to 'disk' of the preset data.
I would either explicitly save the AUM project (which will save the current state of everything -- and in Loopy state includes audio) and/or use Loopy Pro's save mechanism. Or both.
I think if you do that, you won't run into as many glitches.
Btw, my sense is that there has been less feedback from people using it as an AU than as a host -- so there may be some issues that you'll see that Michael doesn't know about.