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.
Multiple instances of Beathawk AUv3 in Cubasis 3 problem
I am working on a song in Cubasis 3, using Beathawk as an AUv3 instrument on a MIDI track, which works fine. However, adding Beathawk as an instrument on a second track intermittently crashes the first instance, which stops producing sound. If I add it on a third track, the second one intermittently crashes. If I reopen the project, the AUs fail to load properly.
Am I doing something wrong, or is this a bug?
As a test, I set up four separate instances of Beathawk in AUM, sequenced by four separate MIDI processors, which worked fine.
I went a bit crazy on the last Beathawk IAP sale and would like to use it in Cubasis, so any tips welcome please. 
Comments
Running (another) search after posting, I came across this post:
https://forums.steinberg.net/t/auv3-instruments-crashing-on-3-2/682490
As per that post I’ll switch off the Latency/multi-core settings to see if that might help.
Fingers crossed, that seems to have fixed it.
If It is indeed the multi-core cpu support that is causing the issues between Cubasis and BeatHawk it might be worth to alert UVI about it?
BeatHawk is if I recall correctly quite a memory/cpu hog so depending on the device being used that might also be one thing to watch out for...
I’ve reported the issue many months ago to UVI which never answered after their investigation and to Steinberg which was not able te repro…
Just disable multicore processing in Cubasis, it sucks to have to do that but no more crashes. Please report to them too.