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

1282931333456

Comments

  • ^ I think we will have to settle for just midi atm. Atom doesn’t produce audio. Well not yet :)

  • @blueveek said:
    All the trigger settings you'll probably ever want :)

    There's presets you can choose from: Ableton-style, Launchpad-style, the modes in BM3 like "Hold", "One-shot" and "On Release", and the Atom-flavoured "Legato trigger".

    The bottom settings are determined by the preset, but you can build your own: you get complete control of everything that happens when you press a pad, or when Atom receives a note or CC message on from a master arranger instance or some other plugin.

    Whoa. Crazy. Did not know this would have clip launching.

    @blueveek A suggestion comes to mind, if it’s not already been thought of, is to have a clip view without the piano roll. That way you could save a lot of screen space, and be able to launch clips once you’re done making them in the piano roll.

    Haven’t been following this, nor have I read through all the thread, just something that came to mind. :p

  • edited December 2020

    @Richtowns said:
    ^ I think we will have to settle for just midi atm. Atom doesn’t produce audio. Well not yet :)

    Yes, I want to make sure I manage expectations here. Ableton live set export seems doable, I'll have to learn how to do it, and won't come in 2.0. Feature creep is real.

    @Dunamis said:

    Whoa. Crazy. Did not know this would have clip launching.

    ...also seamlessly interface with external controllers. There's a lot more customisability that isn't shown in the screenshots which I hope at least a handful of people take advantage of :)

    @blueveek A suggestion comes to mind, if it’s not already been thought of, is to have a clip view without the piano roll. That way you could save a lot of screen space, and be able to launch clips once you’re done making them in the piano roll.

    Haven’t been following this, nor have I read through all the thread, just something that came to mind. :p

    Thanks for bringing it up. Yes, master orchestrator views (or separate AUs) are planned for offering more cohesive clip launching and track building. The main theme however (you might've guessed it) – not in 2.0, but in a 2.x update.

  • @Poppadocrock cheers, I’ll keep an eye out and probably get 2 as I’m always happy to learn new approaches to making tunes.
    I’ve recently started using aum so I’m sure it’ll be cool 👍

  • @horsetrainer have you looked into RhythmBud? That combined with a generator like ChordBud 2, then record into a piano roll of your choice. It should cover at least part of what you're outlining.

  • We still looking at a 2020 release @blueveek?

  • @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!

  • @blueveek said:
    Feature creep is real.

    I just had this image of creepy musicians haunting your dreams with multiple feature requests, like zombies asking for brains.

    “Audiooooo!”

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

    I'm not Blueveek's spokesperson, but as a beta tester I can confirm he is still working hard on Atom.

    Nobody wants to get version 2.0 out more than him.

  • @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!

    LMFAO “Back in the cage!” whip cracks

  • edited December 2020

    @tk32 said:

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

    I'm not Blueveek's spokesperson, but as a beta tester I can confirm he is still working hard on Atom.

    Nobody wants to get version 2.0 out more than him.

    Godspeed @blueveek. Godspeed.

  • 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.

  • @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.

    Yes, but if the feedback in the thread is helping to inform the development in any way then I think it’s worth it.

  • @gusgranite said:

    @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.

    Yes, but if the feedback in the thread is helping to inform the development in any way then I think it’s worth it.

    Definitely! It’s great to see a developer who is so engaged with user feedback.

  • Seems to be down to feature creep with external controller support etc. I’m just looking forward to having an AU multitrack midi recorder in AUM.

  • 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.

  • 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..😉

  • @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.

This discussion has been closed.