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.
Pumphouse in Cubasis
Does someone else have problems, integrating Pumphouse (more than one time) into Cubasis. The function is granted - first - but after a while in the project, or after reopen that, Cubasis freezes. After restart Cubasis and put all Pumphouses out of the project, I can continue the project.
Ok - the solution would be, to put Pumphouse in a group channel. But we know, how long we are waiting for groups in Cubasis.
Are there other workarounds?
🤔
Comments
Hey, which ipad do you use? May it be a memory problem?
How many instances of PH did you run? I have not worries with iPad Pro 2018 and three instances and some AU synth plugins.
I‘m using a big iPad Pro 2017 - shouldn‘t be an performance/memory-thing. On the other hand, the project is not too small. 13 channels audio, a bunch of plugs plus 5 Fabfilter ProQ - 1 Kleverb - 1 Waves L1. Two PH on top. Not huge, is it? Didn‘t noticed and other performance findings.
And I do remember the same behavior on a smaller project too. I try to recreate this...
I used Pumphouse in Cubasis a lot on the project I released last summer. I didn't experience any problems with Pumphouse in particular but generally speaking (based on what I remember reading), Apple has put into iOS a hard limit on the amount of RAM that AU plugins can access within an app.
This is regardless of how much memory your device has or how much is being used. Apparently the iOS "walled garden" approach is structured differently than a normal desktop OS and AU plugins are "an app running within an app" and apps have a limit of the amount of RAM access. You probably hit that limit as Pumphouse buffers the audio and perhaps uses a fair amount of memory.
I would occasionally have some unexplained slowdowns. The workaround I found was to make a habit to freeze, bounce, then delete tracks with heavy plugins, then create an additional project with those changes at different stages and keep working. I'd keep the same title but add a version letter/number to the name just to keep track of everything.