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

1…1718202223…27

Comments

  • SamSamSamSamSamSam

    @supadom said:
    I was talking more in broad economic terms. Most governments printed so much money during the pandemic and now with energy prices at record high the cost of living is going up for most.
    I don’t know your needs but I pretty much stopped buying apps since Drambo cropped up.

    Thanks for the follow up @supadom and @natuurlijk

  • BroCoastBroCoast

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

  • McDMcD

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    The current model serves the user's needs since updates and new features cost the user nothing.

    But it starves the developer as the number of purchasers reduces to a trickle. I hope we have all learned by now what happens when a developer ceases to maintain or update an app because the revenue dried up. We should care about the motivations of the developers that make tools we continue to use daily.

    @micheal has many apps up in the store but his income started to reduce. He focused on Loopy Pro for a couple years and had better results (I assume) and hopes to maintain working on this app for the roughly the same number of users for years with his model. He based his model on an app he uses regularly and has for years. It's a niche product for developers that gets regular maintenance.

  • wimwim
    edited May 2022

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    May I ask why? I ask that sincerely wanting to understand, not as a challenge.

  • vasilymilovidovvasilymilovidov

  • joniqwestjoniqwest

    @vasilymilovidov 👍

  • Michael_R_GrantMichael_R_Grant
    edited May 2022

    @McD said:

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    The current model serves the user's needs since updates and new features cost the user nothing.

    But it starves the developer as the number of purchasers reduces to a trickle. I hope we have all learned by now what happens when a developer ceases to maintain or update an app because the revenue dried up. We should care about the motivations of the developers that make tools we continue to use daily.

    @micheal has many apps up in the store but his income started to reduce. He focused on Loopy Pro for a couple years and had better results (I assume) and hopes to maintain working on this app for the roughly the same number of users for years with his model. He based his model on an app he uses regularly and has for years. It's a niche product for developers that gets regular maintenance.

    Yep. I would fully support giku going down this road. It does seem to be the only model that makes sense for ongoing iOS music app development if you have one flagship product that you intend to develop for a number of years. That being said, there has been absolutely no indication that this will happen for Drambo.

  • RajahPRajahP

    @FP0 said:
    I hope there will be comprehensive documentation and video tutorials covering all new features, whenever this release happens. After this amount of time there really is no excuse for this not to be the case.

    I’m a fan of Drambo but hardly use it at all. I think it’s biggest problem is the lack of decent patches. The standout being the paid work by COTCD. The factory patches are few and pretty uninspiring. Patchstorage after two years has just c.400 patches (but many aren’t instruments). Compare that to the new Virsyn Tera Pro synth at 1800 and you’ll see the point.

    Drambo is a ‘vast’ app, I think the idea is to make it into what you need.. My personal interest is the StepSeq, PLocking.
    But these long durations between updates make it very dif

    @vasilymilovidov said:

    :p

  • BroCoastBroCoast

    @wim said:

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    May I ask why? I ask that sincerely wanting to understand, not as a challenge.

    It’s a good idea and all. I just prefer the IAP model so I can pay for what I want to use.

  • tk32tk32
    edited May 2022

    @vasilymilovidov said:

    I've just realised what is going on here. That's an instance of Drambo inside another Drambo(!)

    I originally assumed the second window was added in post to hide spoilers - but no.

  • LorichsLorichs

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    +1

  • vasilymilovidovvasilymilovidov

    @tk32 said:

    @vasilymilovidov said:

    I've just realised what is going on here. That's an instance of Drambo inside another Drambo(!)

    I originally assumed the second window was added in post to hide spoilers - but no.

    yep, took me a while too. I'm very happy right now

  • tahichetahiche
    edited May 2022

    @Michael_R_Grant said:

    @McD said:

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    The current model serves the user's needs since updates and new features cost the user nothing.

    But it starves the developer as the number of purchasers reduces to a trickle. I hope we have all learned by now what happens when a developer ceases to maintain or update an app because the revenue dried up. We should care about the motivations of the developers that make tools we continue to use daily.

    @micheal has many apps up in the store but his income started to reduce. He focused on Loopy Pro for a couple years and had better results (I assume) and hopes to maintain working on this app for the roughly the same number of users for years with his model. He based his model on an app he uses regularly and has for years. It's a niche product for developers that gets regular maintenance.

    Yep. I would fully support giku going down this road. It does seem to be the only model that makes sense for ongoing iOS music app development if you have one flagship product that you intend to develop for a number of years. That being said, there has been absolutely no indication that this will happen for Drambo.

    My simplistic and probably naive way of seeing this is that I’d willingly pay for enhancements that make me happy.
    Seems like we have no issue in paying 8€ for a new fun sequencer, or a promising synth, even though you have 20 of each. But paying that same amount for an IAP, new version or yearly (loopy) model for an app you already own, somehow makes users doubt more. In a “better be worth it” kind of way.
    I’d pay 3 times as much for having proper midi routing and CC’s in Zenbeats than I’d pay for any new app. I know it’d make my life easier.
    I’d gladly pay for a stupid no-thrills count in in Loopy. That silly feature would take away some frustration.
    I’d also pay more for a simple Drambo choke group thing than for a brand new sequencer. I’d rather pay for Drambo v2 and “buy” the right to complain about it not having “choke groups for dummies”.

    And the list goes on and on.
    We can either accept that new features and fixes are gonna take a long time because the dev has a day job and has do it on weekends, or we accept that we have to pay more.

  • espiegel123espiegel123

    @tahiche said:

    @Michael_R_Grant said:

    @McD said:

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    The current model serves the user's needs since updates and new features cost the user nothing.

    But it starves the developer as the number of purchasers reduces to a trickle. I hope we have all learned by now what happens when a developer ceases to maintain or update an app because the revenue dried up. We should care about the motivations of the developers that make tools we continue to use daily.

    @micheal has many apps up in the store but his income started to reduce. He focused on Loopy Pro for a couple years and had better results (I assume) and hopes to maintain working on this app for the roughly the same number of users for years with his model. He based his model on an app he uses regularly and has for years. It's a niche product for developers that gets regular maintenance.

    Yep. I would fully support giku going down this road. It does seem to be the only model that makes sense for ongoing iOS music app development if you have one flagship product that you intend to develop for a number of years. That being said, there has been absolutely no indication that this will happen for Drambo.

    My simplistic and probably naive way of seeing this is that I’d willingly pay for enhancements that make me happy.
    Seems like we have no issue in paying 8€ for a new fun sequencer, or a promising synth, even though you have 20 of each. But paying that same amount for an IAP, new version or yearly (loopy) model for an app you already own, somehow makes users doubt more. In a “better be worth it” kind of way.
    I’d pay 3 times as much for having proper midi routing and CC’s in Zenbeats than I’d pay for any new app. I know it’d make my life easier.
    I’d gladly pay for a stupid no-thrills count in in Loopy. That silly feature would take away some frustration.
    I’d also pay more for a simple Drambo choke group thing than for a brand new sequencer. I’d rather pay for Drambo v2 and “buy” the right to complain about it not having “choke groups for dummies”.

    And the list goes on and on.
    We can either accept that new features and fixes are gonna take a long time because the dev has a day job and has do it on weekends, or we accept that we have to pay more.

    @tahiche : I think you misunderstand the Loopy model. You don’t have to pay a yearly fee. Once you own Loopy you own it for life with whatever features it has or are added in that year. You can use those features for life without paying another cent.

    You only pay another fee to add new features. If the new features don’t interest you, you can keep using the app without paying anything.

  • vasilymilovidovvasilymilovidov
    edited May 2022

    bitwig has the best model, in my opinion. you buy an activation code and you don't have to activate it right away. right now I have an active license and an additional code that I bought when there was a discount. I know that there will be no significant updates to bitwig for a while now, so I can keep that code for when I need it.

  • vasilymilovidovvasilymilovidov
    edited May 2022

    .

  • GrandbearGrandbear

    @vasilymilovidov said:

    More flexible AU window management? Niiiice

  • erosseross

    looks cool. any chance it will get update this week? superbooth is this week, and sometimes there are fun app releases to go along with that. just curious

  • wimwim

    @BroCoast said:

    @wim said:

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    May I ask why? I ask that sincerely wanting to understand, not as a challenge.

    It’s a good idea and all. I just prefer the IAP model so I can pay for what I want to use.

    Ahh, thanks, I see now. This feels like taking a level of choice away and selectivity away. I can understand that.

    I think the challenge with an app like Loopy is general improvements can't always be bucketed into a nice and tidy feature IAPs.

    Thanks for the insight though. Makes sense.

  • drezdrez

    @tk32 said:
    While we wait..here’s a gentle reminder of what you can already do in Drambo v1.

    I started by building a synth clap module*.. and then suddenly nostalgia for my 1990s Amiga gaming days came flooding back and I spontaneously spent the next 2 hours building this cover version of the Chris Huelsbeck classic.

    100% Drambo (v1). No plugins. No Samples.

    *more info on this side project soon

    Great stuff! Your dedication to sequencing chords in the step sequencer is to be commended!

  • tk32tk32

    Thanks @drez

    I've picked up a few good techniques for tweaking (and auditioning) chords, but I am definitely looking forward to the sequencing and workflow improvements on the horizon.

  • espiegel123espiegel123

    @BroCoast said:

    @wim said:

    @BroCoast said:

    @McD said:
    I think this is a lifetime app and should follow the model @michael researched and adopted to provide a steady income over multiple years of effort.

    I really don't want that model.

    May I ask why? I ask that sincerely wanting to understand, not as a challenge.

    It’s a good idea and all. I just prefer the IAP model so I can pay for what I want to use.

    That level of granularity for IAP’s can make things more complex and difficult to maintain. Probably to the point of impracticality..which is why almost no complex music software that is profitable does it that way.

  • GravitasGravitas

    Practical timestretching. ;)

  • RajahPRajahP

    Great Drambo Demo videos... will you kind souls please post one on the step-sequencer and what it will have in store for us... quite excited... Thank You.

  • aleyasaleyas
    edited May 2022

    @vasilymilovidov said:

    Thanks for posting my track 😁

    A little more info about the process behind it:

    A new feature in Drambo 2.0 is the 'step entry' mode for the main sequencer. When the transport is stopped, but record is enabled, notes and chords will fill the steps one by one. An exploit of this is that when when rack midi (midi generated in the rack space, from CV converted into MIDI) is sent to AU Drambo, AU Drambo can then autofill its sequencer from that generated midi. With careful patching, this can allow rapid population of each step when you use something like the retrigger module. With a density of 16, you can instantly fill 16 steps. With a density of 8, you can instantly fill 8 steps, etc. Taking advantage of the new Nav Bar, you can focus on individual bars of the sequence, or add additional bars, and auto-fill just those. There are many methods to generate the pitch, but here I used a Graphic Envelope as a rising ramp (for piano sequence) and falling ramp (for Tines sequence). The Graphic Envelope is quantized with the CV Quantizer to specific chords, and converted to midi with the MIDI Note Gen module. It's a stroke of genius that we can auto-fill the Drambo sequencer with rack midi. And now that we can also drag clips between instances, we can take all of that rack generated midi, and 'bounce' it right back into the host's launcher. All that from one tap.

    Oh, and we now have floating AU windows =)

    Trigger Button -> Retrigger -> MIDI Note Gen (Gate)
    Trigger Button -> Graphic Envelope -> Scale+Offset -> Quantize -> MIDI Note Gen (Pitch)
    MIDI Note Gen -> Drambo AU

  • el_boel_bo

    @Gravitas said:
    Practical timestretching. ;)

    Blimey! Sounds great…all the way down :)

  • el_boel_bo

    @aleyas said:
    A new feature in Drambo 2.0 is the 'step entry' mode for the main sequencer. When the transport is stopped, but record is enabled, notes and chords will fill the steps one by one.

    Do you mean like Logic Pro's 'Step Input' functionality?

  • aleyasaleyas
    edited May 2022

    @el_bo said:

    @aleyas said:
    A new feature in Drambo 2.0 is the 'step entry' mode for the main sequencer. When the transport is stopped, but record is enabled, notes and chords will fill the steps one by one.

    Do you mean like Logic Pro's 'Step Input' functionality?

    Classic step entry ala SH-101, Keystep, Midisteps, etc. Step, Rest, Tie.

  • SamuSamu

    @el_bo said:

    Do you mean like Logic Pro's 'Step Input' functionality?

    Yepp, that's the way it will work :sunglasses:

  • aleyasaleyas
    edited May 2022

    @Samu said:

    @el_bo said:

    Do you mean like Logic Pro's 'Step Input' functionality?

    Yepp, that's the way it will work :sunglasses:

    Not quite. Logic is more advanced, allowing you to select the note length per each note/chord entered. So you could have the first three entered notes be half notes, with the next 4 notes entered being eighth notes. Kind of like how a tracker like Sunvox works with the number of lines skipped per entry. Drambo just does single step, no regard to note length (ie, the 'classic' way ;))

Sign In or Register to comment.

© Vanilla Keystone Theme 2025