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
@tahiche No. This use case wasn't a common request but indeed, step components could be enhanced.
Would a "Length" slider on a Param Lock step component help?
Nice work @Michael_R_Grant you have received a thumb and sub from yours truly 🤪
hi. is it possible to set a different number of steps per track/pattern? (like on the octatrack)
for polymeter/-rhythm-stuff…
i don't mean the „steps per beat“ or „beats in pattern“ option!
I have reciprocated so that I can learn even more from a Drambo master!
Yes. You can also set different timing per track. Just tap this icon to adjust your Track timing and Track lengths (Scale in OT terminology)
@banalytic
There'a a "Jump" step component that allows you to jump from any position to any other position in a clip.
More features in this regard have been requested already so stay tuned 😊
Great!
Seems to be a lot going on in Drambo. It's quite an achievement that it manages to appear so clean and clear.
Only thing that's a slight downer is that it's not possible to hear the notes while changing velocity. I wonder if that could be snuck in as a global setting option
Good idea!
Yeah! It's crucial for sounds that have different samples at different velocity-layers, but generally really useful anyway
Time and resources no-doubt. A DAW is a hugely complicated piece of software and routing is deeply buried in the architecture. I'm sure it comes down to the developer's perceived importance of such a thing. The fact that just about every DAW has shipped out of the gate without the requisite routing to record AU Midi output backs that up. Unfortunately, if that aspect wasn't accounted for in the original architecture of the program, re-fitting it is likely a big job. Just maintaining a DAW for these individual developers or small teams, while trying to work in the never-ending pile of other feature requests, is as much as most can handle as it is.
Is there a good tutorial on MIDI routing in Drambo? Particularly with using master controller scripts (mozaic) that EVERYTHING gets routed to and from? I.E. all controllers go to it then out to their respective tracks, and MIDI out of that track/instrument/au also gets routed back into the script (to update the controllers).
I'm have a bear wrapping my head around the midi routing and how to best view/follow previously made connections.
Drambo standalone? Or Drambo in AUM or some other DAW? The answers are totally different depending on this question.
In standalone, your Mozaic script would need to go on the Main track so that it's "to the left" of anything else you want to route the midi to. Then you'd need to have midi out modules on each track to handle the routing back to the controller.
In AUM you would send everything to Mozaic and from there to Drambo. Then you'd use midi channel filtering on each Drambo track to handle the routing. You'd use midi out modules to route back to the mozaic script.
Yep, good plan.
No issues with routing the midi from say Track 15 back to the main track in the script? Isnt there a signal flows left to right, top to bottom?
I dont have issues getting midi into or out of drambo (to and from other hosts and apps)..its the rats nest of routing I will need to address. I could mock something up in the AUM matrix what the routing will look like, but to give you an idea, theres 4-6 controller scripts...and ~20-30 midi endpoints that all will need to get routed back to scripts on the master track. None of the controller scripts get routed to each other...
(this midi is also get split/duplicated (a fair amount) and routed outside of the ipad, but i'll probably handle this at the coreMIDI level)
There would be an issue routing back to the main track. I think I read earlier that there's a feedback module that might be used for this.
As for the rest. Sorry, I don't think I can get my brain around what you're trying to do. Not gonna even try. Sorry.
Thanks! At least it's not a limitation of AUv3, so there's hope
Anyway, I know this is off-top (And I'll really stop this line of questioning now), but can you think off the top of your head which DAW do allow it?
thanks for info! also @echoopera
No, not off the top of my head. Probably others can chime in on this.
I can say with reasonable certainty that of those none can do full MPE recording with any accuracy though. And providing editing capability for MPE is a huge challenge technically and especially from a UI perspective.
Something to help out Koala users inside of Drambo. Had a tough time getting the midi to record by just using the pads in Koala. Turns out midi route from the midi tools suite by Victor Porof right after Koala allows the midi to be recorded by using the pads within koala. In Koala midi settings midi map must be selected and everything else off. Not sure if there is a better way to achieve this with the Drambo modules but I couldn't get it to work.
MPE = MidiPlaguE
Haha. It's pretty simple really. I really only need help wrapping my head around the internal routing in drambo. The rest (splitting and doing the coreMIDI stuff), I already can do...it how to handle it all once its in drambo.
Script 1 -----> controller ------> 5ish apps (say tracks 1-5)
|
V
Script 1(for cc logging and recall)
Repeat the above about 5 times
Edit! Well my formatting didn't work
(There's a ton of lighting control and stuff that goes on as well)
I remember the developer of Xequence 2 giving it a serious try long ago but he dropped it at some point.
Too much work for too few people using it.
I can get a multi-out auv3 to output audio to different tracks, but is it possible to feed the midi from each track back into the auv3? 🤔
Basically what i'm asking above. Routing source midi back onto itself (but on different tracks).
Yes, the right and downwards flow is true for every signal.
MIDI routing is still in its infancy but the current #1 workaround is to have an app like FreEWI or Streambyter standalone running in the background and route MIDI like this:
This will allow you to record the MIDI output of an AUv3 MIDI plugin on the same track. Or on any other track.
@rs2000 so its not as simple as dropping a midi output on a track and routing it output back to the main track?
If the workaround is run streambyter in the background, then I would just do that at the coreMIDI level before it goes to drambo and grab it on the way out as well. Rewriting 1000-line mozaic scripts in streambyter isnt gonna be fun (especially when i dont know it). Maybe Mozaic standalone, which will have its own issues (like only being able to run 1 script standalone).
I guess the other option is to host drambo in something else and figure it out in that host, but thats a whole different issue (and nothing to do with the MIDI).
@AlmostAnonymous
No!
You can keep using Mozaic, Streambyter running as a standalone in the background will do nothing but mirror incoming MIDI to its own virtual MIDI port that can be used as an input in Drambo. As you can see in my screenshots.
https://apps.apple.com/us/app/midiflow/id879915554
That's worked for me previously. You can also do this kind of stuff in Mozaic relatively easily, so you don't have to use Streambyter.
Zenbeat and Cubasis does record Auv3Midi to the same track.. thought I had Blueverk’s Route to MiDi working earlier.. but..
Edit.. yes BlueVerk RTM does it ..
See my last post on the previous page. It does work.