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
Wonderful, thanks a lot for testing and reporting back!
@MoogMusicInc Thanks a lot for the public beta 👍🏼
I tested the new version on my iPad Pro 10.5 IOS 14.8 and i am quite unhappy to be the bearer of bad news.
.
In AUM with 44.1 Khz and 512byte buffers i tried to find out the limit‘s, ie max number of instances without crackles with/without GUIs open.
I know that DPS% doesn’t really tell a thing, but crackling does. To confirm my findings, i re-installed the shop version and immediately re-tried the test (resulting in the above, better behavior).
Then took a break until the pad had cooled down, installed the new beta and re-run the tests again, verifying the numbers and that the beta hits crackles earlier than the shop version.
Sorry, would have loved to present a differnt result
Regards, -ki
That looks great! Nice job. I've often thought of building one with the Shantea controls platform but haven't made the leap yet.
Thanks for the detailed testing, this is very useful.
It indeed looks like you're seeing differences at edge conditions, we'll investigate further to see if something stands out that we can improve. So far, on devices that were struggling before, it seems to consistently make a significant improvement. Also, the memory usage overall makes iOS not kill the plugins anymore, allowing for multiple open windows on Model 15 (they use the same engine).
❤️ your friends at Moog
@MoogMusicInc
I see that the Model 15 beta thread has disappeared, so I'm hoping this will reach you...
I am using a single instance of the Model 15 within LPX 10.7 on my M1 MacBook Air. When I switch to a different preset, however, the entire UI disappears to a black screen with the following comment at the top:
"iOS memory restrictions require all Model 15 instances to be hidden before the UI can be fully used again"
I'm not exactly sure what this means. I've tried closing the plug-in window and reopening, but no joy. Any suggestions?
Is this with the beta or the App Store version?
@sch : the model 15 discussion is at
https://forum.audiob.us/discussion/47483/model-15-v2-2-11-beta
They are identical architecturally / features-wise, but (over-simplification alert) the Minitaur is (by design) better for bass, and also maxes out at (I think...) C4. But the oscillators do sound different. You can hear the difference and it's quite noticeable on a scope. They're different enough to (just about) justify owning both. Which I (just about) do
And of course, they both sound great!
I've only briefly played with the Minotaur but the first thing I looked for was a way to adjust the pulse-width which unfortunately is a no-go, but it does sync and some other nice things.
There's still one Moog synth I'd love to see as an app and that's the Subsequent 25 with 'poly' option since it would be software
(Had I know what I know today I could have saved a bunch by getting the SubSequent 25 when it was released instead of spending on a bunch on other hardware that is mostly collecting dust the the moment).
Thanks for reporting this, are you using the store macOS build or this iOS beta on the Mac?
It is the Mac store Mac OS build.
Should I try to reload the plug-in?
The Mac store build is still the same, without the improvements of this beta. What you're reporting is one of the reasons why we did a rework of the graphics engine.
Cool, thanks for the feedback. I'll just wait for the update. Cheers!
I did my quick Cubasis multi-core rendering test before and after the update to the beta. Before I could run 30 instances of Model D without crackles, after the update 29 - I had to delete one track to get rid of the rare crackles.
iPad Pro 2021, 11 inch, 256 GB, M1, 8 GB RAM, iPadOS 15.0.2. No audio interface. Preset Border Bass. Audio settings, see screenshot.
Do you still get 30 instances if you use one of the polyphonic presets and trigger chords?
I need to try but I don’t think so. I use Model D as a mono synth. Any particular preset in mind?
Ay poly would do, try 'Compugame' under Keys category, it's medium heavy and doesn't use all the effects
Hi everyone,
We uploaded a new version v1.3.7 build 134 to TestFlight:
https://testflight.apple.com/join/8oJrJ9ha
We're curious to see if this makes any difference for those that tested towards edge conditions and were able to create one less instance than with v1.3.6.
Thanks for the help!
Another day another update. We did more detailed profiling when running a lot of instances and noticed a performance regression that we managed to fix.
We uploaded a new version v1.3.7 build 135 to TestFlight: https://testflight.apple.com/join/8oJrJ9ha
Please let us know if this restored the previous performance for you, or maybe even made things better than before
Thanks for the help!
@MoogMusicInc Yay, you nailed it 👍🏼
The beta v1.3.7 (135) allows to open the same numbers of instances as the store version, i can even open up one of the GUIs without cracles which wasn‘t possible with the store version. Moving the window will start crackles, but one can interact with the Model D UI without problems
Thanks a lot, -ki
Awesome thanks so much for testing and reporting back!
We made this version available as the public App Store release. Thanks everyone for testing!
We released the update for the macOS version also, hopefully this fixes your problem.
❤️ your friends at Moog
Whoa!!! For a moment I thought you meant you’d released a MacOS version of Model D!
Sure hope that is on the timeline! 🤤
Ah sorry, since your original post was on this thread to didn't specify. Yeah, the update of Model 15 is available on macOS, not Model D
We hear you though
What does "support for MPE zones" mean? Where are the zones?
With the latest beta I‘m back to 30 instances with my Cubasis multicore test. @Samu, I adjusted my test to the preset you proposed and now looping a Midi part with 4 quarter note triads. Surprisingly I can still run 30 instances without crackles in Cubasis 3.3. Wow 🤩
It’s amazing to see that with a good multicore rendering of the software, the M1 iPad Pro seems to really deliver the performance I was hoping for, probably coming close to the performance of a M1 MacBook.
That is indeed impressive!
I'm quite happy with the performance on my ancient iPad Air 2 even though it's not a speed monster
MPE provides a lower and upper zone, configurable through the MPE configuration message. An MPE controller has to option to expose that as a setting, including the number of channels it will dedicate to that zone. Model 15 and Model D now honor this and reserve those channels.
Thanks so much for the additional testing! Very happy and excited to see this result.
The Minimoog Model D app is built on the Model 15 app's sound engine, which is a modular where we didn't feel like dynamic voice allocation had its place. You should be able to just play it without using the keyboard and use CV for anything, which is what it does. We are internally using vector math operations for almost everything, leveraging the power of NEON and Apple's Accelerate. So four voices only take a slightly more CPU power than one voice. On Intel though, this is not the case, which is why Model 15 on Intel machine takes up a lot more CPU.
Also, with these latest changes, we finally figured out how to have almost no graphics at all linger in the CPU anymore and have everything that's heavy pushed to private GPU regions without any CPU coordination necessary. That really leverages the architecture of the Apple CPUs.