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.
Moog D/15 apps issues with iPad Pro 13 m4
Hello everyone ! I am exploring new iPad Pro 13 m4 (running iPadOS 17.5) that seems a big jump from an old iPad Pro (2016) ! However, after apps transfer, I found some UI issues with Moog Model 15 and Minimoog Model D standalone apps. Some button labels have disappeared. I tried to reinstall without no change. AU mode works perfectly. Any suggestion would be appreciated.
Comments
Congrats on your new iPad and the obvious suggestion is: contact the developer.
@MoogMusicInc are very responsive here and I'm sure will appreciate the heads up
Just to reassure you, both Moog apps look exactly as 'glitched' as yours on my new iPad too (13" M4). I only ever use in AUv3 mode, so didn't worry about it too much.
Thanks for your replies !
I’m on the fence about upgrading to the 13” M4 from my 2018 iPad Pro; I’m very curious what CPU % you’re getting on cpu heavy plugins like Tera Pro or Moog Mariana. Some patches get me up to 35-40% load on my iPad. I’d be a happy camper if I could run 8+ Tera/Mariana instances in Drambo or Logic without any glitching.
I upgraded from a 2021 M1 iPad Pro. Using Logic Pro, I typically start off a track with a low buffer size (for low latency midi keyboard playing) then as the track builds, increase the buffer size to suit. By the end of the track, buffer is usually around 512, and I have a bunch of mastering plugins on the master channel, along with all live synths & effects etc. (I don't like bouncing down!)
At this stage, on the M1 iPad, I'd usually start to encounter some audio dropouts here & there (particularly if the buffer size was still low). I know Logic Pro takes advantage of multi-core processors, so my main reason behind getting the M4, was to increase my synth/plugin/latency headroom even further, before encountering issues.
I haven't really stress tested the M4 at all yet (haven't really started anything new yet to be honest) but I'll give multiple Moog Marianas a go when I remember, and report back...!
Edit: 8 Marianas was no problem (all playing the same pattern on different random presets). I got to 11 on 128 buffer size before the CPU meter was in the red. I then increased buffer size to 512 and got to 16 instances before I got a 'CPU overload' message!
@mosquito, @DanSebPage
Do your M4 iPads run hot at high CPU load when playing a challenging song or multiple hungry synths for a few minutes?
I haven't had a good long session with it to really tell yet, in the time I've had it. It's certainly not something I've noticed so far, and I can't detect any heat at all after having run the quick Moog Marianas 'stress test' above!
I also don't know how 'scientific' any of the above is, as I've read numerous times, that the iPads dynamically manage their CPU usage, engaging and disengaging cores as required to be most power-efficient in any given situation.
A 50% CPU usage for example may only be 50% of the cores currently in use, and once the app demands more power, more cores get activated etc.
All I know is, the M1 iPad could pretty much handle a finished track of mine all running completely 'live' (example) so the M4 iPad should give me plenty more future headroom for more power-hungry synths, lower latency, more plugins etc.
Thanks, good to know!
I did not notice any particular heating of my iPad m4 despite multi-track/plugin sessions on Cubasis 3. CPU usage remains very moderate compared to my old iPad 12.9.
Furthermore, regarding the nano texture version, the finger adjustments are very precise due to the incredible sliding of the screen.