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 2.0 is LIVE!!!

1111214161761

Comments

  • @drewinnit said:

    @prtr_jan said:
    How to go about recording stems?

    Tap the icon that looks like tape reels, it’s there on each mixer channel for individual stems and the top one is for the master out.

    You still have to tap the tape icon up top to record any stems. If you don’t arm any tracks with their individual tape icon, tapping the top one arms master track.

  • @drewinnit said:

    @prtr_jan said:
    How to go about recording stems?

    Tap the icon that looks like tape reels, it’s there on each mixer channel for individual stems and the top one is for the master out.

    Ah great! So simple. Thanks!

  • @MadGav, @jsmonzani
    Both are issues indeed, will report them. Thanks.

  • edited May 2022

    Anybody else seeing this issue? It’s replicatable, Audio Units don’t load with the autosaved project if Drambo is kicked out of memory by iOS. Force quit from the task manager doesn’t seem to have the same issue, but it happens every time I return to Drambo after using a bunch of other apps.

    iPhone SE 2020, iOS 15.5

    Can anybody else replicate? @giku_beepstreet

  • @ahallam Yes, if the AUv3 is "dead", maybe Drambo should automatically try to re-load it?

    So far, Drambo is careful enough to not automatically re-load something that crashed - be it an AUv3 or a project that crashed Drambo the last time it was run. It's about avoiding crash loops.

  • @MadGav said:

    @0tolerance4silence said:
    Imo it works as intended...
    The three buttons are not all grouped together.
    The first is your layout selector - you can decide whether you prefer keyboard or pads as your input device. This one is ‘sticky’, remembering its state.
    The other two (TRK, PAT) are pad modes. Tapping them once will enter mode, second time will exit mode, or you switch between modes.
    This mechanism supports temporary mode selection... f.e hold PAT to enter mode, release PAT to go back to your input device.
    When you are in one of the modes (PAT or TRK) and you tap layout selector button, you effectively do two things - exit mode and switch layout.

    It’s clearly inconsistent, taking your approach the layout selector should do nothing visible when either PAT or TRK is selected, which is not the case. Doing nothing visible isn’t useful, so I still put forward my suggestion.

    Not against ideas or improvements, just explaining currently implemented mechanism and it’s benefits :)

  • @yowza said:
    This is an example of what I was talking about earlier where iOS tends to cater to a certain kind of electronic musician but leaves out basic things that a non iOS musician would expect to be there.

    I see these kind of comments a lot and find them kind of funny.

    Odd time sigs and tempo changes have always been a cinch in most any iOS apps and Drambo especially, it just involves looking at things differently.

  • @jaijai said:
    I was GASsing hard on some new hardware which were announced at Superbooth. This release of Drambo cured it. This update is just so awesome. Thank you for al your hard work and dedication.
    I feel like buying you a coffee @giku_beepstreet , I could not find a donate button on your site. Please let me know, how I can buy you a coffee/beer :)

    The OP1field it keeps calling out to me.....
    I don't know if Drambo will be enough.......LOL!

  • edited May 2022

    @rs2000 said:
    @ahallam Yes, if the AUv3 is "dead", maybe Drambo should automatically try to re-load it?

    So far, Drambo is careful enough to not automatically re-load something that crashed - be it an AUv3 or a project that crashed Drambo the last time it was run. It's about avoiding crash loops.

    Makes sense, but I can’t say that I’ve ever experienced similar behaviour from any other auv3 host app. Even if you reload the audio unit, you still have to go into the app and reload the patch, which would be a pain if you were running Drambo just as a host for AUs. I’ve also never experienced it in Drambo before this release, and my usage behaviour on my devices is quite consistent.

    Given that terminating background apps is an expected part of iOS memory/resource management, it couldn’t really be considered a crash. It seems like it’s more like a failure in loading the saved state.

    The curious part is how manually terminating the app doesn’t show the same behaviour at all AFAICT, I’ve only seen it if Drambo has been terminated as part of the normal iOS resource management processes.

    I’m willing to concede that it may be related to running iOS betas, which is why I’d like to know if anyone else can replicate this behaviour on public iOS releases.

  • @Gravitas said:

    @Skyblazer said:

    @Gravitas said:

    @yowza said:

    @Gravitas said:

    You don’t actually have to build anything in dRambo.
    Use auv3’s for both instruments and effects as with any other
    DAW/groovebox/music program and use dRambo for the sequencing.
    dRambo is a modular playground and it’s now a fully fledged sequencer.
    Saying that “horses for courses”, if it doesn’t rock your boat then it doesn’t.

    Can the Drambo sequencer do tempo changes and different time signatures in the same song?

    To do tempo changes you would have to map a cc to Tempo and automate that.
    You would need something like FreEwi to do it.

    We’ve been discussing time signatures recently.
    There’s a couple of ways to do this.
    There’s a poly speed thingy and you could also use Jump components
    to create subdivisions via Steps per beat so instead of having
    the sequencer play all 16 steps you get it to play only 14 steps.
    I’ve yet to fully explore true polyrhythms via dRambo so this is good question for me also.

    Correct me if I'm wrong, but I think "Song Mode" will always play a multiple of 16 steps per clip. So if I use the "Jump" condition on the 7th step, it will repeat the sequence twice, and then play the first two steps again. Or it can play two other steps from that clip. But it cannot jump to the next clip.

    Using a combination of Jump, Cycle and Retrig you can do
    odd time signatures and the maximum steps in a Clip is 64 steps.

    Screenshot.

    So basically, if you're composing in an odd time signature, and you want to write a full song, eventually you need to have a NoteOff that coincides with a multiple of 16.

    See above.

    I think it would be fair to say that "support for odd time signatures" has become the "most requested feature of the AudioBus forum Drambo 2.0 release exploration extravaganza". :)

    Agreed, it has.

    I set it up exactly as you have it in the screenshot, and it's not advancing to the next pattern. It plays those 14 notes, and then it plays the first two notes again, before advancing to the next pattern. I must be missing something here.

    I also can't figure out what the "Retrig" does; it doesn't seem to do the same thing as the new "Retrig" bar graph page...I feel like it did do the same thing as that page, before.

    I understand "Cycle Condition", but that's for variations when the same sequence is repeating.

  • @yowza - to save time and everyones energy I think you might do better to look at a linear sequencer like Cubasis which will be better suited to the types of music that you seem to be pointing to. Drambo started its journey as a step driven pattern sequencer which as you probably know has roots in early electronic music and drum machines, hence its underlying grid like structure. There are other sequencers like Cubasis which are in some ways more suited to capturing and editing the nuances of traditional performative instruments.

  • @ahallam said:

    @rs2000 said:
    @ahallam Yes, if the AUv3 is "dead", maybe Drambo should automatically try to re-load it?

    So far, Drambo is careful enough to not automatically re-load something that crashed - be it an AUv3 or a project that crashed Drambo the last time it was run. It's about avoiding crash loops.

    Makes sense, but I can’t say that I’ve ever experienced similar behaviour from any other auv3 host app. Even if you reload the audio unit, you still have to go into the app and reload the patch, which would be a pain if you were running Drambo just as a host for AUs. I’ve also never experienced it in Drambo before this release, and my usage behaviour on my devices is quite consistent.

    Given that terminating background apps is an expected part of iOS memory/resource management, it couldn’t really be considered a crash. It seems like it’s more like a failure in loading the saved state.

    The curious part is how manually terminating the app doesn’t show the same behaviour at all AFAICT, I’ve only seen it if Drambo has been terminated as part of the normal iOS resource management processes.

    I’m willing to concede that it may be related to running iOS betas, which is why I’d like to know if anyone else can replicate this behaviour on public iOS releases.

    @ahallam this happened to me all the time before v2 when Drambo is in the background with my iphone, on which I have background audio disabled, and the behavior remains unchanged after the update. Reloading from _autosaved has always worked for me. Nevertheless, I did report it to Giku directly along with another issue now that the big update is out.

    With background audio enabled this never happens to me; I keep a session always running on my ipad. I did have a different issue with memory leaking in this case which was solved in v2.

  • @Grandbear said:

    @ahallam said:

    @rs2000 said:
    @ahallam Yes, if the AUv3 is "dead", maybe Drambo should automatically try to re-load it?

    So far, Drambo is careful enough to not automatically re-load something that crashed - be it an AUv3 or a project that crashed Drambo the last time it was run. It's about avoiding crash loops.

    Makes sense, but I can’t say that I’ve ever experienced similar behaviour from any other auv3 host app. Even if you reload the audio unit, you still have to go into the app and reload the patch, which would be a pain if you were running Drambo just as a host for AUs. I’ve also never experienced it in Drambo before this release, and my usage behaviour on my devices is quite consistent.

    Given that terminating background apps is an expected part of iOS memory/resource management, it couldn’t really be considered a crash. It seems like it’s more like a failure in loading the saved state.

    The curious part is how manually terminating the app doesn’t show the same behaviour at all AFAICT, I’ve only seen it if Drambo has been terminated as part of the normal iOS resource management processes.

    I’m willing to concede that it may be related to running iOS betas, which is why I’d like to know if anyone else can replicate this behaviour on public iOS releases.

    @ahallam this happened to me all the time before v2 when Drambo is in the background with my iphone, on which I have background audio disabled, and the behavior remains unchanged after the update. Reloading from _autosaved has always worked for me. Nevertheless, I did report it to Giku directly along with another issue now that the big update is out.

    With background audio enabled this never happens to me; I keep a session always running on my ipad. I did have a different issue with memory leaking in this case which was solved in v2.

    I see, I do keep background audio turned off on apps on my phone. I have had way too many moments of playing with something on transit, then finding that an app with background audio had drained half my battery two hours later because iOS hadn’t terminated it. I’m glad at least that I’m not the only one that noticed it.

    All of this being said, I think that 2.0 is fantastic. My musically challenged monkey mind appreciates the piano roll and new sequencer functions a great deal. I didn’t expect this update to be as huge as it is. Thank you so much for your hard work @giku_beepstreet 💕💕

  • N00B Q: If you know nothing (self) and are thinking about committing to 'start from the start' all over again, am I (we) now a bit buggered because the original tuts will be V1 and new ones for V2 will presume you already know how things were? OR do you think if one just dives into the original tutorials all will be well? And if so (hope so :), best starting point at this moment in history?

  • edited May 2022

    @JohnnyGoodyear said:
    N00B Q: If you know nothing (self) and are thinking about committing to 'start from the start' all over again, am I (we) now a bit buggered because the original tuts will be V1 and new ones for V2 will presume you already know how things were? OR do you think if one just dives into the original tutorials all will be well? And if so (hope so :), best starting point at this moment in history?

    Ones regarding modules will be fine, but anything involving UI or workflow will be very out of date. Why don’t you give mine a go? They’re for beginners and returners!

    Sequencer and auto-grow recording:

    Clip mode and some tricks:

  • @ahallam said:

    @rs2000 said:
    @ahallam Yes, if the AUv3 is "dead", maybe Drambo should automatically try to re-load it?

    So far, Drambo is careful enough to not automatically re-load something that crashed - be it an AUv3 or a project that crashed Drambo the last time it was run. It's about avoiding crash loops.

    Makes sense, but I can’t say that I’ve ever experienced similar behaviour from any other auv3 host app. Even if you reload the audio unit, you still have to go into the app and reload the patch, which would be a pain if you were running Drambo just as a host for AUs. I’ve also never experienced it in Drambo before this release, and my usage behaviour on my devices is quite consistent.

    Given that terminating background apps is an expected part of iOS memory/resource management, it couldn’t really be considered a crash. It seems like it’s more like a failure in loading the saved state.

    The curious part is how manually terminating the app doesn’t show the same behaviour at all AFAICT, I’ve only seen it if Drambo has been terminated as part of the normal iOS resource management processes.

    I’m willing to concede that it may be related to running iOS betas, which is why I’d like to know if anyone else can replicate this behaviour on public iOS releases.

    Are you sure that Drambo is being terminated by the iOS resource management process (jetsam). If you look in Analytics , you can find a jetsam log at the time that will indicate the process that was terminated (search for "reason). Drambo is not very large, so I'd suspect it was one of the AUv3s that was killed by the system. If that happens, Drambo would experience that as a crash of the AUv3. The safest way would be to save your project and force-quit Drambo when not using it.

  • @uncledave said:

    @ahallam said:

    @rs2000 said:
    @ahallam Yes, if the AUv3 is "dead", maybe Drambo should automatically try to re-load it?

    So far, Drambo is careful enough to not automatically re-load something that crashed - be it an AUv3 or a project that crashed Drambo the last time it was run. It's about avoiding crash loops.

    Makes sense, but I can’t say that I’ve ever experienced similar behaviour from any other auv3 host app. Even if you reload the audio unit, you still have to go into the app and reload the patch, which would be a pain if you were running Drambo just as a host for AUs. I’ve also never experienced it in Drambo before this release, and my usage behaviour on my devices is quite consistent.

    Given that terminating background apps is an expected part of iOS memory/resource management, it couldn’t really be considered a crash. It seems like it’s more like a failure in loading the saved state.

    The curious part is how manually terminating the app doesn’t show the same behaviour at all AFAICT, I’ve only seen it if Drambo has been terminated as part of the normal iOS resource management processes.

    I’m willing to concede that it may be related to running iOS betas, which is why I’d like to know if anyone else can replicate this behaviour on public iOS releases.

    Are you sure that Drambo is being terminated by the iOS resource management process (jetsam). If you look in Analytics , you can find a jetsam log at the time that will indicate the process that was terminated (search for "reason). Drambo is not very large, so I'd suspect it was one of the AUv3s that was killed by the system. If that happens, Drambo would experience that as a crash of the AUv3. The safest way would be to save your project and force-quit Drambo when not using it.

    Yes, the safest way would be to always save my project :)

    I suspect that the reason I never encountered this before was because Drambo was presenting a blank slate every time I opened it rather than an auto save, so I was always loading a saved project.

  • @BroCoast said:

    @yowza said:
    This is an example of what I was talking about earlier where iOS tends to cater to a certain kind of electronic musician but leaves out basic things that a non iOS musician would expect to be there.

    I see these kind of comments a lot and find them kind of funny.

    Odd time sigs and tempo changes have always been a cinch in most any iOS apps and Drambo especially, it just involves looking at things differently.

    Right back at you, I find your type of comments as equally comical.

    I don't have Drambo (yet) so I can't comment on that other than to say that having to use any workaround to play different time signatures and switch between them is a total workflow killer for me. You might think it's no big deal but to many people it is. Compared to using Logic which easily lets you change tempo and time signature at will, many IOS apps often come off as toys in comparison. Please tell me which iOS apps let you do that without a workaround? NS2 and Auria and the old app Drum Studio come to mind but not much else.

    By all means you keep using your workarounds if that floats your boat.

  • edited May 2022

    @panthera86 said:
    is there a way to pitch "Noise" for snares?

    all my synth generated snares, sound the same.

    or better asked any tips? to get snare sounds in the realm of seekbeats or elastic drums?

    you can't really "pitch" noise cause it has no root note it is simply whole spectrum (all frequencies from bottom to top), so trchnically pitching up noise has same effect like hipass filter

    for different color of snare, use EQ (boost or attenuate certain frequencies - that's the trick).. ot you can use even filtering with some envelope.. Equalisation of noise is first of main 2 trick how to affect snare character

    also play with second snare layer which is responsible for snare "punch" - usually pitch modulated sine - there you can play with root pitch, putch modulation curve, add some overdrive, etc ..

  • I have paid for the waves iap on my iPad. But when I download Drambo on my iPhone, it won’t let me restore the purchase.. do we need to buy this waves iap again on each different device?

  • edited May 2022

    This Drambo version is really incredible.
    There’s row facilities I didn’t succeed to find
    is it possible to record audio in sync when using clip launcher
    Is it possible to load a Drambo project using a program change

    Thanks

  • @dokwok2 said:

    @eross said:
    is there a way to shit notes

    Reply like a Bosch!

  • @Samu said:

    @gusgranite said:

    @Grandbear said:

    @gusgranite said:
    Is there a quick way to bypass a module?

    Enable the mute button, then tap the module header

    That doesn’t seem to work on Midi modules?

    Tap on a track and set its 'Mute Style' to Midi.

    Thanks but that doesn’t appear to work, unless I’m doing something wrong.

  • @oldschoolwillie said:

    @jaijai said:
    I was GASsing hard on some new hardware which were announced at Superbooth. This release of Drambo cured it. This update is just so awesome. Thank you for al your hard work and dedication.

    The OP1field it keeps calling out to me.....
    I don't know if Drambo will be enough.......LOL!

    This won’t help, but Drambo 2 is amazing with the original OP-1. It would be even better with the Field ;)

  • @0tolerance4silence said:

    @gusgranite said:

    @Grandbear said:

    @gusgranite said:
    Is there a quick way to bypass a module?

    Enable the mute button, then tap the module header

    That doesn’t seem to work on Midi modules?

    It should, but there were modules that didn’t respect mute state.
    Drop the name of the module here so we can report it.
    In the meantime you can use Midi mixer (mute) modul as a workaround. Send midi through them and use mute button on the mixer. :)

    Testing this a little more. The midi mixer truly mutes, as in no midi gets through, which is not what I’m looking for but is good to know for other uses. The midi rack however let’s the midi pass through when you mute it and that’s what I’m looking for. Although it would be nice to see the module mutes allow the midi to pass through unaffected. Muting the midi modules I mentioned doesn’t appear to do anything at the moment.

    cc @Samu

  • @gusgranite said:

    @0tolerance4silence said:

    @gusgranite said:

    @Grandbear said:

    @gusgranite said:
    Is there a quick way to bypass a module?

    Enable the mute button, then tap the module header

    That doesn’t seem to work on Midi modules?

    It should, but there were modules that didn’t respect mute state.
    Drop the name of the module here so we can report it.
    In the meantime you can use Midi mixer (mute) modul as a workaround. Send midi through them and use mute button on the mixer. :)

    Testing this a little more. The midi mixer truly mutes, as in no midi gets through, which is not what I’m looking for but is good to know for other uses. The midi rack however let’s the midi pass through when you mute it and that’s what I’m looking for. Although it would be nice to see the module mutes allow the midi to pass through unaffected. Muting the midi modules I mentioned doesn’t appear to do anything at the moment.

    cc @Samu

    Yep I believe this is truly a bug, I've seen it in previous versions. The modules I see beeing affected are:

    • Strum
    • Strum Generator
    • Chord
    • MIDI Chance
    • Latch
    • MIDI Humanizer
    • Transpose
  • @yowza said:
    Compared to using Logic which easily lets you change tempo and time signature at will, many IOS apps often come off as toys in comparison. Please tell me which iOS apps let you do that without a workaround? NS2 and Auria and the old app Drum Studio come to mind but not much else.

    Gadget has tempo and time signature per scene.

  • @yowza I agree that it shouldn't be such a hassle.
    My fav app in this regard is KORG Gadget - not perfect but at least I was always able to get different odd time signatures in each pattern which is a must in experimental and Zappa-esque compositions where "anything can happen anytime" ;)

    Since this is obviously an often requested feature, chances are that there's going to be a better solution soon.

  • @cuezaireekaa said:
    I have paid for the waves iap on my iPad. But when I download Drambo on my iPhone, it won’t let me restore the purchase.. do we need to buy this waves iap again on each different device?

    Also I have another (probably stupid) question…
    Is 8 tracks/instruments the max we can use in a session on Drambo? And what are the extra 4 tracks/pads for that are empty at the end after the master track?

  • @yowza said:
    Why would my comment need to be turned around? I'm not sure of the point you're trying to make. Do you make your music based on which apps you use? Music comes from inside my head not from any specific app. I play guitar in most of my music so does that mean all the music sounds the same just because there is a guitar present?

    Your comment didn't need to be turned around. It certainly wasn't done as some kinda 'Gotcha!'. I just thought it useful to look at your issue from a different perspective.

    You made the claim that a certain piece of music sounded like it could've been made in various different apps, yet you seemed to want to make the same music you could (and presumably do), in many other apps, but within Drambo. My overriding point, I guess, is that perhaps instead of thinking how you can mould each bit of software to do what you normally do, maybe try to take each software at face-value, letting it guide you to do things you wouldn't normally do. It worked for Herbie Hancock ;)

    As for my process? In some ways, we're probably quite similar (albeit, I'd guess you're way more talented). I've been playing guitar for over 40 years, and while I do compose with electronic elements (Synths, drum-machines etc.), I wouldn't say my music is EDM!. I've never used tempo-changes, but time-signature changes are all over my work.

    My initial hope when coming back to iOS music was just to use various apps (Sampler, primarily), to do sound-design while out-and-about, with the results then exported to my desktop DAW, for using in full pieces. The various missteps I've made over the past few months have all come about due to me completely ignoring my initial intentions, and trying to mould an iOS workflow to what I normally do. I know that if an iPad were the only music-making apparatus I had access to, that I could make it work. But when I have a fully-loaded desktop DAW, it makes no sense to try and bend the iPad to my will. Instead, I'm trying to get myself back to my original workflow ideas, but to also experiment with playing to the iPad's strengths and to let various apps and workflows dictate the course of my ideas, as opposed to the other way 'round.

    And, to clarify: I don't ever hear music in my head before writing )I think it might've happened once). It always starts with a sound and throwing shapes on an instrument. From theres, it's an increasingly-tortuous process to arrive at some semblance of a piece ;)

    @yowza said:
    I realize I hijacked this thread and made it about me so I apologize for that but my questions were related to Drambo so I was on topic somewhat. With the limited time I have to make music, I tend to like to work in more traditional work flows and the experimental side of modular takes me out of that zone. I become more of a sound designer and tend to waste so much time creating and tweaking sounds that I often don't get any real music made. I've realized that I'm more of an old school musician that likes playing with notes and rhythms more than I like modulating filters with an LFO (though I do know how to do that).

    I don't think you were off-topic, nor that you hijacked anything. If anything, you presented more experienced users with the opportunity to further clarify what Drambo is, and, more importantly, what it isn't. But from reading this paragraph, I'm even more confused. Again, it's no criticism. Just you seem very aware of the limitations of the medium, and have already experienced frustration with modular environments (due, it seems, to the inherent limitations and/or your own tendency to go down, what you seem to deem as unproductive rabbit-holes).

    @yowza said:
    A number of old school jazz musicians I know are jazz holes and think arch top guitars should be the only guitars in jazz so not all of the jazz world has a view as expansive as yours. I do agree the spirit of jazz is about experimentation (more with musical forms than with tweaking sounds) but I don't think the whole jazz world agrees with us.

    "Jazz holes"? I think I can guess what you mean by that, but not 100% sure. Are these the same folks who think that banjos belong nowhere near jazz? ;)

    Ultimately, you know yourself. And it seems that you already know this isn't for you. So it makes no sense that I, a non-Drambo-owner, with my own concerns about how i'd effectively use such an app, would be defying you to take a chance on a completely different workflow.

    But who knows? Perhaps a year down the line, we'll be part of the same throng...totally captivated/addicted, and banging the dRambo drum :)

Sign In or Register to comment.