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.
Loopy Pro: FIRST LOOK
This discussion has been closed.
Comments
oops. sorry, I used the wrong term. see the post just above this. Sync works, but through MIDI clock messages, not through MMC. Same result, wrong terminology.
I was thinking more that instead of having a menu dive to find a feature, you would have them on a page in Touch osc. Then perhaps people who are having trouble finding stuff would have it right in front of them?
Personally, I think that having a variety of preset templates to cover basic use cases, accompanied by a well-written manual, is going to be more useful than a single everything-and-the-kitchen-sink template, but then I'm an avowed RTFM guy.
I'm seriously tempted to use Loopy Pro to build additional interface layers for my hardware loopers, actually. A simple touchscreen interface that manages loop volumes and feedback levels in, for example, the LP2, which conceals a lot of its functionality in MIDI beneath a bare-bones on-device control surface, would be pretty awesome.
What I think you may be missing is - you can create pages with nothing but custom controls right in Loopy Pro. Any neat layout you could create in TouchOSC for this purpose you could create in Loopy Pro.
I can't imagine what such a page would look like in either app, but I still can't think of any advantage to doing something like that in TouchOSC rather than directly in Loopy.
Don't let my lack of creativity detract from your ideas though.
I’ve been wondering whether Loopy Pro might provide control UIs for Drambo. Seems like they would make a useful pair.
Heck, you can use Loopy Pro as purely an AUv3 control surface for other apps and forget the looping altogether if you like.
Yeah, I use Loopy Pro sometimes in a MIDI slot as the u.i. for a Mozaic script because Loopy lets me build an interface with exact controls I need.
True enough. Just tried it with a simple oscillator, filter and comb filter in Drambo and then loaded Loopy Pro in to create a 3 slider surface for it. Really simple to get working and works like a dream! So many possibilities will be brought by LP, even, like you say, without the looping.
Will try Loopy hosting Drambo next, to see whether i5 has any advantages that way.
Here’s a proof of concept for using Loopy as a control surface. I’ve been working on this effect in drambo loosely modeled after the Shallow Water pedal, always wishing that drambo had larger knobs to play around. Enter Loopy’s beautiful, wholly customizable interface. Magical.
Loopy is loaded as MIDI Fx but it only sees the AUM destination. Not sure what needs to happen for Loopy to show up as MIDI source, but it’s not a big deal. Will have to check if Loopy will run in my old Mini 2. Hopefully there will be a text widget to label the UI elements.
@dvi: You can already give the UI elements names that show up in the interface. Open the editing window for that element and click on its title at the top.
Oh thanks! I don’t know why I didn’t see that before. @michael is really on the ball with everything isn’t he.
@wim, @espiegel123, @Jocphone, @dvi, @celtic_elk
Thanks for the inspiration about the custom controls! 👍🏼
(Huh. The below was still in the message field as a draft, so maybe I didn't send it. Sending now just in case)
This is indeed on my list - but while we're talking, would you mind sending me a trace recording? I haven't enabled it in Loopy yet, so you'll have to do it with Audiobus: first enable diagnostic mode in the Audiobus section in the system settings app. Then open up Audiobus, make sure the DT is setup as clock source, and just start sending clock. Audiobus will record automatically.
FYI: I'm not reading anything here, too busy; if anyone needs to report issues, use the Slack or email me
Maybe a silly question but, how can I reverse a loop????? Can’t find it!
You can't yet. It's on the development map for post-1.0 release.
Ouch!! That’s one of the most importante features in my workflow back from the DL4 times…. ! Hope @Michael can develope it soon!
The feature set as it currently exists makes it basically impossible to replicate the DL-4 - something I've been actively trying to do - or most of the post-2000 looping devices that grew out of the DL-4's popularity. I have a feeling that the various testing groups have been strongly slanted towards producers, DJs, and beatboxers, and not so much towards instrumentalists, particularly guitarists, who have developed workflows with existing hardware. I'm intrigued by the possibilities of Loopy Pro, but I'm not likely to make much use of it musically until some of the missing features (which I consider basic) are added.
Sent!
TouchOSC has proper Lua scripting now, which Loopy Pro will never have. This makes it very interesting for me to have some kind of remote scripting control implemented. Although I don't know how much status you will be able to get out.
Probably you need to send it with MIDI bindings explicitly.
Could be a future extension, as Michael stated he is not interested in implementing scripting, also he already has powerfull actions and follow-actions, which is much more musician-friendly, of course. But not as general.
I’m not sure if I agree that the slant is toward electronic musicians vs guitarists but I can certainly see how Michael splits his time addressing diverse use cases. It’s quite a balancing act working out deep looping stuff vs DJ/Launchpad type stuff, I’m sure.
Good point about LUA scripting in TouchOSC. Not to mention OSC itself. In that respect TouchOSC could certainly augment Loopy if either of those are needed.
is loopy gonna have MIDI capabilities too?
if not maybe loops could also be "filled" with AUs like Atom
I assume you’re referring to midi looping. Support for midi looping is planned but not for the initial release.
There are other ways that midi is supported already other than looping. For instance controls such as knobs buttons and faders can be set up to send midi messages. Midi can be set to be triggered when events such as a loop starting to play occur, etc. and of course virtually everything can be controlled via midi as well.
It’s not exactly like that, but yes, midi AUs are supported.
yes, I was referring to midi looping.
that's nice to hear, sounds like this is really gonna be an all-in-one solution
Btw. Michael stated yesterday that IAA support is coming. Very welcomed by me, it may even be huge for others.
Use it with AUM side by side..
Also Camelot Pro is on my radar.
Of course using Loopy Pro as an AU is an alternative, but I may for example want it to manage its own AU effects.
I'm happy that it will play along well with other apps in all kinds of scenarios. Just a friendly competition. This helps everyone.
Wow and wow to IAA support and using it’s widgets as a customized Auv3 midi controller.
Will it be able to load it as a host within a host like ApeMatrix opens in Aum or Audiobus?
I think this is what IAA support means. It may look like this or the other way around. Shouldn't matter much in pratical terms.
But don't disturb the developer with this at the moment.
Edit: I tried in Cubasis, and you can't load AUM as an insert effect (as you can do with ApeMatrix), or the other way around. But you can link them side to side (Cubasis only with stereo out into AUM).
I guess that Michael will allow this scenario (first), so you can most importantly use all IAA instruments and effects inside of Loopy, and also you then can link AUM or Cubasis, Auria... to Loopy's multiple inputs (same way as IAA Instruments) or outputs.
For example, multitracked recording of Loopy (as a standalone hosting other AUs or IAAs) into AUM (or Cubasis,..) should well be possible.
Loopy would then appear as an IAA source (with multiple ports available) in AUM (..) and AUM's input ports would appear as multiple audio destinations in Loopy.
I'm ready to ditch my EHX45000 looper to travel with an iPad. Can I have an invite?
I'll help out as well as I can, search the forum before I post etc.
If I can join my mail is [email protected], and
Apple account: [email protected]
@Michael