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.
New Direction ?
I'm not sure it's going to pan out for Audiobus, and by that I mean how it will change when the uptake in AU integration really kicks in.
Yes, in many circumstances you will still need audiobus to do certain types of routing jobs, but for many situations, eg, routing softsynths to apps, it will probably be overtaken by AU integration.
However.
Personally, I love using my iPad for hosting some incredible synths, many not available on the desktop, so I wonder if a new 'mode' could be added to the Audiobus armoury ?
As a flexible AU host ?
I for one would love to be able to host say 3 instances of iSem etc and be able to send midi internally or from an external source.
For example, my Mac running Ableton or whatever DAW, but use my iPad to act as a compact, reliable multitimbral sound source.
One that does not take CPU cycles from the host machine, but I can use to recall multiple 'setups' of synths and effects.
Now, this doesn't mean I have haven't already tried this, but with disappointing results.
After a few synths are loaded, it starts to crackle at even modest latency settings and the recall of presets is less than relaible.
If AU hosting was available, that at least, would most likely go away as an issue, then it would be a case of optimising the app to be able to provide reliable latency and CPU usage.
Opinions ?
Comments
So many dramatic posts these days. I think things will 'pan out' fine and that the same creativity behind the original Audiobus has the same ear to the ground working on wonderful workflow solutions and possibilities for Audiobus 3.
Yeah AB has many a moon left in it just yet and has plenty of scope for future expansion.
Let's not forget that while AB was a shining light throughout the dark years of iOS (
), AU as yet is just a blink of light still firmly in the distance. Yes some great AU hosts and apps will come, but as yet it is nothing when compared to AB compatible apps.
Also the future may well bring with it more surprises. For now, AB is here and usable. AB remote is here and extends the control I have while jamming. AB has embraced Link.
AB also has one hell of a forum that makes my life easier, with all the help people here extend
I personally think it's going to be quite a while before AU gets anywhere near what it is on desktops mostly because of what Sebastian and other devs have said about the memory limits placed on AUs by iOS. Until devices have more RAM I just don't see it taking off. People posting here every day have the expectation that AU is going to be what it is on the desktop but I think once more AUs show up these same people will bitch about how bad performance is.
My two cents.
I think the term "pan out" is very harsh. Audiobus absolutely has "panned out" for years, providing vital capability that Apple did not for a long time.
I also think that any kind of AB integration of AU is probably a ways off, for reasons already mentioned in this thread.
But with that, I love the idea of AB acting as a kind of AU hub for an iDevice, that would be routed to a DAW on a computer. If/when iDevices get such power, that would be an excellent use!
I prefer so much the AB approach rather then the multiple instances of the same plugin. It's more hardware style, it will get you easier to lucky accidents and keep your work AND your workstation AND your workflow tightly organized.
I'm glad to say I like both worlds: AB and AU or Gadgets
DRAMA! MOAR DRAMA!
That is a good point but there are still so many issues apps working not with other apps. Not Audiobus fault but it cut the workflow in pieces. The really annoying pop up is also not my cup of tea. That´s also not Audiobus fault but again.... this breaks the fun too a bit.
I just wish Apple would let a working standard just work for a longer time until they break it!!!
Maybe we all need a good game of Dungeons and Dragons
DRAMA MORTAR DRAMA!
What I love about posts like these is that they're not really about the topic at hand. I mean I could talk for hours about what AU is and what it isn't and why nobody's really got any real incentive to make them yet and why that is. And then what users are expecting and the differences between a live workflow and a mastering/offline kind of workflow and how DAWs work on the desktop and how they're different on an iPad.
But I don't think that's really what this is about. It's just... you know... about opinions and creating some sort of fertile bed for a heated argument.
Actually I do have a question:
So having lots of screen real estate for apps is great, right? And the most innovative apps make sure to use every inch of it in the best possible way. Now why would you throw more half your screen away to 90% of the time display something like a standard keyboard - the arguably worst way of note input on a glass surface?
And what about Split View?
See? That's how you stir the pot.
Also: what makes you think that we're never going to do anything with Audio Unit Extensions?
Hah, I would really like to know that, and would be very interested in your view, which I value highly, as I think that could enlighten me on why the uptake hasn't been bigger/faster.
This is a thought I've had many a time since I a) bought my external midi keyboard and realised half of what was shown on my screen was redundant and could be used better and b) since I am a fan of apps like TC-11 and Samplr. I really think on-screen keyboard should be(come) an optional setting in most apps that have them.
Admittedly I have actually used both the on-screen keyboard (well, holding a note) whilst playing with my midi keyboard at the same time, but that was once, not always.
I'm going to take this as an invitation to brainstorm.
I know you've mentioned here that MIDI is a future implementation of AB. You should contact the devs of AB compatible apps with the suggestion that they ditch on-screen keyboards in the future for the alternative of an AB-centralized keyboard (for those who really want to use an on-screen keyboard, because those folks exist). The AB-keyboard wouldn't be invasive, but could be accessed either via-split screen, the AB screen, or an AB Remote type setup.
Sometimes a built-in virtual keyboard is useful, @Sebastian: you need to get work done and don't have access to a real controller, for an example, and drawing MIDI is not an option given the time it woul take. I recorded the organ solo in the song I posted in the link live, using Auria Pro's Lyra and its virtual keyboard and, boy!, wished it was a little more like the one in SampleTank: https://forum.audiob.us/discussion/comment/198820/#Comment_198820
@Sebastian Are AU's restricted to use a specific portion of the screen ?
I wonder also why it's so hard to have an on/off option for the virtual keyboard (like Sunrizer) and more option to customize them too.
I also wonder why there are no things like drop and drag a LFO or whatever from a list and put that direct to a modulation destination instead of scrolling trough pages etc. (like in Tera). Not sure if iOS allow it...
I love touch screens but sometimes i think it's wasted in many areas where it could be so much more!
Edit: It would be even better if i could have also a full screen as virtual keyboard too as option.
ThumbJam is just genius here!!
I normally always point out that those who attempt to create drama where none exists are bored and aren't satisfied enough with their own music production abilities so have to entertain themselves with manufactured drama derived from their own half-baked armchair pontifications.
But, Sebastian, I warned you a couple months ago that the FUD (Fear.Uncertainty.Doubt) crew from different platform vendors are creeping onto this site.
I'm certain you'll agree eventually.
Who benefit the most financially? There is the direction of IOS music.
As we see, the most beneficial functionality or productivity for the user is NOT the OBJECTIVE used in formulating the function of music making apps and Apple.
Patents, Non-Disclosures, and Non-Competes will soon become more so much MORE important on the business end of music apps. I interact with so many developers who are like "no worries" or "I don't do those" and I just shake my head.
Everything will be just fine. Plenty of money and users out there. Maybe more divided lines of platforms will actually serve to create more ingenuity and competition. These are the things important to me as a user.
Nah, I just think people loooove drama.
And the award goes to.....
Damn you....I hired a tux and still did not win
You don't hire a tux. You wear them. (Sorry, couldn't resist.)
I wondered why people were staring
Actually aftertouch "3D touch" on the new phones is great, I have been waiting years for the flat surface to become more sensitive to touch ...
Split view allows me to do crazy things without to much jumping around...
You need to come up with something more dramatic to get the water cooking
I also like the no NDA atmosphere on iOS
It keeps things going a lot quicker than all the hm, well I can't talk about this at all stuff
Look at the all the hush hush ableton is doing, all the documents are under NDA, that's bad
How are people supposed to know what is going on when they can't read the docu
Don't ask me where I got it from
If everyone treats each other fair there is no need for NDAs
Or do you want to deal with "the suits"?