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 feel lucky" - nah
Lol.
I have no idea how to solve this. I don't think there is a consistent way to do this, that doesn't do other stuff that may or may not be expected.
I guess you spend more time thinking about this than me.
Doesn't work. Meh.
Thanks for trying.
As long as I can save the midi set up and link stuff with the state saving I am in 7th heaven ...
Support for 'legacy' MIDI clock in from external devices would be appreciated for integrating an iOS device as part of a larger studio setup.
I realise this doesn't provide ideal synchronisation for all apps due to the fragmented nature of MIDI support, but would be the most useful for many uses within this sort of setup and is the closest thing to a standard for multiplatform sync/start stop.
We're not disabling MIDI clock support or anything. We just don't have a way to manipulate it in the Audiobus app itself. If you want to do that with third party apps that are part of the Audiobus session you can.
@Sebastian Glad to hear there is a v3 coming with midi .
I hope V3 , if not an earlier update , can also bring multi layer StateSaving :
whilst an SS compliant app X can save its state whilst hosted directly in AB ,
if it is hosted in another app such as Aum , although Aum is SS compliant & hosted in AB , X will not currently save its state within AB preset.
I previously discussed this issue with @j_liljedahl on a Aum thread here , but a couple of @call signs to AB devs were unanswered .Seems apt now to mention again.
With more & more host apps , each with their uses , AB Statesave needs to work through layers of apps to " make everything better(TM)". hopefully this would also encourage lagging devs to finally implement SS , most notably absent being AB's @Michael of LoopyHD sh/f- ame .
I might be alone wishing for this but midi learn capabilities would bring something that would be a game changer imo. To this day, there is no solution to switch to an app at the push of a button and audiobus is the only thing in the ios world that have the door opened to that, the only thing missing is the midi learn function.
Yes, agree. But heck, I'd take midi PC messaging to change presets as a starter. At least with that I'd be able to scroll through presets without having to fiddle with my iPad on stage looking like I'm checking my email.
My biggest issue with everything is timing. I want to be able to start everything (including the record option in the host), and then very quickly be able to be on the instrument screen that I will be playing on. A rewind button isn't important, because I can rewind when I'm setting up, but being able to set record and start from the instrument that I'm playing live on is pretty important. Does that make sense? I would like to be able to do that from the transport on the instrument that I'm about to play/record, to avoid jumping around screens.
Currently, one has to go to the host app, hit record and play, and then very quickly move to the instrument app that is to be played. It makes it really hard to do without setting up a couple of bars of nothing in front of the song. And it makes it almost impossible if one is going to overdub a part....
I hope what I'm saying makes sense..... Do you have any ideas to improve upon this scenario without adding global Link play/record to the Audiobus transport control?
I don't understand
U r in the app u want to play
U hit go in the ab sidebar
Everything with link goes
Press stop and everything stops
This works already
But don't ask me what app sets the tempo? Lol
@Sebastian
If I have 5 Apps with Link ... what Starts First / Sets the Tempo? If I press Play in the sidebar ... The Current App on screen?
Humm ... I don't get it either. Unless the host doesn't support a play button in AudioBus? With most apps you can just go to the app you want to play in, and then press the play button for the host in the AB sidebar, or in some cases the master play button if you want to start more than one app.
Both are on my wish list, for sure.
https://itunes.apple.com/us/app/link-to-midi/id1066216595?mt=8
Hm, Midi...
Flip through ab presets via programm change?
MIDI, YIPPEE!
That's definitely on the list, but probably not for version 3.0. Maybe 3.1 but it really depends. We know it would be great though.
@Audiojunkie: Regarding a global play button: we already have that in the connection panel... What's missing there for your workflow?
cheers, but this one won't take MIDI clock from a DAW as master.
The other one by Coding Cod will, but is still a bit of a hassle and by link's nature won't start synchronously with incoming MIDI either.
YES!
We're most likely not going to do that. Having another layer in between Audiobus and the app that can save state goes against a core design philosophy of Audiobus. It would establish the same dilemma that MIDI configuration in multiple apps currently causes - users would not know at which place they should save and configure things and the whole process of setting up stuff would become prohibitively opaque.
Hihi, yes prohibitively opaque that's midi on iOS now
@Sebastian surely it would solve the problem by saving once & ALL in a Global Audiobus preset with all other host apps loaded in AB along with their hosted synths & fx apps ? . The StateSave dilemma is already established , at least in my (lack of ) workflow , & if you claim to want to solve the midi dilemma & "minimise the setup hassle " surely AB should include this .
I don't know but using 2 hosts like aum and modstep in a 3rd host ( audiobus ) is complete madness meaning no good idea?
That's the most confusing setup I can think off.
AUM is quite powerful while being very complex but that's okay because it caters to users like you who understand (most of) the underlying technologies.
What we're going to do with Audiobus 3 is to make things easier for lots of users (and most likely also for AUM users) but we're not going to focus on a feature that is only relevant to a relatively small number of people (AUM users who also use Audiobus) while also contradicting our core design philosophy which has served us well over half a decade.
having to save & then load each hosted synth & fx app preset individually in Aum &/or ModStep is current madness to me when so many of them are StateSave compatible.
some people are wiring equally mad audio chains between Aum & AB just to use the Statesave of AB with the audio power of Aum .
what is so mad about using the host app you want , then loading that into AB and clicking
" save preset" .StateSave was meant to be a global preset , but it seems new host apps are not to enjoy the benedits of the statesave protocol . I would have thought it would be an added dimension to AB IOS ubiquity that even if other host apps were preferred , their StateSave protocol were still integral to IOS musicmaking .
To confusing for my taste
In what app did I host what app and what happens there?
Maybe that's just me ...
But I would lose overview quicker than I can say elaborate mess ^^
I wasnt just talking about AUM , there are ever more host apps , in which users will want to load hopefully ever more StateSave compatible apps , but wont be able it seems to use the Global nature of StateSave .
I didnt realise the number of users who wanted to save & recall their work easily was " relatively few "
re: AB "core design philosophy " as I've argued with @Sebastian before , focusing on ease for new users ignores the fact they are only new for the first few weeks , & then become lifelong seasoned users wanting to know why the software doesnt do x,y & z .
Maybe I'm seeing a bug (or doing something wrong). Here's what I'm doing...
Trying to record this way, leaves a measure or two of silence at the beginning of a track. Also, the Global start doesn't even get used....
What I would like to do, is set everything up to record, go to the app that I am going to record, and press the global start and then play.
I must be doing something wrong...
Maybe this will help me too: