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!

1235710

Comments

  • Can't wait to update!! Does it seem to be running better on ios 12 or ios 13 ? ..guessing it was tested pretty well with 13

  • edited October 2019

    Can’t say I’m off to an encouraging start.
    Crashed immediately after launching.
    Crashed opening the store.
    I tried downloading a pack that still didn’t show as downloaded. The importing files step took several minutes. Then the pack still didn’t show as installed so I refreshed the store and then it only showed about 10 packs. I refreshed again and it crashed.

    On multiple iPads now I’ve never been able to get all the content installed and the bug with packs state text being randomly green or grey continues.

    This was my 2018 iPad Pro 12.9 on 13.1.2.

  • @Liquidmantis thanks for mentioning the store , I had some problems too. In my case

    Bug 5 (ignore the number it’s just my list)
    Store content doesn’t show that the pack is downloading , only after 10 sec which results in multiple downloads (since I keep pressing to download) and can’t cancel later.
    So I end up with multiple copies...

  • got an AU effect loading crash (electrogene) but all good otherwise. Jammed for a while last night in bed and that was my only crash. i am training myself to hit that save button every time i change screens or load anything.

  • @Korakios said:
    Second bug
    Using BM3 inside AB3 (workaround for midi FX routing by hosting midi in AB3) , causes BM3 to show 28 instances of the same single midi FX plugin (on the midi IO settings tab & Bank/pad IO)

    Third bug
    BM3 midi port is not available to Banks . Only way to work is select ‘ALL’ option which routes all midi from all midi ports.

    4th bug
    Unused - unchecked midi ports from the settings , are still showing on the bank/pad midi routing.

    iOS 13 latest ,Air2

    Hi @Korakios - I am trying to recreate your bug #2 as this an unusual use case that probably didn’t come up in testing. Can you give more specific info please? Which apps? Screenshots of setup would be really helpful. Thanks.

  • @Korakios said:
    @Liquidmantis thanks for mentioning the store , I had some problems too. In my case

    Bug 5 (ignore the number it’s just my list)
    Store content doesn’t show that the pack is downloading , only after 10 sec which results in multiple downloads (since I keep pressing to download) and can’t cancel later.
    So I end up with multiple copies...

    I don’t think the store received any updates in this release unless it was backend stuff that wasn’t communicated to the beta team. So the request is you would like to see an indicator that it is downloading content so you don’t keep hitting the download button?

  • To everyone experiencing any bugs - we have the rare opportunity of an active beta team in place right now so if you are up for it, we will work with you to reproduce the issue and let the developer know. It will take some detail from you however. Screenshots and screen videos will be very helpful. If not, then a detailed explanation of which apps in which order and what you were doing at the time, etc. iPad version too of course.

    Thanks!

  • edited October 2019

    @gusgranite said:

    @Korakios said:
    Second bug
    Using BM3 inside AB3 (workaround for midi FX routing by hosting midi in AB3) , causes BM3 to show 28 instances of the same single midi FX plugin (on the midi IO settings tab & Bank/pad IO)

    Third bug
    BM3 midi port is not available to Banks . Only way to work is select ‘ALL’ option which routes all midi from all midi ports.

    4th bug
    Unused - unchecked midi ports from the settings , are still showing on the bank/pad midi routing.

    iOS 13 latest ,Air2

    Hi @Korakios - I am trying to recreate your bug #2 as this an unusual use case that probably didn’t come up in testing. Can you give more specific info please? Which apps? Screenshots of setup would be really helpful. Thanks.

    It’s very simple setup , BM3 (new empty) ,ROZETA,AB3

    @gusgranite said:

    @Korakios said:
    @Liquidmantis thanks for mentioning the store , I had some problems too. In my case

    Bug 5 (ignore the number it’s just my list)
    Store content doesn’t show that the pack is downloading , only after 10 sec which results in multiple downloads (since I keep pressing to download) and can’t cancel later.
    So I end up with multiple copies...

    I don’t think the store received any updates in this release unless it was backend stuff that wasn’t communicated to the beta team. So the request is you would like to see an indicator that it is downloading content so you don’t keep hitting the download button?

    Yes, something like preparing to download indication and prevent double downloads.
    Also there are 2 “drum tags” in banks

    It also crashes AB3 most of the times.
    Since BM3 doesn’t load in AB3 ,I have to launch first BM3 and when I launch AB3 ....boom....
    (send a crash report to @Michael )

  • @rezidue said:

    @wim said:
    Maybe it’s because I’m on 12.3.1. I’ll table this until I can update to iOS 13.

    You aren’t crazy, I just confirmed the same behavior and I’m running 12.4.1. Keys trigger normally until you hit play.

    OK, I can reproduce it as well. What's weird is in Redshrike it looks like you can override it by changing the Amplifier Release value in the synth.

  • @Korakios #2 confirmed. Will report. Thanks

  • @Korakios you may already know this but just in case, you can use Rozeta Baseline in BM3 directly by adding it as a MidiFX. You just cannot capture the midi output to the timeline.

  • edited October 2019

    @gusgranite said:
    @Korakios #2 confirmed. Will report. Thanks

    Since we are live ,plz check bug #1
    load a sample set it to loop forward ,adjust the loop points to a second and hit reverse.
    You might don’t want to use headphones or unplug it from your setup because the audio will go wild and iPad will mute audio when BME crashes (a soft reset restores audio)

    @gusgranite said:
    @Korakios you may already know this but just in case, you can use Rozeta Baseline in BM3 directly by adding it as a MidiFX. You just cannot capture the midi output to the timeline.

    But I want to capture the midi out ,to edit it in the timeline and then delete Rozeta :)

  • @gusgranite said:

    @rezidue said:

    @wim said:
    Maybe it’s because I’m on 12.3.1. I’ll table this until I can update to iOS 13.

    You aren’t crazy, I just confirmed the same behavior and I’m running 12.4.1. Keys trigger normally until you hit play.

    OK, I can reproduce it as well. What's weird is in Redshrike it looks like you can override it by changing the Amplifier Release value in the synth.

    Cool, thanks for taking the time to reproduce it. I was ready to assume it was iOS version related.

    Changing the release value to a longer time would have the appearance of overriding it, but probably just sounds like it is. Release is the amount of signal that fades out over time after you let go of the key. What seems to be happening here is the synth is a Note OFF is being processed immediately after the Note On instead of waiting for the key to be released. All extending the fade-out time of the note.

    I need to see if Midi Tools Monitor will work inside BM3 to see if these premature note-off messages are being sent by BM3, or somehow invented internally in the iceGear synths. I suspect iceGear since it’s only with these plugins.

  • @wim said:

    @gusgranite said:

    @rezidue said:

    @wim said:
    Maybe it’s because I’m on 12.3.1. I’ll table this until I can update to iOS 13.

    You aren’t crazy, I just confirmed the same behavior and I’m running 12.4.1. Keys trigger normally until you hit play.

    OK, I can reproduce it as well. What's weird is in Redshrike it looks like you can override it by changing the Amplifier Release value in the synth.

    Cool, thanks for taking the time to reproduce it. I was ready to assume it was iOS version related.

    Changing the release value to a longer time would have the appearance of overriding it, but probably just sounds like it is. Release is the amount of signal that fades out over time after you let go of the key. What seems to be happening here is the synth is a Note OFF is being processed immediately after the Note On instead of waiting for the key to be released. All extending the fade-out time of the note.

    I need to see if Midi Tools Monitor will work inside BM3 to see if these premature note-off messages are being sent by BM3, or somehow invented internally in the iceGear synths. I suspect iceGear since it’s only with these plugins.

    That makes sense and is helpful

  • edited October 2019

    Thanks for reporting those bugs. I second @gusgranite request.

    As for the store that was disabled during beta so we had no way of testing it so we will mark that up.

    The rozeta issue is weird we'll tag that also.

  • @Michael it appears to be any MidiFX that is loaded in ABF gets instantiated multiple times (26?) in BM3 Input Devices so letting you know as well. Thx

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

    I cannot reproduce this yet. I load a sample onto a pad, set Sample Loop as FORWARD, hold a key to loop the sample, and then hit Reverse as it is looping? Thx

  • @wim said:

    @gusgranite said:

    @rezidue said:

    @wim said:
    Maybe it’s because I’m on 12.3.1. I’ll table this until I can update to iOS 13.

    You aren’t crazy, I just confirmed the same behavior and I’m running 12.4.1. Keys trigger normally until you hit play.

    OK, I can reproduce it as well. What's weird is in Redshrike it looks like you can override it by changing the Amplifier Release value in the synth.

    Cool, thanks for taking the time to reproduce it. I was ready to assume it was iOS version related.

    Changing the release value to a longer time would have the appearance of overriding it, but probably just sounds like it is. Release is the amount of signal that fades out over time after you let go of the key. What seems to be happening here is the synth is a Note OFF is being processed immediately after the Note On instead of waiting for the key to be released. All extending the fade-out time of the note.

    I need to see if Midi Tools Monitor will work inside BM3 to see if these premature note-off messages are being sent by BM3, or somehow invented internally in the iceGear synths. I suspect iceGear since it’s only with these plugins.

    I’ve checked with Midi Monitor, and the notes being sent to RedShrike are as they should be when the transport is running. So, this is something about the iceGear synths themselves. Unfortunately not usable at this point in BM3.

    I’ve reported it to support @ iceGear.com.

  • @wim said:

    @wim said:

    @gusgranite said:

    @rezidue said:

    @wim said:
    Maybe it’s because I’m on 12.3.1. I’ll table this until I can update to iOS 13.

    You aren’t crazy, I just confirmed the same behavior and I’m running 12.4.1. Keys trigger normally until you hit play.

    OK, I can reproduce it as well. What's weird is in Redshrike it looks like you can override it by changing the Amplifier Release value in the synth.

    Cool, thanks for taking the time to reproduce it. I was ready to assume it was iOS version related.

    Changing the release value to a longer time would have the appearance of overriding it, but probably just sounds like it is. Release is the amount of signal that fades out over time after you let go of the key. What seems to be happening here is the synth is a Note OFF is being processed immediately after the Note On instead of waiting for the key to be released. All extending the fade-out time of the note.

    I need to see if Midi Tools Monitor will work inside BM3 to see if these premature note-off messages are being sent by BM3, or somehow invented internally in the iceGear synths. I suspect iceGear since it’s only with these plugins.

    I’ve checked with Midi Monitor, and the notes being sent to RedShrike are as they should be when the transport is running. So, this is something about the iceGear synths themselves. Unfortunately not usable at this point in BM3.

    I’ve reported it to support @ iceGear.com.

    Thanks - have let BM3 dev know.

  • @gusgranite said:

    @wim said:

    @wim said:

    @gusgranite said:

    @rezidue said:

    @wim said:
    Maybe it’s because I’m on 12.3.1. I’ll table this until I can update to iOS 13.

    You aren’t crazy, I just confirmed the same behavior and I’m running 12.4.1. Keys trigger normally until you hit play.

    OK, I can reproduce it as well. What's weird is in Redshrike it looks like you can override it by changing the Amplifier Release value in the synth.

    Cool, thanks for taking the time to reproduce it. I was ready to assume it was iOS version related.

    Changing the release value to a longer time would have the appearance of overriding it, but probably just sounds like it is. Release is the amount of signal that fades out over time after you let go of the key. What seems to be happening here is the synth is a Note OFF is being processed immediately after the Note On instead of waiting for the key to be released. All extending the fade-out time of the note.

    I need to see if Midi Tools Monitor will work inside BM3 to see if these premature note-off messages are being sent by BM3, or somehow invented internally in the iceGear synths. I suspect iceGear since it’s only with these plugins.

    I’ve checked with Midi Monitor, and the notes being sent to RedShrike are as they should be when the transport is running. So, this is something about the iceGear synths themselves. Unfortunately not usable at this point in BM3.

    I’ve reported it to support @ iceGear.com.

    Thanks - have let BM3 dev know.

    Cool. I’ve also mirrored some of these details over on the BM3 forum. Very quiet over there though.

  • @hansjbs said:
    Thanks for reporting those bugs. I second @gusgranite request.

    As for the store that was disabled during beta so we had no way of testing it so we will mark that up.

    The rozeta issue is weird we'll tag that also.

    @hansjbs One minor thing with the store. If I’m trying to scroll down through the content it will keep scrolling back to the top without being able to make any selections. Quitting the store and going back will clear it but eventually issue comes back.

    That being said, I have not used BM3 for a while because there were just too many issues in overall user experience. This version seems much more stable, smooth and user friendly than it was before. Air 1 12.4.1

  • edited October 2019

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

    I cannot reproduce this yet. I load a sample onto a pad, set Sample Loop as FORWARD, hold a key to loop the sample, and then hit Reverse as it is looping? Thx

    My bad ,you have to set the cross fade to some value . I can upload a screen recording if needed

  • @Korakios said:

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

    I cannot reproduce this yet. I load a sample onto a pad, set Sample Loop as FORWARD, hold a key to loop the sample, and then hit Reverse as it is looping? Thx

    My bad ,you have to set the cross fade to some value . I can upload a screen recording if needed

    Confirmed! Nice bug ;)

  • @gusgranite said:

    @Korakios said:

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

    I cannot reproduce this yet. I load a sample onto a pad, set Sample Loop as FORWARD, hold a key to loop the sample, and then hit Reverse as it is looping? Thx

    My bad ,you have to set the cross fade to some value . I can upload a screen recording if needed

    Confirmed! Nice bug ;)

    +1 let the countdown (another year?) to the next update begin ;)

    Personally I've stopped doing any sample edits while something stuff plays in BM3 just to avoid crashes...
    Same goes for adding plug-ins etc... (AUM and apeMatrix are rock solid in comparison).

  • @Samu said:

    @gusgranite said:

    @Korakios said:

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

    I cannot reproduce this yet. I load a sample onto a pad, set Sample Loop as FORWARD, hold a key to loop the sample, and then hit Reverse as it is looping? Thx

    My bad ,you have to set the cross fade to some value . I can upload a screen recording if needed

    Confirmed! Nice bug ;)

    +1 let the countdown (another year?) to the next update begin ;)

    Personally I've stopped doing any sample edits while something stuff plays in BM3 just to avoid crashes...
    Same goes for adding plug-ins etc... (AUM and apeMatrix are rock solid in comparison).

    You got the freaking monitoring working , so pretend to be happy :tongue:

  • @Korakios said:

    @Samu said:

    @gusgranite said:

    @Korakios said:

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

    I cannot reproduce this yet. I load a sample onto a pad, set Sample Loop as FORWARD, hold a key to loop the sample, and then hit Reverse as it is looping? Thx

    My bad ,you have to set the cross fade to some value . I can upload a screen recording if needed

    Confirmed! Nice bug ;)

    +1 let the countdown (another year?) to the next update begin ;)

    Personally I've stopped doing any sample edits while something stuff plays in BM3 just to avoid crashes...
    Same goes for adding plug-ins etc... (AUM and apeMatrix are rock solid in comparison).

    You got the freaking monitoring working , so pretend to be happy :tongue:

    Haha. Tough crowd but I get it.

    I wasn’t actually sure we would ever see an update so, personally, I’m over the moon!

  • @Samu said:

    @gusgranite said:

    @Korakios said:

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

    I cannot reproduce this yet. I load a sample onto a pad, set Sample Loop as FORWARD, hold a key to loop the sample, and then hit Reverse as it is looping? Thx

    My bad ,you have to set the cross fade to some value . I can upload a screen recording if needed

    Confirmed! Nice bug ;)

    +1 let the countdown (another year?) to the next update begin ;)

    Personally I've stopped doing any sample edits while something stuff plays in BM3 just to avoid crashes...
    Same goes for adding plug-ins etc... (AUM and apeMatrix are rock solid in comparison).

    Beat it up and report the crashes, please!

  • @Korakios said:

    You got the freaking monitoring working , so pretend to be happy :tongue:

    I'll try to do my very best but it ain't easy when old things creep back to the surface :)

  • @Liquidmantis said:
    Can’t say I’m off to an encouraging start.
    Crashed immediately after launching.
    Crashed opening the store.
    I tried downloading a pack that still didn’t show as downloaded. The importing files step took several minutes. Then the pack still didn’t show as installed so I refreshed the store and then it only showed about 10 packs. I refreshed again and it crashed.

    On multiple iPads now I’ve never been able to get all the content installed and the bug with packs state text being randomly green or grey continues.

    This was my 2018 iPad Pro 12.9 on 13.1.2.

    This sequence of events would make an excellent screen share video for the developer as you are covering a lot of ground here.

  • edited October 2019

    @hansjbs said:

    @RajahP said:
    Maybe it’s me.. but can’t seem to get Rosetta’s Scaler MdiFX to work?

    Midi fx are still not working in BM3. It's one of the more complicated things to get working properly. On the to do list definitely high up.

    Ok.. Thought it was me...

    Edit.. then again.. BM3 has its own built in scaler... that I forgot... off to the lab..

Sign In or Register to comment.