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.

BeatMaker 3 July 15th.

1666769717277

Comments

  • These should be fairly simple but how do you change the key of your song ? And is it not possible to change the starting position of a midi pattern ?

  • After a few days use I think I can say i love it and will be using it a lot. I'm using it more as a daw.

    Here's a workflow I'm using. Load a drum kit on bank a. Program some beats. Load up some loops in bank b. I've got lots of projects recorded into AUM - unfinished bits and pieces recorded from various apps. Sequence a few of those samples. Then I load either IAA or AU instrument into bank c. Find a sound in a synth - record a pattern. Tweak midi. Record automation. (Or record it live ). Add a new audio track and set input to bank c. Record that midi into audio. Remove the pattern from timeline. Go back to the IAA or AU synth and find a new sound I like. Record new midi pattern - then add another track and record audio of that midi. Mute one or both of those audio tracks and maybe unload the synth and load a new one and record some loops of that like above. Keep adding audio tracks and then it's easy to arrange those clips on timeline.

    I've had little issues - a few stuck midi notes, and Blocs lost sync via Link tonight and even restarting blocs didn't help. I'm sure after a restart of iPad it'll work again. Barely tapped into the fx yet - and no macros used yet. This feels like the holy grail of recording apps for me so far. It'll get even better with updates and a new iPad for me (iPad 4 currently - surprised how well BM3 runs on it!)

  • Love it too! Great explanation thanks!

    @Halftone said:
    After a few days use I think I can say i love it and will be using it a lot. I'm using it more as a daw.

    Here's a workflow I'm using. Load a drum kit on bank a. Program some beats. Load up some loops in bank b. I've got lots of projects recorded into AUM - unfinished bits and pieces recorded from various apps. Sequence a few of those samples. Then I load either IAA or AU instrument into bank c. Find a sound in a synth - record a pattern. Tweak midi. Record automation. (Or record it live ). Add a new audio track and set input to bank c. Record that midi into audio. Remove the pattern from timeline. Go back to the IAA or AU synth and find a new sound I like. Record new midi pattern - then add another track and record audio of that midi. Mute one or both of those audio tracks and maybe unload the synth and load a new one and record some loops of that like above. Keep adding audio tracks and then it's easy to arrange those clips on timeline.

    I've had little issues - a few stuck midi notes, and Blocs lost sync via Link tonight and even restarting blocs didn't help. I'm sure after a restart of iPad it'll work again. Barely tapped into the fx yet - and no macros used yet. This feels like the holy grail of recording apps for me so far. It'll get even better with updates and a new iPad for me (iPad 4 currently - surprised how well BM3 runs on it!)

    @Halftone said:
    After a few days use I think I can say i love it and will be using it a lot. I'm using it more as a daw.

    Here's a workflow I'm using. Load a drum kit on bank a. Program some beats. Load up some loops in bank b. I've got lots of projects recorded into AUM - unfinished bits and pieces recorded from various apps. Sequence a few of those samples. Then I load either IAA or AU instrument into bank c. Find a sound in a synth - record a pattern. Tweak midi. Record automation. (Or record it live ). Add a new audio track and set input to bank c. Record that midi into audio. Remove the pattern from timeline. Go back to the IAA or AU synth and find a new sound I like. Record new midi pattern - then add another track and record audio of that midi. Mute one or both of those audio tracks and maybe unload the synth and load a new one and record some loops of that like above. Keep adding audio tracks and then it's easy to arrange those clips on timeline.

    I've had little issues - a few stuck midi notes, and Blocs lost sync via Link tonight and even restarting blocs didn't help. I'm sure after a restart of iPad it'll work again. Barely tapped into the fx yet - and no macros used yet. This feels like the holy grail of recording apps for me so far. It'll get even better with updates and a new iPad for me (iPad 4 currently - surprised how well BM3 runs on it!)

  • Had my first few crashes today. I think I'm noticing it crash more when there are IAA and AU plugins saved along with the session. My pure bm3 sessions never crashed, but the more complex ones seem a bit unstable. I'm sure they'll iron out what they can.

  • wimwim
    edited July 2017

    @boone51 said:
    Had my first few crashes today. I think I'm noticing it crash more when there are IAA and AU plugins saved along with the session. My pure bm3 sessions never crashed, but the more complex ones seem a bit unstable. I'm sure they'll iron out what they can.

    Sounds like the bad old days with ModStep all over again.

    [edit] not meant as a slam to Modstep, just a commentary on how hard this app hosting business must be. I blame Apple.

  • edited July 2017

    @wim said:

    @boone51 said:
    Had my first few crashes today. I think I'm noticing it crash more when there are IAA and AU plugins saved along with the session. My pure bm3 sessions never crashed, but the more complex ones seem a bit unstable. I'm sure they'll iron out what they can.

    Sounds like the bad old days with ModStep all over again.

    Made me think of Cubasis. I've lost some work. You learn to save a lot in these early days. Cubasis was so bad and made me lose so much work that I shelfed it and didn't come back for over a year. When I did, everything else had caught up and it wasn't all shiny and new anymore, and so it hit the bin again. Shame to toss away fifty bones like that. Wish I could sell it.

  • @boone51 said:

    @wim said:

    @boone51 said:
    Had my first few crashes today. I think I'm noticing it crash more when there are IAA and AU plugins saved along with the session. My pure bm3 sessions never crashed, but the more complex ones seem a bit unstable. I'm sure they'll iron out what they can.

    Sounds like the bad old days with ModStep all over again.

    Made me think of Cubasis. I've lost some work. You learn to save a lot in these early days. Cubasis was so bad and made me lose so much work that I shelfed it and didn't come back for over a year. When I did, everything else had caught up and it wasn't all shiny and new anymore, and so it hit the bin again. Shame to toss away fifty bones like that. Wish I could sell it.

    I love Cubasis (and Auria Pro, Modstep and now BM3). I don't consider any of them a loss by any stretch.

  • @wim said:
    I love Cubasis (and Auria Pro, Modstep and now BM3). I don't consider any of them a loss by any stretch.

    That's the right attitude to have, and I was there for a long time. Once Auria pro landed, though, my ability to tell myself that Cubasis still had a purpose on my iPad ran out of steam. Not bashing the app at all. It's an amazing little app, and I know there are tons of people out there who absolutely love it. Just for me, I don't have any reason to keep it around. We're all different though. Mercifully.

  • Yes, if space got to be a problem then I'd need to get more comparative than I've been. But until then I'm just as happy as can be. B)

  • edited July 2017

    @Halftone said:
    After a few days use I think I can say i love it and will be using it a lot. I'm using it more as a daw.

    Here's a workflow I'm using. Load a drum kit on bank a. Program some beats. Load up some loops in bank b. I've got lots of projects recorded into AUM - unfinished bits and pieces recorded from various apps. Sequence a few of those samples. Then I load either IAA or AU instrument into bank c. Find a sound in a synth - record a pattern. Tweak midi. Record automation. (Or record it live ). Add a new audio track and set input to bank c. Record that midi into audio. Remove the pattern from timeline. Go back to the IAA or AU synth and find a new sound I like. Record new midi pattern - then add another track and record audio of that midi. Mute one or both of those audio tracks and maybe unload the synth and load a new one and record some loops of that like above. Keep adding audio tracks and then it's easy to arrange those clips on timeline.

    Very similar to the way I'm using it, but I'm also sampling IAA stuff, then sending the slices to pads.

    I've only had one freeze issue so far, on the first day, so pretty happy with things. I lost a bit of work when Auria Pro came out but that soon stabilised, so I can see the same happening for BM3. I just hope they don't get distracted with creating the desktop version, and make fixing the iOS bugs a priority.

  • @MonzoPro said:

    @Halftone said:
    After a few days use I think I can say i love it and will be using it a lot. I'm using it more as a daw.

    Here's a workflow I'm using. Load a drum kit on bank a. Program some beats. Load up some loops in bank b. I've got lots of projects recorded into AUM - unfinished bits and pieces recorded from various apps. Sequence a few of those samples. Then I load either IAA or AU instrument into bank c. Find a sound in a synth - record a pattern. Tweak midi. Record automation. (Or record it live ). Add a new audio track and set input to bank c. Record that midi into audio. Remove the pattern from timeline. Go back to the IAA or AU synth and find a new sound I like. Record new midi pattern - then add another track and record audio of that midi. Mute one or both of those audio tracks and maybe unload the synth and load a new one and record some loops of that like above. Keep adding audio tracks and then it's easy to arrange those clips on timeline.

    Very similar to the way I'm using it, but I'm also sampling IAA stuff, then sending the slices to pads.

    I've only had one freeze issue so far, on the first day, so pretty happy with things. I lost a bit of work when Auria Pro came out but that soon stabilised, so I can see the same happening for BM3. I just hope they don't get distracted with creating the desktop version, and make fixing the iOS bugs a priority.

    Pretty much the same workflow I've started using. It's very reminiscent of sampling vinyl onto audio tracks in ableton. Only problem is my 64gb iPad is running out of space alarmingly fast now lol. Definitely need the new pros to release here in India fast. Just need to survive 2 more weeks!

  • edited July 2017

    I'm very impressed with BM3. The sampling and editing capabilities are versatile and fantastic. I sampled some of my favourite patches on my Roland D50 and JD800 and used the live stretch functions and multi sample mapping and it's awesome. This is definitely the go to DAW for me on iOS.

  • Has anyone tried BM3 yet here? I heard some people here discussing previously.

  • edited July 2017

    @Tritonman said:
    Has anyone tried BM3 yet here? I heard some people here discussing previously.

  • @Tritonman said:
    Has anyone tried BM3 yet here? I heard some people here discussing previously.

    I don't think it's gotten a lot of traction so far. It's so hard for the word to get around about new apps these days.

  • Never heard of it.

  • wimwim
    edited July 2017

    Quite apart from the scene mode, I discovered something very nice about the sequencer once I understood it. If you touch one of the patterns in the list at the left as the sequence is playing, BM3 swaps that pattern in instead of the currently playing pattern in that bank. It'll just keep looping until you touch another pattern, or return control to the sequencer by touching the little play button at the right of the sequencer.

    This is terrific you can:

    • Mark a section of your song that you want to work on using the loop markers, and turn on looping.
    • Press play, and any patterns you have on the timeline in that section will play.
    • Audition other patterns, temporarily to try out new combinations.
    • Finally replace the patterns in that section with what works best.

    This is a great workflow for me. It allows me to do the easy part (bank a bunch of short loops that I'm happy with), then with minimal fuss get to the part where I always fall down - arranging them in a timeline to actually finish something (occasionally).

    The problem I've always had with timeline sequencers is all that moving around, copying, deleting, etc. Plus, the "bank" of patterns all have to "go" somewhere in the timeline if you want to make use of them, so where to park them as you churn them out?

    The problem I've always had with Modstep / clip launching is getting from there to a timeline arrangement before I lose interest or get too confused.

    This gives the best of both worlds. A place to hold all the patterns, and a way to quickly get them into the timeline after non-destructively trying different things out. Forget Scene mode - I think I've found my sweet spot.

    The only thing keeping it being perfect IMO is the inability to have track "lanes" for each pad. One pattern per bank, or the need to overlay patterns is a bit of a buzz kill. Still, I don't all that often get up over 8 parts, and by then should be committing to audio anyway. B)

  • @wim thanks for the workflow description. I understand this dilemma and will study your suggestion

  • @wim said:
    Quite apart from the scene mode, I discovered something very nice about the sequencer once I understood it. If you touch one of the patterns in the list at the left as the sequence is playing, BM3 swaps that pattern in instead of the currently playing pattern in that bank. It'll just keep looping until you touch another pattern, or return control to the sequencer by touching the little play button at the right of the sequencer.

    This is terrific you can:

    • Mark a section of your song that you want to work on using the loop markers, and turn on looping.
    • Press play, and any patterns you have on the timeline in that section will play.
    • Audition other patterns, temporarily to try out new combinations.
    • Finally replace the patterns in that section with what works best.

      This is a great workflow for me. It allows me to do the easy part (bank a bunch of short loops that I'm happy with), then with minimal fuss get to the part where I always fall down - arranging them in a timeline to actually finish something (occasionally).

    The problem I've always had with timeline sequencers is all that moving around, copying, deleting, etc. Plus, the "bank" of patterns all have to "go" somewhere in the timeline if you want to make use of them, so where to park them as you churn them out?

    The problem I've always had with Modstep / clip launching is getting from there to a timeline arrangement before I lose interest or get too confused.

    This gives the best of both worlds. A place to hold all the patterns, and a way to quickly get them into the timeline after non-destructively trying different things out. Forget Scene mode - I think I've found my sweet spot.

    The only thing keeping it being perfect IMO is the inability to have track "lanes" for each pad. One pattern per bank, or the need to overlay patterns is a bit of a buzz kill. Still, I don't all that often get up over 8 parts, and by then should be committing to audio anyway. B)

    I like all of this, but to me the sequencer is beyond repair when compared to what I’m used to in Auria. I can achieve everything you’re saying in there without much work, and I’ve been doing that for a long time now. Love BM3, but I dont see it ever replacing Auria for sequencing. At least not in my workflow.

  • wimwim
    edited July 2017

    @boone51 said:
    Love BM3, but I dont see it ever replacing Auria for sequencing. At least not in my workflow.

    Yep. If it ain't broke don't fix it.

  • The user and all related content has been deleted.
  • edited July 2017

    Can ruismaker be loaded and then played on the pads?

    Can synth AUs be played on the pads like how soul keys loads?

  • edited July 2017

    @tja said:

    @boone51 said:
    I like all of this, but to me the sequencer is beyond repair when compared to what I’m used to in Auria. I can achieve everything you’re saying in there without much work, and I’ve been doing that for a long time now. Love BM3, but I dont see it ever replacing Auria for sequencing. At least not in my workflosaid

    I did not notice any looping-section or song-building part in Auria Pro.

    Where do I need to look for this?

    Double tap the timeline and drag. You'll get the trusty handles that you can drag out to your desired length. This will work the same as bm3, as in, this is where you'll record. If you want it to quantize, simply select that from the quantize menu at the top. Finally, loop is an option (kind of hidden for my tastes) under that "transport options" drop down at the top right. Select loop from there, and you're off. Playhead will loop there, and you can just record take after take to your hearts content, slicing and forgetting the bits you love or hate.

    As far as the "song building" section, you'll find that will fill up the entire screen as soon as you open the app. ;-)

    Disclaimer; I am not and have never pretended to be someone who is proficient at making edm. I record analog instruments for the most part. I don't do sequencing of beats etc. BM3 still holds plenty of promise for those of us outside of the "Beat Making" world, though.

  • @raindro said:
    Can ruismaker be loaded and then played on the pads?

    Yes, but maybe not exactly how you're thinking. Ruismaker can be loaded onto a pad. Then you can switch that pad to keys mode to play notes like you would on a keyboard. In the case of Ruismaker, you would play the usual C#, D#, etc. So, the pads aren't in order like you might want them to be, all grouped together, but they are playable as pads.

    In theory, you could load one Ruismaker instance per pad, and set the pad note so that it works as expected, but there's a known BM3 bug that crashes it on open if there's more than one Ruismaker instance.

    Can synth AUs be played on the pads like how soul keys loads?

    Yes they can be played on the pads. I don't know what you're referring to re: soul keys specifically though.

  • @wim said:
    Quite apart from the scene mode, I discovered something very nice about the sequencer once I understood it. If you touch one of the patterns in the list at the left as the sequence is playing, BM3 swaps that pattern in instead of the currently playing pattern in that bank. It'll just keep looping until you touch another pattern, or return control to the sequencer by touching the little play button at the right of the sequencer.

    This is terrific you can:

    • Mark a section of your song that you want to work on using the loop markers, and turn on looping.
    • Press play, and any patterns you have on the timeline in that section will play.
    • Audition other patterns, temporarily to try out new combinations.
    • Finally replace the patterns in that section with what works best.

      This is a great workflow for me. It allows me to do the easy part (bank a bunch of short loops that I'm happy with), then with minimal fuss get to the part where I always fall down - arranging them in a timeline to actually finish something (occasionally).

    The problem I've always had with timeline sequencers is all that moving around, copying, deleting, etc. Plus, the "bank" of patterns all have to "go" somewhere in the timeline if you want to make use of them, so where to park them as you churn them out?

    The problem I've always had with Modstep / clip launching is getting from there to a timeline arrangement before I lose interest or get too confused.

    This gives the best of both worlds. A place to hold all the patterns, and a way to quickly get them into the timeline after non-destructively trying different things out. Forget Scene mode - I think I've found my sweet spot.

    The only thing keeping it being perfect IMO is the inability to have track "lanes" for each pad. One pattern per bank, or the need to overlay patterns is a bit of a buzz kill. Still, I don't all that often get up over 8 parts, and by then should be committing to audio anyway. B)

    Ahhh...thank you Mr Wim. That might explain some of the unexpected behaviour I noticed when I first bought the app and inadvertently selected patterns on the left.

    Not sure if I'd really use this feature, but nice to know about it - and how to switch it off!

  • @raindro said:
    Can ruismaker be loaded and then played on the pads?

    Can synth AUs be played on the pads like how soul keys loads?

    Just to add, you can also load Ruismaker, record all the drums of a preset in a single take, slice it and auto distribute it to different pads. Then you can save it as a bank

  • @wim said:

    @raindro said:
    Can ruismaker be loaded and then played on the pads?

    So, the pads aren't in order like you might want them to be, all grouped together, but they are playable as pads.

    How about this to order the pads a little better.
    (Using the default (black key trigger) ruismaker setting.)
    Load Ruismaker into bm3
    Set the pads to minor pentatonic scale
    Set the first note to d#1

    The 5th to 12th pads in the bm3 instument have the corresponding ruismaker pads.
    Not perfect but a little better, maybe!

  • Can I delete a sound from a pad once it is put there? Is there an actual manual with an index yet?

  • edited July 2017

    @srcer said:

    @ElGregoLoco said:
    I still have regular crashes on my side (like every 5-6 hours of use) and I identified many odd behaviors when playing with audio files/pattern (like when you slice a pattern on a audio file and then want to edit it, the ending loop marker is not at the right place, etc), but after more than 30hrs on the app I can now confirm that it is (or will be in fact) wonderful... I will now probably wait until the 'public beta' is over i.e. wait for a few updates before I use it again (in the current state it is not stable enough for me to build a full project in... Too risky IMO), but I'm really looking forward to be able to use it correctly...
    Peace.

    Perhaps @mathieugarcia should add you to his beta team so you can test the forthcoming code before it's released :)

    Don't ... Just don't... I begged to be in the beta when it was opened and they rejected my proposal in a 'not very nice' way... That's why I made jokes back then to say it was a VIB (Very Important Beta)...
    I really wish I could have been part of the beta as it seems that most beta testers have not really used the thing given the instable state it is in right now...
    Yesterday night I spent 6 hours working on a project, I thought everything was fine and then I tried to save a sliced loop to AIFF so that I could reload it in the same bank on the second page of pads to slice it again with a new effect on (HP filter to make the intro, would have been good). At first it seemed to worked but once sliced to pad on the second page of the bank, the app crash completly everytime I touch pad... Another 6 hours to the trash can I guess (I already lost about 40hrs on the app trying to finalize at least one simple project, but I was never able to because of the instability of the app)... Right now, I'm very frustrated and feel like back when I was believing in Retronyms... Sad

    @Tritonman said:
    Can I delete a sound from a pad once it is put there? Is there an actual manual with an index yet?

    It seems sometimes you can and sometimes you can't... Probably linked to the fact that the sample is currently playing or not I guess... Sometimes when I cannot delete a pad, I close the app and restart it and I can then delete it ...
    The same goes with files/folders that you delete from the library on 'Edit' mode... You have to quit the app and restart it to see them disappear from the lib...
    What a good beta tested app... For sure...

    PS : Sorry for being so sarcastic and negative... But given the teasing and the first feed back from beta testers, I admit I really thought this app would be the holy grail for me.. .And therefore, I am very disapointed today...
    I still love what the app intend to propose and the functionnalities it tries to achieve... But the fact that it is so buggy and instable make it impossible to finish a project...
    I mean, it's supposed to be really more suited to my sample based music style than Gadget (for which it take me hours to put to the right tempo and slice loops outside the app before I load in Bilbao) but at least, Gadget has never crashed on me, has always been supa stable on my iPad Air2 and allows me to finalize music projects (it does less than BM3 regarding samples, but at least it does it correctly).

  • @ElGregoLoco said:

    @srcer said:

    @ElGregoLoco said:
    I still have regular crashes on my side (like every 5-6 hours of use) and I identified many odd behaviors when playing with audio files/pattern (like when you slice a pattern on a audio file and then want to edit it, the ending loop marker is not at the right place, etc), but after more than 30hrs on the app I can now confirm that it is (or will be in fact) wonderful... I will now probably wait until the 'public beta' is over i.e. wait for a few updates before I use it again (in the current state it is not stable enough for me to build a full project in... Too risky IMO), but I'm really looking forward to be able to use it correctly...
    Peace.

    Perhaps @mathieugarcia should add you to his beta team so you can test the forthcoming code before it's released :)

    Don't ... Just don't... I begged to be in the beta when it was opened and they rejected my proposal in a 'not very nice' way... That's why I made jokes back then to say it was a VIB (Very Important Beta)...
    I really wish I could have been part of the beta as it seems that most beta testers have not really used the thing given the instable state it is in right now...
    Yesterday night I spent 6 hours working on a project, I thought everything was fine and then I tried to save a sliced loop to AIFF so that I could reload it in the same bank on the second page of pads to slice it again with a new effect on (HP filter to make the intro, would have been good). At first it seemed to worked but once sliced to pad on the second page of the bank, the app crash completly everytime I touch pad... Another 6 hours to the trash can I guess (I already lost about 40hrs on the app trying to finalize at least one simple project, but I was never able to because of the instability of the app)... Right now, I'm very frustrated and feel like back when I was believing in Retronyms... Sad

    @Tritonman said:
    Can I delete a sound from a pad once it is put there? Is there an actual manual with an index yet?

    It seems sometimes you can and sometimes you can't... Probably linked to the fact that the sample is currently playing or not I guess... Sometimes when I cannot delete a pad, I close the app and restart it and I can then delete it ...
    The same goes with files/folders that you delete from the library on 'Edit' mode... You have to quit the app and restart it to see them disappear from the lib...
    What a good beta tested app... For sure...

    PS : Sorry for being so sarcastic and negative... But given the teasing and the first feed back from beta testers, I admit I really thought this app would be the holy grail for me.. .And therefore, I am very disapointed today...
    I still love what the app intend to propose and the functionnalities it tries to achieve... But the fact that it is so buggy and instable make it impossible to finish a project...
    I mean, it's supposed to be really more suited to my sample based music style than Gadget (for which it take me hours to put to the right tempo and slice loops outside the app before I load in Bilbao) but at least, Gadget has never crashed on me, has always been supa stable on my iPad Air2 and allows me to finalize music projects (it does less than BM3 regarding samples, but at least it does it correctly).

    Its getting a bit old with you constantly stating the fact that they turned you down from the beta. i think i personally have seen at-least 10+ posts now. you're bitter that they turned you down. we get it. but please stop posting it again and again.

    Yes. the app is a mess. no i am not a tester. that being said the release branch isn't the betas the testers have. its atleast a couple versions behind. so many of these bugs have already been fixed. I'm just going to patiently wait till the broken stuff gets fixed. but even in its broken state this is the best sampler on IOS. I'm having a blast tinkering around in it for the challenge @JangoMango created.

Sign In or Register to comment.