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.
Comments
Correct. We currently do not support it within MIDI clips.
Cool. thanks
If you guys add support for multi core processor then you’ll be way ahead of Cubasis !
Cubasis supports multi-core. In what way would that put Zenbeats ahead? I don't ask that to be pedantic, but because I'm genuinely curious what you think.
Other than certain favorite features, I don't find either Zenbeats or Cubasis as ahead of either overall. They're equally capable ... just different (multi-processor support aside).
In exactly that way, Cubasis can support almost as many instances of auv3 as you can imagine using, stable and smooth UI, great workflow, arguably best sound library, lot of other things ; but zb3 has midi learn, PDC, more key/time sig choices , cycle recording, so I consider the only competition , somewhat, to Cubasis to be zb3 ; together they are a perfect and complete daw to me - separately they can learn from each other
And I mean this in relation to logic being basically the most professional ; i would like zb3 or cb3 to improve on two or three things to be on par with logic : im almost thinking of getting platform unlock for $30
I still think Cubasis is #1 but it clearly lacks features zb3 and logic excel in , and logic could def use better midi controller integration
Does that satisfy your curiosity ?
Thanks. I think that part is what I was after.
I was looking for some indication of which features you think would put Zenbeats way ahead of Cubasis if only multi-core support was added.
I have a question here:
”Multi-core” is already present in the Apple A-series, my A14 for example has a quadcore, four cores in the processor meaning it basically can do four calculations/tasks simultaneously. The words are often used in layman’s terms.
As I understand it, Zenbeats and others like Cubasis do not yet utilize the full power of the M-series. If run on an M-series Zenbeats and Cubasis might very well be faster and handle AUv3s more efficient due to both faster processor and more RAM, but they still only use the number of cores they are coded for. Technically, they basically ”handle” the different architecture of the M-series just like the A-series, not using the M-series to its full extent. That is why when checking specs for the M-processors you have two different readings, one when used with apps not specifically coded for the M- series, and one using apps coded to make full use of the M-series, like Logic Pro. Am I right?
/DMfan🇸🇪
@DMfan - Cubasis does support multi-core processing.
The terms "cores" and "threads" need to be clarified a little bit to better answer that. All apps can and make use of multiple cores. The operating system alone decides which cores and how many to use at any one time. Developers can't write code to run on specific cores.
What changed in the audio world was really more related to "threads". Audio processing used to need to happen in a single audio thread. Think of a thread as a queue of instructions that has to run one task at a time. A thread can only operate on one processor at a time.
Apps obviously do other things such as display themselves and handle user input. Those things don't need to (and should never) run in the audio thread, so they can be running on other cores as decided by the operating system at any time. Nothing special needs to happen for those loads to be distributed to other cores. In fact, the developer has no control over which cores anything runs on.
When multi-core audio processing (more accurately multi-threaded audio) was introduced, it became possible to have more than one thread processing audio at a time. Each thread can only runn on one processor at a time, but multiple threads mean multiple cores can be put to use simultaneously. That is something that has to be architected into an app and isn't trivial to do. Because having multiple threads means multiple cores can concurrently process the audio, it gets referred to as Multi-Core audio.
As for that question ... I haven't seen those specs. I don't think multi-core audio is particular to M(x) series. It benefits non M(x) devices as well, so I don't think that's what's being referred to. tbh I don't know what coding specifically for M(x) processors would mean, so I can't answer.
(I'll probably get roundly corrected for any and all of the above. I used to think I understood it all pretty well, but now I'm not as confident in my understanding. So take all the above with a grain of salt.)
Thanks @wim, you definetly understand all this way better than I do!
Geekbench uses the terms single- core vs multi-core with the latter ones scoring way better on iOS, so I guess that is what started me trying to understand.
I’ll just crawl back into my Zenbeatscave and make music with the threads and cores that I have…😂.
/DMfan🇸🇪
Hi! Is anyone successfully using Playbeat 3 within Zenbeats? I can barely get it to make a sound, definitely not to play an entire rhythm.
Assuming it's not just me, are there any other apps known not to function in ZB? Was considering picking it back up as I hadn't used it in a while and it seems there have been a lot of improvements since my last venture which is great. However, Playbeat might be a dealbreaker for me as I'm pretty heavily invested in it.
I don’t recall seeing a list of apps, might be a good idea to start one though. I know of a app or two that for some reason won’t show up as AUv3…
Hit it folks, what apps won’t work inside of Roland Zenbeats?
@MatthewAtZenbeats
/DMfan🇸🇪
a bit quiet from Roland isn't it? Anyone knows if they are cooking something?
I can only speculate but it does feel like it's about time for ZenBeats 4 or something similar to get a bit more cash from those that do not subscribe to any tier of Roland Cloud
@MatthewAtZenbeats I’ve just emailed Roland with regards to the very poor audio editing in Zenbeats
Hello Roland/ Zenbeats 3 issues.
I can not find a way to edit clips on multiple audio tracks at the same time. Been trying and trying and trying to select multiple clips I have on separate tracks and then split them at the same time like how most DAWs work but seems impossible. Yes I can select all or select multiple clips on separate tracks but can not edit them together.
Can this only be done on each audio track one at a time. Please tell me there is a way
Also why do imported audio clips in Timeline window default to Timestretched ?I have to turn Timestretch off for each imported audio clip so they play back at their correct BPM. This is very time consuming when importing a lot of audio.
Zenbeats audio editing is seriously lacking and some weird decisions during development as I’ve described above
Roland reply :
We will work on an update at some stage addressing the auto
Timestretch when importing audio.
We will work on a future update selecting multiple regions to edit.
As of now you can only duplicate , split regions one region at a time.
Does anyone on the audiobus forum have any work arounds?
TIA
Let’s put it this way: there’s sound coming from behind the closed kitchen door so… but only Roland the Chef knows what’s in the pots.
😎
/DMfan🇸🇪
oh, so You hear something? Because I don't
As long as it’s gonna be delicious , and I’m sure with all this time simmering lol
Thanks for the report. I've added that one to the list of AU plugins to investigate.
I agree this is something that we need to improve upon. 👍🏼
As always thanks to everyone for reporting issues/feature requests and keeping the conversation going 🙂
Cheers
Matt
I’ve run into a pretty annoying bug. When I try to use the AUv3 Loopy Pro plugin, the display is so tiny that it’s basically unusable. It’s a real pain because it stops me from making the most of Loopy Pro within Zenbeats.
It’d be awesome if you could check this out and maybe fix it in a future update. Thanks again for your help and for keeping Zenbeats awesome!
Did you resize your plugin window size to 100%?
@MatthewAtZenbeats ok thanks for reply and being in full agreement regarding Zenbeats audio editing.
“select all” is another headache . Zenbeats selects all regions on all tracks but does not have any option to copy & paste “all” so there is no way to arrange a full track properly with out the headache of work arounds pressing the x2 function on each and every tracks regions / parts. Same issues with splitting regions on multiple tracks.
It’s a shame really because Zenbeats for mixing is excellent . The Zenbeats plugins and Zenbeats audio engine coding is brilliant.
ZenBeats is amazing. My favorite after Cubasis
For sure but it doesn’t help.
It might help to post screenshots so that the developer sees what the situation is.
Here it is.
The same in AUM
Thanks again for the feedback! All noted
Try going into Zenbeats Settings/Plugins and enable "Use Plugin Windows" and see if that fixes the issue
I already try, but unfortunately it doesn’t change anything