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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Drambo generative question

124

Comments

  • edited November 2025

    @Squishy said:
    So many nuggets of drambo wisdom in here to unpack! Just wanted to pop in and say thanks to everyone contributing. Super helpful 🤙

    Was just about to post the same thing. I love the drambo question threads as it lures out the likes of @wim @rs2000 @tyslothrop1 @timfromtheborder (and others)

    You guys are appreciated.

  • It is so helpful to have input from these guys while learning something as deep as Drambo. Not joking, but I might have brushed it off as too complicated and abandonned it without their presence and generosity. Instead, it sparked my modular journey and I look forward to learn more and more.

  • @oscillotus said:
    It is so helpful to have input from these guys while learning something as deep as Drambo. Not joking, but I might have brushed it off as too complicated and abandonned it without their presence and generosity. Instead, it sparked my modular journey and I look forward to learn more and more.

    Regarding Drambo in general...
    ...personally I've learned it 'the hard way' (ie. 'Learning By Doing' since the early pre-release betas) and still learn new more efficient ways of doing the things I need it to do.

    Even after all these years I still can't say I know 'everything' there is to know about Drambo :sunglasses:

    The positive in this has been that I've been able to drastically cut down on getting new apps simply by asking myself a question like "Can it be done With Drambo?". If the answer is yes then I've saved myself a buck or two.

    I encourage all users to ask how things can be done with Drambo as it's a good way to use long-timers to also refresh the current knowledge base, this doesn't mean 'ready cooked solution' but rather guidance on their Drambo journey.

    It's like the saying, "Don't give the man a fish but learn him to fish instead" really holds true regarding learning to use the more advanced apps.

  • wimwim
    edited November 2025

    Learning modular apps has improved my understanding of other synths. As I learned to piece together a few basic synths and generative patches, I had a better feel for the architecture of any synth, which in turn has helped me with sound design.

    I love threads like this which nudge me to open an app and explore it in new ways. I don't remember having done a generative patch in Drambo, only miRack. I had a great time and also got a new appreciation for Drambo's power.

    I find patching a little easier to follow in miRack, but I feel like Drambo has the edge in overall power and speed of adding, and moving modules. I'm glad this new avenue opened up for me. 👍🏼

  • wimwim
    edited November 2025

    I still think it's funny that I lose interest in listening to generative patch based music after a few minutes ... unless I patched it together myself. Then I can enjoy listening for a long time, even to an inferior patch. 🙃

  • edited November 2025

    @Samu said:

    @oscillotus said:
    It is so helpful to have input from these guys while learning something as deep as Drambo. Not joking, but I might have brushed it off as too complicated and abandonned it without their presence and generosity. Instead, it sparked my modular journey and I look forward to learn more and more.

    Regarding Drambo in general...
    ...personally I've learned it 'the hard way' (ie. 'Learning By Doing' since the early pre-release betas) and still learn new more efficient ways of doing the things I need it to do.

    Even after all these years I still can't say I know 'everything' there is to know about Drambo :sunglasses:

    The positive in this has been that I've been able to drastically cut down on getting new apps simply by asking myself a question like "Can it be done With Drambo?". If the answer is yes then I've saved myself a buck or two.

    I encourage all users to ask how things can be done with Drambo as it's a good way to use long-timers to also refresh the current knowledge base, this doesn't mean 'ready cooked solution' but rather guidance on their Drambo journey.

    It's like the saying, "Don't give the man a fish but learn him to fish instead" really holds true regarding learning to use the more advanced apps.

    Funny thing is I feel the same with buying apps, I'm sure it will help save some bucks. But I have to speak to myself not to indulge in an eurorack... yet 🙈 Oh my, oh my, this is a disaster in the making...! 💸

  • @wim said:
    I still think it's funny that I lose interest in generative patch based music after a few minutes ... unless I patched it together myself. Then I can enjoy listening for a long time, even to an inferior patch. 🙃

    I first told myself, why should I even care to do shitty patches to begin with, when there are such great ones out there. But I had so much fun manipulating the ones I made myself. I think it has to do with the simplicity and the immediate knowledge of the purpose of each module.

  • edited November 2025

    @wim said:
    I still think it's funny that I lose interest in listening to generative patch based music after a few minutes ... unless I patched it together myself. Then I can enjoy listening for a long time, even to an inferior patch. 🙃

    I have the same problem, I love listening to crazy generative patches… if they are my own 😄 nobody else seems to have the patience but that’s ok

  • @wim said:
    I still think it's funny that I lose interest in listening to generative patch based music after a few minutes ... unless I patched it together myself. Then I can enjoy listening for a long time, even to an inferior patch. 🙃

  • edited November 2025

    @timfromtheborder said:

    @wim said:
    I still think it's funny that I lose interest in listening to generative patch based music after a few minutes ... unless I patched it together myself. Then I can enjoy listening for a long time, even to an inferior patch. 🙃

    Yeah that’s about it although I hate to agree with the donkey on the right

  • Is there a way to multiply a synced lfos time? I'd like to go past 16 bars. The pulse divider would be perfect, but it changes the shape of the wave...

  • @oscillotus said:
    Is there a way to multiply a synced lfos time? I'd like to go past 16 bars. The pulse divider would be perfect, but it changes the shape of the wave...

    Use a Mini LFO and hook it up to a Scale Time module. Transport Time so it doesn’t reset with the playhead. You’ll have to do your own calculation.

  • @timfromtheborder said:

    @oscillotus said:
    Is there a way to multiply a synced lfos time? I'd like to go past 16 bars. The pulse divider would be perfect, but it changes the shape of the wave...

    Use a Mini LFO and hook it up to a Scale Time module. Transport Time so it doesn’t reset with the playhead. You’ll have to do your own calculation.

    Damn I was close, I had this setup minus the Transport Time. Thanks :)

  • Is there a reason why the normal LFO doesn't have this clock input?

  • @oscillotus said:
    Is there a reason why the normal LFO doesn't have this clock input?

    I guess it would clash with the sync options already in there. Like the program sync is super useful. Just use the one that suits the situation.

  • @wim said:
    I still think it's funny that I lose interest in listening to generative patch based music after a few minutes ... unless I patched it together myself. Then I can enjoy listening for a long time, even to an inferior patch. 🙃

    Exactly the reason why I started building my own. Including my own weird preferences of course 😅

  • @oscillotus said:
    Is there a reason why the normal LFO doesn't have this clock input?

    Just one of many design decisions which are always a compromise between simplicity and functionality.
    But you're right, I don't see where a time input in the standard LFO would hurt.

  • I tried to create a rack with 4 lfos already set to specific frequencies that serve as song structure, but the rack has only 1 out and I can't plug anything directly into the lfos. Is there another way to achieve something like this?

  • Oh, I might need to use the Rack module and create the individual outputs myself. Will try that later!

  • @oscillotus said:
    Oh, I might need to use the Rack module and create the individual outputs myself. Will try that later!

    Exactly :)

  • @oscillotus said:
    Oh, I might need to use the Rack module and create the individual outputs myself. Will try that later!

    You could also use a Layers module. Also a nice way to organize things.

  • @timfromtheborder said:

    @oscillotus said:
    Oh, I might need to use the Rack module and create the individual outputs myself. Will try that later!

    You could also use a Layers module. Also a nice way to organize things.

    Yeah, I began playing with Layer modules. They are neat! I like the idea of the Layer switch for example, but I haven't incorporated it in my workflow yet.

  • @oscillotus said:

    @timfromtheborder said:

    @oscillotus said:
    Oh, I might need to use the Rack module and create the individual outputs myself. Will try that later!

    You could also use a Layers module. Also a nice way to organize things.

    Yeah, I began playing with Layer modules. They are neat! I like the idea of the Layer switch for example, but I haven't incorporated it in my workflow yet.

    I use the layerswitch a lot. There are very easy use cases. For starters if you have an FX, you don't need on all the time, put it in a layer switch add an empty layer and you can switch it off and save CPU, if that setting is on.

    Another would be a number of CV-sequencers to switch between. You can start with one, put a seq in, you like, copy that into another layer, slightly change it, copy again... If you connect a synced LFO to the index, you can chain them, too.

    So many useful things you can do with the layerswitch.

  • edited November 2025

    You can also use the Layer Switch to have multiple instances of the same auv3 plugin, each having a different preset loaded. Use clip p-locking to change preset (or even step p-lock). It works well as long as the plugin is not too memory intensive (it doesn't work well with OneShot on my old ipad).

    For your collection of lfos the Misc/Rack is better, using multiple output signals. All the layers modules have only single output. I have done the same for having a collection of lfos and envelopes.

  • @bleep said:

    For your collection of lfos the Misc/Rack is better, using multiple output signals. All the layers modules have only single output. I have done the same for having a collection of lfos and envelopes.

    The basic Layers module has an output per layer.

  • Really great use cases. Love it! I look to find ways to create song structures without the use of a sequencer, mostly with lfos, so these will come in very handy to create variations.

    I was using the basic layers module already with Piano Motifs to separate midi channel 1/2/3 while staying in the same rack, but your ideas will definitely open some doors. Thanks :)

  • @timfromtheborder said:

    @bleep said:

    For your collection of lfos the Misc/Rack is better, using multiple output signals. All the layers modules have only single output. I have done the same for having a collection of lfos and envelopes.

    The basic Layers module has an output per layer.

    I will try that, as it can reduce side scrolling when having a lot of modules. I like the idea of having things ordered in tabs. Thanks!

  • @oscillotus you can create interesting structure/variation using the Switch 1-N/N-1 modules as well, which can be triggered with gates. You can use them to make different signal paths. Switch 1-N is 1 input into N outputs — Switch N-1 is N inputs into 1 output. This is a way to increase side scrolling ;)

  • Haha! This seems way out of my league, for now at least. But when I get there, I'll come back to this message! I have a hard time to wrap my head around the math and conditional modules.

  • It is not so hard :smile: Here is a good experiment using the switch modules, you end up with some nice bleeping drones.

Sign In or Register to comment.