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.
SOLVED - Model D issue (Cubasis 2.4)
UPDATE
Minimoog Model D App v1.0.3 was just approved by Apple and is being propagated through the App Store. This update should fix the issue described in this thread.
Dear all,
Some users have found out, that loading more than one Model D instances in Cubasis 2.4 can lead to serious problems, when trying to re-load these projects again at a later point.
We already exchanged with Moog, who confirmed to provide a fix for the issue with the next Moog Model D app update.
From what we know the update is expected to be released very soon.
Until the issue is being addressed by Moog, we recommend to limit the number of Model D apps used in Cubasis projects to a single instance.
Best,
Lars
Comments
Thanks for the heads up
It’s all a ploy to make me buy a hardware Model D! (Joking
)
Thanks so much for the heads up.
A hot tip in these trying times. Running one as AU and one as IAA in Cubasis seems solid.
I guess you could also try hosting a few in AUM and routing its audio into Cubasis if you're really deperate to use lots.
I find Moog stuff is so thick and nuance-y that I tend to just like to have one take center stage. It feels like one of those ones where I just want to noodle and jam out as audio then chop it up later.
So very true
Except in my case, I just want to twiddle and noodle...stuff the recording.....I'm selfish like that sometimes 
Same here. Sometimes it’s more about annoying the wanker neighbours than the needs of recording - unless it’s recordings of the neighbors crying lol
Actually through the tv sound bar. Maybe not as nice sounding as my monitor speakers, but they are attached to the wall so the bass travels lol
I love that Cubasis now has file support, but Ive been having other issues since. The last project I started and mixed down had major issues with Model 15 producing a static glitchy sound, even when I started and bounced another project with just one instance of it and and drum track. Also in reference to the first project I mentioned , when I reloaded the project today, 2 other au's didnt load (Ruismaker FM and BASSalicious)
🔜☑️
hehehe... Give 'em hell
Minimoog Model D App v1.0.3 was just approved by Apple and is being propagated through the App Store. This update should fix the issue described in this thread. Please let us know how it goes!
Have you tried our AB Forum sound pack yet? Give it a go
After the update all is fine. More than one ModelD in cubasis are no longer a problem. The projects which weren‘t able to load, can be opened like they should.
Thanks for the exellent support!
👍🏽
I do love the way Steinberg and @LFS reach out to other devs to get things fixed.
@LFS
Tardigrain same issue. When you try to add a 2nd instance, it shows a black au screen. When i restart cubasis it can't reload the previous session. The project folder becomes glitchy and showing weird behaviour creating new project names. I hope this can be fixed because it's my favorite most used au at the moment.
Hi Proto,
Please get in touch with the app vendor and let them know about the issue,
Thanks
Lars
I'll do.
Hi Strizbiz,
Please go to Setup/Mixdown / Share and enable "Audio Unit Mixdown Compatibility Mode", which has been added for instruments that consume massive CPU. Make sure to deactivate the option again, when not required.
Best,
Lars
Worked perfectly!!!!! Soooooo hyped now!!! lol, thanks!
That's nice to hear however 'Freeze/Mixdown' when using Cubasis 2.4 seems to be somewhat malfunctioning?!
The real-time render option in Cubasis 2.4 slows down the tempo of the rendered audio from Model D causing the frozen audio to play back slower than the original midi-notes?! (Does the off-line renderer set a 'fixed' sample-rate or use the sample-rate set by the project? Are the 'buffer sizes' changed?).
Changing Cubasis 2.4 sample-rate to 48Khz makes the rendered audio-file somewhat shorter but the timing is still wonky?!
When using the regular (non-real time) render it's crackle fest deluxe even with a single instance of Model D.
I know my iPad Air 2 is not the fastest iOS device on the planet but I'm hardly pushing past 40% CPU and everything plays back fine in real-time but doing a mix-down is a no-go.
Don't really know how to trouble shoot this further, but the conclusion is that Mixdown/Freeze not working properly at the moment.
It was the same under both iOS11.2.6 and still the same under the just released iOS11.3.
I love Model D and wish it was possible to properly use it with Cubasis.
I've had no issues with it using BeatMaker 3...
Since @MoogMusicInc and @LFS (Cubasis/Steinberg) are already in touch with each other I trust these issues will be worked out in due time.
Cheers!
That works for me as well. Thank you.
This is what I get...
With the 'realtime' option the audio plays at correct pitch but waaaay slower.

With 'normal' it plays distorted garpage.

Realtime playback has no issues what so ever...