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
@Samu , Audiobus Forum superstar : Thanks once again!👍🙂
@VirSyn I think it might be a good idea to add a settings for 'voice limit', 'buffer size' and 'ram cache'?
I know the iPad Air 2 is not 'super fast' but it's quite easy to get into crackle fest (1024 buffer in AUM) with pads having a bit longer longer (~3s) release times. The source sample is <1mb so it should be kept in ram to avoid un needed flash/disk read access.
When 'crackle' starts to happen notes get stuck so a 'midi panic' could come in handy as well.
I think I've had enough AudioLayer for today
I just re-opened the app and tried that patch and it works fine now. So I think what I described above only happens when creating or editing a patch. If I have time I’ll dive deeper to see how to replicate it.
I have it installed on my iPad 2018 and created some new "instruments" (wave file and AudioLayer settings).
Then I installed it on an old iPad 2 with 12GB of storage. It runs slow there but it does run. I was surprized to find my "instruments" in the list. The custom wave samples get downloaded to the iPad 2 after confirming I want them there to run the new "Instrument". I created a pretty light weight instrument making a piano with 3 layers using 3 different Piano C octaves. I also created a heavier one with 3 layers from 3 waves and it crackles on the iPad 2. So, it can run on an iPad with 256MB of RAM but just barely. Creating very light weight instruments with short wave sample would help. Let me try my iPhone 5S now.
Nice
I'm in BM3 about 90-95% of my time on iOS--it just fits my sample-happy workflow. If I didn't turn around and use multi-layered pads in my live act, I wouldn't have gone for this app. But, for playing live, especially just being able to bring an iPhone, this is nearly ideal.
You are so knowledgeable with what I would term EDM. There has to be a new acronym for current TechKnow/Remix music genre.
So, I'm curious. I'm beginning to understand what "sampler" can mean for different uses. I jumped from acoustic instrument world that records with audio interfaces and typically mics into this IOS music creation world. So, I don't have the "resample" understanding that makes EDM function using tools like Ableton, etc. They are another continent to me.
This "sampler" is right in my lane: import wave files and play them across a MIDI controller using FX. I needed this to have more instruments live in my DAW so I don't have to keep freezing to audio to add another track. I can also point a MIDI sequencer at 5-6 instruments at once in AB3 or AUM without crackling.
So, do you use VirSyn's "ReSlice" and is it anything like Propellerhead's ReCycle: take a wave file and cut it into slices and trigger the slices with MIDI events. And do lot's of manipulations of waves: warp, reverse, etc. Then play back the slices using time-shifting and looping to let you tweak the BPM's and not change the sample's pitch. Does BeatMaker do all that?
Does BeatHawk, Auria Pro or Cubasis have any capability with that "Sampler" use case?
Still, trying to understand what's what. I thick I get stems now after looking into @Lady_App_titude's remix of a Todd Rundgren project where he supplied the "stems". They looked like little audio blobs on sticks... is that why they are called "Stems".
Just curious and looking for expertise to make me less ignorant.
It works great on the iPhone 5S and I think I could create instruments there too. The GUI is layed out well for that little screen. I got my 2 "instruments" downloaded and playable in about 15 seconds each.
I'm sure we can share "instruments" as a group... you would just want to label the size of the download in the name I'd think.
I’m going to have to buy this now. God, I hate spending money....
I'm telling you that sharing Instruments across devices feels like magic somehow...
Also, just tried PC messages and my first experiment confirmed that I can change instruments in AudioLayer using PC changes from a MIDI controller, which is huge for playing live! @VirSyn: do program change messages for instruments work as in your other apps?
I am feeling you, bro!!
So there is Patch Sharing via iCloud implemented? Man I have to get this too...
@VirSyn maybe you will look at hosting patch sharing just like Patterning’s Cloud Kits. Such a cool feature.
Yessir. Anything created on one device appears in the list on the other device. You do have to tap the little download button, but that's easy and fast enough.
Yer just found that out myself works great.
Just to check - can you definitely use samples from your iPad? I think Doug picks up samples from Audioshare in his vid, but I couldn’t see the file source properly as it went blurry at that bit.
My cloud account is full, so I’d want to be able to load/save onto the iPad. Don’t mind using Audioshare if Files isn’t working yet. Not bothered about sharing presets with other devices.
And if so, is there any difference in performance using local files?
Yes, you can import directly from AudioShare.
And the 'Files.app/DocumentPicker' will be fixed in the next update so iCloudDrive doesn't have to be used in order to access files from other FileProviders on the device.
This is super fun with single cycle wave forms (https://www.adventurekid.se/akrt/waveforms/). Its basically like an unlimited oscillator synth.
I got heavily into this with BM3, also in Gadget /Vancouver. But have largely strayed away from those guys in general lately. Having this ability in a portable package is very cool.
@Samu to tune these properly, set the root note to D2? Maybe add some detune? I’m being lazy and hope you can save me having to figure it out.
Wow...what a great app!
I've pulled in files from AudioShare with no issues or performance differences.
Yeah, but I think the pitch detection should nail them?
(Have not tried the AKWF waves with AudioLayer yet).
Yeah, I am pretty shure @thesoundtestroom blurred that on purpose because of his NDA that is so tight - we’ll played me Doug. Well played
Will buy later with your link btw
@VirSyn - small feature request:
When a scale is set on the keyboard, it would be helpful to have the scale root notes a slightly different shade. The tiny note names are almost impossible to read, so this would help a lot.
Nope, the pitch detection is all over the place. Thanks for responding though.
[edit] Humm... working perfectly now? I think I’m losing it today.
Great stuff, thanks for the confirmations guys.
I’ll grab a copy shortly via Doug’s link when the Mrs isn’t looking.
Yeah, if you set the loop to 600 samples it will get the pitch right.
Now it would be nice to 'jump' the loop start in 600 sample steps while keeping the loop length at 600
(and the cross fade should be 0 for authenticity)
How would you compare this with the sampler in BM3? Or the sampler in Cubasis, which never gets talked about for some reason.
Obviously, this is AU. But if you're already working in Cubasis or BM3....
AutoLayer automatically thinks that Samples less than 1000 samples are single cycle waveforms and set the Root key for you to the inverse of the sample length which is exactly the right key. Nothing to do from user side. If you layer them then detuning will be the icing on the cake of course...
The Cubasis sampler is very simple in comparison but it's useable for single-shots, sound effects etc.
BM3 is 'different' and deeper in some areas like parameter modulation, sample-editing, slicing etc.
All have their use cases and I can't 'dictate' what works for each and every one, they are all tools and everyone need to find what fits their flow