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
Wow! 1GB per instrument is not too bad! How many instruments do you think a modern device would be able to handle? There is freeze functionality as well, isn't there! Nice!
2? :)
Really, these devices do not have a lot of memory. The iPad PRO has 2 or 4 GB memory if I'm not mistaken. Older iPads/iPhones have 512MB. You can have a look here:
Please look at Memory, not Storage.
If exceeded, does the app just crash without warning? What will happen? It sounds like I have to do some advanced planning if I'm using large files. :-)
To be honest, I haven't tried. It also depends on how the BASS library deals with that. It looks like I can determine the amount of free memory on iOS, so I might be able to prevent a crash, but I'm not sure: you could for example have 512MB free in chunks of 64MB, spread out over the address space. If BASS loads a 256MB preset and requires a contiguous memory block for that, it will still fail.
One idea that I've actually seen used (BeatMaker 2) is to have a configurable setting for the amount of RAM that can be allocated for just for sampled instruments. Configurations could be something like 128MB, 256MB, 512MB, 1024MB, and 2056MB. If the amount of RAM being loaded will exceed the amount in the configuration, the system will stop you and keep you from loading beyond that amount. This way, you can configure a safe amount and have a way to keep the system stable. :-)
By the way, is it possible to have sub folders for samples? I have several sampled instruments that need to be in sub folders to keep them from getting confused with other samples in my setup. For example, guitars: Acoustic, 12-string, electric, bass. And within each instrument are articulations for that particular instrument: power chords, single notes, slides, mutes, legato, staccato, fret noise, etc. With multiple guitar instruments, it can get really, really confusing. Thanks again!!
I'm afraid it does not handle that correctly.
As far as I remember, there's still no reliable way for an iOS developer to determine the amount of free available memory and pre-setting the memory limit seems to be one of the few ways to go ... although I wouldn't limit the values to such coarse steps.
Cool news!! I found that if I create and name the folder and put the sound fonts into it ‘before’ copying it into AEM, then it shows up and works fine! I can go into my sub folder of Shreddage guitar articulations and use them fine. They are all grouped together like I want them to be. So, even though AEM has little file management of its own, it can accept folders of samples, which works just as well!
Cool find! Thanks!
I wish there were more apps that surprise us with hidden features!
The value’s coarse steps were just examples on my part.
But as far as pre-setting a sample RAM usage limit, that would be fine for me. I just don’t want to use too much RAM and crash. 
I’m starting to use desktop sample sets on my iOS device now (like Impact Soundworks’ Shreddage Guitar 1.5GB from 22 articulation sample sets), and I don’t want to lose my work 
I’ve got several more that I’m going to convert with ChickenSys’ Translator Pro 6, and I’ll be a happy user. 
I hope more developers will create disk-streaming samplers like AudioLayer.
Given how sophisticated the BASS library is otherwise, I wonder why they can't stream samples from disk.
@dwrae
Is there a way for developers to determine how much memory loading a certain SF2 preset would consume, before actually loading it?
Imagine a list of presets inside a sound font with the size of each preset written next to its name, plus a display of how much memory the currently loaded presets already consume in total 😀
Well, I’ve successfully added several giant sampled instruments, with multiple articulations as individual instruments, plus my immense GrooveMonkee library!! I am a happy boy!!
I estimate that I’ve got close to 5GB in samples for about 6 sampled instruments. Desktop quality Drums, Bass, and Guitar!!
Oh, since you mentioned samples, I thought you were referring to importing/using audio files with the 'File browser'. For soundfonts, you can indeed create subfolders. I have added this feature very recently.
Further interesting news! I have now created an entire hierarchy of all of my sample imports under the name, ‘SFZs and Soundfonts’ and within that folder I have sub-folders like bass, guitar, drums, etc. And under each instrument folder I’ve been putting all of my instruments. The only instrument I’ve left out of the folder is the general midi Soundfont, because at least one Soundfont is required to remain in the folder. It REALLY cleans up my instrument list!
Here’s the key: Do all file management through iFiles!
I can see that I’m REALLY going to ramp up my SFZ and Soundfont usage!! Please Davy, could we get some kind of RAM usage crash management in AUM? I am so afraid I’m going to have unexpected crashes with all of the samples I’m going to be using.
I can certainly try.
Well, I love and appreciate this feature!! Thank you very much!!
Wonderful!! Thank you!!!
In my case, I have an iPhone 7 Plus. Which gives me more than I expected:
7 Plus: 3 GB LPDDR4 RAM
😎👍🏼
I'm afraid the BASS MIDI library does not give information on the memory usage of individual presets.
Is there a way to report "TOTAL" app RAM usage for AEM (including any samplesets loaded)? With that, we can make an estimate of how much RAM is left based on our model type. As long as we aren't running any other programs at the same time, that should give us useful information that we can use to manage things ourselves.
Only global, but I did some tests and the functions I found were just not reliable enough.
Audio Evolution Mobile Studio 2.1.2/2.1.3 for iOS released:
Please note that version 2.1.3 fixes a problem where these type of effects were not loaded from a project. And thanks to the FabFilter guys helping me out getting this to work!
OK, thank you for trying.
Interesting! Aside from the FabFilter effects, what effects might this include? What makes the AVAudioUnitTypeMusicEffect different from other AU effects?
If only Apple had documentation, lol! But I guess it's the type of audio effect that can also accept MIDI. Not that AEM does anything with it, but oh well. The Spacecraft effect is also of this type, which actually only generates audio without doing anything with the audio input.
OK, that makes sense. Might Enso be of this sort? (ie. Using midi commands to start and stop and control the looping transport)
Not sure. If it didn't show up pre-2.1.2 and now it does, then yes.
Fair enough!