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

1222325272856

Comments

  • edited November 2020

    @0tolerance4silence Tell me more about this. You mean a time offset in samples or beats that is applied per clip? Sounds a little bit like scrubbing that DJs do to sync up the beats.

  • @blueveek said:
    @0tolerance4silence Tell me more about this. You mean a time offset in samples or beats that is applied per clip? Sounds a little bit like scrubbing that DJs do to sync up the beats.

    I think he means like manual latency compensation?

  • That would benefit me too. Some orchestral samples start early, and I have to nudge every section back by a little bit in NS2, which takes a bit of time.

  • @0tolerance4silence said:
    @blueveek
    Yes, a built in delay per instance. Samples or milliseconds.
    I think scrubbing is catching up to tempo over time. This would be just a simple positive offset.
    I’m usually checking the latency reported by the host on various devices and then doing manual ‘delay compensation’ where needed.

    This is a very useful feature in many MIDI sequencers. Best case is time offset per track -- as sometimes you find after tweaking your synth sound, you need to shift the track ever so slightly in one direction or another.

  • edited November 2020

    @0tolerance4silence I like the use-cases. The one I found most relevant for myself is essentially time-shifting the sequences that are routed into expensive plugin chains that introduce latency. So by adding a bit of manual offset, everything is on-beat again. Technically the AU API has an elegant solution for this problem, but it seems that not all AUs make use of it (at least not correctly). The nice thing is that because this is per-clip, you can target individual plugins to offset. It's also automateable :)

    @Skyblazer I've also incorporated your suggestions for more granular button-based movement on the X and Y axis. Let me know if something like this is what you've had in mind.

  • For the love of god, can we all stop asking for new features so this thing can be released!!!

  • @gregsmith said:
    For the love of god, can we all stop asking for new features so this thing can be released!!!

    ‘Hot’ Airware?

  • So this is the piano roll that @giku_beepstreet is going to incorporate in Drambo, right? 😎

  • @despego said:
    So this is the piano roll that @giku_beepstreet is going to incorporate in Drambo, right? 😎

    Yep it'll be fully incorporated as soon as AU hosting drops. Lol.

  • @gregsmith said:
    For the love of god, can we all stop asking for new features so this thing can be released!!!

    Amen 🙏

  • @Lil_Stu07 said:

    @despego said:
    So this is the piano roll that @giku_beepstreet is going to incorporate in Drambo, right? 😎

    Yep it'll be fully incorporated as soon as AU hosting drops. Lol.

    :#

  • @gregsmith said:
    For the love of god, can we all stop asking for new features so this thing can be released!!!

    👍🏻

  • @gregsmith said:
    For the love of god, can we all stop asking for new features so this thing can be released!!!

    Yep.. there is always tomorrow.. and, I need this today..

    The import a midi part, scale/key quantize to project key. etc etc etc.. Drum Computer, IBassist export, etc etc..

  • Perhaps we need to start a belligerent political discussion in here so Michael shuts down the thread and @blueveek gets no more new feature requests?

  • @lukesleepwalker said:
    Perhaps we need to start a belligerent political discussion in here so Michael shuts down the thread and @blueveek gets no more new feature requests?

    Please, don’t mix Trump and Atom. It can destroy the world.

  • @lukesleepwalker said:
    Perhaps we need to start a belligerent political discussion in here so Michael shuts down the thread and @blueveek gets no more new feature requests?

    Trump junior running for president in 2024, best news ever! 😛

  • @tk32 said:
    I now realise everyone was hoping for my video to a brilliantly executed piece of marketing for all of Atom's new features.

    ...and it was none of those things.

    What it was.. apart from being a nice little toe-tapper... was proof that Atom integrates so neatly with AUM that it lets you compose full songs in midi almost as if it were a regular linear DAW.

    My next video will be far more technically competent, show some advanced 2.0 functions, and give everyone a glimpse of what an amazing app this has become.

    i fully enjoyed your video as it stood!

  • @blueveek That looks perfect! Can be it used to move selected notes or the view of the window itself? If so, that would be ideal.

  • edited November 2020

    @Skyblazer said:
    @blueveek That looks perfect! Can be it used to move selected notes or the view of the window itself? If so, that would be ideal.

    Not yet. I’ve added this to the backlog, and as mentioned before, “features for power users” is a theme I’m quite interested in understanding more in the future.

  • @despego said:
    So this is the piano roll that @giku_beepstreet is going to incorporate in Drambo, right? 😎

    Wouldn’t that be something!

  • edited November 2020

    @RJB said:

    @despego said:
    So this is the piano roll that @giku_beepstreet is going to incorporate in Drambo, right? 😎

    Wouldn’t that be something!

    🤤

  • OK... but the problem with AUM is that doesn't have a timeline that you can situate the arrangement. It starts ALWAYS from the beginning and that is all, for what I know. We still need some DAW for composition and arrangement of a song.

  • edited November 2020

    @Vlad11 said:
    OK... but the problem with AUM is that doesn't have a timeline that you can situate the arrangement. It starts ALWAYS from the beginning and that is all, for what I know. We still need some DAW for composition and arrangement of a song.

    There's a very clear comparison between linear and clip-launching workflows that @Paulinko made earlier in this thread, I encourage you to read it: https://forum.audiob.us/discussion/comment/874811/#Comment_874811

    These are very different ways of composing and making song arrangements. Some people strongly prefer the former, some strongly prefer the latter, and I can definitely empathise with both schools of thought. Atom 2 is leaning heavily on enabling the clip-launching approach for now, while allowing for some linear arrangement approaches with "master Atom arrangers" and editable loop markers (but optimises for modular workflows).

    Ultimately, one size never fits all, so I invite everyone to explore and find their preferred workflow. I for one used to be a die-hard linear fan until I found out about clip launching and scene grouping, but who knows: I could switch back :smile:

  • I also used to be a die-hard linear sequencer user too - which is why (full disclosure) I only purchased AUM after joining the Atom2 beta.

    Clip launching finally clicked for me with this app (and a Launchpad) and I now really enjoy both approaches.

  • edited November 2020

    @blueveek said:

    @Vlad11 said:
    OK... but the problem with AUM is that doesn't have a timeline that you can situate the arrangement. It starts ALWAYS from the beginning and that is all, for what I know. We still need some DAW for composition and arrangement of a song.

    There's a very clear comparison between linear and clip-launching workflows that @Paulinko made earlier in this thread, I encourage you to read it: https://forum.audiob.us/discussion/comment/874811/#Comment_874811

    These are very different ways of composing and making song arrangements. Some people strongly prefer the former, some strongly prefer the latter, and I can definitely empathise with both schools of thought. Atom 2 is leaning heavily on enabling the clip-launching approach for now, while allowing for some linear arrangement approaches with "master Atom arrangers" and editable loop markers (but optimises for modular workflows).

    Ultimately, one size never fits all, so I invite everyone to explore and find their preferred workflow. I for one used to be a die-hard linear fan until I found out about clip launching and scene grouping, but who knows: I could switch back :smile:

    When stagelight was my main jam, I used to like coming up with ideas in the clip launcher bit, then ‘recording’ to the linear timeline view later to arrange. I’m hoping I’ll be able to do something similar in atom.

    I’m guessing the master arranger will have a moveable play head, and hopefully loop points (please note this is not a feature request... yet) so it won’t matter about AUM always starting from the beginning?

  • edited November 2020

    @gregsmith said:

    @blueveek said:

    @Vlad11 said:
    OK... but the problem with AUM is that doesn't have a timeline that you can situate the arrangement. It starts ALWAYS from the beginning and that is all, for what I know. We still need some DAW for composition and arrangement of a song.

    There's a very clear comparison between linear and clip-launching workflows that @Paulinko made earlier in this thread, I encourage you to read it: https://forum.audiob.us/discussion/comment/874811/#Comment_874811

    These are very different ways of composing and making song arrangements. Some people strongly prefer the former, some strongly prefer the latter, and I can definitely empathise with both schools of thought. Atom 2 is leaning heavily on enabling the clip-launching approach for now, while allowing for some linear arrangement approaches with "master Atom arrangers" and editable loop markers (but optimises for modular workflows).

    Ultimately, one size never fits all, so I invite everyone to explore and find their preferred workflow. I for one used to be a die-hard linear fan until I found out about clip launching and scene grouping, but who knows: I could switch back :smile:

    When stagelight was my main jam, I used to like coming up with ideas in the clip launcher bit, then ‘recording’ to the linear timeline view later to arrange. I’m hoping I’ll be able to do something similar in atom.

    I’m guessing the master arranger will have a moveable play head, and hopefully loop points (please note this is not a feature request... yet) so it won’t matter about AUM always starting from the beginning?

    The master Atom arranger (which is just another Atom instance) has its playback still linked the host. However, loop points/markers make it possible to target an individual part of an arrangement – and start playback from a later part of the song.

    Regarding this, @winconway is now working on a bunch of cool templates to make it easy to get started. But building a project from scratch should also be fairly quick if you're used to AUM.

  • @blueveek said:

    @gregsmith said:

    @blueveek said:

    @Vlad11 said:
    OK... but the problem with AUM is that doesn't have a timeline that you can situate the arrangement. It starts ALWAYS from the beginning and that is all, for what I know. We still need some DAW for composition and arrangement of a song.

    There's a very clear comparison between linear and clip-launching workflows that @Paulinko made earlier in this thread, I encourage you to read it: https://forum.audiob.us/discussion/comment/874811/#Comment_874811

    These are very different ways of composing and making song arrangements. Some people strongly prefer the former, some strongly prefer the latter, and I can definitely empathise with both schools of thought. Atom 2 is leaning heavily on enabling the clip-launching approach for now, while allowing for some linear arrangement approaches with "master Atom arrangers" and editable loop markers (but optimises for modular workflows).

    Ultimately, one size never fits all, so I invite everyone to explore and find their preferred workflow. I for one used to be a die-hard linear fan until I found out about clip launching and scene grouping, but who knows: I could switch back :smile:

    When stagelight was my main jam, I used to like coming up with ideas in the clip launcher bit, then ‘recording’ to the linear timeline view later to arrange. I’m hoping I’ll be able to do something similar in atom.

    I’m guessing the master arranger will have a moveable play head, and hopefully loop points (please note this is not a feature request... yet) so it won’t matter about AUM always starting from the beginning?

    The master Atom arranger (which is just another Atom instance) has its playback still linked the host. However, loop points/markers make it possible to target an individual part of an arrangement – and start playback from a later part of the song.

    Regarding this, @winconway is now working on a bunch of cool templates to make it easy to get started. But building a project from scratch should also be fairly quick if you're used to AUM.

    Loop points/markers sounds perfect 👌

  • So if you were to set up your Atom "particles" like so would they automatically link to pad on the launchpad or will you have to manually assign them?

  • edited November 2020

    @Lil_Stu07 said:

    So if you were to set up your Atom "particles" like so would they automatically link to pad on the launchpad or will you have to manually assign them?

    Launchpad mapping of Atoms is independent of their location in AUM, and as you'll see in upcoming videos, there are multiple good reasons why this setup is preferable.

  • edited November 2020

    I guess each instance has it's own unique identifier which Atom tracks, there's no way of Atom knowing their location in AUM midi "tracks" since they aren't like a daw track which has it's own midi port etc.. unless Jonatan adds some kind of identifier to the channel the plugins can read. idk :)

This discussion has been closed.