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!

2456710

Comments

  • Does BM3, record the output of AU Midi fx now?

  • @realdawei said:

    @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.

    That’s D1...it doesn’t multi instance well in any host

    Aight, thank you.

  • edited October 2019

    Not sure if it is an issue with the plugins (maybe?) or BM3 (probably?) but I find Synthmaster One, Factory and DRC do not receive the proper BPM when midiclock is on so arps are all messed up.

  • Still crashes when looping a sample (2 sec) and hitting reverse . Sometimes it mutes the sound and have to reset .

    Needs to address the midiFX routing and a sample toggle trigger mode .

  • @espiegel123 said:
    Does BM3, record the output of AU Midi fx now?

    No. That’s a much bigger issue which is on the table for a future update.

  • @Korakios said:
    Still crashes when looping a sample (2 sec) and hitting reverse . Sometimes it mutes the sound and have to reset .

    Needs to address the midiFX routing and a sample toggle trigger mode .

    Please post any crashes on the Intua forum where we can properly reproduce and log.

  • @AudioGus said:
    Not sure if it is an issue with the plugins (maybe?) or BM3 (probably?) but I find Synthmaster One, Factory and DRC do not receive the proper BPM when midiclock is on so arps are all messed up.

    We did extensive testing with tempo match can you please post in the forum.

  • @hansjbs said:

    @AudioGus said:
    Not sure if it is an issue with the plugins (maybe?) or BM3 (probably?) but I find Synthmaster One, Factory and DRC do not receive the proper BPM when midiclock is on so arps are all messed up.

    We did extensive testing with tempo match can you please post in the forum.

    I wonder what ios version you are on?

  • @hansjbs said:

    @Korakios said:
    Still crashes when looping a sample (2 sec) and hitting reverse . Sometimes it mutes the sound and have to reset .

    Needs to address the midiFX routing and a sample toggle trigger mode .

    Please post any crashes on the Intua forum where we can properly reproduce and log.

    No way, I am not going back there. If Intua decides to have a bug tracker or at least an official email support I’ll post it there. Forums are for users....

    Plus I kindly got a pm from a beta tester and uploaded my crash report and video before this update .

  • @[Deleted User] said:

    @hansjbs said:

    @AudioGus said:
    Not sure if it is an issue with the plugins (maybe?) or BM3 (probably?) but I find Synthmaster One, Factory and DRC do not receive the proper BPM when midiclock is on so arps are all messed up.

    We did extensive testing with tempo match can you please post in the forum.

    I wonder what ios version you are on?

    Latest iPadOS version but we have testers various ios versions

  • @hansjbs said:

    @[Deleted User] said:

    @hansjbs said:

    @AudioGus said:
    Not sure if it is an issue with the plugins (maybe?) or BM3 (probably?) but I find Synthmaster One, Factory and DRC do not receive the proper BPM when midiclock is on so arps are all messed up.

    We did extensive testing with tempo match can you please post in the forum.

    I wonder what ios version you are on?

    Latest iPadOS version but we have testers various ios versions

    Sorry hansjbs i meant @AudioGus

  • @Korakios said:

    @hansjbs said:

    @Korakios said:
    Still crashes when looping a sample (2 sec) and hitting reverse . Sometimes it mutes the sound and have to reset .

    Needs to address the midiFX routing and a sample toggle trigger mode .

    Please post any crashes on the Intua forum where we can properly reproduce and log.

    No way, I am not going back there. If Intua decides to have a bug tracker or at least an official email support I’ll post it there. Forums are for users....

    Plus I kindly got a pm from a beta tester and uploaded my crash report and video before this update .

    Ok Cool.

  • @[Deleted User] said:

    @hansjbs said:

    @AudioGus said:
    Not sure if it is an issue with the plugins (maybe?) or BM3 (probably?) but I find Synthmaster One, Factory and DRC do not receive the proper BPM when midiclock is on so arps are all messed up.

    We did extensive testing with tempo match can you please post in the forum.

    I wonder what ios version you are on?

    Oh snap, good call, I have been sleeping on the last iOS update. Ok will do now.

  • @AudioGus said:

    My DRC AUv3 syncs perfectly with BM3(3.0.13), Don't have Factory.
    Is your DRC updated to the latest version(2.2.5)?

    Some AUv3's have an option to enable host sync, don't know if Factory has one?
    (DRC Stand Alone app has setting for this next to the tempo while the AUv3 has sync enabled by default and can not be changed).

    I'm on iPad Air 2, iPadOS13.1.3...

  • edited October 2019

    The MIDI improvements will make this 100% more useful for me. BM3 will now be able to be integrated into my studio.

    Many thanks

  • Quick Saturday morning coffee jam to check out the new release. Only a sketch but I’m looking forward to getting my head back in the BM3 world now it is actively being developed again. The full public verdict on this release will come in due time but what I can say is that I saw first hand just how much effort went into getting this update out and it was significant. Both from the developer and the testers.

  • @AudioGus seems to be working ok for me in Factory as well. Did you have anything running at 300bpm in another host previously that didn’t close down gracefully? Maybe reboot and retest?

  • edited October 2019

    All I ask (most politely) is that when anyone encounters an issue in this new update, they realise that it's not always automatically the host's fault.

    Here are a handful of other things that could be to blame (instead of BM3):

    • iOS version
    • iPad model (esp. if older/ lower RAM)
    • buggy AUv3 plugins
    • incorrect midi sync/slave settings
    • incorrect midi controller setup
    • triggering 'known issues'
    • user error

    Having said that, if you do spot an issue, please post it here, at the Intua forum, on our Discord server, or as a direct email to Intua, and we will do our best to test/confirm and bring it to the dev's attention. Hell, you can even PM it to me if that's what works for you :)

    Peace.

  • edited October 2019

    @Samu said:

    @AudioGus said:

    My DRC AUv3 syncs perfectly with BM3(3.0.13), Don't have Factory.
    Is your DRC updated to the latest version(2.2.5)?

    Some AUv3's have an option to enable host sync, don't know if Factory has one?
    (DRC Stand Alone app has setting for this next to the tempo while the AUv3 has sync enabled by default and can not be changed).

    I'm on iPad Air 2, iPadOS13.1.3...

    @gusgranite @hansjbs

    Hmmm, well I updated to the latest iOS (apps all up to date) but still getting a bunch of midi clock issues. I will try different clock hosts (circuit, samplitude, different midi interfaces etc) later on and see if I can find a source to my issues. Could entirely be on my end. Ultimately the midi playback start/stop that was already working previously in BM3 (and still does) was/is fine for my needs, so clock sync is icing if I get it working,

  • @AudioGus said:

    @Samu said:

    @AudioGus said:

    My DRC AUv3 syncs perfectly with BM3(3.0.13), Don't have Factory.
    Is your DRC updated to the latest version(2.2.5)?

    Some AUv3's have an option to enable host sync, don't know if Factory has one?
    (DRC Stand Alone app has setting for this next to the tempo while the AUv3 has sync enabled by default and can not be changed).

    I'm on iPad Air 2, iPadOS13.1.3...

    @gusgranite @hansjbs

    Hmmm, well I updated to the latest iOS (apps all up to date) but still getting a bunch of midi clock issues. I will try different clock hosts (circuit, samplitude, different midi interfaces etc) later on and see if I can find a source to my issues. Could entirely be on my end. Ultimately the midi playback start/stop that was already working previously in BM3 (and still does) was/is fine for my needs, so clock sync is icing if I get it working,

    Ok let us know anyway we can help.

  • Fantastic news about the arrival of the update. Thanks to everyone involved. The clocks go back tonight here in the UK, so an extra hour to play.

  • @tk32 said:
    All I ask (most politely) is that when anyone encounters an issue in this new update, they realise that it's not always automatically the host's fault.

    Here are a handful of other things that could be to blame (instead of BM3):

    • iOS version
    • iPad model (esp. if older/ lower RAM)
    • buggy AUv3 plugins
    • incorrect midi sync/slave settings
    • incorrect midi controller setup
    • triggering 'known issues'
    • user error

    Having said that, if you do spot an issue, please post it here, at the Intua forum, on our Discord server, or as a direct email to Intua, and we will do our best to test/confirm and bring it to the dev's attention. Hell, you can even PM it to me if that's what works for you :)

    Peace.

    Thank you.

    OK then, here's the settings page related to MIDI slave sync.
    Again, BM3 follows MIDI clock very well and the built-in clock smoothing window seems just about right for real-world scenarios, the only issue is that there is constant latency added that cannot be corrected from what I've found 'til now: The higher the audio buffer, the higher the latency. Negative latency adjustment up to about -100ms would be very helpful I think. (See Groove Rider GR-16 for a great example how to do it "right")

  • edited October 2019

    That X button is so hot right now.

  • edited October 2019

    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?

  • Happy to see this finally drop. I had already come to being in a good space with Bm3 so I don’t even really notice anything different except a few new UI buttons and tweaks. It’s been stable for me since the last update.

  • @OscarSouth is there a difference in the library sizes?

  • @gusgranite said:
    @OscarSouth is there a difference in the library sizes?

    Yeah, the machine that's taking ages has a larger library.

  • 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.

  • @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...

  • @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.

Sign In or Register to comment.