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.

ButterSynth Is Released!

11617181921

Comments

  • edited July 30

    @satchnut said:
    Update for those still left wondering...

    BS re-released a few days ago at $6 sale, no app update, unfortunately.
    On Discord Aarto posted about re-release and something about removing a BS patch, again unfortunately no comment on anything related to present bugs.

    On a personal note, even at $6 probably going to pass this one up, if nothing else because I don't think Aarto is doing enough living up to people's reasonable expectations to deserve my business (yet).

    I bought this synth and then requested a refund long ago because it was not functional for me.

    I think the problem with this synth might be that it is far too ambitious. If the developer comes back and makes something simple and easier for him to maintain (and keep stable), then I might even be convinced to buy. I buy other plugins from small developers because they have a history of correcting mistakes and being there when problems arise.

    The developer tried to make a massively complex synth to please everyone (honestly, I think he listened to too many people here asking for their specific functions, which multiplied its complexity) and ended up with a bigger problem.

    Keep it simple. Learn from this and move on. It is not possible to please everyone, so do something that works for you first. And place an internal limit on requests just so "the customers" don't drive you crazy.

  • @NeuM said:

    @satchnut said:
    Update for those still left wondering...

    BS re-released a few days ago at $6 sale, no app update, unfortunately.
    On Discord Aarto posted about re-release and something about removing a BS patch, again unfortunately no comment on anything related to present bugs.

    On a personal note, even at $6 probably going to pass this one up, if nothing else because I don't think Aarto is doing enough living up to people's reasonable expectations to deserve my business (yet).

    I bought this synth and then requested a refund long ago because it was not functional for me.

    I think the problem with this synth might be that it is far too ambitious. If the developer comes back and makes something simple and easier for him to maintain (and keep stable), then I might even be convinced to buy. I buy other plugins from small developers because they have a history of correcting mistakes and being there when problems arise.

    The developer tried to make a massively complex synth to please everyone (honestly, I think he listened to too many people here asking for their specific functions, which multiplied its complexity) and ended up with a bigger problem.

    Keep it simple. Learn from this and move on. It is not possible to please everyone, so do something that works for you first. And place an internal limit on requests just so "the customers" don't drive you crazy.

    So @satchnut you never paid for the app and @NeuM you got a refund? Got it.

    Did you at least make a note of the bugs so those of us who want to support this developer can help fix them? Please post them here if so.

  • edited July 30

    my personal recipe for stable experience on iOS is always resample all AU instruments into audio.. i always try to minimise amout of running AUv3 synths to zero.. AUv3 standard is just sooo wrongly designed (especialy in terms of memory management).. that way i don't have issues "synth XYZ crashes on me" .. i just create sound i need, record melody with some tweaks, i save preset just in case in future i need to record some additional stuff, resample it to audio and remove synth from project

    i learned this workflow while using hardware synths which is basically only viable wav how to used them - i just apply same method also on AUv3 instruments..

    this method has for me another advantage - it forces me to finish things more quickly - i try to record "final" version of given sequence because i know it will be not that easy later return to it and re-record it with changes..

    ironically, it often allows me to do things which would be not possible if i have realtime running synth - i can cut recorded wave, rearrange it, load into sampler and so with it things whixhnwould be not possible on realtime running synth..

    so it's win-win for me.. or actually win-win-win 🤣

  • @gusgranite said:

    @NeuM said:

    @satchnut said:
    Update for those still left wondering...

    BS re-released a few days ago at $6 sale, no app update, unfortunately.
    On Discord Aarto posted about re-release and something about removing a BS patch, again unfortunately no comment on anything related to present bugs.

    On a personal note, even at $6 probably going to pass this one up, if nothing else because I don't think Aarto is doing enough living up to people's reasonable expectations to deserve my business (yet).

    I bought this synth and then requested a refund long ago because it was not functional for me.

    I think the problem with this synth might be that it is far too ambitious. If the developer comes back and makes something simple and easier for him to maintain (and keep stable), then I might even be convinced to buy. I buy other plugins from small developers because they have a history of correcting mistakes and being there when problems arise.

    The developer tried to make a massively complex synth to please everyone (honestly, I think he listened to too many people here asking for their specific functions, which multiplied its complexity) and ended up with a bigger problem.

    Keep it simple. Learn from this and move on. It is not possible to please everyone, so do something that works for you first. And place an internal limit on requests just so "the customers" don't drive you crazy.

    So @satchnut you never paid for the app and @NeuM you got a refund? Got it.

    Did you at least make a note of the bugs so those of us who want to support this developer can help fix them? Please post them here if so.

    I totally understand if you don’t have the time or inclination to have to work through issues with a dev.

    For those that do, please speak to @Kirnu on the Discord. @NeuM is right about BS being extremely ambitious, so some bugs take an a while to get to the bottom of.

    From my experience, @Kirnu has been extremely responsive to bug reports and solved every single issue I’ve had, to the point that I can use BS multiple times in every project without issue in Loopy Pro and Logic Pro.

  • @gregsmith said:

    @gusgranite said:

    @NeuM said:

    @satchnut said:
    Update for those still left wondering...

    BS re-released a few days ago at $6 sale, no app update, unfortunately.
    On Discord Aarto posted about re-release and something about removing a BS patch, again unfortunately no comment on anything related to present bugs.

    On a personal note, even at $6 probably going to pass this one up, if nothing else because I don't think Aarto is doing enough living up to people's reasonable expectations to deserve my business (yet).

    I bought this synth and then requested a refund long ago because it was not functional for me.

    I think the problem with this synth might be that it is far too ambitious. If the developer comes back and makes something simple and easier for him to maintain (and keep stable), then I might even be convinced to buy. I buy other plugins from small developers because they have a history of correcting mistakes and being there when problems arise.

    The developer tried to make a massively complex synth to please everyone (honestly, I think he listened to too many people here asking for their specific functions, which multiplied its complexity) and ended up with a bigger problem.

    Keep it simple. Learn from this and move on. It is not possible to please everyone, so do something that works for you first. And place an internal limit on requests just so "the customers" don't drive you crazy.

    So @satchnut you never paid for the app and @NeuM you got a refund? Got it.

    Did you at least make a note of the bugs so those of us who want to support this developer can help fix them? Please post them here if so.

    I totally understand if you don’t have the time or inclination to have to work through issues with a dev.

    For those that do, please speak to @Kirnu on the Discord. @NeuM is right about BS being extremely ambitious, so some bugs take an a while to get to the bottom of.

    From my experience, @Kirnu has been extremely responsive to bug reports and solved every single issue I’ve had, to the point that I can use BS multiple times in every project without issue in Loopy Pro and Logic Pro.

    Yes, my comments were certainly not meant as a slight against the developer or anyone who uses and likes the app. I posted my own particular experience (which may or may not reflect the experiences of others), which I also posted at the time I originally tried it out.

  • edited July 30

    @Pictor said:

    @satchnut said:
    On a personal note, even at $6 probably going to pass this one up, if nothing else because I don't think Aarto is doing enough living up to people's reasonable expectations to deserve my business (yet).

    I’ve got it with the deal and I’m surprised how it runs stably (Auv3 in AudioBus or BAM). I’m on ipad Air 3 (ios 15).
    It’s quite a powerful app.
    Used it for 2 days with no issues or crashes for now.

    Only an issue with notes (or pitch) changing randomly sometimes, on one patch in BAM; I need to figure out if it’s a bug in the host tho. [BAM issue: reported to devs]

    However the developer explained on social media that the removal happened because he was in vacation and didn’t check emails.
    Although, yes, I understand the expectation for bugfixes (especially if crashing), especially on a young product.

    If it can help, try to keep memory consumption low; often the reason for crashes is RAM usage.

    I’m on an air 3 as well. I use BAM and AUM. Did you change some settings? If so, which ones?

    Would love to use it but on the default settings it’s unusable on my air 3.

    What “social media” are they on? I follow a lot of apps and I’ve never seen one taken off the store for a developer not checking their emails. This person is confounding.

    To make such a well thought out product and then to be so aloof is quite something. The only iOS developer I’ve encountered like this. I’ve had an iPhone since 3GS. So not for lack of experience.

    And before anyone try and claim that I’m “mauling” him, I’m not. It’s standard to hold a person accountable for a product that is indie made and complex as this one is. They really need a person to help with customer service and to be more accountable to their customers.

    I mentioned in another thread they should put a warning about the apps high memory usage at the top of the App Store description. Will they see that? Probably not. But small things like that would help this apps success In my opinion.

  • @offbrands : it is not that all that uncommon for developers to miss the annual renewal deadline or not know that there was a payment issue. If one was on vacation and not checking email, one might not know that the App Store had suspended the account.

  • @espiegel123 said:
    @offbrands : it is not that all that uncommon for developers to miss the annual renewal deadline or not know that there was a payment issue. If one was on vacation and not checking email, one might not know that the App Store had suspended the account.

    If app development is a person's business, they tend to keep track of payments due and pay attention to deadlines.

  • @NeuM said:

    @espiegel123 said:
    @offbrands : it is not that all that uncommon for developers to miss the annual renewal deadline or not know that there was a payment issue. If one was on vacation and not checking email, one might not know that the App Store had suspended the account.

    If app development is a person's business, they tend to keep track of payments due and pay attention to deadlines.

    How very understanding of you.

  • @gusgranite said:

    @NeuM said:

    @espiegel123 said:
    @offbrands : it is not that all that uncommon for developers to miss the annual renewal deadline or not know that there was a payment issue. If one was on vacation and not checking email, one might not know that the App Store had suspended the account.

    If app development is a person's business, they tend to keep track of payments due and pay attention to deadlines.

    How very understanding of you.

    Why do you continue to pester and harass me? Stop it.

  • Guys.... I'm a developer..... and I know it's a messy job. And is hard to be a single-developer company. Can't expect them to provide the same support as big companies.
    It's not nice to read this user entitlement.

    The high standards we have nowadays is because of big companies. (or stuff like Amazon... exploiting the world and the humans, so that they can always guarantee returns and provide customers with low-quality products and make the users deceived but happy).
    Small developers do what they can; they aren't necessarily "a business". They aren't necessarily experienced on the business side but just be good at tech stuff and wanted to make a product. They didn't necessarily know beforehand that they'd become a business and everybody will demand them the high standards that iOS users are used to. They might have simply wanted to share something with the community; and get a bit of compensation (never enough) for that.
    I read a lot of entitlement, without understanding how damn hard and time consuming is to program even the smallest feature.... or, worse, debug memory issues and system-level crashes. No success is guaranteed; and most times the time ROI is negative.

    Sure, he could pay a bit more attention to the product..... but do you know if this person has another main IT job, that maybe is making them burnout or not leave time to care of the pet product.
    I don't read my emails everyday, and I don't have to remember I'm a programmer, when I'm in vacation.

    Sure a memory-consumption note in the description would certainly help and prevent some issues. But again... we are assuming that this person is posing themselves as "business". Probably they are not.

    We are lucky we have people that put a lot of effort, because of passion for practically no economical reward (coding is damn expensive), to make us have amazing apps.

    I understand the grief for a half-baked product, I have the same for Synthmaster2..... but saying that it doesn't deserve even 6 bucks is a bit beyond the limits. Especially if a refund is guaranteed by Apple.
    Market rules still apply; the customer also has the responsibility to choose what to buy, what to not buy, or what to not buy next time.

    [/half-rant MODE OFF]

  • @NeuM said:

    @gusgranite said:

    @NeuM said:

    @espiegel123 said:
    @offbrands : it is not that all that uncommon for developers to miss the annual renewal deadline or not know that there was a payment issue. If one was on vacation and not checking email, one might not know that the App Store had suspended the account.

    If app development is a person's business, they tend to keep track of payments due and pay attention to deadlines.

    How very understanding of you.

    Why do you continue to pester and harass me? Stop it.

    I’m replying to your public post. I disagree with what you have stated like it’s a fact, and find it judgemental and anti-developer.

    I also find your repeated posting of why the app wasn’t up your high standards and that you got a refund distasteful to the point that it comes across like you have it in for this hardworking and creative developer.

  • edited July 30

    @offbrands said:
    I’m on an air 3 as well. I use BAM and AUM. Did you change some settings? If so, which ones?

    Not really; I simply avoid updates as hell, so I'm still on iOS 15. That might be the difference. Also I have a loooot of free storage space (iirc mobile devices they take ram from the storage space).

    Also BAM and AUM aren't configured anyhow. BAM is actually the beta version from TestFlight.

    I've heard of issues with Air 3, some devices have hardware bugs. But in this case I suppose the issue is more related to software problems.
    Do you have iOS 15 or higher? Apple often breaks things and never fixes them for years (just to compare with how the big companies behave over customer support).
    Also one of those Apple PRAM resets combination might help.

    Would love to use it but on the default settings it’s unusable on my air 3.

    Sorry I can't be much of help here.
    Also I'm not sure exactly what is the problem you are having; so I guess a bug report would be more useful.

    What “social media” are they on? I follow a lot of apps and I’ve never seen one taken off the store for a developer not checking their emails. This person is confounding.

    iirc I read about it on a Facebook group, but I think they wrote the answer on Twitter Discord.

  • @gusgranite said:

    @NeuM said:

    @gusgranite said:

    @NeuM said:

    @espiegel123 said:
    @offbrands : it is not that all that uncommon for developers to miss the annual renewal deadline or not know that there was a payment issue. If one was on vacation and not checking email, one might not know that the App Store had suspended the account.

    If app development is a person's business, they tend to keep track of payments due and pay attention to deadlines.

    How very understanding of you.

    Why do you continue to pester and harass me? Stop it.

    I’m replying to your public post. I disagree with what you have stated like it’s a fact, and find it judgemental and anti-developer.

    I also find your repeated posting of why the app wasn’t up your high standards and that you got a refund distasteful to the point that it comes across like you have it in for this hardworking and creative developer.

    Stop replying to me.

  • @NeuM maybe you stop replying to him, if you don't want an answer?
    Who do you think you are, to order users what to do? He just stated opinions and argued it, like you did.
    We are trying to not steer on toxic discussions but rather have a balanced conversation.

    It's iOS apps we are talking about, not food or survival.

  • @Pictor said:
    Guys.... I'm a developer..... and I know it's a messy job. And is hard to be a single-developer company. Can't expect them to provide the same support as big companies.
    It's not nice to read this user entitlement.

    The high standards we have nowadays is because of big companies. (or stuff like Amazon... exploiting the world and the humans, so that they can always guarantee returns and provide customers with low-quality products and make the users deceived but happy).
    Small developers do what they can; they aren't necessarily "a business". They aren't necessarily experienced on the business side but just be good at tech stuff and wanted to make a product. They didn't necessarily know beforehand that they'd become a business and everybody will demand them the high standards that iOS users are used to. They might have simply wanted to share something with the community; and get a bit of compensation (never enough) for that.
    I read a lot of entitlement, without understanding how damn hard and time consuming is to program even the smallest feature.... or, worse, debug memory issues and system-level crashes. No success is guaranteed; and most times the time ROI is negative.

    Sure, he could pay a bit more attention to the product..... but do you know if this person has another main IT job, that maybe is making them burnout or not leave time to care of the pet product.
    I don't read my emails everyday, and I don't have to remember I'm a programmer, when I'm in vacation.

    Sure a memory-consumption note in the description would certainly help and prevent some issues. But again... we are assuming that this person is posing themselves as "business". Probably they are not.

    We are lucky we have people that put a lot of effort, because of passion for practically no economical reward (coding is damn expensive), to make us have amazing apps.

    I understand the grief for a half-baked product, I have the same for Synthmaster2..... but saying that it doesn't deserve even 6 bucks is a bit beyond the limits. Especially if a refund is guaranteed by Apple.
    Market rules still apply; the customer also has the responsibility to choose what to buy, what to not buy, or what to not buy next time.

    [/half-rant MODE OFF]

    @Pictor 💯

    👍

  • @Pictor said:
    @NeuM maybe you stop replying to him, if you don't want an answer?
    Who do you think you are, to order users what to do? He just stated opinions and argued it, like you did.
    We are trying to not steer on toxic discussions but rather have a balanced conversation.

    It's iOS apps we are talking about, not food or survival.

    Feel free to comment, but this doesn’t involve you.

  • @NeuM said:

    @gregsmith said:

    @gusgranite said:

    @NeuM said:

    @satchnut said:
    Update for those still left wondering...

    BS re-released a few days ago at $6 sale, no app update, unfortunately.
    On Discord Aarto posted about re-release and something about removing a BS patch, again unfortunately no comment on anything related to present bugs.

    On a personal note, even at $6 probably going to pass this one up, if nothing else because I don't think Aarto is doing enough living up to people's reasonable expectations to deserve my business (yet).

    I bought this synth and then requested a refund long ago because it was not functional for me.

    I think the problem with this synth might be that it is far too ambitious. If the developer comes back and makes something simple and easier for him to maintain (and keep stable), then I might even be convinced to buy. I buy other plugins from small developers because they have a history of correcting mistakes and being there when problems arise.

    The developer tried to make a massively complex synth to please everyone (honestly, I think he listened to too many people here asking for their specific functions, which multiplied its complexity) and ended up with a bigger problem.

    Keep it simple. Learn from this and move on. It is not possible to please everyone, so do something that works for you first. And place an internal limit on requests just so "the customers" don't drive you crazy.

    So @satchnut you never paid for the app and @NeuM you got a refund? Got it.

    Did you at least make a note of the bugs so those of us who want to support this developer can help fix them? Please post them here if so.

    I totally understand if you don’t have the time or inclination to have to work through issues with a dev.

    For those that do, please speak to @Kirnu on the Discord. @NeuM is right about BS being extremely ambitious, so some bugs take an a while to get to the bottom of.

    From my experience, @Kirnu has been extremely responsive to bug reports and solved every single issue I’ve had, to the point that I can use BS multiple times in every project without issue in Loopy Pro and Logic Pro.

    Yes, my comments were certainly not meant as a slight against the developer or anyone who uses and likes the app. I posted my own particular experience (which may or may not reflect the experiences of others), which I also posted at the time I originally tried it out.

    And you should be allowed to do so without being attacked

    This place has become way too toxic.

  • @NeuM said:
    Feel free to comment, but this doesn’t involve you.

    It does, as long as it's in a public forum.

    @espiegel123 said:
    it is not that all that uncommon for developers to miss the annual renewal deadline or not know that there was a payment issue. If one was on vacation and not checking email, one might not know that the App Store had suspended the account.

    Indeed; slavery was luckily abolished :)
    Probably the issue is with Apple not providing enough time span after the email notification.

  • edited July 30

    @Fear2Stop said:

    @NeuM said:

    @gregsmith said:

    @gusgranite said:

    @NeuM said:

    @satchnut said:
    Update for those still left wondering...

    BS re-released a few days ago at $6 sale, no app update, unfortunately.
    On Discord Aarto posted about re-release and something about removing a BS patch, again unfortunately no comment on anything related to present bugs.

    On a personal note, even at $6 probably going to pass this one up, if nothing else because I don't think Aarto is doing enough living up to people's reasonable expectations to deserve my business (yet).

    I bought this synth and then requested a refund long ago because it was not functional for me.

    I think the problem with this synth might be that it is far too ambitious. If the developer comes back and makes something simple and easier for him to maintain (and keep stable), then I might even be convinced to buy. I buy other plugins from small developers because they have a history of correcting mistakes and being there when problems arise.

    The developer tried to make a massively complex synth to please everyone (honestly, I think he listened to too many people here asking for their specific functions, which multiplied its complexity) and ended up with a bigger problem.

    Keep it simple. Learn from this and move on. It is not possible to please everyone, so do something that works for you first. And place an internal limit on requests just so "the customers" don't drive you crazy.

    So @satchnut you never paid for the app and @NeuM you got a refund? Got it.

    Did you at least make a note of the bugs so those of us who want to support this developer can help fix them? Please post them here if so.

    I totally understand if you don’t have the time or inclination to have to work through issues with a dev.

    For those that do, please speak to @Kirnu on the Discord. @NeuM is right about BS being extremely ambitious, so some bugs take an a while to get to the bottom of.

    From my experience, @Kirnu has been extremely responsive to bug reports and solved every single issue I’ve had, to the point that I can use BS multiple times in every project without issue in Loopy Pro and Logic Pro.

    Yes, my comments were certainly not meant as a slight against the developer or anyone who uses and likes the app. I posted my own particular experience (which may or may not reflect the experiences of others), which I also posted at the time I originally tried it out.

    And you should be allowed to do so without being attacked

    This place has become way too toxic.

    Comments posted in good faith, even if they are critical, are completely fair game. Personal attacks are unnecessary and unproductive and contribute to general unpleasantness. I would rather people better recognize and understand this difference. A critical comment about a thing is not a critical comment about a person.

    And determining "tone of voice" is difficult when reading another person's comments. I will be the first to admit I've managed to misunderstand the intent of posters on occasion here and I'm sure the same can be said for others.

  • OK, out of respect to @Kirnu lets get this focused back on Buttersynth and my apologies to the developer for any tangent.

    Buttersynth is an amazing app and I would say to everyone considering it that $6 is amazing value for such a great sounding and fully featured synth. This is a real labour of love and if you want to help out, please jump onto the Discord server and report any bugs you find with how to reproduce them if possible.

    @offbrands the Kirnu Discord server is https://discord.gg/WJnQvF39

    @Fear2Stop I disagree with your assessment but appreciate your intention.

  • @dendy said:
    my personal recipe for stable experience on iOS is always resample all AU instruments into audio.. i always try to minimise amout of running AUv3 synths to zero.. AUv3 standard is just sooo wrongly designed (especialy in terms of memory management).. that way i don't have issues "synth XYZ crashes on me" .. i just create sound i need, record melody with some tweaks, i save preset just in case in future i need to record some additional stuff, resample it to audio and remove synth from project

    i learned this workflow while using hardware synths which is basically only viable wav how to used them - i just apply same method also on AUv3 instruments..

    this method has for me another advantage - it forces me to finish things more quickly - i try to record "final" version of given sequence because i know it will be not that easy later return to it and re-record it with changes..

    ironically, it often allows me to do things which would be not possible if i have realtime running synth - i can cut recorded wave, rearrange it, load into sampler and so with it things whixhnwould be not possible on realtime running synth..

    so it's win-win for me.. or actually win-win-win 🤣

    Solid advice. As the saying goes, you don’t know what you don’t know, and I hadn’t thought of this at all. So thank you @dendy

    I didn’t mean to be a part of any negativity. I very much enjoy this forum, I disagree that it’s gotten “too toxic” but I can empathize with anyone having issues with a product and wanting some accountability and so on.

    Big ups to anyone speaking on behalf of the dev to try and iron things out with us. I hope they know that you are doing the extra work that typically would be required of themselves.

    I don’t know if I will get on discord or not, I don’t love that platform for a plethora of reasons, but thank you for sharing a direct line @gusgranite - I’ll have to think on it.

    I also agree with your assessment it is a labor of love and that’s evident and the more help the better I’m sure.

    At minimum I hope you can pass that along to dev that they really should add a memory management warning in the App Store description. So people can be aware of the potential crashes and such. I would have been far less surprised and put off had there been. I think imaginado’s and their app FRMS has such a warning on the App Store.

    I also want to be fair to everyone, there are so many different configurations of iOS and what people are running, I’m sure it does run perfect for some but as someone who hasn’t had that experience and is well versed in iOS apps I wouldn’t want to discount those experiences and that the expectations haven’t been set in the best way.

    There’s some verbiage that can be added to set expectations for the customers. Including the contact the dev on discord, etc. Page 7 of the manual should be front and center In my opinion.

  • Can anyone who is getting a crash try limiting polyphony in the settings and reducing the number of oscillators in the patch and see if it helps? In my testing, one of the issues is that enabling all 5 oscillators at the standard 8 note polyphony plus oversampling will bring even the latest iPad Pro to its DSP ceiling. It plays complex multi oscillator patches nicely on my iPad Pro once I reduce polyphony down to 5 (which is all I usually need).

  • @gusgranite said:
    Can anyone who is getting a crash try limiting polyphony in the settings and reducing the number of oscillators in the patch and see if it helps? In my testing, one of the issues is that enabling all 5 oscillators at the standard 8 note polyphony plus oversampling will bring even the latest iPad Pro to its DSP ceiling. It plays complex multi oscillator patches nicely on my iPad Pro once I reduce polyphony down to 5 (which is all I usually need).

    Just so I’m clear with the settings

    • Settings -> Scroll down to “Misc” section
    • Select “Polyphony Limit” -> Max Number of Notes
    • Reduce to 5
  • @offbrands said:

    @gusgranite said:
    Can anyone who is getting a crash try limiting polyphony in the settings and reducing the number of oscillators in the patch and see if it helps? In my testing, one of the issues is that enabling all 5 oscillators at the standard 8 note polyphony plus oversampling will bring even the latest iPad Pro to its DSP ceiling. It plays complex multi oscillator patches nicely on my iPad Pro once I reduce polyphony down to 5 (which is all I usually need).

    Just so I’m clear with the settings

    • Settings -> Scroll down to “Misc” section
    • Select “Polyphony Limit” -> Max Number of Notes
    • Reduce to 5

    Hi @offbrands - yes, try playing with that limit and see if it helps?

  • @gusgranite said:

    @offbrands said:

    @gusgranite said:
    Can anyone who is getting a crash try limiting polyphony in the settings and reducing the number of oscillators in the patch and see if it helps? In my testing, one of the issues is that enabling all 5 oscillators at the standard 8 note polyphony plus oversampling will bring even the latest iPad Pro to its DSP ceiling. It plays complex multi oscillator patches nicely on my iPad Pro once I reduce polyphony down to 5 (which is all I usually need).

    Just so I’m clear with the settings

    • Settings -> Scroll down to “Misc” section
    • Select “Polyphony Limit” -> Max Number of Notes
    • Reduce to 5

    Hi @offbrands - yes, try playing with that limit and see if it helps?

    Will do. Unfortunately I’ve just got around to listening to Fred again.. for the first time and oh man. He’s brilliant

    Now I’m having an existential crisis of why even make music. I’ll snap out of it soon and report back after some through usage.

  • I use BS in almost all my projects in Cubasis 3 on both iPad Air 4 and 13” iPad Air M2, it has to be one of my favourite synths and so easy to program. I did have crashing problems when it first came out, followed by Midi Mappings completely disappearing, but after the v1.03 update everything has been fine, I had an issue where manually operating the WT Pos would accidentally cause the preset selector to be touched and the preset would unfortunately change right in the middle of editing! I did report it to Arto and he promptly replied saying he would try and sort it, it’s been a few months now but I can wait, also as long as I don’t operate the on screen Mod wheel everything is fine (BS CPU maxes out!).

  • I've known about Kirnu a long time, been doing this a very long time, and I personally know the struggle that is being an app developer, so I hope I'm not coming from a place of entitlement or naïveté... and I do wish for Aarto's success in the iOS audio app market (if that's what he wants).

    At this point a $6 supersale might seem to a lesser man as a sign of abandonment or despondence, and I certainly hope that's not the case. I think I'm not the only one just curious as to where Aarto's feelings and intentions are at this time.

    I'm sorry to see this topic has gone down such a weird path, so I'll just leave it there.

  • I’d like to think the $6 sale might be his way to atone for the recent absence.

  • Yes i also see it as an apology rather than abandonment.

    All in all it has been quite stable; got a bunch of crashes (either as AUv3 and standalone) in cases where RAM wasn’t enough, or when I set 3-4 instances at the same time.
    I reduced the max polyphony number, but all the crashes were already on patches with only 1 voices per OSC.
    It’s pretty usable most times, I wouldn’t judge it as brittle based on couple resource-related crashes.

    However when i try the “Re-sample synth to 16 waves” the app crashes systematically. So, yeah, some bug there but in general functionality is quite stable.
    It just sucks a shit load of battery and RAM 😁

    @offbrands said:
    Will do. Unfortunately I’ve just got around to listening to Fred again.. for the first time and oh man. He’s brilliant

    Now I’m having an existential crisis of why even make music. I’ll snap out of it soon and report back after some through usage.

    Who the Fred is fuck? (cit.)

Sign In or Register to comment.