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 is an AU host now / the new Drambo mega thread

1484951535464

Comments

  • @xraydash said:
    @Gravitas @xor
    Got it! Using p-locks for xor’s switch idea on the first and last steps of a four bar pattern, you can automate the resync. Here’s the breakdown:

    As long as you got it working
    the way you need it to.

    Well done.

  • @xraydash said:
    @Gravitas @xor
    Got it! Using p-locks for xor’s switch idea on the first and last steps of a four bar pattern, you can automate the resync. Here’s the breakdown:

    That’s awesome. Here’s an automated version that resets every 10 steps...

    If you want to set this up yourself pay close attention to the delay configuration. I found that about 30ms is needed to properly reset the euclidian sequencer. Set the “number” component to one less than the number of steps you want before the reset.

    There’s one headache with this approach. The euclidian sequencer automatically resets when the transport starts. The counter does not. This messes up the auto-reset behavior. I’ve run into these inconsistencies before in Drambo and I don’t know if they’re intentional design choices or just accidental behavior. As a really hacky workaround I use the trigger button to manually reset the counter before I hit start. That way the sequencer, counter, and transport are all in sync. Wouldn’t it be nice if the track had a start trigger that you could use? Maybe @giku_beepstreet or @rs2000 might know of a better solution.

  • @xor can you send me the project file?

  • edited April 2021

    Thanks. Can you explain why you've chosen that rather complicated setup?
    What are you trying to achieve by modifying the Euclidian's time signal?

    Edit: Just found an inconsistency in how the Euclidean sequencer handles the time signal. To be continued 😉

  • @rs2000 said:

    Thanks. Can you explain why you've chosen that rather complicated setup?
    What are you trying to achieve by modifying the Euclidian's time signal?

    Edit: Just found an inconsistency in how the Euclidean sequencer handles the time signal. To be continued 😉

    There’s a post back on https://forum.audiob.us/discussion/42554/drambo-is-an-au-host-now-the-new-drambo-mega-thread/p50 asking how to reset the euclidian sequencer. It doesn’t have a reset input (new feature request?). It doesn’t reset when a reset time module resets (probably a good thing since there’s no way to differentiate a reset from a wrap-to-zero).

    I figured out that if you remove the clock for a short period of time that it resets. I tried using an x-fader but couldn’t get the binary a/b automation working so settled on a n-1 switch.

    Every Nth step we want to briefly toggle the output of the switch from the clock to nothing. We can use a counter (of a clock generator, the track’s clock wouldn’t work) and an A>B function as the switch’s index input and then route that back to the counter’s reset input via feedback so the counter resets back to 0 whenever the clock is cut. I found that the delay had to be about 30ms or the euclidian sequencer wouldn’t recognize the absence of the clock signal.

    The euclidian sequencer automatically resets when transport starts but a counter doesn’t. (It seems like it would be nice if everything behaved in the same way or at least had the option to). If you stop and restart transport the counter and euclidian sequencer are now out-of-sync. I couldn’t figure out any way to auto-clear the counter on transport start so hooked up a button you could press to clear it manually. (It might be nice to have a transport start signal available either through a plug in the track header or a separate module so that you could clear a counter. A fallback would to add a reset-on-start option to the counter and other modules that might benefit from it.)

    Hope that clears it all up. :)

  • Couple of questions...
    1. What does the little 1 in a circle mean for the Audio Output module? It's visible when you go to load it from the library.
    Does it output a mono signal? Is that different to a multi-bus out channel? I thought they were stereo? (Using Drambo hosted in AUM) I can see how an audio output to a soundcard would be mono, but I thought the multi-bus outs were stereo?

    1. I cant seem to use my external bluetooth keyboard for typing inside a text box module. Works for everything else eg: renaming text box module etc but typing inside the text section doesn't. Anyone else have this issue?
  • edited April 2021

    @soundtemple said:
    Couple of questions...
    1. What does the little 1 in a circle mean for the Audio Output module? It's visible when you go to load it from the library.
    Does it output a mono signal? Is that different to a multi-bus out channel? I thought they were stereo? (Using Drambo hosted in AUM) I can see how an audio output to a soundcard would be mono, but I thought the multi-bus outs were stereo?

    1. I cant seem to use my external bluetooth keyboard for typing inside a text box module. Works for everything else eg: renaming text box module etc but typing inside the text section doesn't. Anyone else have this issue?

    1) all modules handle polyphony by multiplying their signals internally, modules with circled 1 will ‘merge’ polyphonic signals down to 1 voice. They can be mono or stereo.

    2) it may have something to do with D auto selecting keyboard layout according to the input field. @giku_beepstreet

  • edited April 2021

    @xor You know, the time signal is like a rising linear ramp that is evaluated by a number of modules as the beat position inside the pattern. Changing that voltage will make a module with CV input jump to the respective time position.
    The Euclidean sequencer seems to be the only one which does not follow this behavior and in addition to "fixing" it, I've suggested to add a menu option that lets you choose whether to reset with each pattern wraparound.

    As for your suggestion to have a transport module with various outputs regarding transport state, position 1 indicator etc., this is planned indeed.

    But my question was rather about what you wanted to achieve with your project in the first place. Is it that you want the Euclidean seq to pause for 1 step duration every 9th step and then continue where it had paused?
    I'm asking because that could be done by modulating the offset knob.

  • @rs2000 said:
    @xor You know, the time signal is like a rising linear ramp that is evaluated by a number of modules as the beat position inside the pattern. Changing that voltage will make a module with CV input jump to the respective time position.
    The Euclidean sequencer seems to be the only one which does not follow this behavior and in addition to "fixing" it, I've suggested to add a menu option that lets you choose whether to reset with each pattern wraparound.

    As for your suggestion to have a transport module with various outputs regarding transport state, position 1 indicator etc., this is planned indeed.

    But my question was rather about what you wanted to achieve with your project in the first place. Is it that you want the Euclidean seq to pause for 1 step duration every 9th step and then continue where it had paused?
    I'm asking because that could be done by modulating the offset knob.

    I think they just wanted to reset all the sequencers back to their initial positions after a number of bars, here was the initial conversation...

    @xraydash said:

    @Gravitas said:
    @sigma79

    Here’s an article that explains ,’Euclidean sequencers’, and why they are designed the way they are.

    https://www.musicradar.com/how-to/what-is-euclidean-sequencing-and-how-do-you-use-it

    How would you resync the Euclidean sequencers after so many bars as described in this article? I played around with the counter and retrigger modules, but this is beyond my grasp.

  • @xor said:

    @rs2000 said:
    @xor You know, the time signal is like a rising linear ramp that is evaluated by a number of modules as the beat position inside the pattern. Changing that voltage will make a module with CV input jump to the respective time position.
    The Euclidean sequencer seems to be the only one which does not follow this behavior and in addition to "fixing" it, I've suggested to add a menu option that lets you choose whether to reset with each pattern wraparound.

    As for your suggestion to have a transport module with various outputs regarding transport state, position 1 indicator etc., this is planned indeed.

    But my question was rather about what you wanted to achieve with your project in the first place. Is it that you want the Euclidean seq to pause for 1 step duration every 9th step and then continue where it had paused?
    I'm asking because that could be done by modulating the offset knob.

    I think they just wanted to reset all the sequencers back to their initial positions after a number of bars, here was the initial conversation...

    @xraydash said:

    @Gravitas said:
    @sigma79

    Here’s an article that explains ,’Euclidean sequencers’, and why they are designed the way they are.

    https://www.musicradar.com/how-to/what-is-euclidean-sequencing-and-how-do-you-use-it

    How would you resync the Euclidean sequencers after so many bars as described in this article? I played around with the counter and retrigger modules, but this is beyond my grasp.

    Ah OK, thanks, let's first wait for the response from @giku_beepstreet regarding the Euclidean seq, how it handles the time signal and the future transport module.

  • I'm wanting a modular drum machine. Thought I might try Drambo for this. Is there one already baked? Failing that, where do I start please?

  • edited April 2021

    Whats the best way to remove a sequence if you dont see screen?

    Say a kick drum to the standard sequencer only.

    Ideally via a knob from right to left or just a button press.

    This would also be a good system for melodies that work on a track basis ( not a pattern to pattern basis )

    and the knob version could also be a good system for the track length update but as I say might also be good if it can remove midi from grid.

    I think.

    edit. I can test with the screen visible.

  • @ashh said:
    I'm wanting a modular drum machine. Thought I might try Drambo for this. Is there one already baked? Failing that, where do I start please?

    You can start with Patchstorage and the Sampler modules in the D itself.
    Patches for an 808 hi-hat and Buchla type percussion were uploaded recently
    and there are plenty of other ready made percussive sounds available.

  • Is there a way to keep the smooth transition of transposing Euclidean via midi. Like when you disconnect the midi in the euclidean but also be able add notes via screen based on what the euclidean note is but also transpose every note on the standard sequencer, when you transpose the euclidean sequencer via midi.

    Only thing I can think of keeping the sequencer highlighted green but you cant add any note in any position on sequencer.

    So need to transpose Euclidean as I were shown and to not get the additional note from a keyboard when changing euclidean note. This still allow notes to normal sequencer via screen based on what you euclidean note is and master transpose all notes on normal sequencer when transposing or changing note on euclidean via midi.

    Goal is to use normal sequencer to add rolls/repeats to Euclidean sequencer.

    Thanks.

  • If I disconnect midi in Euclidean the notes on normal sequencer dont play. Although I think they still set the note of the Euclidean. Adding a note on the sequencer additionally to the Euclidean sequence creates good rolls/repates. Id need to turn off midi in Euclidean. So that changing note dosent re-trigger via keyboard. That were fixed by Tahiche ( the genius ) and said theres a way to then go to normal sequencer mode.

    Be able to input normal sequencer notes on screen to what the euclidean note is set to but also change all the note steps on normal sequencer, when I change note of the euclidean.

  • edited April 2021

    Thats all I need. An aum master volume side. Adding additional kick notes via screen that dont affect the euclidean note but both respond to midi keyboard. A sequencer wipe via knob for synths so that I can switch presets of synths in Aum, without spiking cpu? And then a global kit launch via Drambo, which would only work for me, when Drambo can be more than 8 multiouts.

    Thanks.

    Edit.
    Adding beats on sequencer live isnt good. Unless you find a rythum or maybe add beats to patterns ( after a track ) sort of editing.

  • Quick question for all you drambo masters. Been searching but I haven't yet found a solution. I am trying to get a flexisampler to respond to velocity when set to loop. I turn up the velocity knob and works fine in 1-shot or 1-slice but when set to loop triggering the loops is at a fixed volume. Thanks in advance to someone that can help with this hopefully simple oversight?

  • never mind - looks like just an amp env after Flexi - sorry.> @mikewb said:

    Quick question for all you drambo masters. Been searching but I haven't yet found a solution. I am trying to get a flexisampler to respond to velocity when set to loop. I turn up the velocity knob and works fine in 1-shot or 1-slice but when set to loop triggering the loops is at a fixed volume. Thanks in advance to someone that can help with this hopefully simple oversight?

  • Euclidean Launcher v1.

    Though based upon rs2000’s Loop Launcher v1,
    this Euclidean sequencer patch is
    launched using midi notes rather than
    using the velocity pads on the screen.
    Assign the required midi note using the ,’midi filter’, module
    and hit start and stop in the time with ,’Transport’.
    The default note is C3.
    To change the sound and the default midi note?
    Expand the instrument rack and you will
    see both the ,’midi filter’, module
    and the ,’Flexi Sampler’, module.

    Enjoy.

    https://patchstorage.com/euclidean-launcher-v1/

  • @rs2000 said:

    @xor said:

    @rs2000 said:
    @xor You know, the time signal is like a rising linear ramp that is evaluated by a number of modules as the beat position inside the pattern. Changing that voltage will make a module with CV input jump to the respective time position.
    The Euclidean sequencer seems to be the only one which does not follow this behavior and in addition to "fixing" it, I've suggested to add a menu option that lets you choose whether to reset with each pattern wraparound.

    As for your suggestion to have a transport module with various outputs regarding transport state, position 1 indicator etc., this is planned indeed.

    But my question was rather about what you wanted to achieve with your project in the first place. Is it that you want the Euclidean seq to pause for 1 step duration every 9th step and then continue where it had paused?
    I'm asking because that could be done by modulating the offset knob.

    I think they just wanted to reset all the sequencers back to their initial positions after a number of bars, here was the initial conversation...

    @xraydash said:

    @Gravitas said:
    @sigma79

    Here’s an article that explains ,’Euclidean sequencers’, and why they are designed the way they are.

    https://www.musicradar.com/how-to/what-is-euclidean-sequencing-and-how-do-you-use-it

    How would you resync the Euclidean sequencers after so many bars as described in this article? I played around with the counter and retrigger modules, but this is beyond my grasp.

    Ah OK, thanks, let's first wait for the response from @giku_beepstreet regarding the Euclidean seq, how it handles the time signal and the future transport module.

    Yes, I incorporated p-locks with xor’s switch as the solution to my little experiment. I’m following your conversation and further reset/sync Euclidean builds with interest though.

  • Hi All - Just discovered that Drambo can host an instance of LK, with LK Matrix visibly sending CC messages to the midi monitor in Drambo. Very cool! I'd like to connect my LK automation lane CC to the Drambo master channel volume for automated fades, but mapping to the master out does not work. If LK is opened outside of Drambo as a stand alone, then it does work. Any thoughts on how to send CC internally from the hosted LK instance to Drambo's master out knob? Does it need some type of MIDI utility between them?

  • edited April 2021

    @baccharis said:
    Hi All - Just discovered that Drambo can host an instance of LK, with LK Matrix visibly sending CC messages to the midi monitor in Drambo. Very cool! I'd like to connect my LK automation lane CC to the Drambo master channel volume for automated fades, but mapping to the master out does not work. If LK is opened outside of Drambo as a stand alone, then it does work. Any thoughts on how to send CC internally from the hosted LK instance to Drambo's master out knob? Does it need some type of MIDI utility between them?

    Direct midi cannot be internally routed within Drambo currently. To do what you’re talking about with would require ‘midi loopback’. Some folks use loopback to bounce midi from the tracks to the main Drambo sequencer, though I forget the details and additional routing apps they are using.

    However, you don’t NEED to use midi. Just add a CC MODULATOR module (midi section) after LK. You can either learn the CC, or manually assign it. This will convert the CC message from LK into a cv signal, which you can then route directly to the Master volume. The only caveat is that there will be a slight delay from the slewing of the CC signal to ensure smooth transitions.

    (Pretend Atom2 in my screenshot is LK)

  • @aleyas thanks! I'll give that a try. It did seem strange trying to both send and receive midi inside Drambo

  • It seems to me like a MIDI to CV module would solve these kinds of issues. I've always wondered why there isn't one.

  • edited April 2021

    @ wim. Don’t you mean CV to MIDI?
    I also missed that the other day. But i must be honest and admid that i can’t remember why 😂

Sign In or Register to comment.