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.
Cubasis 3 praise.... I spoke to soon
Buyer beware!
Today I purchased Cubasis 3 with high hopes...they were soon dashed
I followed the instructions I was given to transfer my IAP’s from Cubasis 2 to 3
So far so good.
After a quick google search I found how to transfer the project I was working on from cubasis 2 to 3.
I hit play: pops crackles and things not sounding right?
I check my settings the make sure they match my Cubasis 2 session (which was working flawlessly) all set everything matches
Some AUV3’s did not load properly I go back and find my original sounds and effects
Still lots of crackle and pops and some sounds are still not right
Agonizer did not select the correct patch I fix that then a hung note
I quit and restarted at least 14 times reloading IAA’s Auv’s- it think it is all set then a crackle at the one part in the chorus , then again a bit later and then another random place
I have 19 tracks 8 of which are individual drum tracks, kick, snare hi hat etc.
Most tracks are all Cubasis instruments with the exception of 1 Auv3 Track (Agonizer)
And two IAA Tracks (IM1 and Poison-202)
Four instances of an Auv3 effect tone bridge (all the same)
No Automations, no ARP, no loops, no samples
Now please understand that all this works in Cubasis 2 without any issues at all
It does not work in Cubasis 3
That being sad if it does not work then I can not use it. I wanted to because of the fancy new update with midi control but that does no good if the basic app does not work.
Seriously!? Cubasis 2 is still working on my iPad, Cubasis 3 does not! The same damn project with the same damn settings!
In my job I provide a service, when I return to that client to provide the same service it has to be as good or better, they do not want something they can not use! I would be fired!
So how do you justify your employment?
how do I get a refund?
Comments
@ralis Check the setting for using multiple cores to accelerate processing. Even if your device is capable, it may work better with that feature turned off. I don't know the details, but this was discussed when the feature was added some months ago.
Yes thank you that was second thing I checked, right after my 48/24 settings.
Such a disappointment. I really wanted to love it.
Hi @ralis,
Which iOS device/iPad OS do you have in use?
In addition, please share more details about your exact latency settings.
Best,
Lars
Answered in the previous thread.
I really should not have these issues and be this frustrated. If version 2 works then logically everything in version 3 would work as good as version 2 plus.
Like I said I vote with my wallet. I have requested a refund.
I will take some responsibility as I had read about the plethora of issues users have with Cubasis 3. So I did not purchase it, but when you rolled out 3.3. With midi control I had tunnel vision and just went for it. I was blinded by the shiny new thing.
I will be more cautious.
@ralis Unfortunately I have to agree. Cubasis 2 and 3 have a beautiful UI and it could be such a great app, yet the unfixed issues have finally made me stop using them except opening collab projects and exporting stems (which can also fail or produce unexpected results at times).
I would have preferred Steinberg to fix long standing issues with Cubasis 2 but instead we got the next buggy version.
I really hope they will focus on fixing the reported issues first instead of putting out yet another major release.
Thanks to @LFS anyway for doing his best to communicate and taking care about collecting bug reports. If he was a developer, he'd certainly be a good one.
https://support.apple.com/en-us/HT204084
I believe it’s up to the developer to allow refunds on the app or not.
Hi @AlmostAnonymous,
Please note that App Store app refunds are only granted via Apple, as stated in the article above!
Best,
Lars
i dont know what device you’re on but in general this assumption is totally wrong if ver 3 was built for modern devices with greater capacity to run extended features not capable on systems when version 2 was made.
nonetheless, it’s unfortunate you’re not having a good experience. hope it gets worked out for you.
Could some of the instability here been have been related to project transfer?
Sometimes software projects doesn’t transfer well. A fresh project from scratch could yield clues.
I wouldn't necessarily blame Cubasis for Agonizer misbehaving. I find this app very unstable; it'll lose its settings/change things mid-song for me.
Of course they con only be refunded though apple.
What I’m saying is I’ve had refunds refused because “the developer does not allow this app to be refunded” in the past. Maybe this has changed. You would know more than I would on this, tho.
Apple fully decides about refunding requests themselves, developers are not included in this process!
At least this is the case for us.
Best,
Lars
I’m honestly amazed every time I see anyone saying C3 works for them. I’ve got it on 3 iPads and it doesn’t work on any of them as well as C2 does.
Don't know, maybe depends on the amounts of track you have etc. For my very small projects it has worked just fine for now on an iPad Air 3rd gen. I don't own CB2 as a comparison, so limited experience, but I only experience pops and crackles with very CPU heavy synths and I can solve that by freezing the track.
Hi @ralis,
If possible, please share your project with us, to allow us evaluating the problem.
Alongside, a short clip which visualises the issue and that shows your latency settings would be of additional help.
Please upload both files via Dropbox or similar, and let me have the download link via private message.
Just to make sure, you've already gave it a try to set Latency to OFF, correct?
Best wishes,
Lars
Man, that screenshot is confusing!.
“Multi-core rendering disabled” - OFF.So if it’s off, you’re disabling the disable, hence it’s ON ... (head explodes)
Wouldn’t it be better to just label it “Multi-core rendering” and make that ON/OFF?
Which brings me to... Have you guys heard “Double Negative” album by LOW?. Best production ever, a masterpiece.
iPad Air 2 and no problems so far. For older devices don’t use to much midi tracks at once and bounce them to Audio tracks as soon as possible. Most of my problems with unstable apps were solved with a fresh install.
😂😂🤣 This is amusing!.
So in that screenshot. You thought multi-rendering was disabled?. To me it’s enabled.
I don’t have that setting, btw. Must be cos I’m on a new iPad ?
Yes, that album is really good.
Hi,
actually you turn "Audio Engine Latency" to "OFF" and disable "Multi-core rendering" via this setting.
Best,
Lars
AFAIK these settings appear if CB thinks your iPad has enough cores so that the audio engine can operate in the multi-core mode. I think there was another thread discussing that. The problem is that on some iPad models this detection makes a wrong decision. On a modern iPad not all cores are high performance cores. There are also low performance, high efficiency cores. Such an iPad runs normally on the efficiency cores and the high performance cores are only used when there is a high load. This behavior seems to be a problem for CB‘s multi-core implementation. BUT it is very rewarding to go in this direction as it has a much higher performance. They just need to master this problem. For the time being you need to turn it off if it causes trouble.
AFAIK no other DAW or AU host utilizes multi-core in this advanced way. Go Steinberg, go go go. It‘s worth the effort.
I’ve also had issues with Agonizer as AUv3, hanging notes and crashing projects (using LK) in AUM. Crunchy audio in IAA use too
@LFS still have the same audio quality issues as the last version of cubasis had. in regards to bluetooth headphones. regardless of the studio quality/ bluetooth setting being engaged.
i have the latest ios , iphone 8plus, with apple airpods pro.
My experience with cubasis:
Buy cubasis 1 with all the IAP a week later cubasis 2 is released
"Ok, well fuck you too, cubasis."
Waits a year or two, pull the trigger and buy cubasis 2 less than a week cubasis 3 is released
"Looks like I'll just live the rest of my days continuing to pirate Ableton Suite on Audionews, fuck this shit."
Hi @louis,
Something must be wrong here…
Cubasis 2 was a free update for existing users of Cubasis…
Best,
Lars
Hi @eross,
Please use the following steps to use Cubasis 3 with the AirPods Pro:
If the problem persists, please go to Setup/Project and choose (or reselect) the matching sample rate of your project.
Best
Lars