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.
Comments
I'm still getting the same faulty/weird behavior with modulating travel speeds that was introduced in the last update or if it was the update before that. And autorotation, which also got worse in the same update, is still present. I'm not getting any kind of feedback from anyone involved with this synth on it all...But AB 2! Thumbs up on that
Have you sent Rolf an email about it?
@Sebastian I asked via twitter if he could look into the some of the issues. But he seems like a very busy man, so I'll probably give his mail a go. Also tried Waldorfs official Nave Facebook a while back regarding a few other issues, I guess social networks are not the primary channel for getting in contact with the Nave guys
Doesn't crash for me. It could be your annoying tendency to only post requests to update audiobus that is doing it? I would suggest closing all requests to update in your head. Rebooting your head, and then running cmemory to clear any persistent requests.
Previous version crashed when using the recorder on my ipad2. So far so good with this update.
@ChrisG No autorotation here either. What's the issue with modulating the travel speed?
I just did a quick test but didn't notice anything weird.
@R_2 said:
All presets in my Nave that had the travel speed set to "clock", LFO 1 & 2 or the XY on the keys (or pads) modulating the travel speeds, just sounded like Mosquitos or really fast garble after the update before the last one. All due to the wave locator traveling waaay too fast obviously, (irregardless of tempo clock).
I don't know what exactly they changed (or why?), but I had to readjust LFOs, XYs and travel speeds to get the old sounds back at least somewhat to what they sounded and acted like before the update. A few keys gives a very different travel speed then all other keys btw (on the iPad screen, not tried it with a midi keyboard), completely unrelated to any key tracking, and I can't find any consistent behavior on that one either.
It's been quite a while since I stopped making presets for Nave, maybe I need to dig a bit further and see what's up.
@ChrisG I see, perhaps they needed to change the parameter value of the travel function. That would make all presets done with the older value sound different... Just guessing.
@R_2 said:
Yea they changed something with the clock and travel values quite drastically. I can't figure out exactly what values/parameters in that mess that has been changed, or how it works now for that matter...Still, changing something in a synth that will affect the sounds should be clearly posted, and what exactly it is that has been changed so a user can at least "back engineer" their own presets to a working state again.
Or it is a bug. I'm gonna ask Rolf via mail if he can look into it, if I can't figure it out here..
Agreed, a change/fix like that should have been mentioned in the update description at he AppStore.
So it's not simply a matter of turning down the modulation speed (or strength) to replicate your old presets?
I assume you're not syncing nave to some external clock? (If that's even possible)
Nop the sync is tied to Naves internal BPM setting. I've tried twisting and turning most stuff, it's just acting weird. And that a few keys on the keyboard plays the travel speed completely different then all other keys is also just weird. All this happened in connection to when they implemented poly aftertouch and channel pressure from external controllers. Anyway, I've had enough of Nave for today. I'll look into it all more during the weekend.