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
...^ and the SDK for the gagillion other apps that might use it is somehow easier to implement than Audioshare's...
Hehe, that's one of the reasons I've been advocating 'iOS Document Picker' and 'Open In...' for ages.
It's Apples 'standard way' of sharing files between apps.
Now we'll just have to wait for apps to implement drag'n'drop support but that in turn would mean dropping legacy pre iOS11 support and that will cause quite a stir among those who are hostile towards keeping the OS on their devices up-to-date
The entire “this thing makes that thing redundant” mentality is a consumerist fallacy.
Why even bother with the 'AudioShare SDK' if the functionality is supplied by iOS?
AudioShare already provides it's 'files' via a FileProvider extension and this could be streamlined even more by adding direct integration thus making the content accessible to all apps that support standard iOS way of interfacing with files.
Time will tell where this all goes...
But when it's "a solid solution built into the OS" making "a proprietary workaround" obsolete there tends to be some truth in it
Note: I don't count IAA as a "solid solution" when compared to Audiobus. There's nothing particularly solid about an app-zombifying half-finished protocol without state-saving
True that, same goes with the 'half-baked' AUv3 preset handling in iOS
It should technically be possible to allow all AUv3's r&w access to the 'preset folder'.
(Which is most likely in the same location on iOS as it is on macOS ie. /Library/Audio/Presets/ and each app has it's own folder there).
Anyways, ACP4 has already caused a bit of discussion and I will be installing it when it's released
AU is amazing and clearly a big part of the future, but AAB/IAA(AUM) is still (for me) a vastly more stable and practical system in performance. AU fits inside it wonderfully and creates new possibilities, but doesn’t replace anything that already existed.
For pure production, I can see AU having a much bigger role. Audiobus Remote and a couple of controllers touching various parts of the system is wonderfully immediate fully featured and fantastically creative for performance though. I’ve had a lot more technical problems working with AU than working in this way.
Simply a case of thorough standard practice. You’ve got to tune your instrument before you play.
Yes. It's a dog of a standard. I wish people would would just move on. I pride myself in fully supporting AU, yet 90% of my development time is wasted on supporting a half a dozen ancient standards, eating up time I could be investing in moving things forward instead of backwards.
I can see and completely understand it from your perspective, but from my perspective my primary (and only) consideration is for total amount of possibility. Everything is fair game and just gives me more opportunity for creativity! I still find that AB/AUM(hosting a mix of IAA an AU) is the best platform for performance.
One of my live devices has already been transitioned to run BM3. I do run a few AU in there but primarily (preferabably) run sampler instruments for stability and processor efficiency.
Interested to understand the big picture here. What features/apps/connectivity/filemanagement things are holding you back from moving to an integrated all-AU setup for your use cases?
With AB/IAA, I can summon any app which I need on screen access to with a single click on a secondary screen. With AU I’ve got to go clicking through menus or scrolling around in the middle of a performance. AU is great for working with controllers though.
Full screen apps are generally BY FAR better for performance usability (roll on full screen AU).
I’ve also found AB state saving to be much more reliable than AU state saving (AU’s sometimes randomly won’t load on AUM patch initialisation and then when reloaded, can recall an init patch. Also had patches recall incorrectly in BM3).
I’m sure there’s more but that’s just off the top of my head and I’m not around my equipment at the minute in order to boot up and psychoanalyse myself! It’s mostly related to the brilliance of what AB brings to the table!
most useless audio app ever created.. basically it's just tool for Retronyms to sell their shitty sample packs .. not usable as sample librarian, for this Audioshare rules the world ..
I didn't get my point across because I'm all for FileProvider. It's more, as a developer, why would I want to integrate another copy/paste SDK when there's already a native one and a dirt simple, very popular third party one (audioshare's)?
The Retronyms ACP (as the successor to the Sonoma ACP) was there as a Free alternative to Apples audio paste before AudioShare started being sold (the advantage being you could paste several samples at a time) so having already incorporated it as a developer you might want to continue supporting it.
Further, as a developer retronyms will pay you a small % of any sound packs purchased via the retronyms store link in your apps ACP....
http://retronyms.com/audiocopy/dev/
One of the few reasons a developer might be tempted to include the AudioCopy SDK would be to get a small share of the revenue if the customer buys any sound packs from within their app.
http://retronyms.com/audiocopy/dev/
What I would love to see is a 'unholy merger' between AudioCopy and AudioShare regarding some of the features.
(AudioShares sample editor is lacking compared to AudioCopy while AudioCopy's file management and format support is lacking compared to AudioShare).
They must have many fans as their apps sell loads
Loopmasters are the worlds leaders in sample packs, I wonder why they are keeping the acp app loaded with more and more packs?
Perhaps they are selling tons of them lol
Probably so, I’m just not one of them
Hmm how cares, it's from retronyms, and can't be good.
That's not really true. AudioShare was available 2 years before Retronyms made their ACP!
Sonoma ACP was a protocol that used a "private" pasteboard to share audio data between apps. AudioShare, released 5 years ago, had support for Sonoma ACP from the start. Then in some iOS version, Apple broke this protocol by disabling all uses of private pasteboards. As a response, Retronyms made their own protocol + SDK for ACP, which depended on their new AudioCopy app, released 3 years ago.