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

1394042444556

Comments

  • @tk32 said:
    OK...

    I've changed my mind.

    I now vote for Option 1

    Literally, anything that will put a stop to this runaway thread. :D

    I think this thread is unstoppable now. The hype train is rolling, credit cards are creaking in expectaion, my bank manager is sweating cold sweat.

  • edited March 2021

    There is a sweet spot between something so immediate and simple to use that you, you know use it, versus something so goddam deep that it is too intimidating to use in the first place. For all it’s acknowledged shortcomings, Atom 1 falls happily and heavily on the usability side. The UI for Atom 2 is already looking pretty busy - I’d hate for it to succumb to a feature bloat so huge it renders it too far on the deep side. That after all looks to be the big appeal of its more limited ‘rival’ LoopBud - just fire and forget. A release now would give time for reflection over what, and how, future development should proceed - without the future risk of compromise to the all-important usability that ‘can you add just one more thing...’ implies.

  • Naturally option 1!

    Then plenty of time without stress to finish what’s left out in this build...

  • need release now, there is currently no guarantee developer will be healthy and sane to complete update at a later date

  • edited March 2021

    Option ONE 🤩
    It's a good time to release something new. Atom 2 will surely be THE app of early 2021 👍🏻 !

  • @Svetlovska said:
    There is a sweet spot between something so immediate and simple to use that you, you know use it, versus something so goddam deep that it is too intimidating to use in the first place. For all it’s acknowledged shortcomings, Atom 1 falls happily and heavily on the usability side. The UI for Atom 2 is already looking pretty busy - I’d hate for it to succumb to a feature bloat so huge it renders it too far on the deep side. That after all looks to be the big appeal of its more limited ‘rival’ LoopBud - just fire and forget. A release now would give time for reflection over what, and how, future development should proceed - without the future risk of compromise to the all-important usability that ‘can you add just one more thing...’ implies.

    I second that, too.

  • There is also a sweet spot between being sober and being blind drunk.

    Doesn't make it any easier to land there though. :p

  • Option 1

    And please add MPE support in due time. I’m more interested in recording it than in editing it.

  • I've got a mild preference for option 1, but can live with either decision. Atom 1 is still pretty damn good!
    As someone who's been in the software industry for decades, I know there's extra stress that comes with trying to deliver the perfect product 1st time vs releasing a minimum viable product (MVP) and then iterating on it to make it good. It sounds like you're waay beyond having an MVP, so my suggestion would be to release now and start getting feedback on what's important to people.
    Me? I'd love MPE support, but as long as I know it's somewhere on your radar I can live with that. I'd also love bug free software, but again I can live with something that's pretty solid and going to approach bug-free over time. In fact, there's a zillion features I'd like if I put my mind to it, but more than anything I'd like to see a product that's pretty solid, does much of what I want now, plus visibility of some sort of sequence of what you're planning to add next.
    There's a lot of stress in deciding "what to do next?"; one solution to that stress is to take input from your users, and let them have input to your next move. If something like MPE is only important to 5% of users, then it probably wouldn't be at the top of your "to do" list and (as someone who wants MPE support) I can live with that. You can get people to prioritise bug fixes vs new features, and generally take the burden of deciding what to do next off your shoulders by letting others have their say.
    Maybe even run a poll here every few months, throw your top 3 feature ideas out there and let people vote on them. You won't keep everyone happy, but if people can see you're taking suggestions they'll be more inclined to accept whatever you decide.

  • @tk32 said:
    There is also a sweet spot between being sober and being blind drunk.

    Doesn't make it any easier to land there though. :p

    Hah, true enough.

  • edited March 2021

    @Gavinski said:
    @Jeezs said:
    Don’s understand the dilemma.
    If it is release now those who want to buy it can buy now, it those who want to wait can wait. 😀😀
    Where is the problem ?

    Exactly. Releasing now is a no-brainer

    Agreed. If it’s in a finished state up to a stopping point, push it out. Can always add those other features later as an update or even an IAP.

    I’d say option #1

  • I would say option 1 so that you don’t feel pressured to overwork yourself. Release now, and take the necessary time to implement everything else you have planned.

  • Option 1. We can create and get comfortable with the app as it is. You can get immediate feedback and any additions will be a huge bonus.

  • edited March 2021

    Initial Atom 2 Release
    1. Piano Roll record/Edit MIDI note information including channel #
    2. CC Looper record MIDI CC# with the ability to undo/delete/overdub and edit channel#
    3. Support for different levels of CC precision
    4. The ability to have CC sequences in sync with MIDI note sequences
    5. MIDI Mute controls for output (e.g. route an Atom sequence to control CC mutes or notes)
    6. Export options: specify note information, channels, and CC numbers to include in MIDI files.
    7. State Savings (this is the biggest drawback of Photon AU)

    I think a CC Looper where you record/edit via traditional looper techniques rather than a piano roll editor would be very useful as often you want to tweak automations with the MIDI note sequencer running. Having notes and CC in sync yet independent would be a very useful modular functionality as there are many sources of CC via apps or hardware.

    Continuous versus Discrete MIDI
    A big difference between CC and MIDI note information is their continuous versus discrete nature when changing clock speed as you have to deal with interpolation rather than relatively simple scaling with notes. This is also another reason why a separation yet ability to sync them together would be better.

    User feedback on what sorts of interpolation options for CC they want seems necessary.

  • I think option 1 is best, and you make customers happy twice, once on release and second with a new features update :)

    I can underdstand wanting to release a perfect app, but it's not possible.
    Getting it out sooner will reveal some more bugs as it's a wider user base which will need fixing anyway, so after that you can concentrate on the automation.

  • edited March 2021

    @blueveek @tk32
    How about new thread with a poll for option 1 or 2 starting , now calculate results on Monday ? ( If someone already suggested this please ignore this comment)

  • @joniqwest said:
    @blueveek @tk32
    How about new thread with a poll for option 1 or 2 starting , now calculate results on Monday ? ( If someone already suggested this please ignore this comment)

    This thread is actually fine, I am keeping track of what everyone has to say believe it or not! I'm amazed at the level of support and nuance in analyzing the situation from everyone here.

  • MPE please. You could be the first one on iOS — excuse me — iPad OS! So go for it. Automation can bee done in other Apps for now. But MPE‘s a killer feature.

  • @blueveek said:

    @joniqwest said:
    @blueveek @tk32
    How about new thread with a poll for option 1 or 2 starting , now calculate results on Monday ? ( If someone already suggested this please ignore this comment)

    This thread is actually fine, I am keeping track of what everyone has to say believe it or not! I'm amazed at the level of support and nuance in analyzing the situation from everyone here.

    👍👍👍

  • @Ploe said:
    MPE please. You could be the first one on iOS — excuse me — iPad OS! So go for it. Automation can bee done in other Apps for now. But MPE‘s a killer feature.

    Nothing against MPE but I think a lot more people would use and appreciate automation before MPE. It is a standard feature in producing a track.

  • @gusgranite said:

    @Ploe said:
    MPE please. You could be the first one on iOS — excuse me — iPad OS! So go for it. Automation can bee done in other Apps for now. But MPE‘s a killer feature.

    Nothing against MPE but I think a lot more people would use and appreciate automation before MPE. It is a standard feature in producing a track.

    No question. 👍🏼

  • @gusgranite said:

    @Ploe said:
    MPE please. You could be the first one on iOS — excuse me — iPad OS! So go for it. Automation can bee done in other Apps for now. But MPE‘s a killer feature.

    Nothing against MPE but I think a lot more people would use and appreciate automation before MPE. It is a standard feature in producing a track.

    As an FYI, all that the level of MPE support suggested entails is that it record incoming MIDI (including the channel the events come in on) and be able play it back. There is less to it on the recording/playback side than most people realize.

  • Option 1 but only if it records and plays back midi CCs (actually, preferably all MIDI, period). I don't care at all if they're editable. That can wait for a later release (preferably IAP). Some kind of rudimentary display just to show that cc data exists and perhaps a basic curve.

    I would probably not use Atom 2 much without that. Sustain pedal anyone?

    As for MPE, maybe along the same lines? Just record it, but only allow note editing. I can see making an effective MPE editor could be a huge challenge.

  • If it can’t record CC I suppose it will not record pitch bend and I wait for this for recording iFretless bass lines since Atom 1... please Atom 2 needs CC automation even if not editable!!

  • @espiegel123 said:

    @gusgranite said:

    @Ploe said:
    MPE please. You could be the first one on iOS — excuse me — iPad OS! So go for it. Automation can bee done in other Apps for now. But MPE‘s a killer feature.

    Nothing against MPE but I think a lot more people would use and appreciate automation before MPE. It is a standard feature in producing a track.

    As an FYI, all that the level of MPE support suggested entails is that it record incoming MIDI (including the channel the events come in on) and be able play it back. There is less to it on the recording/playback side than most people realize.

    I still think it’s lower priority.

  • The common sense pragmatic approach is to release what you have today keep the masses happy then release an update when you add a decent new feature like automation.

    It’s a Win Win situation for all.

    @blueveek - thanks for all your hard work. I’d say the count is around 80% for option 1 from what I’ve noticed over the last few days :).

  • After reading everyone’s ideas I go with ..
    Option 1
    I now agree with release quick and with regular updates, if you can. I remember devs that do it this way and it seems a professional way to do things.

  • @krassmann said:
    1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1....... 😊

    Get the feedback of the community for the version without automation. You will get a lot of bug reports and feature requests for this core functionality. And I would surely handle this with higher priority than the automation. First getting the core straight, then extend it. I’m quite sure the automation that we’ll get with the iterative approach will be a different one. Good automation is not trivial. Take your time for this big feature and get the feedback of the release now.

    I’m a software architect with 30+ years in the industry, being a developer myself for many years. I know that in the world of commercial software development with overambitious timelines and unrealistic promises to customers the developers are often pushed to release software they are not happy with. I know your pain but now you are overreacting. Look how open source projects are doing it, they also release more often. Also don’t create a feature monster now. Put all your need for perfection in the core functionality. As a dev I’m sure you love UNIX, so respect the UNIX philosophy, stay focused, do one thing and do it well.

    That’s my advice and also a bit selfish wish of an iOS musician 😄

    this

  • Option 1! Please ship now. Never been so excited about an app. In fact, this is the only reason I signed up to this forum. :D

This discussion has been closed.