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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Some Bleass Alpha patches overload my Air2 (info obtained Thanks all)
![[Deleted User]](https://secure.gravatar.com/avatar/019589e50c568257a91aaad27bb47b18/?default=https%3A%2F%2Fvanillicon.com%2Fe904907fe2a35d99a300eeed7d16603f_200.png&rating=g&size=200)
The Bleass Alpha fully pumped up with 6 voice unison and many keys played, can totally destroy any project I’m running on my Air2. Would almost love to see a button that could lock this beast down to better drop notes rather than totally destroy the running of the project with crackles from Hell.
It got me thinking, any of you guys with powerful iPads - can you pump up an Alpha with no issues? Can you run two fully pumped Alphas on a Pro? Just wondering if the current Pro models (not the 1gb model with extra ram though, as I’m not going to afford that model.
If anyone can test for me, I would be interested to know. Just ramp the unison up with some high detune and play some BIG chords with long release levels - how’s those mighty Pro models hold up?
Title changed.
Comments
I have the second-newest Pro model, the 2017 10.5 inch. I can run one "pumped up" instance in AUM with no external effects, and CPU is around 40-50%. Two instances and I get crackles.
Another thread had Alpha at the low end of CPU usage. Quite low, IIRC. Haven’t looked into it myself, though I work out ideas on the phone during the commute to I’m paying more attention to things that drain the battery.
I might’ve missed it but what daw r u in?
@Fruitbat1919 : what buffer settings in your host?
Sorry should have said. AUM 256.
Sorry - AUM 256
Yep, without doubt it can be low on some sounds - pretty much as low as anything else I use really. Not slating it for what it’s doing, just wondering how much more a Pro model can cope when apps are really pumped up.
Thanks that’s helpful. That means with the most recent iPad Pro’s there is going to be at least a reasonable overhead when using this app pumped - at least plenty to get a clean recording
Hi guys,
Thanks for pointing out that the Alpha CPU performances can vary depending on many parameters.
For instance, if you use a low buffer or put a lot of unison on polyphonic presets.
For example, unison is not always available along with polyphony in many others synths apps, and there's a reason for that: it's very CPU hungry (because it generates lots and lots of new oscillators) !
Yet we had to make a choice : should we limit the Alpha Synth sonic possibilities to older iPads'computing ability, or should we let the users be able to push the synth to its most interesting sonic possibilities? We have chosen the latter. Yet, you can still use many instances of the Alpha Synth in a single DAW, but of course, the more oscillators and effects you use, the more CPU it will require, all the more if you use an older iPad.
Yet don't hesitate to test out other synthesizers in comparison to notice the difference!
Also, please note that we still put lots of effort into engineering a highly efficient yet versatile synth. A new update is coming fixing the motion sequencer crash, as well as new other features... stay tuned and feel free to check the thread about the Alpha Synth news here : https://forum.audiob.us/discussion/36920/bleass-alpha-synthesizer-by-bleass/
Hi,
I emailed the dev about this issue. It happens only when using inside an AU host, ie when you use BLEASS on its own it’s fine. Also, I have since tested on an iPad Pro3 and have replicated this issue.
To be clear, 1 instance of BLEASS, causes crackles when you play polyphonically (that does NOT happen when you use it in standalone mode). Here’s the original email I sent, showing how to replicate it for those interested:-
Using an iPhoneXS Max, iOS 12.3.1, iPhone speakers, testing Alpha slow pad (Bank A, 4th preset). Bug: audio crackling when playing many notes
Bleass Alpha works perfectly when used on its own, ie can play many notes & it sounds perfect. When used in the host AUM, playing many notes (eg, by sweeping left and right index fingers across the keys) causes audio glitches. It’s easier to hear if u edit the envelopes to have a faster attack. I think this may be a sample rate/48kHz issue (this is what AUM uses on newer iOS devices)
Thanks for reading, wishing you all the best
I’m glad you took the route to not limit the synth. While I’m still on an Air2 at this time, it’s only common sense that I will have to upgrade if I want to make the most out of modern tech as it’s designed.
Software always has traditionally pushed the hardware as its developed and I wouldn’t want that changed, as long as the apps are at least stable and usable on the current tech, which Alpha clearly is.
Nice to see you are getting the motion sequencer crash sorted and to be honest the only thing I would change is some more control over signal paths to and for the dual filters. I do also understand though that decisions are made in design and the complexity vs ease of use equation will always come up with some design that doesn’t make every synth - good job too, or we really would have a boring range of synths that were all the similar.
Good luck with future products
What settings have you got AUM on while using that preset? The preset in question, is it Alpha Slow Pad? Because that uses only two voice unison and I can run that on my Air2 in 256 AUM with no issues. Only at 128 do I get problems. If you are running at 256 or above, I would suggest it’s probably something else happening.
Try an iPad restart to clear any ghosties and make sure nothing else is switched on. Maybe even try the iPad without connection to anything else too. If it’s then still happening on that preset, then there may be other issues, as I would expect an iPad Pro to be able to run that preset with no issues at a decent 256 or maybe even lower.
@Fruitbat1919 : Have you tried a larger buffer?
Yep. I should have posted the buffer so that people posting results on an iPad Pro would do the same - just forgot. Have a good idea of the results now from some peeps with Pros.
I wasn’t posting this to moan about Alpha or other such apps, just wanted a comparison of how this sort of power use equates to a modern iPad, as I’m upgrading soon. Yes, I should have stipulated the buffer from the start, maybe even have chosen a preset to compare with, but jobs done now and I’ve got results in discussion with people that I needed to gauge with.
@Fruitbat1919 : if you use a larger buffer, things will probably work better.
My test was done with AUM, and I used the default 256 frame buffer. I just tried it with 512, and I can run two instances with long decays and 6 unison, with AUM's CPU going up to about 85%. But yeah, either way, it works.
Yep and gives me a good idea what an iPad upgrade will mean to my projects thanks
You're welcome.
Thanks for the reply 😺. I’m on buffer 256 for Aum btw
I restarted my phone after the bug, yet that didn’t fix it. I’ve restarted my iPad Pro3, & loaded BLEASS into Aum, tried playing with Aum’s keyboard & immediately the BLEASS icon went red, meaning it needed reloading - this is a new issue - after reloading, the audio crackling didn’t happen, but I only quickly tested it, & don’t have time to test thoroughly atm
Also, in case the dev’s reading, the method I use to reproduce this bug, ie sweeping fingers across the keys, is an easy way to make this happen, but I never play this way normally - For pad sounds at most I’m playing 4 keys at a time, usually 2 though to be honest especially on the phone, so even with long releases (which I usually lower too) I’m not using a lot of polyphony & I still get this intermittent audio bug
Thanks for reading, wishing you all the best
If the app goes red in AUM, and needs reloading, does that then produce a crash log? If anyone knows, this may help find where the issue stems from.
Just to add, as the dev tells us there is a new update coming out soon, it might be good to try that as soon as available.
@Fruitbat1919 : it might be nice if you edited the thread title--it gives a very negative impression of the app as if the app is misbehaved in a severe way that is not really the case.
Really? Not the impression I get from the title. What do you suggest?
@Fruitbat1919 : the thread title sounds like Bleass Alpha causes problems ("destroys my iPad"?)
Maybe, something like "some Bleass Alpha patches overload my Air2" gives a clearer impression. People often form impressions of apps from seeing complaining topics -- even if the core issue is a user misunderstanding or unrealistic expectations.
While I can’t see it myself, maybe it’s just a matter of how we differ in our understanding of the words within differing contexts. I however have changed it and hope this works for you. It wasn’t a ‘complaining topic’ though and presume you are just meaning that in a wider context. People will often see what they want from topics however worded, so it’s pretty difficult to please all people, especially on an international site where people’s understanding of the context of specific words can vary wildly
@Fruitbat1919 thanks for the info re: crash log - if it happens again I’ll send it. I’ll definitely be trying the new update when it comes out. Also, the dev emailed me back, & I sent a vid showing the bug, its worth saying again, that it doesn’t happen all the time, but it definitely happens.
Also re: Topic title I think it’s fine, I didn’t get any impression that Bleass break/harm my iOS device in any way, but it’s all subjective
Cheers guys! 👍😺🚀
That’s cool. Maybe we can all share some sounds we make eventually when we’ve all got to grips with this beast
Sure, why not? 😺 HST, these days I usually make crazy drone sounds, which aren’t for everyone 😉
Thanks for your benevolence guys, glad that we could sort out your answers. Thanks also for changing the thread title, indeed it could have been misinterpreted ^^
May you find something that looks like a bug feel free to reach the App support through bleass.com so that we can have more information!
new update coming soon!
thanks again!
We could discuss a whole other topic there regarding the title lol. I did change it because I wouldn’t want or intend to cause harm to your app, but at the same time, I find that pandering to those that simply follow a course of shouting ‘this offends’ at every avenue, is a lost cause. People need to take responsibility for their own feelings regarding what offends, as has been shown of late - it’s really really easy to offend and the law (as shown in a Scottish case at least), shows little care for intent.
Look at slang and how it eventually becomes officially recognised language in many ways. Words that once meant something, now mean something else entirely. So word policing on sites such as these is virtually impossible, as it’s virtually impossible not to offend at some time or other and guilt and apologies are often sought for purely selfish purposes.
So, while a few words at times may cause a little offence, inconvenience or misunderstandings, constantly pandering to those who crave the quick thrill of social justice, may help create more problems in itself. Maybe we all need to learn from this. Yes, words can have consequences, yet how we deal with our own feelings and how we find a middle ground for discourse regarding words, still needs much work.
In my opinion, when we work to see less negative intent, we will eventually see less negative in the world full stop. This will also enable us to see with more clarity where real negative intent and the real harmful actions make their home - as political correctness has shown of late, see fascists everywhere, and you will no longer be able to recognise when real fascism pervades your system.
Just a little food for thought for all of us, as obviously it was not an inconvenience to change the title, the intent of the person questioning the title was quite interesting to myself. This was because the manner in which it was written may have inferred that all responsibility of any offence is with the words themselves and none with the reader, which I think is harmful. Yet, I did not question this, because it is more beneficial for myself to try to see most things from a point of positive intent first - hence, I just changed the title, but would not just state that I could see harm in the words when I cannot. That is just me being honest, because there was no malice or harm intended and I truly could not see how those words would be perceived as negative.
However saying all the above, it obvious that sometimes words can produce offence in someone and while intent can be quite easily questioned and the intended meaning clarified quite easily, people can be quite ‘lazy’ when reading and purvey misunderstandings. I use the term lazy, because while we naturally skim over much while reading, it is actually our responsibility to gain as much understanding as possible before we respond. The response we have control of and hence we are responsible for.
Pretty much like the person that wrote the seemingly ill informed one star review for the app in question, responsibility is sometimes easily pushed aside. I take responsibility for the words I used and the intent I meant, but we really do need to start encouraging others to be responsible for their own feelings.
I do not intend this as a rant or a sermon. I am not preaching, merely expressing my thoughts on a subject I find interesting. My thoughts as in all things though are a work in progress and change as I meander my merry way through this musical life. So, I encourage any comment and hope that these words are received in the respectful, thoughtful and inquisitive manner they were intended and not as a slur to anyone who has so far commented on this thread.
Live well people and make great music