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
Amen, brother.
You can still have beer when fasting right?
Yeah, of course you can, but only when you need to alleviate the pain when you hear people whining about app prices on IOS.
I know we all have different life circumstances but surely $10 ain't gonna break anybody's bank. My 6 year old could afford it if she wasn't splashing out all the coins she finds under the sofa on stuffed toys.
I'm intending to buy AB 3 on release. Not just to support an excellent game changing developer, but because I believe it will be a very useful tool. But there are features I hope will be included from day one, such as AU support.
@Sebastian
Would it be possible for you to keep on developers' backs about adding State Saving into their apps? Propellerheads for their Thor synth is one. Roland for their Sound Canvas is another. IK Multimedia for their Sampletank is a third. Also, could you get on Roland and IK Multimedia to give their aforementioned apps multi-timbral outputs please?
In my opinion, State Saving really shouldn't be an optional thing for app developers anymore mate but rather mandatory within the AB3 APK. It's too much of a pain half the time to open apps and constantly recall patches rather than just opening up one huge saved state within AB3. Cheers.
>
Agree with this. State Saving is my favourite AB feature, and when I find an app that is otherwise great, but whose developer can't or won't implement it, it's always frustrating.
Agreed. This should really be enforced as it's hurting the Audiobus brand.
With the best will in the world I think it's a symbiotic relationship between the AB team and other developers.
Having AB can help devs sell their apps sure, but conversely without other apps including the AB sdk the Audiobus team have no product.
I cant see how trying to enforce support for state saving and or AB remote would really help either side.
>
Fair enough. Then offer increased, preferential promo for developers who do include it. Apps listed as being _fully _AB compatible.
FWIW, there are potentially great apps such as Remix Live, which I've ended up deleting, because they won't add Sate Saving. It was simply too much of a pain to follow a screen grab or written notes to recreates what I was doing exactly. Especially when I can do just that using Launchpad!
I no longer use Audiobus because I got sick of apps not implementing state saving...
When expected behaviour is not there it feels broken. This is clearly the fault of the individual apps, but AB has been banished from my workflow because of it which is a shame.
@BiancaNeve
"I cant see how trying to enforce support for state saving and or AB remote would really help either side."
From the "average producer's" side of things mate...not having State Saving is a major pain. Thor, Sampletank, and Sound Canvas are the only non-AU, non-Gadget-based apps without state saving I bother to keep on the iPad given each of these can do unique things most other apps can't do (Sampletank=high quality orchestral sounds, Sound Canvas=fun and cheesy 90s tat, and Thor=that cool bread-and-butter synth from Reason). If a non-state-saving app out there has a comparable alternative which has state saving, the former gets chucked off my iPad and I'm relegated to spending a little more money.
@nrgb
"I no longer use Audiobus because I got sick of apps not implementing state saving..."
This wouldn't really be Sebastian's fault. This is the fault of the developers who could care less to update their apps to 2016 standards and implement State Saving. With AB3, Sebastian can make State Saving a mandatory feature. I know what you'd say, "Well, IAA exists as the alternative." One trick I've learned is apps that have AB State Saving also have IAA State Saving. Those who don't have AB State Saving will NOT recall their settings via IAA. So, 99% of non-state-saving-apps that don't load into Gadget nor have an AU capability are basically good for shite. Just my two cents anyway.
There are times when I don't want audiobus to save apps state, especially if a particular app crashes or gives errors.
If you want developers to implement latest state saving your best bet is to write to them yourself. If several of us write it's bound to be more effective than audiobus team, I'm pretty sure audiobus folk already shoot them with latest sdk news anyway.
@supadom
Sounds like a plan mate. I already wrote Propellerheads, IK Multimedia, and Roland, and only heard back from the first two, lol. FRIENDLY, wonderful staff.
You should write them yourself to "put on the pressure" if you so chose.
The one established company you'll get nowhere with is Cakewalk, so don't even bother. Wrote them three times since 2015, was replied to once, and still they don't care to bother updating z3ta+ with state saving let alone with essential bug fixes. Cheers.
Without reading through all 14 pages of this thread, can anyone point me to an overview of AB3's planned feature list (if available)? Just wondering if it'll have say, MIDI sequencing features as per Modstep, for example.
Afaik no sequencer. AB 3.0 will be more a competitor of AUM, with some extra features AUM does not have, but the 3.0 will not support AU. Saying that AB 3.0 is now set to be launched Spring 2017, so maybe AU will be implemented.
Ah ok, cheers.
hmmmm.... Spring 2017...
I apologize if I overlooked the below earlier in the thread. Is Apple not going to freak out with, and prohibit, the internal API/libraries that AB3 is publishing? Has Apple given some sort of tacit approval? I know this is AB3 stuff, not hidden iOS APIs but given Apple's authoritarian streak it would not surprise me if they said sorry, you can't do that.
All holderness apps got updated with AB3 support today.
Surely AB3 must be coming soon...
...ish
I hope it comes with AU support out of the gate, if not look forward to seeing it's new lick of paint anyway...
that is quite a maddening video. I can ALMOST see what's going... and the dialogue is a bit...unhelpful.
MAN 1: Um, if the developer's high tops might combine us already...
MAN 2: O.K.
MAN 1: Cool beer.
[CLOSE UP ON SOMETHING THAT SAYS "RUNNING METHOD" WHICH YOU WOULD THINK WOULD HELP BUT DOESN'T.]
MAN 2: It stood proud rock.
[LAUGHS ALL AROUND]
It had some text which didn't appeared just "sharing" it...
MAN 2: It stood proud rock.
[LAUGHS ALL AROUND]
It's still prog rock?
haha.
One hopes not.
But yes.
Instant prog Rock, must be a new AB setting
Oh I hope that doesn't happen again - otherwise we'd be in another potential iOS 7->8 situation. OTOH, I hadn't heard or read of anything like that happening with AB3...