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
Audiobus SDK already sends a "signal" when the app is ejected, and it's up to each app to react on this and do what they like. Personally I prefer to have my apps suspend when ejected, to not eat up resources. I think this is more important than avoiding the extra delay that happens if the users chooses to add the same app back again. (So I don't agree with Sebastian here). But the problem is that this isn't enforced, so users never know which apps will need manual termination or not.
And, IMHO the most annoying thing with launching new apps in audiobus, and the biggest cause of this delay mentioned above, is the automatic "switch back". I would love to see this gone, and instead stay in the app that I just started. When I start an app, I want to keep it open until I explicitly switch back to audiobus or any other app. Maybe I'm the only one, but if not I hope Sebastian and Michael will consider removing this feature. And I don't think I'm the only one with this opinion, I have often seen in demo videos how people launch an app, waits for the switch back, only to then again switch to the app they just launched. Sometimes they forget to wait for the switch back, and starts interacting with the app only to have it pulled away "under their feet" and then having to switch to it again.
I agree, the switchback is usually only helpful once or at most, twice, right at the start of the session, thereafter, it tends to leave you where you don't want to be. What if we had a one finger wakeup which does the switchback and a two finger wakeup which doesn't? Then we could choose depending on what we intend to do next.
Strange, my last post didn't bump this topic up the list.
This thread is getting real hard to follow. The 'press eject long to shut dow an app after disconnecting' is a pretty good idea though. Might take some time to have every app support it though because it might require an update of the SDK in client apps, which makes it hard to advertise it as something that works across 100% of all apps.
Ready for the switch back to leave the building. Audiobus icon in the panel of the open app could indicate if there is an active AB connection happening.
Why not simply keep the existing "Eject" button exactly as it is now, and add a 2nd dedicated "Close" button? Perhaps just make it an "X" in a red circle in the corner of the app (ie, exactly like the "close app" icon from the taskbar).
IMHO this would be more intuitive than "hold Eject long enough to close", and also would be faster to execute (better for workflow efficiency & live performance).
"just add another button" isn't a great to solution, especially since adding this functionality would require every app in question to update its Audiobus SDK, which means every app would have to be updated. Providing a button that is either only shown for some apps or wouldn't do anything for many apps until all apps have been updated (which can take months) is not the solution I have in mind.
It was purely a User Interface suggestion, an alternative to the "press and hold eject" idea you seemed to be entertaining in your previous post.
Either way, you will still have the same problem of actually getting apps to close somehow (likely requiring a SDK change as you say), but this is a separate issue from how this option is presented to the user. I certainly understand that merely adding a button won't make apps magically support a "request close" signal from AB.
I'm glad this topic generated so many responses and feedback. It seems as if it one of those Apple quarks and even more so, a problem with the iOS platform in general. @Dubhausdisco - I totally agree with you; I have to pinch myself every time I download a new synthesizer for $10 that would have cost me a few grand just a few years ago. I was just having this conversation and mentioned that I feel sorry for younger kids who don't understand how awesome this really is! That being said, I'm not really complaining about the platform or anything else. I'm simply wondering if there is a more logical workflow for this particular issue. @Sebastian thanks for all the replies. I have a better sense of the issues you have to work with that its a wonder any of this works as well as it does.
I agree the post app launch into Audiobus switchback is unnecessary most of the time and if presets were implemented then it would probably become redundant for the most part.
I don't understand how is the switchback is unnecessary. If there was no switchback you'd have to manually switch back after every app that you connect. Can someone elaborate?
@Sebastian for me i pretty much always switch right back to the app to set it up. If you load bm2 for example. It pops up the chose project dialogue and then right back to AB. Obviously then you have to go right back in to chose your project.
When I launch a new app in Audiobus to utilise in my currently loaded project that i am working on it switches me back to Audiobus.
This switching back to Audiobus for me at least is unnecessary because I want to utilise the chosen app not Audiobus.
When I first load up a project I have previously been working on the switch back is handy because I need to open several apps initially, say Cubasis, Animoog, Remaster & iMini into Audiobus, but as Ryan says there are certain features to set up in each chosen app.
This process would be made slicker by having presets, because in theory all the apps should load up when I choose the above setup in a preset for example.
Therefore if we had presets the only reason I would need to have an app i just opened in Audiobus switchback to Audiobus is if I asked it too.
I hope this makes sense.....and again this is my personal preference.
I agree, Ryan. Another example in favor of no switchback to A-bus:
I have a synth input and Loopy HD output rolling with several loops. The synth is playing a nice groove from Little MIDI Machine. Before I record the synth, I want to see if Magellan's compression and EQ would help a bit.
So, back to Audiobus, tap effects+ , choose Magellan, tap zzz's to launch it. Everything is flawless so far. I love Audiobus
Then, Magellan pops up, I start to switch to Magellan's effects page to check where I last left all the levels. I see the compressor is jacked way up, start to adjust it... And Audiobus engine kicks in, putting Magellan in the sound path, while simultaneously switching back to the Audiobus page. What follows includes ripping off my headphones, frantic mashing of the iPad volume button, and other techniques (effective or not) to get the sound under control. And no, ...cursing/ screaming is not one of the more effective steps in the process.
So, I have learned my lesson and will remember the workaround to make sure that does not occur. Ever again. XD
Still, the experience would be easier, smoother, and save a bit of time, without the switchback feature.
And I still love Audiobus. This is not at all a complaint, just elaborating on a worst case scenario. Hopefully it helps.
I think you'll find that most users do not want the switchback most of the time. I'll repost my suggestion from above in case it was lost in the noise:
It would be cool if the AB controller would give the user a few seconds of extra time before the switchback, during which it attempts to detect touch events, and if seeing any cancels the switchback.
I think it is a good compromise that prevents you from having to introduce more buttons or options in the AB UI.
Or go wild and allow slot loading from within the AB panel.
Allow me to be absurd (again) for a moment:
My second spitballing suggestion this week to get rid of the app from my workflow. Not rid of the app but I just don't need to see it so much once I start making music. Not for lack of wild eyed unhinged teenage love for AB!
I'm thinking of it like my hardware patchbay next to my mixer. Yes, I want it and couldn't live without it but when I'm mixing a song the last thing I want to do is look at my patch bay! I want to push a button on my mixer that reroutes stuff for me without having to lose track of what I was doing - making music.
So yes, absurd suggestion that doesn't take into account whatever you mad scientists have on the burners right now. But I'd love for things to generally move toward 'less Audiobus, more magic'.
First of all: Thanks a lot for your input everybody. Very appreciated!
Ok here's the problem: We HAVE to switch back if the connection graph isn't fully set up yet. We don't know if the connection graph is fully set up yet because the user (you) might still need to add another app. So we always switch back.
For new users not switching back is especially confusing because they might not yet know how to switch back manually (either via the connection panel or the multi-tasking menu of iOS).
So if we disable switching back, we'd break Audiobus for quite a few new users. Note that my definition of 'broken' is 'everything that users cannot use without previous knowledge'.
Fair enough. I dislike settings as much as the next settings-disliking guy but the amount of "no switch back" feedback in this thread combined with your thoughtful concern for new users sounds like a prime candidate for a setting that defaults to the current behavior.
Maybe a Switch back switch
@Sebastian That makes sense. Perhaps like Dave said, it could be a switch or button up in the area with the buffer settings, by default it's on but if you don't want the switch back you could tap, tap, tap it off. lol :-) . I don't have a problem with the switch back so it's no tan off my hide. It's merely a very minor inconvenience at best. But if i could have the option, I'm positive I'd use it.
Agreed that switch back is absolutely critical for new users, until they figure out how to work the connection panel. Unfortunately for us
When setting up a new session of n apps, the typical workflow (I think) is launch app 1, configure app 1, go back to AB, launch app 2, configure app 2, go back to AB, etc. The auto switch-back after launching each app adds an extra step that's unnecessary since the user really wants to switch back to AB after configuring the app, not before. Plus, after configuring the "last" app the user doesn't want to switch back to AB at all, may stay in the last app or go back to the other ones. So it'd definitely be "really nice" to have the option to get rid of this switch-back somehow.
Note that when AB adds the presets feature, opening a preset will require switching to each app to open it up. Ideally this goes app1, app2, app3 etc, rather than app1, AB, app2, AB etc. This will hopefully also configure all the apps (to the right patch, preset, settings etc), rather than just launching them. The preset will ideally also know which is the final app the user wants to be in at the end of the launch sequence, which I suspect will typically be one of the Input apps (or an effect app if the input is microphone).
@Rhism your last paragraph sounds like a dream come true !
Thanks for the brilliant feedback guys! We're having a talk about this @ AB HQ
Since this has kind of become the 'what's up with the switchback' thread as well, may I add:
I use Beatmaker 2 in the output slot primarily. It's pretty much necessary to stay in BM2 to create a project, so I think the "switchback" there is a little unnecessary.
Just a shot in the dark, but is it possible to have the switchback disabled on the output?
Maybe I don't use enough apps in output to know if this makes sense at all....
I vote touch for switchback and either long press or two finger touch for no switchback, regardless of which slot.
I like the idea of presets, would be great if they could be called by midi, so from a single ipad I could automatically send some patch change to all audiobus instances, would be a real time saver.
How about when you first select the chosen app for use in Audiobus it opens but you don't switch to it and back Audiobus you just stay in Audiobus and see the timer to show its loading ?
Then if you want to open the app you can select it once it has loaded in the back ground.
Just a thought.
I believe loading apps in the background is not actually possible on iOS. You actually need to switch to it to load it. If the app were already running though, this should be possible.
agree with Ryan. just have a button on the AB page--- give us a few options. have it set as it is now for new people as default. but allow a few options in a menu for the people that are comfy with AB. like the buffer size ---- it looks good but could of been completed alot less graphic intense wise with just a simple menu that could also incorporate a few other options ------like kill app when removed from the bus------ would be great to have a few options------- I am so happy AB as happened, but i feel like now, after 6 months a little update could take place.
AB screen is rather empty and there is room for a menu button
could have cpu meter etc etc
please please lets keep this app a must have that keeps growing
PaulB: "I vote touch for switchback and either long press or two finger touch for no switchback, regardless of which slot."
Love this idea... very intuitive. Press & hold = "I want to stay on this app, not quickly come back".