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.0.13 update Is now LIVE!

1356710

Comments

  • @Samu said:

    @OscarSouth said:
    One of my devices is sitting on the splash screen indefinitely (over an hour now) where the other device passed through pretty much immediately. Should I kill the app an reboot or let it keep working?

    Guess the 'optomized' database engine didn't make it to 3.0.13...

    I would let it do it’s thing. It will scan through eventually I expect.

  • Does BM3 come with preinstalled sample library ? Because after installing I downloaded the free content and got some doubled samples

  • @gusgranite said:

    @Apex said:
    Got it syncing to my external gear straight away thru midi clock. Works effortlessly. Can’t really speak to the “tightness” yet, will have to do more testing....... but it works!!! Will make recording 100x easier now. Many thanks to everybody who made this happen. BM3 is now back in the mix with the rest of the studio.

    Right on.

    MIDI Sync is very responsive and I'm more than happy to finally see it arrive in BM3!
    The only thing that needs fixing is the constant latency which increases with higher audio buffer size.

  • Good to see effort and progress is ongoing. Thanks much to the developer(s) and also the fine cadre of testers etc. :)

  • @gusgranite said:

    @Samu said:

    @OscarSouth said:
    One of my devices is sitting on the splash screen indefinitely (over an hour now) where the other device passed through pretty much immediately. Should I kill the app an reboot or let it keep working?

    Guess the 'optomized' database engine didn't make it to 3.0.13...

    I would let it do it’s thing. It will scan through eventually I expect.

    This is still going. It's not that big of a library -- reckon I can close and re-open without any danger of projects being corrupted?

  • @OscarSouth said:

    @gusgranite said:

    @Samu said:

    @OscarSouth said:
    One of my devices is sitting on the splash screen indefinitely (over an hour now) where the other device passed through pretty much immediately. Should I kill the app an reboot or let it keep working?

    Guess the 'optomized' database engine didn't make it to 3.0.13...

    I would let it do it’s thing. It will scan through eventually I expect.

    This is still going. It's not that big of a library -- reckon I can close and re-open without any danger of projects being corrupted?

    Thoughts and prayers

  • System restart sorted it and BM3 is slaving perfectly to AB3. Awesome!

  • @OscarSouth said:
    System restart sorted it and BM3 is slaving perfectly to AB3. Awesome!

    Brave! 😉

  • Is there a consensus yet on whether this is significantly more stable than earlier releases (with non-problematic AUs like Digital D1 which seems to have troubles in other hosts). I've been waiting to get BM3 till its stability was better than previously reported. I would probably be using it often as a slicer and for re-exporting as AppleLoops for GB and BeatHawk and as an IAA Sampler.

  • @OscarSouth said:
    System restart sorted it and BM3 is slaving perfectly to AB3. Awesome!

    👍

  • @[Deleted User] said:

    @OscarSouth said:
    System restart sorted it and BM3 is slaving perfectly to AB3. Awesome!

    👍

    Can it be slaved to Xequence 2?

  • edited October 2019

    BM3 is unusable now on latest 12.9 ipad pro and ios 13.1.3 – the volume is stuck at 100% and the ipad volume buttons / system volume doesn’t affect it at all. Anyone else?

    Tried restarting both app and ipad

  • edited October 2019

    @espiegel123 said:

    @[Deleted User] said:

    @OscarSouth said:
    System restart sorted it and BM3 is slaving perfectly to AB3. Awesome!

    👍

    Can it be slaved to Xequence 2?

    I dont have Xequence anymore but if it send midi clock it should.

  • @mistkerl said:
    First (audio) crash after 1 minute of using it:

    I played 3 chords with d1, loaded another instance of d1 and the sound crashed.
    Bm3 Restart fixed the problem. Everything is allright now.

    Same problem in Nanostudio 2.10...

  • I've been one of the fortunate ones who has never had any significant problems with BM3 and I have to say that right now it feels great to use to a level beyond where it was 4 hours ago. Whether it's the seamlessness of the MIDI clock (which is a huuuuge help to me), the GUI/UX tweaks or other stuff going on under the hood, it just looks and feels smooth as fuck right now.

  • @tk32 said:
    Just wanted to break the news that this current BM3 beta round has now finished, and you should see the new 3.0.13 update appear in all appstores shortly.

    I’ll post the official changelog once that happens

    :+1:

    Can you hear them calling you....whispering desperately on the breeze...."the book......please the book....book....." :)

  • @JohnnyGoodyear said:

    @tk32 said:
    Just wanted to break the news that this current BM3 beta round has now finished, and you should see the new 3.0.13 update appear in all appstores shortly.

    I’ll post the official changelog once that happens

    :+1:

    Can you hear them calling you....whispering desperately on the breeze...."the book......please the book....book....." :)

    I’m flattered by your excitement for the book; and humbled by your continued patience. I promise to PM you as soon as it’s ready - not long now, i promise.

  • Much thanks to the dev and beta team.. it’s really a beautiful DAW.. Midi Export is great..

    Thanks..

  • edited October 2019

    Looks like Vincent and beta testers have done an excellent job. It is actually a lot smoother now. Start, stop midi clock and Link is love, makes the BM3/BlocsWave Workflow so much tighter. Exporting much better.

  • edited October 2019

    Happy to see how happy many of you are with this update. We will definitely forward the message from here to Vincent. More to come!

  • I used to have frequent stability issues with AU and then even with slicing up large samples. I’ve not been able to get it to crash like I used to. It has been fun watching the beta issues get resolved. Gives me a lot of hope that BM3 is on the up and up.

  • I’m having an issue with Redshrike AU. It’s fine when BM3 transport isn’t playing, but as soon as I press play, notes played in Redshrike only sound for about a millisecond. Arp is not engaged.

    I thought I’d ask if anyone else sees this before I spend a lot of time troubleshooting an issue that may just be me.

  • Hmmm.....less then 10 mins in it crashed, and now when I try to reopen the session it says session is corrupt and cannot open. So Looks like it’s Zenbeats for me 🤷🏽‍♂️

  • @Strizbiz said:
    Hmmm.....less then 10 mins in it crashed, and now when I try to reopen the session it says session is corrupt and cannot open. So Looks like it’s Zenbeats for me 🤷🏽‍♂️

    Can you detail the session for us?

  • @wim said:
    I’m having an issue with Redshrike AU. It’s fine when BM3 transport isn’t playing, but as soon as I press play, notes played in Redshrike only sound for about a millisecond. Arp is not engaged.

    I thought I’d ask if anyone else sees this before I spend a lot of time troubleshooting an issue that may just be me.

    Only Redshrike?

  • I had three banks. Fractal Bits AU, BASSalicious 2 AU, with a simple pattern on each. Tried to add RedShrike and it won’t play right from the BM3 keyboard or key pads if the BM3 transport is running.

    I’ve done no further tests. Just thought I’d throw it out here in case I’d be wasting my time trying to figure out if it’s just me. The troubleshooting path is different if it’s an issue for others as well.

  • I just had an hour playing around with this update and Im loving it. Great work beta testers.
    For the first time, I kind of get scenes as well, Im not sure if it has changing or Ive just twigged but its very useful to try out combinations of patterns to try and get out of the 4 bar sticking point. Im still a rank beginner with this one but it is now feeling much more comfortable to work with. Looking forward to the book also @tk32
    Go BM3. <3

  • @wim said:
    I had three banks. Fractal Bits AU, BASSalicious 2 AU, with a simple pattern on each. Tried to add RedShrike and it won’t play right from the BM3 keyboard or key pads if the BM3 transport is running.

    I’ve done no further tests. Just thought I’d throw it out here in case I’d be wasting my time trying to figure out if it’s just me. The troubleshooting path is different if it’s an issue for others as well.

    Do you have a midi sequencer running at the same time? That disables keys and pads I think.

  • @gusgranite said:

    @wim said:
    I had three banks. Fractal Bits AU, BASSalicious 2 AU, with a simple pattern on each. Tried to add RedShrike and it won’t play right from the BM3 keyboard or key pads if the BM3 transport is running.

    I’ve done no further tests. Just thought I’d throw it out here in case I’d be wasting my time trying to figure out if it’s just me. The troubleshooting path is different if it’s an issue for others as well.

    Do you have a midi sequencer running at the same time? That disables keys and pads I think.

    Nope. Only what I described. Thanks for the suggestion though.

  • @Strizbiz said:
    Hmmm.....less then 10 mins in it crashed, and now when I try to reopen the session it says session is corrupt and cannot open. So Looks like it’s Zenbeats for me 🤷🏽‍♂️

    By chance did you rename this session folder, the included .bm3 file, or move the sessions .bm3 file out of its required folder before saving? This will produce a corrupt session.

Sign In or Register to comment.