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.

ATOM Piano Roll update is coming soon

1…3536384041…56

Comments

  • Pierre118Pierre118
    edited March 2021

    My humble opinion : go for option 2. Everybody would say 1, but after a while people are going to ask what the status of automation is and when it will be released. You can wait for that.

    Of course I want option 1, but it's wiser to go for option 2.

    One request : please make it MacOS M1 compatible.

  • CharlesalbertCharlesalbert

    1😂😂😂 then You have less pressure and You can work better on the modular update😁

  • lasselulasselu

    I'd say option one...

  • aleyasaleyas
    edited March 2021

    @Pierre118 said:
    My humble opinion : go for option 2. Everybody would say 1, but after a while people are going to ask what the status of automation is and when it will be released. You can wait for that.

    Of course I want option 1, but it's wiser to go for option 2.

    I'm kind of agreeing with this too. Releasing it sooner isn't going to stop the questioning about the features-to-come. There may be the need for additional support or emails to answer from new users etc.

  • GdubGdub

    1
    For me
    Get the app
    Get really good at the app
    Automation arrives a bit later , for the gravy
    You get income now for your hard work
    We get an amazing app with toppings to come
    Either way I’m happy
    Be safe and don’t destroy ya self in the process

  • FloRi89FloRi89

    Cool, personally automation ist not my main goal with ATOM piano roll, I'd say release with the polished features, add automation whenever you have time in an update. Takes the pressure off development and off you also. Only my personal opinion though, maybe someone can setup a voting or something?

    Lot's of different apps release bite by bite and seem to do very well with it.

  • audio_DTaudio_DT

    @blueveek , I say ship it now. I'd be happy to wait for the other stuff while I still using the bulk of the features. You'd get yourself a break, too.

  • SpartanClownTideSpartanClownTide

    @blueveek said:
    Hi.

    Help me out :)

    I have this vision for how to properly do fully (and I mean fully) modular automation, and it's hard. There's quite a few moving parts, and I won't ship something that's incomplete: it needs curves, it needs transforms, it needs interpolation, it needs user programming, it needs accuracy, it needs performance, it needs to work standalone. It needs to be at the same polish and depth as the rest of the features in Atom.

    As it stands, even after my crunch in February, it's still not there yet.

    So, you decide:
    1. Ship now, with no automation, but with all other features planned for 2.0 finished. It's pretty much 99% the December build.
    or
    2. Wait some more. I honestly don't know how much longer.

    If we go with (1), I'll make the current build the final build. In store hopefully within a week or two after that, depending on Apple. Automation will ship later, once my life settles down a bit. If we go with (2), I'll keep working on the automation features until I get them the way I want to.

    I'm happy with either approach. I'm not in a rush for income, I don't want to keep you waiting, and this doesn't really affect anything: in the long term we'll arrive at the same thing :)

    Now, I really mean it when I say "you decide". I'd like to gather your thoughts for the next few days and whichever the outcome is by the end of the week, that's what's going to happen.

    1. Everyone would prefer it sooner rather than later
    2. Everyone loves an exciting big update
  • rs2000rs2000
    edited March 2021

    @blueveek
    I know myself. Getting something new in my hands is exciting for the first few hours but without automation, I'll have no chance but to go back to LK.

    So a it's clear 2 for me.

  • aleyasaleyas

    Man, its a hard question. In the end what matters most is your own health and well being. If releasing now would relieve any sense of pressure then that would definitely be a good thing.
    @Gdub did make a good point that releasing it earlier would allow users to become familiar with the app, and have time to master a smaller set of features first. Sometimes an app with lots of features can be overwhelming to learn.

  • reasOnereasOne

    I’m down for atom 2 now and adding automation later if you find time to make it possible

  • ik2000ik2000

    @blueveek said:
    Hi.

    Help me out :)

    I have this vision for how to properly do fully (and I mean fully) modular automation, and it's hard. There's quite a few moving parts, and I won't ship something that's incomplete: it needs curves, it needs transforms, it needs interpolation, it needs user programming, it needs accuracy, it needs performance, it needs to work standalone. It needs to be at the same polish and depth as the rest of the features in Atom.

    As it stands, even after my crunch in February, it's still not there yet.

    So, you decide:
    1. Ship now, with no automation, but with all other features planned for 2.0 finished. It's pretty much 99% the December build.
    or
    2. Wait some more. I honestly don't know how much longer.

    If we go with (1), I'll make the current build the final build. In store hopefully within a week or two after that, depending on Apple. Automation will ship later, once my life settles down a bit. If we go with (2), I'll keep working on the automation features until I get them the way I want to.

    I'm happy with either approach. I'm not in a rush for income, I don't want to keep you waiting, and this doesn't really affect anything: in the long term we'll arrive at the same thing :)

    Now, I really mean it when I say "you decide". I'd like to gather your thoughts for the next few days and whichever the outcome is by the end of the week, that's what's going to happen.

    Firstly, thanks @blueveek for the honesty in that post. Software development is often hard at the best of times and the differences you are proposing between the current version of Atom and the new version is huge. I know there are probably hundreds of people who just want you to release this (option 1) now, but I’m sure there are just as many who will want you to continue developing (option 2). Personally, we’ve waited this long so I’m happy to wait for option 2, but I’m sure option 1 will be a great improvement too.

    Like many other people have said, releasing option 1 now will result in many asking about when the updates in option 2 will be ready, but I think the same people will probably keep asking you when option 2 will be complete if you go down that route anyway.

    I think people will always ask questions no matter your choice @blueveek.... I think you do what you are most happy with!

  • GrimLuckyGrimLucky

    I’d be quite happy without automation to begin with so would go for option 1. Plus there may be suggestions for the update based on initial user feedback.

  • auxmuxauxmux

    Option 1 seems like a good choice, because every product will continue to mature and grow in features over time. While it's nice to have everything ready and perfect from the start, it's much harder and honestly people will continue to want more things either way.

  • blueveekblueveek

    @GrimLucky said:
    I’d be quite happy without automation to begin with so would go for option 1. Plus there may be suggestions for the update based on initial user feedback.

    Oh I'm super certain of this! It might make sense to do a bit of public iteration, at least while it's slightly easier to move things around.

  • SamuSamu

    I'll say #1 if it can already record, playback and edit CC's...
    ...if not then #2.

  • MisplacedDevelopmentMisplacedDevelopment

    I prefer little and often releases (agile/iterative/insert current buzzword here) which seems to have worked well with LK, for example. I do however recognise the downsides to this approach, e.g. more chance of functional regressions being introduced and perhaps some expectation of constant feature updates when you would rather stabilise the code.

    My vote goes to (1) because I am impatient :smile: but either way it sounds like we will end up with something fab.

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • HalftoneHalftone

    @Samu said:
    I'll say #1 if it can already record, playback and edit CC's...
    ...if not then #2.

    Same here

  • KrupaKrupa

    I’d lean #1 too, as long as it doesn’t lead to a slew of new feature requests that put you off your goals...

  • ALBALB

    Option 2.

  • SvetlovskaSvetlovska
    edited March 2021

    I’d selfishly go for #1 because my principle use case for wanting Atom #2 is to be able to file export MIDI to go with the wavs I am already taking as whole cloth from my AUM sessions across into Ableton. Any automation I want to do can be done there on the ‘basic’ MIDI file if needed.

    I’m also a ‘bird in the hand’ kind of a person. Having something now beats everything later. I think of the example of the great Piano Motifs app, which has grown in usefulness over time due to lots of little iterative improvements, fueled in part by user feedback. And just like that app, I’d be happy to pay for such additions down the line as IAP or ‘tip jar’ offerings.

  • enkayteeenkaytee
    edited March 2021

    I think option 1. At least you have the bulk of the app out there and can focus on automation in your own time - people will probably still hassle you for a release date but if the core of the app is as amazing as it appears from this thread you'll make a lot of people happy and get a bit of income as well...👍

  • GavinskiGavinski
    edited March 2021

    I say release now and add automation later - what kind of automation are we talking here? Can’t we in the meantime use exposed parameters in hosts to automate?

  • dafrimpsterdafrimpster

    I would choose option #1. Let them eat cake!

  • espiegel123espiegel123

    @blueveek said:
    Hi.

    Help me out :)

    I have this vision for how to properly do fully (and I mean fully) modular automation, and it's hard. There's quite a few moving parts, and I won't ship something that's incomplete: it needs curves, it needs transforms, it needs interpolation, it needs user programming, it needs accuracy, it needs performance, it needs to work standalone. It needs to be at the same polish and depth as the rest of the features in Atom.

    As it stands, even after my crunch in February, it's still not there yet.

    So, you decide:
    1. Ship now, with no automation, but with all other features planned for 2.0 finished. It's pretty much 99% the December build.
    or
    2. Wait some more. I honestly don't know how much longer.

    If we go with (1), I'll make the current build the final build. In store hopefully within a week or two after that, depending on Apple. Automation will ship later, once my life settles down a bit. If we go with (2), I'll keep working on the automation features until I get them the way I want to.

    I'm happy with either approach. I'm not in a rush for income, I don't want to keep you waiting, and this doesn't really affect anything: in the long term we'll arrive at the same thing :)

    Now, I really mean it when I say "you decide". I'd like to gather your thoughts for the next few days and whichever the outcome is by the end of the week, that's what's going to happen.

    For me option 1. I won't be using automation daily but would be getting daily use out of having something that captures and plays back multichannel MIDI.

  • gusgranitegusgranite

    @blueveek I think option #2 but maybe set yourself a deadline for release and stick to it what ever.

    If you release now then you are going to get swamped with support questions and feature requests and you may find it hard to focus on completing automation.

  • JeezsJeezs

    @Samu said:
    I'll say #1 if it can already record, playback and edit CC's...
    ...if not then #2.

    Same for me

  • SergiuSergiu

    +1 > @Halftone said:

    @Samu said:
    I'll say #1 if it can already record, playback and edit CC's...
    ...if not then #2.

    Same here

  • erosseross

    ship now is my vote. it’s always great to see the apps continue to improve and get new features in updates while already owning it.

This discussion has been closed.