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
Option 1 now and add automation and striped curtains in updates Msr Veek ... all his work isn't earning you a penny while it's sitting on the bench. Should be a very popular app with an eager audience.
Must say I’ve been pleased to read so many supportive and sensible responses above.
The problem with Atom2 - speaking as one of the very small number of lucky beta/QA testers - is that once you start using this deep app, it’s so very easy to keep thinking of deeper and deeper ways you would like to use it. In other words... you can’t help thinking of new niche use-cases that suddenly require the dev to expose more settings or a raft of new tick boxes that enable users to override default settings under the bonnet that were previously assumed would never need to be adjusted.
I must accept that responsibility for some of the delays to releasing this app rest squarely with me. This app is nothing if not ambitious (as you will soon see). And you should see some of the deep and exciting stuff we’ve already pencilled onto the (potential) roadmap for a 2.X update on our beta tester’s Trello board! (feel free to ask about my obsessive enthusiasm for a ‘state machine’ add-on)
As both a modular piano roll and clip launcher, this app needs to be versatile enough to slot into almost any host and/or workflow... no easy task. It also needs to strike the right balance between power and flexibility and ease of use... an even harder task. And on top of all this it supports deep integration with Launchpad hardware controllers!
Suffice it to say... I’m completely torn between supporting option 1 and option 2. I wish Blueveek good luck in making his choice. It will be awesome whenever it releases: now or later.
Option 1 and those who wanna wait for 2, are more than welcome hehe i wanna get this thing rolling and get familiar with it!
I'd say option 1 with draft ,delete automation, reverse automation , inverse automation buttons
Later on detailed editing automation can be added
BUT
if option 2 requires GUI rearrangement , major code rewrite , then I'd prefer waiting for a polished release
This is like the hype man before a show asking "can i get some NOIISSSEEE??!?!?!" and if we are loud enough he'll finally drop this bad boi
Another +1 for option 1 Plus the CC recording. Even if it can't be edited on release it's still something. It'd be nice if overdub was included just to refine a looped part for example but still. I like Xequence but I'm tired of having to rely on an external app and having to load the same songs on multiple apps, which is why I'm eager to try the new Atom option 1. I'm fine with using Drambo for automation; doesn't seem like a hassle imo. I just want a convenient piano roll for the compositional bit.
A key concept in AGILE software development is release early and release often. It is a more modern approach than waterfall which relies on one big release later. Your users get more value from the frequent releases, the users get to be testers and provide feedback (if you want it) and as long as Option 1 doesn't come with a price and what comes in 2.X also has a price, then I'd say do Option 1 at whatever upgrade fee you were planning... and then only make the automation available to those who have the updated Atom 2 and paid your upgrade fee.
Release early and release often. We do two week sprints.
Exactly. Releasing now is a no-brainer
I cant argue with that and I follow same practice in my workplace as dev.
However, in my personal projects I definitely feel this need to "complete" or "perfect" or "reach end-goal" before releasing. I'm not sure its logical or rational and most likely is a more emotional response.
If the goal is to fulfil a need of the community then it makes sense to make it an iterative process.
I think there's also a perspective of what makes the most people happy.
Releasing option 1 now makes a lot of people happy now.
At a later date when the version with the automation is released, then all who wanted automation will be happy to have that feature.
I can't see any reason why releasing option 1 now, should make those who are waiting for option 2 unhappy...
Because they would have had to wait for option 2 anyway.
All the people using option 1 now will be happily making music with it, because it serves a music making purpose that is needed now.
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.