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

1363739414256

Comments

  • I’d go for option #1, because as a creator - it’s a load lifted to say “ship it” and move into the next phase of development. And with the reality of what your app earnings are likely to be relative to the work invested, add more features as IAPs.

    And then just accept that some people will be only partially happy and possibly negatively vocal. 😃

  • @espiegel123 so this will be MPE ready?

  • @rs2000 said:
    @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.

    Me as well.

  • Kick it out🤪
    For me it would be great to see the possibilities now in my current use.
    As some mentioned, the version you can release now is a BIG improvement and useful in any case.
    I also like very excited for every upcoming update. An later update will also bring it to people who join the iOS community later, because with an new update you get more attention to the app😎

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

    Exactly my view!

  • edited March 2021

    I can wait so I have no need for option 1. As someone who has managed many software projects, I can assert that option 1 is the right one without question. As long as your first phase of AtomV2 meets a core "job to be done" for your users (and it clearly does based on the videos we've seen), it is far better to get that functionality out to users and have them give you feedback before you add more functionality in. In fact, if money isn't a big deal and you'd rather not "launch" then open up your beta so that you at least get a wider pool of people using the app and letting you know how it goes. If launching with phase 1 gives you a much-needed mental/emotional lift, then that's worth considering. Life is short... Two cents!

  • @Gavinski said:
    @espiegel123 so this will be MPE ready?

    If, like photon, it records and plays back all midi it receives (on the channel received), yes.

  • Definately 1
    You can then work at an easier pace on prefecting the automation.

  • Option 1 definitely. Get it out the door.

  • edited March 2021

    @blueveek You will probably be better to run a poll.

  • edited March 2021

    @espiegel123 said:

    @Gavinski said:
    @espiegel123 so this will be MPE ready?

    If, like photon, it records and plays back all midi it receives (on the channel received), yes.

    No, Atom doesn't support MPE yet (it came up in this thread a few months ago, but demand was very low, so I deprioritized it).

  • Option 1 - get the monkey off your back! :smile:
    It sounds like there is plenty to dig in to with this release as it stands.
    I'm also happy to pay for both as upgrades - your time should be financially rewarded!
    Good luck with the release! Cheers for the update. B)

  • @blueveek said:

    @espiegel123 said:

    @Gavinski said:
    @espiegel123 so this will be MPE ready?

    If, like photon, it records and plays back all midi it receives (on the channel received), yes.

    No, Atom doesn't support MPE yet (it came up in this thread a few months ago, but demand was very low, so I deprioritized it).

    What midi info is atom not recording? CCs ? Channel info?

  • @espiegel123 CC.

    It would be very annoying to record CC and not be able to edit/delete it (e.g. if a new layer or a different phrase is recorded).

    Regarding channels, you can pick whichever channel to output on (there's a new toolbar on the left that was shown in previous screenshots). Atom listens to everything it receives, and filtering input can be done at the host level.

  • I personally wouldn’t use it without automation. I automate everything :lol: But I’m not a randomization person, I’m a sequence what I want it to do person.

  • edited March 2021

    @drez said:
    I personally wouldn’t use it without automation. I automate everything :lol: But I’m not a randomization person, I’m a sequence what I want it to do person.

    To clarify: in my post, "automation" meant CC editing. Atom itself is automate-able (parameters exposed etc.).

  • @blueveek said:
    @espiegel123 CC.

    It would be very annoying to record CC and not be able to edit/delete it (e.g. if a new layer or a different phrase is recorded).

    Regarding channels, you can pick whichever channel to output on (there's a new toolbar on the left that was shown in previous screenshots). Atom listens to everything it receives, and filtering input can be done at the host level.

    I disagree somewhat. I would strongly recommend an option to be able to record all received information and play it back even if it weren’t editable (other than say maybe select all and moving everything in time).

    It is the single biggest hole in the MIDI recording AU world..the ability to simply capture and playback everything that comes in.

    Sure there are lots times where one wants to edit the CC stuff...but I’d rather be able to capture and play everything without editing than not have that.

  • Definitely release it! the current feature set looks amazing and music will be made!

  • I vote for going with option #1. While automation is great, it's not like there aren't other ways we can do it right now on iOS, so that's not really a deal breaker. Plus, it means that we'll get multiple updates, which is always more exciting! It's why I always like Hanukah over Christmas - more days of presents!

  • Number one - out now. improve over time.

    I want to be able to IMPORT and edit MIDI without having to jump to a full DAW
    That’s enough for me right now. I know you’ll get the rest right eventually and it sounds like you need some time to think about it passively and inspirationally without forcing a decision.

  • @espiegel123 said:

    @blueveek said:
    @espiegel123 CC.

    It would be very annoying to record CC and not be able to edit/delete it (e.g. if a new layer or a different phrase is recorded).

    Regarding channels, you can pick whichever channel to output on (there's a new toolbar on the left that was shown in previous screenshots). Atom listens to everything it receives, and filtering input can be done at the host level.

    I disagree somewhat. I would strongly recommend an option to be able to record all received information and play it back even if it weren’t editable (other than say maybe select all and moving everything in time).

    It is the single biggest hole in the MIDI recording AU world..the ability to simply capture and playback everything that comes in.

    Sure there are lots times where one wants to edit the CC stuff...but I’d rather be able to capture and play everything without editing than not have that.

    I 100% agree with this

  • @espiegel123 I'll think about it!

  • @blueveek said:
    @espiegel123 I'll think about it!

    That would be great! In this 'mode', ATOM could be really dumb.

  • @blueveek said:
    @espiegel123 I'll think about it!

    There is a lit of interest I. Recording mpe at the moment after the release of the swam sounds. Loopbud was released but currently does not record ccs or record all channels, whichever one of you does this will definitely get sales. I'll certainly be happy to explain in a video why a mode like this would be so useful, even without editing.

  • Unless doing option 1 delays releasing w modular automation by a lot, it seems to be the most optimal one? It will make ppl like me, who doesn't need the full fledged version right now, very happy. And for people that are willing to wait, it would be no different.

  • @Gavinski said:

    @espiegel123 said:

    @blueveek said:
    @espiegel123 CC.

    It would be very annoying to record CC and not be able to edit/delete it (e.g. if a new layer or a different phrase is recorded).

    Regarding channels, you can pick whichever channel to output on (there's a new toolbar on the left that was shown in previous screenshots). Atom listens to everything it receives, and filtering input can be done at the host level.

    I disagree somewhat. I would strongly recommend an option to be able to record all received information and play it back even if it weren’t editable (other than say maybe select all and moving everything in time).

    It is the single biggest hole in the MIDI recording AU world..the ability to simply capture and playback everything that comes in.

    Sure there are lots times where one wants to edit the CC stuff...but I’d rather be able to capture and play everything without editing than not have that.

    I 100% agree with this

    +1!

  • MPE is becoming essential. More and more apps and DAW's support it at this moment. So please give it support. And a +1 for MacOS M1 support.

  • Option 1 for me.

    MPE would be great in a future update.

    Thanks for all your hard work.

  • Selfishly I’d like option 1, mostly because I wanna start experimenting with how it fits into my workflow.

    But there’s some good points raised here re. Option 2 and if that feels right to you then it’s the right option.

    PS. Fwiw LK shipped with very basic automation which works just fine. I have every faith it’ll improve but it’s not stopped me finishing a track with it.

This discussion has been closed.