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 - this was just posted on Facebook

12122242627

Comments

  • @shazbot said:

    @Gravitas said:

    @shazbot said:
    I love how you can use the Nav bar to select patterns and the clip view options for song building.

    The bezier curves in the automation editor? HOW. IT. SHOULD. BE. DONE. in any DAW.

    Now just me checking the store every 15 minutes for the update:

    @vasilymilovidov said:

    @shazbot said:
    I love how you can use the Nav bar to select patterns and the clip view options for song building.

    The bezier curves in the automation editor? HOW. IT. SHOULD. BE. DONE. in any DAW.

    Now just me checking the store every 15 minutes for the update:

    also, it looks like I finally won't be thinking with dread about using automation

    In regards to automation?

    There's not an app right now that can touch it, not one.
    The automation is superb.
    It's off the hook.

    I couldn't screen record the piece because I'm in the beta team
    but I can share this description now as this was my test piece.
    Every CLIP on the synth bass sound has it's own automation.
    I think at one point there's 22 lanes of automation on one CLIP.

    Here's the piece.

    I then took out the stock oscillators and put in MiRacks and this is what it sounds like.

    😎😎😎 Off the hook indeed. Most appropriate way to put it I think.
    Sweet beat ,visuals and great examples, thx for sharing.

    No problem.
    Thank you.
    Glad you like it.

    Looks like Drambo might breathe new life into dusty ol mirack too 😬

    More than.
    I've been experimenting with using cv signals from dRambo into MiRack
    because I'm thinking about exploring physical Eurorack and as MiRack
    is close to hand it's the best and most convenient way to do so.
    The results are really good.
    The combination of dRambo and MiRack is very promising
    for using dRambo as the main sequencer for a Eurorack rig.

  • edited May 2022

    @Grandbear said:

    @shazbot said:

    @Grandbear said:

    @shazbot said:
    Since I've typically used AUM there's always had to be the process of connecting an LFO (or graphic shaper) to a CC but then it's even more cumbersome if you want it in a song-mode context....it might very well be that standalone Drambo will take over AUM as the main host.

    Aside from the setup convenience, when going through MIDI CC-based automation instead of modulating the AU params directly, you lose resolution by being forced to CC's 128 values, so I consider this a better solution in many aspects

    What's the default resolution for AU params then? Dependent on host ie 16/24bit?

    I don't think it depends on the host; I believe this is specified when param is defined in the AUv3 plugin itself (it can be indexed, floating point value with different units, etc.) Disclaimer: I'm not an audio developer.

    Right right. Floating at least. It'd be nice if one so chooses to send out automation through a CC that's 14-bit if possible...

  • edited May 2022

    @Gravitas said:

    @shazbot said:

    @Gravitas said:

    @shazbot said:
    I love how you can use the Nav bar to select patterns and the clip view options for song building.

    The bezier curves in the automation editor? HOW. IT. SHOULD. BE. DONE. in any DAW.

    Now just me checking the store every 15 minutes for the update:

    @vasilymilovidov said:

    @shazbot said:
    I love how you can use the Nav bar to select patterns and the clip view options for song building.

    The bezier curves in the automation editor? HOW. IT. SHOULD. BE. DONE. in any DAW.

    Now just me checking the store every 15 minutes for the update:

    also, it looks like I finally won't be thinking with dread about using automation

    In regards to automation?

    There's not an app right now that can touch it, not one.
    The automation is superb.
    It's off the hook.

    I couldn't screen record the piece because I'm in the beta team
    but I can share this description now as this was my test piece.
    Every CLIP on the synth bass sound has it's own automation.
    I think at one point there's 22 lanes of automation on one CLIP.

    Here's the piece.

    I then took out the stock oscillators and put in MiRacks and this is what it sounds like.

    😎😎😎 Off the hook indeed. Most appropriate way to put it I think.
    Sweet beat ,visuals and great examples, thx for sharing.

    No problem.
    Thank you.
    Glad you like it.

    Looks like Drambo might breathe new life into dusty ol mirack too 😬

    More than.
    I've been experimenting with using cv signals from dRambo into MiRack
    because I'm thinking about exploring physical Eurorack and as MiRack
    is close to hand it's the best and most convenient way to do so.
    The results are really good.
    The combination of dRambo and MiRack is very promising
    for using dRambo as the main sequencer for a Eurorack rig.

    can't wait to see Drambo driving modular h/w

    What are some of your favorite mirack modules?

  • @shazbot said:
    I'm not getting what Clip locks do though.... can anyone explain?

    due to my excitement I'm not able to process things atm

    EDIT: I guess it's just keeping all the P-Lock settings for that track (including automation I assume)

    Clip - lock (or rather clip p-lock) allows you to lock parameters on a clip in the launcher.
    F.e Clip1 locks Filter Cutoff half open, Clip2 locks Filter Cutoff fully open. So with change of your sequence you can initiate changes to the sound.
    There are other creative ways to utilise it, like locking various master effects (stutter, repeater) and launching those clips - those clips don’t have notes only the locks so you effectively use it as a snapshot to certain parameters.

  • Righteous. I cannot wait. Beefy sequencer and stems are going to make things so easy on me, I can feel it.

  • I watched the video linked above. Wow. The sequencer alone sells it for me. Like a software OP-Z.

  • @Gravitas said:

    @shazbot said:
    I love how you can use the Nav bar to select patterns and the clip view options for song building.

    The bezier curves in the automation editor? HOW. IT. SHOULD. BE. DONE. in any DAW.

    Now just me checking the store every 15 minutes for the update:

    @vasilymilovidov said:

    @shazbot said:
    I love how you can use the Nav bar to select patterns and the clip view options for song building.

    The bezier curves in the automation editor? HOW. IT. SHOULD. BE. DONE. in any DAW.

    Now just me checking the store every 15 minutes for the update:

    also, it looks like I finally won't be thinking with dread about using automation

    In regards to automation?

    There's not an app right now that can touch it, not one.
    The automation is superb.
    It's off the hook.

    I couldn't screen record the piece because I'm in the beta team
    but I can share this description now as this was my test piece.
    Every CLIP on the synth bass sound has it's own automation.
    I think at one point there's 22 lanes of automation on one CLIP.

    Here's the piece.

    I then took out the stock oscillators and put in MiRacks and this is what it sounds like.

    Great illustration/example of the upcoming features. Thanks for sharing.

  • edited May 2022

    @bcrichards your 1-hour deep dive into Drambo 2.0 video was simply masterful. Bravo.

  • @0tolerance4silence said:

    @shazbot said:
    I'm not getting what Clip locks do though.... can anyone explain?

    due to my excitement I'm not able to process things atm

    EDIT: I guess it's just keeping all the P-Lock settings for that track (including automation I assume)

    Clip - lock (or rather clip p-lock) allows you to lock parameters on a clip in the launcher.
    F.e Clip1 locks Filter Cutoff half open, Clip2 locks Filter Cutoff fully open. So with change of your sequence you can initiate changes to the sound.
    There are other creative ways to utilise it, like locking various master effects (stutter, repeater) and launching those clips - those clips don’t have notes only the locks so you effectively use it as a snapshot to certain parameters.

    Right, but not just Filter Cutoff from your example, it would be all P-Locks in the track, right? Obviously? Makes sense....

  • @svrc said:
    Don’t know if that was mentioned and i know that is to much but i’m wondering about proper scale on Mac?

    Don't worry, it's about the sexiest piano roll, the most dense launcher grid and the longest rack I've ever worked with on a Mac.
    And yes, full screen does work (although it's probably not supported officially).

  • Is there a way I can filter out redundant CC values so they only send when the value is different?

    I'm trying to do a kind of 'if-else' with OR or XOR but no...are math modules the answer? or trying to quantize the output but quantize isn't doing it...

    I'm sending the CC data to apple Motion and it doesn't take long for the program to start lagging and become close to unresponsive once I tie the cc data to a simple parameter like a shapes width.

  • @shazbot clip locks are for clips are what parameter locks are for steps - it could be any combination of parameters. Consider it like “non-moving” automation for one clip, or like @0tolerance4silence said, snapshots.

  • @tk32 thanks! I’ve been itching to do more tutorials.

  • edited May 2022

    @rs2000 said:

    @svrc said:
    Don’t know if that was mentioned and i know that is to much but i’m wondering about proper scale on Mac?

    Don't worry, it's about the sexiest piano roll, the most dense launcher grid and the longest rack I've ever worked with on a Mac.
    And yes, full screen does work (although it's probably not supported officially).

    Wow, thanks!

  • @bcrichards said:
    @shazbot clip locks are for clips are what parameter locks are for steps - it could be any combination of parameters. Consider it like “non-moving” automation for one clip, or like @0tolerance4silence said, snapshots.

    Right -> 'Snapshots' which is probably also a yes to my question of clarification.

    Thx again for the video btw (Nomo)

  • @shazbot said:

    can't wait to see Drambo driving modular h/w

    Myself also.
    If someone has a EuroRack rig in London give me a holla.

    What are some of your favorite mirack modules?

    All of the ones that make a noise or sound in some way.
    Obviously I've delved into the Audible Instruments,
    SevenSeas Wavetable VCO is very fun.
    The ones by Geodesics are obscure and I find it interesting trying to figure
    them out which is mainly to do with the language more than anything else.
    I've gone through the filters and I use them accordingly.
    I've now learnt how to tune the cut off filters so
    I'm also experimenting with playing melodies and
    percussion loops using self oscillating filters.

    I leave all the sequencing to dRambo.

    @lukesleepwalker said:

    Great illustration/example of the upcoming features. Thanks for sharing.

    Thank you.

    🙏🏾

    A pleasure.

  • The user and all related content has been deleted.
  • @shazbot said:
    Is there a way I can filter out redundant CC values so they only send when the value is different?

    I'm trying to do a kind of 'if-else' with OR or XOR but no...are math modules the answer? or trying to quantize the output but quantize isn't doing it...

    I'm sending the CC data to apple Motion and it doesn't take long for the program to start lagging and become close to unresponsive once I tie the cc data to a simple parameter like a shapes width.

    This is one of the many many fixes and updates that are not apparent at first sight.
    The current official CC Generator sends multiple identical CC messages when the input CV only changes slightly.
    The new one only sends the next CC message if it's different.
    Another enhancement is that you'll be able to set a MIDI channel to send on directly inside the module.
    Yet another enhancement is that you'll have a gate input to send CC messages whenever YOU want.

  • edited May 2022

    @shazbot said:

    @0tolerance4silence said:

    @shazbot said:
    I'm not getting what Clip locks do though.... can anyone explain?

    due to my excitement I'm not able to process things atm

    EDIT: I guess it's just keeping all the P-Lock settings for that track (including automation I assume)

    Clip - lock (or rather clip p-lock) allows you to lock parameters on a clip in the launcher.
    F.e Clip1 locks Filter Cutoff half open, Clip2 locks Filter Cutoff fully open. So with change of your sequence you can initiate changes to the sound.
    There are other creative ways to utilise it, like locking various master effects (stutter, repeater) and launching those clips - those clips don’t have notes only the locks so you effectively use it as a snapshot to certain parameters.

    Right, but not just Filter Cutoff from your example, it would be all P-Locks in the track, right? Obviously? Makes sense....

    Obviously :D
    Any parameter (and any number of params in the rack)

  • @0tolerance4silence said:

    @shazbot said:

    @0tolerance4silence said:

    @shazbot said:
    I'm not getting what Clip locks do though.... can anyone explain?

    due to my excitement I'm not able to process things atm

    EDIT: I guess it's just keeping all the P-Lock settings for that track (including automation I assume)

    Clip - lock (or rather clip p-lock) allows you to lock parameters on a clip in the launcher.
    F.e Clip1 locks Filter Cutoff half open, Clip2 locks Filter Cutoff fully open. So with change of your sequence you can initiate changes to the sound.
    There are other creative ways to utilise it, like locking various master effects (stutter, repeater) and launching those clips - those clips don’t have notes only the locks so you effectively use it as a snapshot to certain parameters.

    Right, but not just Filter Cutoff from your example, it would be all P-Locks in the track, right? Obviously? Makes sense....

    Obviously :D
    Any parameter (and any number of params in the rack)

    It’s unrelated to p-locks... it’s an additional layer of modulation... if clip - lock applied to the same params that has p-locks as well, p-locks will take over as a higher hierarchy modulation.

  • @rs2000 said:

    @shazbot said:
    Is there a way I can filter out redundant CC values so they only send when the value is different?

    I'm trying to do a kind of 'if-else' with OR or XOR but no...are math modules the answer? or trying to quantize the output but quantize isn't doing it...

    I'm sending the CC data to apple Motion and it doesn't take long for the program to start lagging and become close to unresponsive once I tie the cc data to a simple parameter like a shapes width.

    This is one of the many many fixes and updates that are not apparent at first sight.
    The current official CC Generator sends multiple identical CC messages when the input CV only changes slightly.
    The new one only sends the next CC message if it's different.
    Another enhancement is that you'll be able to set a MIDI channel to send on directly inside the module.
    Yet another enhancement is that you'll have a gate input to send CC messages whenever YOU want.

    Thank you for the info 🙏🏽

  • @0tolerance4silence said:

    @0tolerance4silence said:

    @shazbot said:

    @0tolerance4silence said:

    @shazbot said:
    I'm not getting what Clip locks do though.... can anyone explain?

    due to my excitement I'm not able to process things atm

    EDIT: I guess it's just keeping all the P-Lock settings for that track (including automation I assume)

    Clip - lock (or rather clip p-lock) allows you to lock parameters on a clip in the launcher.
    F.e Clip1 locks Filter Cutoff half open, Clip2 locks Filter Cutoff fully open. So with change of your sequence you can initiate changes to the sound.
    There are other creative ways to utilise it, like locking various master effects (stutter, repeater) and launching those clips - those clips don’t have notes only the locks so you effectively use it as a snapshot to certain parameters.

    Right, but not just Filter Cutoff from your example, it would be all P-Locks in the track, right? Obviously? Makes sense....

    Obviously :D
    Any parameter (and any number of params in the rack)

    It’s unrelated to p-locks... it’s an additional layer of modulation... if clip - lock applied to the same params that has p-locks as well, p-locks will take over as a higher hierarchy modulation.

    ohhhhhh ok. P-Locks have nothing to do with Clip Locks. Clip Locks are simply a 'snapshot' of the parameters.

  • @d4d0ug said:

    @Samu said:

    @vasilymilovidov said:
    any updates to the core modules?

    Yepp, and the WaveTable IAP also gets a bunch of new modules (including a vocoder) so it's worth a grab...

    is there a looper module ?

    No audio looper in an official beta but I’ve played with a prototype. Now that the big UI changes are out of the way hopefully Jarek can focus more on modules.

  • The user and all related content has been deleted.
  • edited May 2022

    Also I think not charging for this update is a good idea because with CashApp/Venmo type donations some could donate more than what the update would charge for!

  • Are there going to be any issues loading our older projects in 2.0?

  • @Jscro626s said:
    Are there going to be any issues loading our older projects in 2.0?

    There shouldn't be.

    I haven't had any issues so far.

    Still, to be on the safe side I would make a backup first and if you do
    have any issues with older projects get in touch as fast as possible
    either via here, the Beepstreet Forum or email the dev direct.

  • 104 new messages on this thread!. I was sure there’d be a “finally, it’s out, loving it, bla bla” towards the end so I read all of them, to build up the momentum. Here I am, at the end, with no update. 🤦🏻
    Come on now!

  • Awesome. Yeah, I've learned the hard way about not having backups before updates so I'll be ready.

  • @tahiche said:
    104 new messages on this thread!. I was sure there’d be a “finally, it’s out, loving it, bla bla” towards the end so I read all of them, to build up the momentum. Here I am, at the end, with no update. 🤦🏻
    Come on now!

    same boat here, my guy. And i don't even use drambo.

Sign In or Register to comment.