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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
ATOM Piano Roll update is coming soon
This discussion has been closed.
Comments
First of all, it's a very natural thing that some users are literally crying for features that others would probably never touch. Everyone has their own workflow and being used to find workarounds and alternative solutions while using limited apps, us iOS app musicians have certainly shown how much can be done already.
As for your side note, well yes, even a restricted "record/undo/delete" CC recording will, for me, make the difference of the app being usable or not.
Maybe it's because I'm a keyboard player. Pitch bend and Modwheel (and channel aftertouch sometimes) are part of my playing and I'd be fine for now to undo and redo a recording when the notes have to move. But if they weren't recorded at all then I see no point in using Atom2.
Yep
Option 1. If what I'm reading about how deep this rabbit hole might go is true I will have figured it all out by the time automation is ready to ship.
Option 1 please!!
Why in the world do we think waiting for option 2 will stop anyone here from flooding him with feature requests and complaints?
You already have a more than capable “minimum viable product” as they say in the industry. Let her loose and the patient angels can play with LK until the update comes.
Probably, but those don’t materialize into lasting ATOM 2 ratings if he goes with option 2. Also blueveek has posted that money isn’t the incentive for this project. I’m hoping for the option that ends up with a 4-5 star app and a motivated and interested developer. ATOM 2 looks awesome
Think there are beta testers here who only want it for themselves...😜
This thread is nine months old , time to deliver the baby 😎
Is it out yet?
Just reading between the lines (or maybe not even that, it just seems obvious), the main issue is whether the developer is going to keep nose to grindstone to get option 2 done, or not. If he releases a version now, then the drive toward getting automation done will lose much of its force, so automation will take longer to get here. It's only human nature.
Or, if he waits, life may intervene and we’ll be speculating five months or a year from now about when it will be ready.
hes, and anyone else with similar thoughts.
I suggest you all go back to page 38 of this thread and read again what Blueveek requested of "us".
He told us what he would do, take the man at his word.
Clearly Option 1, release early and often.
After 1,5 years of waiting, time to turn to Xequence TWO. :-)
It’s march of 2021...obviously option 1.....
Well - hard decision.
I would go for #1 - just to use it as i have stopped using Atom1 for missing/not working features and would love to continue making music with a working Atom environment.
@blueveek : As a lot of people seem to not need/want your definition of Automation (editing CC values) maybe you could think about an In-App option for this later on. This depends possibly a little on your decision if you make Atom2 a free upgrade (replacing Atom1) or a new App with a new pricing model.
Just a thought.
I’m starting to worry that this app has been completely ‘overproduced’ because of beta testers wanting it to solve every music making situation that exists. I just hope it’s maintainable after release.
Instabuy regardless of releasedate
OK...
I've changed my mind.
I now vote for Option 1
Literally, anything that will put a stop to this runaway thread.
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 😄
@blueveek I think down the track it will be the same situation. When is automation coming? Is it here yet? I think all you would do is move the same experience a few months down the track and experience it twice. Just trying to look at it from your perspective.
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.
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.
Good point @Svetlovska.
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
Option ONE 🤩
It's a good time to release something new. Atom 2 will surely be THE app of early 2021 👍🏻 !
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.
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.