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
I would be lying if I said that I wasn't secretly hoping for this haha.
So there's an update in review now, it usually takes Apple a couple of hours to approve.
The AudioShare situation ended up taking hours to solve. I wasn't able to add AudioShare, or anything inside AudioShare as a collection. Nothing was working, even though it looked like it was working from the screenshot I shared on Facebook.
After a good deal of research, I found that AudioShare uses an older model that doesn't allow direct, third-party path creation, which is what Cache needs. A new model came out with iOS 16, but it seems that the AudioShare devs haven't implemented it.
It took some time, but I found a smart workaround. I've now made it so that if you go into AudioShare, then tap and hold on a file or folder that you want Cache to have as a collection, then tap Export/Share, and select Cache from the row of available apps, it will open Cache and save the file or folder as a collection reference, without copying or duplicating the original item. So this workaround allows you to store anything from AudioShare in Cache under your collections, exactly as you'd want it to.
This will also work for any app, cloud storage, local storage or external storage that isn't letting Cache add collections using the standard in-app method.
Here's what's new in the update:
Any suggestions that I've received that aren't listed here, I'm currently still working on.
No harm in asking. Just say: dragand drop is definitely possible on iOS, including with desktop JUCE ports. Loopmix by Audiomodern is just one example. What's the worst they can do? 👀
Great job Lewis, I bought this and Dark Park yesterday to show some support.
A question for you if I may, I’ve been looking for a lightweight file player that could play an hour long wav of brown noise (fades in and out) that would just stop at the end of the file and not drain any battery ie. Once I’m asleep. Have you inadvertently solved for that use case with this app too?
Is there a limit for the length of file being played, will the app keep playing the file once the screen is off/locked and put the other side of the room and, once it gets to the end, will the app just stop and sit in the background (overnight) not draining any battery?🤞
Thanks for creating two beautiful apps.
@lewisleval : a couple of requests for your great plugin:
That’s good to know, got me interested if it’s so easy to drop to flexi
Ha! I’m just thinking about their reputation for getting angry and blaming ignorant users who don’t understand things! That ‘no, there’s nothing we can do about it’ from the manual sounds like they’ve been asked about it many times and dug their heels in on their position - that note about drag and drop for iOS was the last thing to be added to the manual!
@lewisleval : the update is out and awesome. Thank you for letting us browse in bundles and download cloud files.
@lewisleval Currently in standalone, CACHE stops on phone screen off/locked. Could we have an optional setting (for those that would like it) for the app to run in the background in standalone? Could you also confirm if there is a length limit to the file being played and if, once the file stops playing, CACHE just sits in the background not draining battery? Don’t mind what the answers are, just want to understand if it can solve for the user case above or if you might be open to the tweaks necessary. Thank you again.
Right, you don't want to be mentioned in their next AppStore update blurb, fair enenough > @MMXXIV said:
Ah, so it’s not possible to share the whole Audioshare folder with Cache it seems either? Can Cache access folders within folders? The current workaround, even if clever, is not ideal for me. I have so many different folders in Audioshare, and the list keeps growing, including various AUM recordings, which all go into new folders. In a tool like this, I would really not want to have to think in advance about this stuff. The ideal would definitely be easy access on the fly, all within AUM, to anything in AuddioShare. Have you maybe contacted the Audioshare dev to ask him whether he could do something on his end?
As this is currently, if I wanted to use Cache regularly, I would probably try to stop using Audioshare. If I kept using Audiohare, I probably wouldn’t end up using Cache much.
I will contact the AudioShare devs and see what they say. I do agree with you, it would be ideal to just add AudioShare itself as a collection.
There are a couple of options for the time being though. You could create a Cache folder inside AudioShare, and then share that with Cache. It will self-update when you add to it, so all of the things you'd need active access to in AUM could live in there, leaving everything else inside AudioShare that aren't anything you'd need in an AUM session. If you wanted every single thing that's in AudioShare to be available in Cache, it could be nice to move everything in AudioShare into one master folder, which is then shared with Cache. Then when adding more stuff to AudioShare, if it goes in the master file, it will self-update in Cache. Then when you're working exclusively inside AudioShare, everything is only one extra tap away.
You could also "select all" in AudioShare then share with Cache, and that will put your entire AudioShare contents in Cache.
As Cache doesnt actually store any files, keeping AudioShare as their native home would be ideal.
I will contact the devs today and will keep this thread updated with their response
Yep I just tried it, I created a folder in AudioShare called AudioShare, then did select all and move to AudioShare. I then shared this with Cache, and now all of my AudioShare contents is available there. Then I added more stuff to that folder in AudioShare, and it instantly appeared in the Cache collection after a "swipe down to refresh"
Sweet, thank you Lewis, though I guess that would mean any aum sessions etc I had containing files loaded in AUM file player would lose their path?
Do you know why it is that Sample Crate has access to Audioshare? Is it only when trying to get access from an AUv3 that it becomes problematic?
Good call, let me test it on my end and I'll get back to you and let you know regarding moving files that are currently saved in AUM projects.
So Sample Crate accesses AudioShare directly, acting almost exactly like the native Files app. What Cache is doing is creating paths to files and folders. Even when you drag and drop from Cache, you're not dragging the actual file, but a sort of path url, which is then recognised by the receiving app or instrument. The app or instrument then accepts the sample from its original source, with no clue that Cache ever did anything.
This is all probaby the reason why Sample Crate doesn't have an AUv3 extension, and why in-app file browsers don't let you audition sounds before loading them in.
When building Cache, I did hit a couple of walls trying to basically let it be closer to an actual file browser, whilst still being able to do all the things it currently does. I'm happy to continue exploring this now that Cache is out and stable, but the first step will be contacting the AudioShare devs, as one tiny update from them would automatically solve everything haha.
Thnx for the detailed explanation!
Also just pinging AUM dev @j_liljedahl, as he can be hard to reach by email, though I also don't know whether he gets forum notifications
How does this stack up against Media Assistant?
@lewisleval We're on the sidelines cheering you on
I can drag and drop WAV files into GarageBand but can’t do it with midi but I can drop midi in Cubasis. Is it GarageBand or me?
Drag and drop if midi files is working for me from Cache to Loopy Pro clips.
Are you dropping in GB somewhere that GB accepts drag/drop of MIDI?
Here I am dropping a midi file dragged from CACHE.
Has anyone gotten the workaround for Google Drive to work? I’m not getting the iOS share option.
I must be doing something wrong but I’m not able to share/add a folder, just files within a folder.
I’m following the instructions in the app.
I’m using it stand alone for now, just testing.
Edit: I managed to add a whole folder/library from the Audio app Jewelcase but not a folder within the library
Edit 2: if this hasn’t yet been requested, please background audio 🙏😬
@Gavinski just dropped a video
Thanks, yes I’ve tried dragging it to a new track and an existing midi track. I can drag and drop midi in Cubasis. It may be that GB isn’t supported. Funnily enough I can drag and drop audio in GB though!
@lewisleval Thanks for making Cache! 👍
For the AudioShare workaround, im not seeing a “Share” option, only copy - I can only share single audio files & there’s no option to Select All. Hopefully AudioShare’s Kymatica dev can assist with a cohesive solution
You're probably trying to share the Audioshare folder in the Files app. It needs to be shared from the actual Audioshare app. That and a few other useful tips are covered in my video, a few posts up
@lewisleval : I tried to add a folder on my NAS (synology nas connection via smb ) that contains a deeply-nested set of files and folders. It crashed CACHE and the collections I had previously added are no longer listed.
I delete the plugin and added it again and there were no collections. None were shown in standalone.
After a reboot, the local folders were shown in the standalone and the NAS folders in gray. In files app, I made sure the NAS was visible and went back to Cache. I pulled down to refresh and walked away. When I came back, the Collection area was empty again.
I suspect that it was some combination of the number of items or depth of nesting that were the issue as some folders on the NAS were working ok before I added the big collection.
I ran into another issue trying to clean this up.
I rebooted and did not log on to the NAS. Shen I deleted greyed out list items non-greyed out list items got deleted too.
Thanks @Gavinski - my brain completely didn’t register that I had to do it from AudioShare! Thanks again! 👍
No problem, I made exactly the same mistake til I figured it out hehe
I bought it!
Now I want things! 🤪
Favorites
Maybe different color dots to select and It sorts automatically. User gets to name the favorites folder.
Like, a drum sample? Blue
A long ambient sample? Purple
A loop? Orange
And when you search stuff, give the option to make a folder of it.
Snares
Favorited snares sift to top.
Etc.
A 99¢ IAP to make it so? Sure, I'd buy that for a dollar!
There's definitely a lot that could still be added to this. Here are some things I find a bit strange / inconvenient:
When I tap to audition a sample, I have to go right down to the bottom of the screen to pause it, that's kinda crazy to me that that's needed.
Also, when I pause it, there's no rewind button down at the bottom. So if I want to start it from the beginning again, I have to go back up and tap on the sample to audition it again. Clunky and inconvenient, in that regard, tbh.
Would be great to see a waveform view of the sample or a view of the midi. With some samples, there is space at the beginning. When you try to audition them you hear nothing. Having a visual of the waveform is useful in that regard to know whether there’s actually any audio there, and how long you’ll have to wait before you hear it (see AUM File Browser, for example).
I sometimes had playback of midi files sounding very distorted. Someone commented the same on my YouTube vid. Now I'm playing back the same midi file and it's totally fine, so I'm not really sure why there might be inconsistencies in that.
Any reason why it gives us no info about the length of a sample and, if paused, where the playhead currently is?
Overall, useful for sure, but a bit rough around the edges, I feel!