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
Electric piano > Combustor > FAC Alteza
🫨😵💫
Good idea. I'll have to try that!
To answer my own question.
One big sweet spot and I like how the color changes depending on which (combination of) sounds are processed.
In short: turn the knobs
I just tried CC mapping in AUM with version 1.1 and am getting really strange results. After assigning CC, the dial jumps around super fast seemingly randomly. Eventually, the movement smooths out, but then I don't get any effect, like it’s switched to 100% dry. Anyone else having issues like this with 1.1?
In the video below I have the same saw up Rozeta LFO mapped to every AU parameter, maybe what you're seeing has to do with parameter scaling?
https://share.icloud.com/photos/05emjS5Ymlq_SybEFshauzZhA
Yes! I'm getting that in AUM too with 1.1.
One thing I did notice is that the DSP is like 99% or max, I felt like it was a midi loopback or similar. It goes on for several seconds, maybe 5-10s.
I did try deleting Combuster and re downloading, opening in standalone 1st then as AUv3, but that didn't help.
[EDIT] i'm on latest iPadOS, 16.5.1 iirc.
[EDIT EDIT] The odd behaviour is when using a midi controller (Novation LC XL), using an LFO (Rozeta) Combuster knobs behave as expected/ok.
I'm on ipads 16.4.1, just tried using an lfo on this in aum now and it is working exactly as expected, no problem
@giku_beepstreet
Sure, LFO works fine for me too.
I'm experiencing the issue when using an external hardware MIDI controller mapped to each knob in Combuster (Novation LC XL)
duplicate
Same. Tested with NanoKEY Studio Bluetooth knobs .
I’ve reported this over on the Beepstreet forum.
Hummm! It works fine in Loopy Pro, but not in AUM.
thanks @wim
He’s on it. 👍
In case anyone was curious - after the update, automation also works in Ableton Live!
Just to double confirm this device is nuts on rhytmical stuff. Very unique
@pedro What is the Wave Scanner you are using here? I can´t find anything like it. It looks sort of like a Flexi sampler, but not quite.
I’m sorry I forgot that’s from the beta, shouldn’t have posted yet. Guess you’ll have to wait…
Looking forward to it! Hoping a new version will land before summer break.
New version?
Drambo is v2.24 now, so 2.25 then.
Whoa just got combustor… not even sure what it is, but I love it!
Haha yep it’s fantastic! If you like this, check out Dagger, their new synth. Not really the same thing but in the same league of “woah this is kinda unique and really awesome”.
Heh my oniomania credits must be good around here, assuredly… I compulsive-bought dagger already… but combustor is pure awesome, anyway
Idk, to me, it just seems natural to run Dagger through Combustor as well. Not that Dagger is lacking in sound.
Wait.. what I meant to say was; it just seems natural to host Dagger, running through Combustor, in Drambo!🤪
I mapped to a controller in Drambo but attack, release, tune, are a different resolution or error by dev.
The 'automation knobs' have a different transfer curve (linear) compared to the knobs used in the plug-in.
Don't know if @giku_beepstreet has any plans of adding a custom transfer curve for every Drambo knob?!
There's plenty of other apps that behave the same where the Plug-In UI knobs have been tweaked to be in the 'sweet spot' or a specific value-range. (Think of it as a linear, logarithmic, exponential or custom transfer curve per knob).
Thanks Samu.
Tried also mapping in aum with kb-1 but dosent map.
Could map to other au.
Hmm, an AUv3 can't directly be mapped to another AUv3 so you'll have to go the Midi CC route thus it makes perfect sense the KB-1 can't directly map parameters present in another AUv3.