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.

Such a shame Beatmaker 3 is likely a very dead app soon…

16791112

Comments

  • I returned when id bought for £8.

    Wish I kept for the sampler.

    You can blame me I guess.

  • £8 for a sampler, which can just route via audio4c.

  • edited June 2023

    @MrSmileZ said:
    I know that since one member of the team left…it has not moved forward since(fact).

    Not true at all. There were fixes/features I wanted since day one that happen well after Matt left.

  • edited June 2023

    @MrSmileZ said:
    Sorry I blemished your golden cow.
    Moo moo buckaroos

    lol you really cannot blame me being BM3 fanboy :lol: :lol: :lol: That is most funny indirect accusation i ever experienced in my life on this forum 🤣🤣

  • @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

  • edited June 2023

    @MrSmileZ : a few things.

    You seem really intent on trying to convince people that BM3is useless…and won’t acknowledge that it has some core functionality that it provides that no other app does. Functionality that many find valuable and useful.

    Maybe that functionality isn’t important to you. That’s fine. Everyone has different features that are important yo them.

    Maybe it doesn’t work well for what you want out of it. That’s different from being dead or useless for everyone.

    In the time since Mathieu (EDIT I mistakenly said Vincent originally ) left there haven’t been new features but there were major stability improvements. I haven’t had a crash in years with my BM3 usage. I don’t use it as a DAW. Maybe it has problems as a DAW. I can’t say.

    I am curious . Which AUs wasn’t it working well with when you tried it?

  • @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    I think the size of the market is typically the limiting factor and not the pricing model. Korg, Steinberg, Apple etc aparently make their big apps out of their marketing budgets with the intention of those apps bringing people into their ecosystem and upselling them etc. A big app for big apps sake is a pretty risky strategy, particularly in this relatively small niche of music making.

  • edited June 2023

    @espiegel123 said:

    In the time since Vincent left there haven’t been new features but there were major stability improvements. I haven’t had a crash in years with my BM3 usage. I don’t use it as a DAW. Maybe it has problems as a DAW. I can’t say.

    Wait, what? Vincent left? I thought people were referring to when Matt left. huh.

  • @dendy said:

    @MrSmileZ said:
    Sorry I blemished your golden cow.
    Moo moo buckaroos

    lol you really cannot blame me being BM3 fanboy :lol: :lol: :lol: That is most funny indirect accusation i ever experienced in my life on this forum 🤣🤣

    I only joust you in jest, laughing out loud
    You are actually helpful…your loyalty to a few brands is undying…
    Can I use “undying”?
    Does this satisfy the council of app idolatry? Lol

  • @AudioGus said:

    @MrSmileZ said:
    I know that since one member of the team left…it has not moved forward since(fact).

    Not true at all. There were fixes/features I wanted since day one that happen well after Matt left.

    BUT
    Were those part of the kick butt update that was recalled? Hmmmm

  • @AudioGus said:

    @espiegel123 said:

    In the time since Vincent left there haven’t been new features but there were major stability improvements. I haven’t had a crash in years with my BM3 usage. I don’t use it as a DAW. Maybe it has problems as a DAW. I can’t say.

    Wait, what? Vincent left? I thought people were referring to when Matt left. huh.

    Oops. Mistake. I meant Mathieu. I’ll correct

  • @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    Beatmaker 3 could stilllllll be a great and stable app…it’s feature rich! It’s just not stable…and believe me I have producer ptsd from it.

    Make beatmaker 4, add what you want…but mostly just get it super stable…and I will buy it again for a good amount of $$$
    Or make a cheap subscription…do something…do anything sheesh.

  • @espiegel123 said:
    @MrSmileZ : a few things.

    You seem really intent on trying to convince people that BM3is useless…and won’t acknowledge that it has some core functionality that it provides that no other app does. Functionality that many find valuable and useful.

    Maybe that functionality isn’t important to you. That’s fine. Everyone has different features that are important yo them.

    Maybe it doesn’t work well for what you want out of it. That’s different from being dead or useless for everyone.

    In the time since Mathieu (EDIT I mistakenly said Vincent originally ) left there haven’t been new features but there were major stability improvements. I haven’t had a crash in years with my BM3 usage. I don’t use it as a DAW. Maybe it has problems as a DAW. I can’t say.

    I am curious . Which AUs wasn’t it working well with when you tried it?

    Many…but I am in IPAD OS 16.5… and that seems to have broken more of them.
    Next time I have a couple of hours to blow and I’m bored I will write down the crashy plugs and list them here.

  • edited June 2023

    @AudioGus said:

    @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    I think the size of the market is typically the limiting factor and not the pricing model. Korg, Steinberg, Apple etc aparently make their big apps out of their marketing budgets with the intention of those apps bringing people into their ecosystem and upselling them etc. A big app for big apps sake is a pretty risky strategy, particularly in this relatively small niche of music making.

    How would you feel about bm3 just being the sampler….without the synth hosting, without the auv3 effects, and without the sequencer….just the sampler and its pitch shifting and layers etc, you know…remove the Daw from it? keep all the sampler goodies though.
    Make it Auv3

    I’d buy that right now, and I’d pay a fair price…I’m not talking 9.99 I’m talking move it up…
    I personally think that is the way to go. Call it Beatmaker 4, leave 3 for those who like it as it is.

    If this sampler was in Logic or Cubasis wow!

    But, Koala is slowly approaching this…and STABLE

  • @MrSmileZ said:

    @AudioGus said:

    @MrSmileZ said:
    I know that since one member of the team left…it has not moved forward since(fact).

    Not true at all. There were fixes/features I wanted since day one that happen well after Matt left.

    BUT
    Were those part of the kick butt update that was recalled? Hmmmm

    Ahh yes the mythical 3.14 update. I recall hearing about the details and being disappointed that my meager wants were unadressed.

  • edited June 2023

    @MrSmileZ said:
    How would you feel about bm3 just being the sampler….without the synth hosting, without the auv3 effects, and without the sequencer….just the sampler and its pitch shifting and layers etc, you know…remove the Daw from it?
    Make it Auv3

    It wouldn't do too much for me as I like the routing/internal sampling of BM3 and being able to assign AUs to pads etc. Having keyboard mode nested into pads is super useful to me and that would be lost in any other host. I actually just skim the surface of the sampler really and it is that grey middle ground of what is sampler and what is host that is great for me with BM3. Being able to quickly record any bit from anywhere is huge and in another host it would be clunky, having to assign a BM3 FX AUv3 on a track to route to a BM3 AUv3 sampler etc. The fluidity I find would be gone. But sure I would find whole other uses for it in something like NS2. You would probably have to select pad or keyboard mode per instance of it though. But yah just being able to easily select large ranges of wavs and copy to pads... but then no sequence-able pitch per pad...

    But as for BM3, I used it for three hours yesterday on my M1 and it was fine, no crashes. Occasionally (one in five times?) I would try to load a project and an AU would fail to load but on the second try it would load just fine.

  • I think all my crashes are centered around auv3 usage?
    And they are what I call fatal crashes…as the whole app just goes poof.
    Now when I tried last time…it wasn’t fatal crashes but rather sound engine crashes.

    Like when you put an audio damage plug in into garageband on iOS. Sound just goes away and I have to kill the app and reboot it.

  • @MrSmileZ said:
    I think all my crashes are centered around auv3 usage?
    And they are what I call fatal crashes…as the whole app just goes poof.
    Now when I tried last time…it wasn’t fatal crashes but rather sound engine crashes.

    Like when you put an audio damage plug in into garageband on iOS. Sound just goes away and I have to kill the app and reboot it.

    I had a lot of that on my 2017 Pro and base model.

  • edited June 2023

    Okay after reading this…

    @AudioGus said:

    @MrSmileZ said:
    Beatmaker in 16.5 isn’t loading as many plug ins properly…so it is in desperate need of a fix update.
    I spent the whole of last night on my new iPad trying to give it a go….and I could only give it a hell no

    Used it for a couple hours this morning and had some plugins not load right the first time but on the second try they loaded.

    I just went through a bunch of patches/synths/effects
    It’s weird but it worked better second time around? That’s so strange…why would it behave like that?
    I got no hard crashes, but I just randomly picked a couple patches on each synth/effect
    I used a sequence with a lead line/chord line for the polys
    I did have a few guis that didn’t immediately come up, but after going back they did.

    IAA in BM3 is not doing well after 16.5, so if you depend on that… maybe don’t go to 16.5?
    I am assuming Apple is ghosting it…like they do ports?

    So Beatmaker 3, iaa, 16.5 …not a good look. Not on my m2 anyways.

  • edited June 2023

    @MrSmileZ said:

    @dendy said:

    @MrSmileZ said:
    Sorry I blemished your golden cow.
    Moo moo buckaroos

    lol you really cannot blame me being BM3 fanboy :lol: :lol: :lol: That is most funny indirect accusation i ever experienced in my life on this forum 🤣🤣

    I only joust you in jest, laughing out loud
    You are actually helpful…your loyalty to a few brands is undying…
    Can I use “undying”?
    Does this satisfy the council of app idolatry? Lol

    undying is good :-) now when almost everybody is going to convert into Logic (at least those wo aren’t going to stay with AUM or Drambo), sometimes i really feel like last old undead zombie with NS 😂😂

  • TBH id buy BM3 again at $50 if i could get it on iphone, i rarely use ipad for music these days and am starting to become a phone only kinda guy for music production (i love hardware too but im poor)

  • @MrSmileZ said:
    Okay after reading this…

    @AudioGus said:

    @MrSmileZ said:
    Beatmaker in 16.5 isn’t loading as many plug ins properly…so it is in desperate need of a fix update.
    I spent the whole of last night on my new iPad trying to give it a go….and I could only give it a hell no

    Used it for a couple hours this morning and had some plugins not load right the first time but on the second try they loaded.

    I just went through a bunch of patches/synths/effects
    It’s weird but it worked better second time around? That’s so strange…why would it behave like that?
    I got no hard crashes, but I just randomly picked a couple patches on each synth/effect
    I used a sequence with a lead line/chord line for the polys
    I did have a few guis that didn’t immediately come up, but after going back they did.

    IAA in BM3 is not doing well after 16.5, so if you depend on that… maybe don’t go to 16.5?
    I am assuming Apple is ghosting it…like they do ports?

    So Beatmaker 3, iaa, 16.5 …not a good look. Not on my m2 anyways.

    For Patterning I had to run it outside of BM3 first and then I could add it which is pretty common in a lot of hosts these days.

  • edited June 2023

    Back in the beginning with bm3, there was going to be a phone release. Vapor.
    I believe that it was really difficult to arrange how it would look on the iPhone, as it is really quite busy on the iPad.
    But if it was properly designed on the iPhone…yea, no doubt…I could see wanting that!

    I have a fellow producer who uses his phone and still has Beatmaker 2 on it. Using it all the time. In fact he kept the old phone, just in case they removed it from the store. He is serious about it. I guarantee he would have megalust for bm3 on his new phone!

  • @MrSmileZ said:
    Okay after reading this…

    @AudioGus said:

    @MrSmileZ said:
    Beatmaker in 16.5 isn’t loading as many plug ins properly…so it is in desperate need of a fix update.
    I spent the whole of last night on my new iPad trying to give it a go….and I could only give it a hell no

    Used it for a couple hours this morning and had some plugins not load right the first time but on the second try they loaded.

    I just went through a bunch of patches/synths/effects
    It’s weird but it worked better second time around? That’s so strange…why would it behave like that?
    I got no hard crashes, but I just randomly picked a couple patches on each synth/effect
    I used a sequence with a lead line/chord line for the polys
    I did have a few guis that didn’t immediately come up, but after going back they did.

    IAA in BM3 is not doing well after 16.5, so if you depend on that… maybe don’t go to 16.5?
    I am assuming Apple is ghosting it…like they do ports?

    So Beatmaker 3, iaa, 16.5 …not a good look. Not on my m2 anyways.

    Since, it is well known that BeatMaker can be a bit temperamental with AUv3, I pretty much only use it as a sampler (in particular for things at other samplers don't do well like, like simultaneous pitch-shift and time-stretch and its flexible release/retrigger behaviors) and leave AUv3 hosting to other apps unless I've determined that the AUv3s are ones that work in BM3. Even for that limited use, I find BM3 worthwhile.

  • @AudioGus said:

    @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    I think the size of the market is typically the limiting factor and not the pricing model. Korg, Steinberg, Apple etc aparently make their big apps out of their marketing budgets with the intention of those apps bringing people into their ecosystem and upselling them etc. A big app for big apps sake is a pretty risky strategy, particularly in this relatively small niche of music making.

    Gazillion ways to get money nowadays
    Donation , Crowdfunding , but this requires Intua to engage with the users and users trust Intua (I don't)
    optional subscription , paid annual updates , which implies the app is working flawlessly and constantly developing features based on user feedback

  • edited June 2023

    @MrSmileZ said:
    I have a fellow producer who uses his phone and still has Beatmaker 2 on it. Using it all the time. In fact he kept the old phone, just in case they removed it from the store. He is serious about it. I guarantee he would have megalust for bm3 on his new phone!

    BM2 was great ! Actually it still is. BM2 really clicked with me a lot.

    edit: looks like audio recording is broken there, it’s just too old app :-)

  • @Korakios said:

    @AudioGus said:

    @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    I think the size of the market is typically the limiting factor and not the pricing model. Korg, Steinberg, Apple etc aparently make their big apps out of their marketing budgets with the intention of those apps bringing people into their ecosystem and upselling them etc. A big app for big apps sake is a pretty risky strategy, particularly in this relatively small niche of music making.

    Gazillion ways to get money nowadays
    Donation , Crowdfunding , but this requires Intua to engage with the users and users trust Intua (I don't)
    optional subscription , paid annual updates , which implies the app is working flawlessly and constantly developing features based on user feedback

    A zillion ways to appeal for funding does not mean that such appeals will generate the needed revenue.

  • If I good remember Bm3 dont support multioutput in auv3.
    sometimes its useful to get more than 1 stereo output from Drambo.

    Now for me BM3 is pure nostalgia and love, daily I use Logic.

  • @espiegel123 said:

    @Korakios said:

    @AudioGus said:

    @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    I think the size of the market is typically the limiting factor and not the pricing model. Korg, Steinberg, Apple etc aparently make their big apps out of their marketing budgets with the intention of those apps bringing people into their ecosystem and upselling them etc. A big app for big apps sake is a pretty risky strategy, particularly in this relatively small niche of music making.

    Gazillion ways to get money nowadays
    Donation , Crowdfunding , but this requires Intua to engage with the users and users trust Intua (I don't)
    optional subscription , paid annual updates , which implies the app is working flawlessly and constantly developing features based on user feedback

    A zillion ways to appeal for funding does not mean that such appeals will generate the needed revenue.

    Yah easy to say a gazillion ways to get money but people know better than to say there are a gazillion potential buyers.

  • @espiegel123 said:

    @Korakios said:

    @AudioGus said:

    @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    I think the size of the market is typically the limiting factor and not the pricing model. Korg, Steinberg, Apple etc aparently make their big apps out of their marketing budgets with the intention of those apps bringing people into their ecosystem and upselling them etc. A big app for big apps sake is a pretty risky strategy, particularly in this relatively small niche of music making.

    Gazillion ways to get money nowadays
    Donation , Crowdfunding , but this requires Intua to engage with the users and users trust Intua (I don't)
    optional subscription , paid annual updates , which implies the app is working flawlessly and constantly developing features based on user feedback

    A zillion ways to appeal for funding does not mean that such appeals will generate the needed revenue.

    @AudioGus said:

    @espiegel123 said:

    @Korakios said:

    @AudioGus said:

    @Korakios said:

    @AudioGus said:

    @Mr_Fox said:
    Honestly I don't think there will be much improvements coming to BM3 unless another company buys them out. Their entire line up probably makes less than 100 bucks a day (you can roughly estimate an app's revenue through its story ranking), and that's just not enough money to support the devs. The people who are experienced enough to make an amazing app like BM3 can easily find a job and make100-200k a year. Passion can only drive devs till a point eventually they would need to find ways to make a living.

    I assume most music app devs have day jobs.

    nope , the dev is not interested , he could discuss a fair pricing model if money was an issue

    I think the size of the market is typically the limiting factor and not the pricing model. Korg, Steinberg, Apple etc aparently make their big apps out of their marketing budgets with the intention of those apps bringing people into their ecosystem and upselling them etc. A big app for big apps sake is a pretty risky strategy, particularly in this relatively small niche of music making.

    Gazillion ways to get money nowadays
    Donation , Crowdfunding , but this requires Intua to engage with the users and users trust Intua (I don't)
    optional subscription , paid annual updates , which implies the app is working flawlessly and constantly developing features based on user feedback

    A zillion ways to appeal for funding does not mean that such appeals will generate the needed revenue.

    Yah easy to say a gazillion ways to get money but people know better than to say there are a gazillion potential buyers.

    ok, 1 way
    crowdfunding , no cost for the dev . If the $$$ amount is not enough then users get their money back

Sign In or Register to comment.