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

1121315171857

Comments

  • edited October 2020

    Guess we don't need FLStudio and its excellent MIDI editing on iOs anymore... Hoping for multi-Track midi Import (or filtering).

    Nice..

    https://forum.audiob.us/uploads/editor/v0/ffjsw8makdbg.jpeg

  • From the looks of it Atom could easily be 'sold' to all major iOS DAW developers so we could finally have a unified midi-editing experience on the platform :)

  • edited October 2020

    @Samu said:
    From the looks of it Atom could easily be 'sold' to all major iOS DAW developers so we could finally have a unified midi-editing experience on the platform :)

    You might be joking, but it makes me want to nerd out a bit on this topic. I'm not sure if I'm completely missing the target audience on this forum, but I love talking about this.

    Atom's UI and interaction engine are extremely embeddable, and I've in fact built them this way from the start, making sure to avoid the situation that made me have to rewrite it in the first place. It already works on every platform, with native UI elements, and in every modern web browser too (if this tickles you to think it's using React Native or some other framework, it's not). I'll probably make some demos on this at some point after the initial release.

    Atom's UI is entirely declarative. You provide a description of the current state of affairs, and Atom will just render it. If something changes, you can then provide a new description of the current state of affairs, and Atom will diff the old and the new state, create a list of updates, and apply them to the UI in the smallest number of steps. It's also entirely vector-based and only a few hunderd kb in size (including all the code that provides the interactions).

    Atom's UI is scriptable, so add-ons are easy. But I don't want to give too much of this away, more on that later ;)

    Apart from being able to receive a description of the current state, Atom's UI communicates with the outside world via a JSON (text) messaging API. This again, works regardless of the OS / platform.

    I've mentioned it in passing before, but this whole setup above makes it so that every time the UI gets hidden (like the window in AUM closes), I can completely nuke everything except for a very small MIDI engine core that is able to function standalone (really small – a few lines of C++). This drops memory usage significantly. In fact, when hidden, Atom barely registers – you should be able to open hundreds of instances with no issue. And because everything is declarative, session restore is free: get the state and send it to a new instance, everything will hydrate back to life instantly (and by everything I mean everything: undo/redo history, open panels, scroll positions, etc.).

    So yeah, not sure I'd want to sell Atom, but it's embeddable as hell this time.

  • @Samu said:
    From the looks of it Atom could easily be 'sold' to all major iOS DAW developers so we could finally have a unified midi-editing experience on the platform :)

    Was thinking similar. I guess we can just use it in any daw regardless, as long as it supports midi fx?

    Only thing I did think is whether it has a timeline view that shows all clips in one instance? Unless I’ve missed it already?

    @blueveek did mention that you can have an instance that triggers clips in other instances so maybe that’s the one?

  • @blueveek said:

    @Samu said:
    From the looks of it Atom could easily be 'sold' to all major iOS DAW developers so we could finally have a unified midi-editing experience on the platform :)

    You might be joking, but it makes me want to nerd out a bit on this topic. I'm not sure if I'm completely missing the target audience on this forum, but I love talking about this.

    I'm not joking at all!

    Look at most piano-roll editors out there at the moment (BM3, Cubasis 3, NS2, ZenBeats, iMPC Pro 2, LK, ModStep, AuriaPro, GarageBand etc.). They don't have even half of the features nor polish that this Atomic 'update' brings to the table...

    So no, it's not a joke but rather a wishful thinking to unify midi-editing on the iOS/iPadOS platform.

    I can always dream, can't I? :D

  • edited October 2020

    @blueveek that sounds like a solid re-write well worth doing!

    @blueveek said:
    In fact, when hidden, Atom barely registers – you should be able to open hundreds of instances with no issue.

    It also sounds like you could have a master clip launcher AU which could set up e.g. 16x16 Atoms (16 tracks with 16 clips each) in a scriptable way, with little concern for memory usage. Wouldn't that be nice? ;-)

  • edited October 2020

    @bleep said:
    @blueveek that sounds like a solid re-write well worth doing!

    @blueveek said:
    In fact, when hidden, Atom barely registers – you should be able to open hundreds of instances with no issue.

    It also sounds like you could have a master clip launcher AU which could set up e.g. 16x16 Atoms (16 tracks with 16 clips each) in a scriptable way, with little concern for memory usage. Wouldn't that be nice? ;-)

    That's correct, and a great idea! This might come as an IAP for users that don't have a hardware controller like the Novation Launchpads, but likely in a future update. Feature creep is real. Someone else also could (and maybe should) build that app too.

    Oh btw, just found this video from a year ago when I started this. Count 'em:

  • @blueveek said:

    @bleep said:
    @blueveek that sounds like a solid re-write well worth doing!

    @blueveek said:
    In fact, when hidden, Atom barely registers – you should be able to open hundreds of instances with no issue.

    It also sounds like you could have a master clip launcher AU which could set up e.g. 16x16 Atoms (16 tracks with 16 clips each) in a scriptable way, with little concern for memory usage. Wouldn't that be nice? ;-)

    That's correct, and a great idea! This might come as an IAP for users that don't have a hardware controller like the Novation Launchpads, but likely in a future update. Feature creep is real. Someone else also could (and maybe should) build that app too.

    Oh btw, just found this video from a year ago when I started this. Count 'em:

    What Philip Glass song is that?

  • @ExAsperis99 it's called " John Cage "

  • edited October 2020

    The anticipation just hit peak! Beta, release candidate? 🙏

    The launchpad integration takes it 10x for me.

  • Ok I have just been lurking in this thread.... but frankly now I am aroused!!!!! Please for the love of Baby Tiny Jesus.. release it!!!!! 😂😂

  • Regret selling my launchpad

  • Can I use maybe an older model of the launchpad?

  • @Sergiu said:
    Regret selling my launchpad

    There's a thread for that. :smile:

  • @mlau said:
    @ExAsperis99 it's called " John Cage "

    hahaha

  • In regard to the ability of direct mapping in the new Atom ( it was mentioned earlier in this thread)> @ecamburn said:

    @Sergiu said:
    Regret selling my launchpad

    There's a thread for that. :smile:

  • He means there's literally a thread on the forums right now for regrets about selling equipment.

    For me, I'm doing the comparison from Launchpad Mini Mk3 vs. Launchpad X vs. Launchad Pro.

    The X is looking kind of great.

  • edited October 2020

    Launchpad feature comparison (bottom table):
    https://support.novationmusic.com/hc/en-gb/articles/360000777685-Launchpad-Comparison

    The Pro has "Fixed length clip feature" and "Print midi to clip" which the X does not have, plus standalone chord mode and step sequencer. Sounds mostly like Ableton integration features. I suppose those will not apply to Atom, @blueveek? Feature creep etc.

    Edit: here is the print to clip thing:

  • @ExAsperis99 said:
    He means there's literally a thread on the forums right now for regrets about selling equipment.

    For me, I'm doing the comparison from Launchpad Mini Mk3 vs. Launchpad X vs. Launchad Pro.

    The X is looking kind of great.

    @ExAsperis99 Go for the LP Pro MK 3 if u can afford it. Its worth it for the extra custom scenes and sequencer and extra controls. All in all its built to last.

  • @bleep said:
    The Pro has "Fixed length clip feature" and "Print midi to clip" which the X does not have, plus standalone chord mode and step sequencer. Sounds mostly like Ableton integration features. I suppose those will not apply to Atom, @blueveek? Feature creep etc.

    I suggest waiting for the official release before anyone buys any hardware in anticipation.

    I’m likely going to have ongoing updates adding support for more controllers after v2.0 hits, and it’d be good to release this thing sooner rather than later.

    Perhaps the most helpful thing (at least for me) right now is to have a poll of the controllers that you already own or would really like to get in the future, this’ll give me an idea for what to prioritize. Anyone care to start that?

  • @blueveek said:

    @bleep said:
    The Pro has "Fixed length clip feature" and "Print midi to clip" which the X does not have, plus standalone chord mode and step sequencer. Sounds mostly like Ableton integration features. I suppose those will not apply to Atom, @blueveek? Feature creep etc.

    I suggest waiting for the official release before anyone buys any hardware in anticipation.

    I’m likely going to have ongoing updates adding support for more controllers after v2.0 hits, and it’d be good to release this thing sooner rather than later.

    Perhaps the most helpful thing (at least for me) right now is to have a poll of the controllers that you already own or would really like to get in the future, this’ll give me an idea for what to prioritize. Anyone care to start that?

    I use a Launchpad X.

    I also have a regular piano MIDI keyboard, and an Akai MPK Mini 2. I plan to get an Akai MPK Mini 3 at some point, as well as a Maschine Mikro Mk3. My next MIDI controller purchase will be an Akai EWI Solo.

  • Akai lpd8

  • Hoho @Sergiu I got that pile of junk too, mite be useful atlast

  • edited October 2020

    It’s ok... I ended up making those pads a bit more sensitive. There is a video on YouTube.It works> @noob said:

    Hoho @Sergiu I got that pile of junk too, mite be useful atlast

  • @blueveek
    Controllers

    Beatstep Pro (first edition)
    Keystep (first edition)

  • @Sergiu said:
    It’s ok... I ended up making those pads a bit more sensitive. There is a video on YouTube.It works> @noob said:

    Hoho @Sergiu I got that pile of junk too, mite be useful atlast

    +1 LPD8 with the customised pad sensitivity

  • edited October 2020

    Beatstep Pro,
    Launchpad Mini (original)
    Launchpad Pro
    Keystep

  • Korg nanoKEY Studio
    Novation Launchpad mk2
    Keith mcMillen K-Board

  • Launchpad X

  • You do realize that it’s IMPOSSIBLE for the dev to read every post .
    He meant making a separate topic with a poll

    https://forum.audiob.us/discussion/41445/atom-controller-poll/p1?new=1

This discussion has been closed.