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
Yeah its been able to load anything I’ve thrown at it, it’s really fantastic for storage when I don’t need a super high quality file of something. I could hold like half my music collection in it haha
I've decided to work on creating a Mocktatrack to see if I can sell my OT. While it's a badass machine, I really don't get it's worth in use. Haha. I've basically got the sampler side handled in Drambo, so now I'm working on the midi side. The biggest thing is the OT's badass arpeggiator. I have StepPolyArp, which I want to use in Drambo. Since SPA receives CC for certain parameters, that means I can do p-locking just like the OT. The hitch I've hit is that for certain parameters in SPA, it only needs values 0-4. I want to use the MIDI CC multi knobs in Drambo, but I can't figure out how to scale them down so they don't send all 127 values. That makes dialing in 0-4 a pain in the arse. Is there a better way to do this, or to scale the individual knobs?
Easy:
Adjust the CC knobs if you need the range to start above 0 and adjust the modulation knobs to set the maximum CC value.
Damn, dude. You are legit epic. Haha. So many crazy things in Drambo. This is why I'm glad I didn't get into real modular. I'd be broke and confused all the damn time. Since you are the guru of gurus, is there a way to view both an AU interface and the Drambo sliders rack at the same time so I can see the changes occurring, or can I only see one or the other? Thank you!
@slicetwo Sure, use the Mixer view. Place your controls on one track, route them to the mapped AUv3 inputs on the track below and open the AUv3 UI. Just remember that routing needs to go from left to right and/or from top to bottom. You won't even need the Multi CC Generator.
Cheers! 😊
Ah. Ok. So it would take up an extra channel rack (sort of like OT neighbor channels). Good to know. Thanks! One day, I'll know something you don't and I'll be able to repay the favor. Haha.
@slicetwo You're welcome. Knowing Drambo comes from beta testing - kinda naturally.
BTW, feel free to dedicate one track to controls and modulations, with all the racks and AUv3 plugins hidden somewhere below. It's quite a powerful setup because you can route e,g. one slider to 10 different destinations simultaneously, each with a custom mod amount. And on top, you can use 16 scenes to store any combination of slider settings and switch or crossfade between them live. 🤯
Yeah. So I guess, for all intents and purposes, there's no real reason to have an Octatrack in my setup anymore. Especially since I can map everything to my Digitakt MIDI or Remote Zero controller. Alrighty then.
If anyone has a Volca Drum or NTS-1, I made a couple midi modules to control the CCs, I think they’re working fine but I may have missed something. The Volca one is for split channel mode, couldn’t get single channel working too great and it’s limited for editing anyway
@slicetwo said:
The warrior retires.
For a 2nd time! Hahahaha. I had a MKI before my MKII.
Seems I can't mute MIDI out when sequencing hardware. Anyone else have this problem?
How do you mute?
Try this:
If the midi is on the main timeline sequencer, that midi mute style will work. But if you're generating midi with something like a euclidian sequencer, or Atom 2, then the mute won't have effect. Kind of surprising at times. I'm not sure if this is the best implementation, I would also like the option to mute midi generated by modules.
To clarify, there are 2 methods of generating midi in Drambo: track midi, and module midi. Midi mute only works on track midi. To mute module midi, activate the mute button, and tap on the header of the module that's generating your midi (euclidian sequencer, gate + velocity sequencer > note gen, etc) .
@aleyas yes, on the Euclidean etc it unfortunately doesn’t work.. I hit mute on the Euclidean module then.
Yep, I share your woes. If you've combined module midi with track midi, and are expecting to mute the midi output of the whole track.. surprise surprise.
Ah that explains it. Thanks everyone!
Hey everyone,
Looking through the comments, it seems that people are generally happy with Drambo's optimizations and battery performance. This makes me think I have a wrong setting somewhere that makes Drmabo drain my battery pretty quickly. I run Drambo in standalone mode with a buffer of 512 on a recent Air (A14). For sound generation I rely on Drambo's own modules. For effects, I use a few of the usual suspects (Eventide, TB, etc.) in AUv3. Usually after just a few hours, say 3 or 4 hours, I have to recharge the iPad. Is this normal behavior? If not, what could I have set incorrectly that would cause this?
dRambo is very efficient for sure.
It depends upon how many effects are being used in your project.
Some will use less and some will use more.
If you're using thirty instances of various apps combined the
iPad will certainly need charging after a short period of time.
What would be of assistance is for you to list the apps
that your using in one project that experiences battery drain.
For instance
Eventide Undulator x 1
Tonestack Pro x 3
MixBox x 5
Velvet Machine x 1
Of course, here is a specific one from this morning:
8 pure Drambo subtractive synth tracks
1 x Eventide BlackHole
1 x Tape Pro in delay mode
1 x TB EQ; 4 bands active
1 x TB Enhancer
1 x DDMF Compressor
in about 35 minutes battery went from 69% to 47%.
Are any of these effects known for high battery consumption?
Thank you.
How many oscillators are you using in these synths and how many of these synths are you using?
As you are using quite cpu intensive apps alongside dRambo then
you will experience high battery consumption which is inevitable.
How intensive these are I don’t know except for TB EQ
which I tend to use sparingly as it can be quite intensive.
35 minutes for a more recent model iPad is quite unusual.
I’ll let someone less chime in here for the apps that I don’t have.
The eight tracks were copies of each other. Each had exactly one basic VCO, analog VCF, ADSR, ENV, and 2 LFOs.
Thanks for the suggestions.
Just for reference, I just played with another patch that had three tracks each with 2 miRack instances. One had one Elements and one simple envleope, the other had one Clouds and four basic LFOs. The only effect was a blackhole on Send bus. Not only the battery went down from 43% to 22% very quickly, the back of the ipad got noticeably hot too. I think something unusual is happening.
With all these plugins running, that's to be expected I would say from my own experience.
Just for sake of thoroughness, you should reboot the iPad to be sure there aren’t any “ghost processes” running in the background, then check battery usage again.
Have you confirmed in Settings that drambo is the cause of the battery drain?
Does the battery monitor split its statistics into host vs. individual AUv3 plugins?
This, or something like it was the culprit. I installed the latest update and after a reboot the same patches that I listed above are running a lot cooler with little battery drain.
Thanks everyone for your suggestions.
No, but I've had dead processes, badly written apps and stuff like that eating my batteries more than once. So it's just meant as a basic step to make absolutely sure it's Drambo and plugins and not something else.
Is there any way to modulate knobs that are not modulatable (no small triangle to the left) other than using P-locks?
Trying to modulate the Scale knob in the CV Quantizer with an LFO. It works well with P-locks and the slider, but would like to try some automation on this.
Curious as to why all knobs are not made modulatable by default?