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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

While we're all cooped up inside, here're some Loopy Pro updates

1222325272846

Comments

  • edited March 2021


  • @Michael said:

    Nice! So this is the result of the code snippet you posted? Send MIDI to target on parameter action? Can that MIDI be Sysex?

  • @SpookyZoo said:
    Nice! So this is the result of the code snippet you posted? Send MIDI to target on parameter action? Can that MIDI be Sysex?

    That’s right. No Sysex just yet; that’s gonna require some annoying UI, so I’ll wait to see if there’s much demand for it

  • @Michael said:

    Damn. That is hot.

    Can a macro/widget control like that also point at an internal-to-Loopy object like a track's volume? Or maybe a group's volume? I think this was discussed earlier in this thread but I can't find it. Sorry!

    The second screenshot's panel label says 'Targets'. Does that mean one can point a single macro control at more than one target? Or perhaps the pluralization is just meant to indicate 'pick on of these targetS'.

    Amen for min and max controls. :heart: Can they be set to min:127 and max:0 so that the control might work "in reverse"?

  • @syrupcore said:
    Damn. That is hot.

    Can a macro/widget control like that also point at an internal-to-Loopy object like a track's volume? Or maybe a group's volume? I think this was discussed earlier in this thread but I can't find it. Sorry!

    Yup, and a bunch more stuff. The widgets use the same set of actions as the midi learn system.

    The second screenshot's panel label says 'Targets'. Does that mean one can point a single macro control at more than one target? Or perhaps the pluralization is just meant to indicate 'pick on of these targetS'.

    The latter, but you can have multiple actions defined per widget/midi trigger/follow action so you can still do that.

    Amen for min and max controls. :heart: Can they be set to min:127 and max:0 so that the control might work "in reverse"?

    Yup

  • @Michael said:

    @syrupcore said:
    Damn. That is hot.

    Can a macro/widget control like that also point at an internal-to-Loopy object like a track's volume? Or maybe a group's volume? I think this was discussed earlier in this thread but I can't find it. Sorry!

    Yup, and a bunch more stuff. The widgets use the same set of actions as the midi learn system.

    The second screenshot's panel label says 'Targets'. Does that mean one can point a single macro control at more than one target? Or perhaps the pluralization is just meant to indicate 'pick on of these targetS'.

    The latter, but you can have multiple actions defined per widget/midi trigger/follow action so you can still do that.

    Amen for min and max controls. :heart: Can they be set to min:127 and max:0 so that the control might work "in reverse"?

    Yup

    Wow. Even hotter. Think that means one can use a single widget to cross-fade between two Loopy tracks/track groups. Which, like, holy yes please.

  • @syrupcore said:

    @Michael said:

    @syrupcore said:
    Damn. That is hot.

    Can a macro/widget control like that also point at an internal-to-Loopy object like a track's volume? Or maybe a group's volume? I think this was discussed earlier in this thread but I can't find it. Sorry!

    Yup, and a bunch more stuff. The widgets use the same set of actions as the midi learn system.

    The second screenshot's panel label says 'Targets'. Does that mean one can point a single macro control at more than one target? Or perhaps the pluralization is just meant to indicate 'pick on of these targetS'.

    The latter, but you can have multiple actions defined per widget/midi trigger/follow action so you can still do that.

    Amen for min and max controls. :heart: Can they be set to min:127 and max:0 so that the control might work "in reverse"?

    Yup

    Wow. Even hotter. Think that means one can use a single widget to cross-fade between two Loopy tracks/track groups. Which, like, holy yes please.

    I love how you people are using Loopy Pro before it comes out!. The level of understanding by just seeing a few screenshots. It’s impressive. Wouldn’t be surprised to see a bug report!.

  • @syrupcore said:
    Wow. Even hotter. Think that means one can use a single widget to cross-fade between two Loopy tracks/track groups. Which, like, holy yes please.

    Yep for sure. I’ll be adding ramps soon too, so you can do it with one button.

  • @tahiche said:
    I love how you people are using Loopy Pro before it comes out!. The level of understanding by just seeing a few screenshots. It’s impressive. Wouldn’t be surprised to see a bug report!.

    It is super spooky! Sometimes I forget @syrupcore and others don’t live in my head.

  • Hope we see users put out tons of videos of how to use this once it comes out looks epic but lots under the hood. I didn’t find bindings in the original Loopy the most easiest thing to understand.

  • @Michael said:

    @tahiche said:
    I love how you people are using Loopy Pro before it comes out!. The level of understanding by just seeing a few screenshots. It’s impressive. Wouldn’t be surprised to see a bug report!.

    It is super spooky! Sometimes I forget @syrupcore and others don’t live in my head.

    😂🤣I feel left out. I’m gonna do this with your screenshots and try to keep up!.

  • Everybody needs a string wall!

  • @Jumpercollins said:
    Hope we see users put out tons of videos of how to use this once it comes out looks epic but lots under the hood. I didn’t find bindings in the original Loopy the most easiest thing to understand.

    Yeah, loopy HD’s binding stuff is a bit half baked. Pro will be much more intuitive.

  • @Michael said:

    @Jumpercollins said:
    Hope we see users put out tons of videos of how to use this once it comes out looks epic but lots under the hood. I didn’t find bindings in the original Loopy the most easiest thing to understand.

    Yeah, loopy HD’s binding stuff is a bit half baked. Pro will be much more intuitive.

    Brilliant thanks @Michael

  • @SimonSomeone said:

    @SealTeamSick said:
    It’s so encouraging that this is built ground up to be a host. For the longest time (and since I supported zenaud.io from the beginning and saw it fail) it just never made sense to me that a live looping workflow would work on that level in iOS because it would require so much to get everything with a host to work together reliably. Genius to have the one guy who can see the hurdles and knows how to make it a robust standalone app that hosts. The hype is palpable!

    I was a Zenaudio ALK user too. It was sad about that thing.

    Me too - they planned to port it over to ios originally. I thought it was a really clever idea.

  • Will Loopy Pro work under Mac M1?

  • edited March 2021

    @mccy said:
    Will Loopy Pro work under Mac M1?

    Should do. At some point after 1.0 is released I’ll also release a Mac native version too

  • @Michael said:

    @mccy said:
    Will Loopy Pro work under Mac M1?

    Should do. At some point after 1.0 is released I’ll also release a Mac native version too

    That's really great news, thanks!

  • @Michael said:

    @mccy said:
    Will Loopy Pro work under Mac M1?

    Should do. At some point after 1.0 is released I’ll also release a Mac native version too

    Would be totally epic if you did this eventually. (especially if it could host other plugins on mac like AU or vst). Im sure it would expand your potential user-base.

  • @sloJordan said:

    @Michael said:

    @mccy said:
    Will Loopy Pro work under Mac M1?

    Should do. At some point after 1.0 is released I’ll also release a Mac native version too

    Would be totally epic if you did this eventually. (especially if it could host other plugins on mac like AU or vst). Im sure it would expand your potential user-base.

    Yeah that’s my plan

  • cool!! Would definitely use both the ipad and mac versions, personally.

  • @Pierre118 said:

    @Michael said:

    @mccy said:
    Will Loopy Pro work under Mac M1?

    Should do. At some point after 1.0 is released I’ll also release a Mac native version too

    That's really great news, thanks!

    yes, how cool is that!!!!!

  • @wawelt said:
    I looked at GTL when I was searching for a good looper and while it does what it says there were some functionalities that I missed. I tried implementing Quantiloop and Enso trying out different setups within AUM. Unfortunately these were not ideal for what I like to do with looping coming from RC505 hardware. Loading too many instances of Enso in AUM would make it crash, then having the controls in each instance made it a hassle to operate. I implemented Mozaic into the game but eventually a simple session with couple tracks felt like an unstable patchwork. Quantiloop is awesome and gives high level of control but 4 tracks is a bit limiting.
    Loopy Pro looks to be the answer as it ticks all the boxes!

    I've built my own group functions using MIDI-Designer [2] - Each channel has it's own mute-command. I press one button in the MIDI-Designer template and it sends all of those messages at once.

  • The user and all related content has been deleted.
  • What will the functionality be like for looping within a loop? Will there be a quantised change?
    I’m not even sure if this is a feature or not - I’m assuming it probably will be - you know like the Sectors in Enso.

    Wouldn’t it be good to see a complete list of the features? I I’m looking forward to reading the AppStore description when it’s ready.

  • Action sequence programming (for on-screen widgets, MIDI triggers, or follow actions):

  • @Michael said:
    Action sequence programming (for on-screen widgets, MIDI triggers, or follow actions):

    Wow!

  • Not only amazing power and flexibility but nifty design.

  • And here's the UI for scheduling actions ("Automatic" will perform the next action immediately after the previous action, like a fade-out, or a count-in, has finished).

  • @Michael you need to ship before the vaccines reach herd immunity... or change this thread's title.

This discussion has been closed.