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

1293032343557

Comments

  • @SNystrom said:
    Perhaps @joniqwest could change the title of the thread once again.

    ATOM Piano Roll update: A work in progress

    "Coming soon" has a different meaning to each individual.

    That way people hopefully won't be inspired to keep asking when — like the kids in the car asking "are we there yet?" Every 15 minutes. 🙃

    It will arrive eventually, and it will be worth the wait.

    Yes 'work in progress' title is a good idea.
    'Cooming soon' is not correct for the customer and for the others developer.

  • @RajahP said:
    I > @freddy said:

    I think the July 'coming soon' title is a joke today.
    Too many words for a product that is still not ready after more than 4 months.

    Should just go ahead and release. and the other stuff can come later.. Nobody is going to be mad... and ‘I’ will even pay for it.. don’t care about ‘free update’. Just release it Veek..

    Thanks..😉

    yes i think so too

  • @blueveek said:

    @Owgill said:
    Thanks @RajahP. From the Atom 2 interface pics I’ve seen I did see the probability icon, and this is super useful. However I didn’t a per note percentage. I’m probably mistaken though.

    Just curious: would you want the probability to reset on every loop, or stick around? How do you see it comparing with a global "clip-level" probability setting that applies a probability equally to all notes?

    @blueveek , I have some thoughts about probability that I'll throw in, mainly from my desire to have some human feel to live playing situations. I'm not 'asking' for these, they are just things I like which you might consider at some point.

    Audio Damage had the 'Tattoo' drum machine (which is no longer around). It had a control for probability of playing the programmed notes (not note by note, just per pattern) but also the probability of playing unprogrammed notes, so random other notes might appear, and you could select on which grid size, so for example random 8th notes might appear, with probability decided by a slider. I found this pretty good.

    Referring to your question about it resetting every time, for the live variability situation that is obviously desirable. If you're just looking for inspiration, not so necessary. A feature that could be cool is to have 'randomise again every x bars', so for example a randomly generated beat plays for 16 bars, then another randomisation occurs for the next 16. Of course then you could get meta about it all and randomise the frequency with which randomisation occurs...

    On the Desktop I had a midi AU called 'Stochas', which was all about probability sequencing. One of it's cool features was that you could enter several notes per step, and assign each a high/medium/low probability of being selected as the note that would play. In this mode only 1 of the notes would play. The more interesting thing was then you could select other chains of notes that would play dependant on which of the notes was chosen. So you could could have a selection riffs or melodies that would play dependant on what original note was selected. I often find a simplified version of this would be good for drum sequencing, where you might want, for example, snare hits to occur randomly, but some will only sound good if they are considered pairs or groups of notes, say 16th notes.

    Anyway Stochas is no longer developed, and it's developer has open sourced it. It would great to see someone in iOS land grab it and release a version :) There are some Youtube videos around of it if anyone's interested.

  • The user and all related content has been deleted.
  • @owgill thanks :) I was obviously feeling more enthusiastic than normal this morning! I missed your reference to Stochas earlier. It was a cool product.

  • "I don't know" is an answer I've grown a bit weary of myself. No, I don't like it either, it keeps me on my toes, and makes it hard to decide when something is good enough. Makes it difficult to know when to stop. Despite that, it's no secret that I've been aiming at a late 2020 release. While still technically achievable, there's two reasons informing what I'm about to do next.

    The first one is simple. While everything is rock solid with the latest beta, there's a couple of key features that I'd really like to get right from the start, especially around automation and integration with AUM. This is important, because it'll set the tone for how the workflow feels like. So I'm after a bit more iteration and experimentation, instead of compromising and releasing something that might change later: you'd be surprised at how many alternative versions of every little thing I've tried out in Atom 2; users would go mad if I did this kind of prototyping publicly.

    The second one is also simple, but actually weighs in the most for this particular situation: burnout. I need a break. Spending every last bit of my free time developing Atom 2 for over a year now, is taking a toll. It's for the best (for my own health, but also the quality of what I'm developing) for me to take it easy for a couple of weeks.

    In principle, I should be upset about this delay too: missing Black Friday and Christmas isn't "smart". Heck, this entire thread isn't "smart" – you'd be surprised how sharp and persistent of a drop in sales an update announcement can make, especially when the details on how the update will come are cloudy, as well as compatibility issues with version 1 being likely. But I still think it's a good idea to keep the ideation and iteration process public, so I appreciate the conversation.

    What I got from each one of your comments is excitement and anticipation. I hope what you got from all my replies is: it'll be fucking worth it.

  • @Liquidmantis said:

    @Lil_Stu07 said:
    We still looking at a 2020 release @blueveek?

    I saw a flurry of new posts and my excitement went up. Stop pulling blueveek from his coding cage!

    :D I'll second that. No disturbing the cage!

  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • edited December 2020

    @blueveek Take a break, take your time. A (early) 2021 release isn't that bad, and take advantage of the lowered Apple commission starting at januari 2021.

  • I think it's a privilege to witness this development process and I admire your willingness to listen to us. Take the time it takes, no need to rush. And please, don't get burn out.

    We will wait patiently.

  • You spending a few minutes to explain you need a break is absolutely fine
    You deserve it
    Delay the release till you’re happy, you’re in charge
    Extremely nice of you to inform people

    Bm3 as an example, just keeps people guessing, which turns into resentment
    You’ll know when the times right
    Good luck

  • If you want to blame anyone for not having Atom 2 in your hands yet, blame us beta testers.

    ...we're the reason for (a fair amount of) the feature creep.
    ...we're the reason some of the existing features have been redesigned/refactored.
    ...we totally failed to discourage him from implementing awesome features now that would normally have been postponed for a 2.x update.
    ...and we're the reason Blueveek has finally agreed to take his own physical and mental well-being more seriously and not crunch in order to meet an arbitrary deadline.

    This app is special, and it'll be worth the wait when it's ready.

  • Whenever it drops it will be amazing and exactly the right time. Much love, @blueveek - it's heartening to know that you realise the importance of your mental health! Music is incredible and I'm sure that the release of Atom 2 will be to benefit of my music, but I don't want that to happen at the expense of your well-being.

    2020 has been a hell of a year so far. If you can find a way to relax as much as possible during the dying embers of it, jump at it - that goes for everyone, not just BV!

  • By all means take your time, get some rest. I was simply asking if, with all the excessive feature requests, this was still planned for a 2020 release like some beta tester said earlier. Funny that a simple yes or no question generates so much response. 🤷🏾‍♂️🙄

  • I’m good with a 2021 release if it means getting everything right. Just glad to know it’s on its way.

  • Ok.. the consensus is.. take all the time you want (well publicly)... never was one the went with the crowd.. I say, if the beta is solid.. let it go.. And, enjoy the season with family, friends, etc etc.. The term is RE-CREATE (recreation).. it’s part of the creation process.. and besides... I NEED it.. 🙂

    Bless..

  • @blueveek take care of yourself brotha. Happy holidays to you and yours.

  • Take care @blueveek and all beta testers @tk32, @winconway included
    Enjoy your break, more than well deserved ;)
    Many thanks

  • @blueveek said:
    "I don't know" is an answer I've grown a bit weary of myself. No, I don't like it either, it keeps me on my toes, and makes it hard to decide when something is good enough. Makes it difficult to know when to stop. Despite that, it's no secret that I've been aiming at a late 2020 release. While still technically achievable, there's two reasons informing what I'm about to do next.

    The first one is simple. While everything is rock solid with the latest beta, there's a couple of key features that I'd really like to get right from the start, especially around automation and integration with AUM. This is important, because it'll set the tone for how the workflow feels like. So I'm after a bit more iteration and experimentation, instead of compromising and releasing something that might change later: you'd be surprised at how many alternative versions of every little thing I've tried out in Atom 2; users would go mad if I did this kind of prototyping publicly.

    The second one is also simple, but actually weighs in the most for this particular situation: burnout. I need a break. Spending every last bit of my free time developing Atom 2 for over a year now, is taking a toll. It's for the best (for my own health, but also the quality of what I'm developing) for me to take it easy for a couple of weeks.

    In principle, I should be upset about this delay too: missing Black Friday and Christmas isn't "smart". Heck, this entire thread isn't "smart" – you'd be surprised how sharp and persistent of a drop in sales an update announcement can make, especially when the details on how the update will come are cloudy, as well as compatibility issues with version 1 being likely. But I still think it's a good idea to keep the ideation and iteration process public, so I appreciate the conversation.

    What I got from each one of your comments is excitement and anticipation. I hope what you got from all my replies is: it'll be fucking worth it.

    That sucks about the drop in sales. Hopefully you’ll win it back in sales for atom 2. I think one thing this thread has done in your favour is really create hype and buzz around the release.

    I know I’ve been (jokingly) trying to get you to release it ASAP, but in seriousness we’re lucky to have devs like you that have the smarts to make something like this, and the patience to take the time to listen and make things right for such modest financial gains.

    Thanks for being honest and setting expectations - We all have plenty of other things to experiment with at the moment I’m sure. Have a good break!

  • edited December 2020

    @j_liljedahl @blueveek
    Regarding the upcoming integration between AUM/Atom2/‘a controller developer’
    Is it based on selectable ‘control surface’ port or hardware being ‘automatically’ recognised when plugged in?
    Hypothetically - if one would try to emulate these controllers from f.e Lemur or Mozaic, what would be the best approach?
    Any pointers much appreciated! :)

  • @0tolerance4silence said:
    @j_liljedahl @blueveek
    Regarding the upcoming integration between AUM/Atom2/Novation
    Is it based on selectable ‘control surface’ port or hardware being ‘automatically’ recognised when plugged in?
    Hypothetically - if one would try to emulate these controllers from f.e Lemur or Mozaic, what would be the best approach?
    Any pointers much appreciated! :)

    The only "integration" on AUMs side is that Victor of Atom Piano Roll asked for a way for plugins to change their node background color.

  • edited December 2020

    Well, we've discussed a bit more than that :) At the moment what's available is setting node colors in AUM, automatically receiving the track and slot index from AUM into Atom, and using instance naming from AUM inside of Atom's UI. This should be sufficient for Ableton-esque clip arrangements, for now.

    Regarding hardware integration, it's all automatic (and the layout and pad lighting on the controllers mimics the node arrangement in AUM, or other hosts that decide to support the APIs we've converged on). Controllers can be individually enabled/disabled.

    @0tolerance4silence For emulating controllers, check out what @tk32 managed in a previous demo. It's pretty wild what you can do with just ChordPolyPad alone, I'm sure a Mozaic script can take this a lot further.

  • Hi @blueveek Will the new Apple M1 chip supported by Atom 2? I ask this because Drambo is working very well on my Mac Mini M1 running Big Sur.

  • @Pierre118 said:
    Hi @blueveek Will the new Apple M1 chip supported by Atom 2? I ask this because Drambo is working very well on my Mac Mini M1 running Big Sur.

    It's on the radar, and I think a worthwhile platform for all developers to invest in. However, to do that sooner rather than later I'd need to buy one of those Macs, and that's not something I can justify cost-wise just yet. That being said, given Atom 2's embeddable nature, I actually wouldn't be surprised if I end up porting it to other platforms even sooner than M1's.

  • @blueveek politely asking for the ETA, still 2020 on the horizon? Take your time off if needed and celebrate some Christmas... 👊🏼🙃

  • @david_2017 said:

    I appreciate the ping. Short answer: no, I'm taking a short break until the end of the year. Here's the long answer: https://forum.audiob.us/discussion/comment/888436/#Comment_888436

  • edited December 2020

    @blueveek said:

    @david_2017 said:

    I appreciate the ping. Short answer: no, I'm taking a short break until the end of the year. Here's the long answer: https://forum.audiob.us/discussion/comment/888436/#Comment_888436

    Thanks for the honesty! Will read the Post now
    Enjoy your freedom and get some sleep and things that make you happy!

    Edit: oh ya, for God‘s sake... please take a vacation and fuel up some energy and love!

  • @blueveek said:

    @Pierre118 said:
    Hi @blueveek Will the new Apple M1 chip supported by Atom 2? I ask this because Drambo is working very well on my Mac Mini M1 running Big Sur.

    It's on the radar, and I think a worthwhile platform for all developers to invest in. However, to do that sooner rather than later I'd need to buy one of those Macs, and that's not something I can justify cost-wise just yet. That being said, given Atom 2's embeddable nature, I actually wouldn't be surprised if I end up porting it to other platforms even sooner than M1's.

    That looks promising, @blueveek

    Have a nice holiday break!

  • @blueveek take your time. Relax and enjoy the break. Well deserved.

This discussion has been closed.