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.
AUM and Drambo multicore WHEN?
When will there be multicore? It's been years since these programs came out and we still can't use the full power of the new m1/m2 processors and they are completely useless.
Comments
Not being multicore from does not make them useless. Not maximally optimized is not the same as useless.
Nice flood mate
You’re proving the flood here “bro”
you can't synchronize audio streams from multiple cores afaik making it only useful for non-realtime use such as exporting. does logic do anything with multi-core?
I think it takes a lot of work to do it unless the app is designed with multi-core from the beginning, so it's a case of developer resources and time, it's not just a simple change.
This isn’t the case. A few yeas ago APIs were released for multicore audio, but they are non-trivial to implement and some implementations crank up the latency in order to make use of it.
A few hosts so far enable this, Cubasis, MTS, AEM.
Regarding Drambo, this question has a better chance of an answer from the developer if asked over on the BeepStreet Forum.
Still, pinging @giku_beepstreet regarding Drambo.
Pinging @j_liljedahl regarding AUM.
The logic has full multicore support and fully utilizes the full potential of m-processors from the very first version. Also Cubasis 3, aems.
I understand that, but let's say the AEMS developer implemented this and it works pretty well now. AEMS was not originally with multicore support.
I think GarageBand too, though I may be wrong.
Ive no idea if Logic, Cubasis (etc) that use multicores are using them in the manner of audio processing.
But the OS will be making use of it, it’s still gonna be better.
There’s probably good reasons it’s not done.
I’m pretty sure Running all cores full whack on a portable device with no cooling isn't clever.
The 127 track guys would be crying when their ipad keeps crackling cos the powers throttled down to stop it overheating.
Actually, no, I don't think overheating is much of an issue with Apple's processors. I'm sure this sounds strange to people who are more used to Intel/AMD processors.
The "good reasons it's not done" consist mostly of "the developer of my host app hasn't had the time to add multi-processing support yet".
There are plenty of posts here on ABF where people post of being able to use Logic Pro, Cubasis, and others to host more instances of AUv3 plugins than they can with same setups on hosts that don't support multi-processing.
Overheating is not an issue because the processors will throttle... well its not a break your ipad issue but i think theres gonna be a practical limit anyhow, far before 100% on all the cores is reached. More is achievable via multicore but yeah… how many more plug ins are claimed to be running by these people? Are they getting double? 50% more?
I think these M chips on Ipads are intended/designed to be blisteringly fast in a responsive experience kinda way (in bursts). The theoretical max is an occasional peak thing… it won’t actually do what some people think it will do when they see 8 cores “on paper”… only 4 are fast cores.
I’ve read the M1 isn’t that great for multicore audio. On a macbook air, pushing it via lower buffer setting to prevent a throttle down is needed for reasonable performance on ableton (bigger buffers dont run well cos it throttles down). But if people can get a that bit more grunt that they need… great!
Yeah, FWIW Traktor 3 on macOS has a selectable multi-core mode, and its “load” meter shows a lower load generally when it’s in single core mode. I think the challenge is you want to keep audio processing off of the efficiency cores, and when it’s running single core it can reserve a performance core; something like that. And yeah, audio software can get my M2 MacBook Air all warm and toasty when it’s doing a big batch processing job. I don’t know, but Imagine that an M-series in an iPad is probably tuned to throttle faster than in a Mac since it’s packed in with the screen and the batteries.
When I replaced my 2017 Pro with a M2 PRO I did a test with both side by side. The single core DAW was Zenbeats and Multicore was Cubasis.
I loaded Butter synth with a specific pad patch and made it play a C3. Then I duplicated the track until I started majorly crackling.
2017 iPad:
Zenbeats 4 instances
Cubasis 8
M2 iPad
Zenbeats 8
Cubasis 20 😱
Edit : I corrected my error on Zenbeats M2
@ecou, it would be a much cleaner test to compare Cubasis 3 with multi-core and without, thus removing other factors between the two apps.
It is also important to make note of latency. One developer pointed out that Cubasis multi-core support requires a sizable buffer…so if one needs a low latency setup that strategy may not work.
I agree with you, it was just a little test I did for fun when I got my new iPad. I was not trying to do the ultimate benchmark.
multicore feature did help my ancient Air2 , we are talking about more than half performance unutilized on hosts that don't support multiple cores . I guess it's hard to implement correctly on iOS . I remember Zenbeats did have that feature but they removed it because the performance was actually worst
Multiprocessing on Apple chips is different than it was on conventional Intel ones. On Intel, all cores were the same, and allocating them was a strait forward symmetric process.
On the Apple Mx side, the operating system manages which core will be allocated, and to be more complicated, you have two types of cores: P-Performance (fast) and E-Efficiency (slow). E-cores have approximately half the processing power of the P-core. And furthermore, they are divided into clusters of the same type.
This type of asymmetric multiprocessing puts our developers in uncharted waters, it’s not easy to give all efficiency design to the hands of the Apple automatic threading system. Especially in audio signal processing, where latency is the main factor.
Thats that. I tried, with layman's words, to explain why our developers hesitate to jump on the multiprocessing wagon. 😅
iPad Pro m2
I tested mirack, it's the same multi-core now. I compared the performance with Logic Pro. Here's an example. Same patch everywhere. 24 channels with Moog model D. Buffer 256, frequency 48. iPad Pro m2. Load averaged 92%+. Logic is better of course, but mirack is really good now. In Cubasis, the same project plays an average of 20-23 tracks, which is not bad either, unlike 8 in AUM or Drambo, which do not support multicore.
I don't understand why people here are trying to justify lazy developers for not doing multicore, or it's the developers themselves who are doing it, or the developers of crafts like zenbeats 😄 Utter stupidity. People pay for software that should work on modern devices, not for mothballed arguments that nobody needs multicore or it doesn't matter.
I don't think it's about 'Lazy Developers' at all. It's about making a living especially when apps do not provide enough income.
It's also easy to forget that both apps mentioned are one person 'sweat shops' which might not even create enough income for decent living and thus side-hustles are needed to cover everyday expenses...
One can always wish but sometimes it's a good idea do a reality-check which will help with managing the expectations.
If I was @j_liljedahl or @giku_beepstreet I'd seriously consider releasing new app versions with multi-core support and yes go full on subscription to create enough income to sustain the app as one time $29.99 apps will not be enough in the long run...
While I do not have any numbers for either AUM or Drambo I doubt it's above >10000 users and considering the apps were released years ago they no longer create any real income...
Right. Developers are rich, fat, and happy drinking Mai Tais on the beach, just letting the dollars roll in while they sit on their lazy asses. Meanwhile we’re all suffering under the crushing burden of not getting all the performance we need to produce our next world changing masterpiece.
Glad we got that all cleared up. Now that these slackers have been properly shamed, we’re sure to finally see it all turn around in the next few months. What would we do without such authoritative and incisive experts cutting through these developmental barriers around here?
LOL. Write more about the children in miserable Africa that you sympathize with. How unfortunate developers are, how hard their lives are, I'm just crying.
I don't really understand the point of such arguments. There are no questions to opensource developers, they do it for free, and if you do something for money, you should and will be questioned. That's the basis. Why should anyone care about the life of a developer who sells his product and has income from it?
This all somehow justified someone only in the case if there were no products like AEMS, where a man alone makes the functionality many times more than any Cubasis 3 and others and great respect to him for this. It may not be the best host for iOS, but it's definitely in the lead.
So let me see if I have this straight. Either the you bought AUM or Drambo before Apple introduced multi-core support and even though you haven't paid a dime more for it since, you expect to get such a major improvement for free on your timetable. Or you bought it afterward, knowing that it didn't have multi-core support and not having read that it was promised anywhere, but still expect to get it for free. Now. Or you're being treated unfairly. Or the developer is incompetent or lazy.
Sad. The developer doesn't owe you squat. You bought a product. It works as it did when you bought it. You're not entitled to any more than that.
OK, that's all I have to say. Feel free to have the last word. I won't see it because you're on my ignore list now, but maybe someone else will enjoy reading it.
Yes, I bought a long time ago both Drambo and AUM, as well as all additional paid features and all plugins of these developers, and even imagine for a moment donated to them. Have you donated? 😁
Who's talking about who owes what to whom? You started to act as Mother Teresa and justify what you couldn't justify without anyone asking you to do so, it's funny to laugh, but nothing more.
Thanks for writing about your "ignore list", that's extremely valuable and useful information 😁
Because if developers go broke your lovely apps are not going to be updated - ever. And that sounds bad bro.
That's great. When you buy bread at the store, you also politely ask if the price you paid for the bread is not too low. Won't the bread shop go bankrupt because you didn't pay enough for it? When buying any thing, should you ask about it? When ordering some service on the Internet or courier delivery you do not ask the courier how he lives and whether he will be able to support his family on his salary? If you ask and inquire and pay everyone extra every time, then there are no questions to you, you are a holy man )