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

1…4041434546…56

Comments

  • [Deleted User][Deleted User]
    edited March 2021

    @wim said:
    I would probably not use Atom 2 much without that. Sustain pedal anyone?

    As for MPE, maybe along the same lines? Just record it, but only allow note editing. I can see making an effective MPE editor could be a huge challenge.

    Full repect for @blueveek todo list. If I insist on MPE is to summon the voices that request it. Maybe it gets re-prioritized 🙃

    As @wim says, just record is enough. Note editing ok too.

    But I go for a clear one: release the thing!

  • GavinskiGavinski

    @wim said:
    Option 1 but only if it records and plays back midi CCs (actually, preferably all MIDI, period). I don't care at all if they're editable. That can wait for a later release (preferably IAP). Some kind of rudimentary display just to show that cc data exists and perhaps a basic curve.

    I would probably not use Atom 2 much without that. Sustain pedal anyone?

    As for MPE, maybe along the same lines? Just record it, but only allow note editing. I can see making an effective MPE editor could be a huge challenge.

    Yup, recording CCs is hugely important I think, and much more important than bring able to edit, for now at least.

  • lukesleepwalkerlukesleepwalker

    @noniman93 said:
    Option 1! Please ship now. Never been so excited about an app. In fact, this is the only reason I signed up to this forum. :D

    But we are generally so charming and attractive!

  • gonekrazy3000gonekrazy3000

    option 1 @blueveek

  • DaubDaub
    edited March 2021

    @Daub said:
    A cynical person would think that this is a marketing campaign or worse still ‘vapourware’.
    As an Atom user, I hope to be proven wrong.

    Ooops, I didn’t mean to cause a stir...

    Option 1 for me

  • RajahPRajahP
    edited March 2021

    Are we still polling? Or, is it safe to say it is overwhelmingly yes for option #1?

  • Xyl_RunXyl_Run

    Hi @blueveek,

    My choice is option 1 because there's already a lot you'll bring to the iOS community with this one.
    You'll make lot of people happy and I guess you already made us happy thanks to your behaviour, your great transparent communication on your Atom 2.
    After releasing it, I would advice you to take your time and make update when you decide it is the right moment.
    You give your personal time as well as the great beta testers do for helping you.
    Take your time, and go forward on automation features by keeping a good health.
    Once more, many thanks for your work and generosity.

  • reasOnereasOne
    edited March 2021

    Push it to Apple review today 😎

  • noniman93noniman93

    @zah said:
    So, that's 513 for option 1 and 20 for option 2 :)

    This app originally came out almost two years ago. I was reading reviews on different country app stores and dev response to a reviewer said that Midi import/export was coming in an update.
    That was in early June. Of 2019. Almost 21 months ago...
    I really wanted an app like this where I could work on some midi stuff away from desktop DAW, but the midi import/export was a deal breaker. So I wasted my money on Xequence2 - which could do that, but the workflow was so kludgey and not suited to touch screen and updates never showed up that it just sits unused now.
    So I would love to have Atom 2 out - especially for the import/export and also since I have bought AUM in the meantime, and those two apps look like a perfect union for a mobile midi solution as well.

    I'm curious as to how many here have Atom 1 and will get this for free (I think) and how many, like me, have not yet bought because of various limitations of the original. I almost bought this at the beginning of this thread, thinking the update was "coming soon", but 8 months later, I still have no clue as to when this app will drop.

    I use Atom quite heavily. It’s so simple and intuitive that it’s been my go-to sequencer always. The interface is smooth! With the new features that are to ship with new update - MIDI Import/Export, Extensive triggering options, ‘Abletonesque’ workflows, etc - I can safely say that it is going to be a game-changer!

    (Option 1 Option 1 Option 1 😛)

  • shinyisshinyshinyisshiny

    i need this to fully sequence, pick sounds, mix, and master my tracks, or else im not biting. neither option will fit my workflow.

    (ok, but seriously, option 1 is great, def was looking forward to option 2, but lets rock)

  • SvetlovskaSvetlovska

  • blueveekblueveek
    edited March 2021

    Ok!

    Thank you.

    A few days ago I said that I'd like to gather your thoughts until the end of the week, and whatever you decide, that's what's going to happen. Well, it's Friday :)

    From what I can tell, the majority would prefer releasing now. There have been tons of amazingly nuanced takes in this thread, in particular around best-practices in software development and well-being in general. You feedback has been great, I truly appreciate it! Now, while I'm hyper-aware that missing automation will undoubtedly be crucial to some of you, I hope that the plethora of other new features will make up for some of that.

    Starting today, I'll begin the process of submitting the app for review. There's a few things to prepare, including the store screenshots and description text, and a couple of demo videos to satisfy Apple's AUv3 review shenanigans. Luckily @tk32 and @winconway are helping me out with that, without them this whole process would've taken me yet more time! It's clear that Audioveek, Midi Tools, Atom v1, and now v2, would not have been the same without them.

    One last thing

    Now that I know release is coming, there's this one feature I've kept hidden, that I feel comfortable sharing now. And that's add-ons:

    Atom 2 has user-scripting support that lets you extend it with your own code, allowing you to do your own hardware scripting to add new controllers or completely change the behavior of supported ones (e.g. Launchpads), as well as overhauling the entire interface with custom styles for new colors schemes and even changing the entire layout. Programming is with a language similar to JS, and styling is done with CSS.

    You can share and import add-ons, so if there's adventurous folks among you that want to add support for their own controllers, or build new themes, you can, and they'll work everywhere and for everyone if you decide to share them. The extensibility surface area is extremely large, it's theoretically possible to even do crazy stuff like write custom arpeggiator or humanizer plugins; however, documenting and supporting this is a daunting task for me, so I'll start with just hardware control and custom theming officially supported for now (though If you want to go ahead and reverse engineer everything else, be my guest).

  • nickneeknickneek

    @blueveek said:
    Ok!

    Thank you.

    A few days ago I said that I'd like to gather your thoughts until the end of the week, and whatever you decide, that's what's going to happen. Well, it's Friday :)

    From what I can tell, the majority would prefer releasing now. There have been tons of amazingly nuanced takes in this thread, in particular around best-practices in software development and well-being in general. You feedback has been great, I truly appreciate it! Now, while I'm hyper-aware that missing automation will undoubtedly be crucial to some of you, I hope that the plethora of other new features will make up for some of that.

    Starting today, I'll begin the process of submitting the app for review. There's a few things to prepare, including the store screenshots and description text, and a couple of demo videos to satisfy Apple's AUv3 review shenanigans. Luckily @tk32 and @winconway are helping me out with that, without them this whole process would've taken me yet more time! It's clear that Audioveek, Midi Tools, Atom v1, and now v2, would not have been the same without them.

    One last thing

    Now that I know release is coming, there's this one feature I've kept hidden, that I feel comfortable sharing now. And that's add-ons:

    Atom 2 has user-scripting support that lets you extend it with your own code, allowing you to do your own hardware scripting to add new controllers or completely change the behavior of supported ones (e.g. Launchpads), as well as overhauling the entire interface with custom styles for new colors schemes and even changing the entire layout. Programming is with a language similar to JS, and styling is done with CSS.

    You can share and import add-ons, so if there's adventurous folks among you that want to add support for their own controllers, or build new themes, you can, and they'll work everywhere and for everyone if you decide to share them. The extensibility surface area is extremely large, it's theoretically possible to even do crazy stuff like write custom arpeggiator or humanizer plugins; however, documenting and supporting this is a daunting task for me, so I'll start with just hardware control and custom theming officially supported for now (though If you want to go ahead and reverse engineer everything else, be my guest).

    !!!!! Nice reveal!

  • mlaumlau

    congrats @blueveek

  • MrBlaschkeMrBlaschke
    edited March 2021

    @blueveek said:
    I hope that the plethora of other new features will make up for some of that.

    Well, i guess you can rest assured that it will - at least for some time. Especially with the revealing of „that little bonus thing“ you did...

    Thanks for the possibility to make this happen. Much appreciated.

  • SkyblazerSkyblazer

    @blueveek said:
    Ok!

    Thank you.

    A few days ago I said that I'd like to gather your thoughts until the end of the week, and whatever you decide, that's what's going to happen. Well, it's Friday :)

    From what I can tell, the majority would prefer releasing now. There have been tons of amazingly nuanced takes in this thread, in particular around best-practices in software development and well-being in general. You feedback has been great, I truly appreciate it! Now, while I'm hyper-aware that missing automation will undoubtedly be crucial to some of you, I hope that the plethora of other new features will make up for some of that.

    Starting today, I'll begin the process of submitting the app for review. There's a few things to prepare, including the store screenshots and description text, and a couple of demo videos to satisfy Apple's AUv3 review shenanigans. Luckily @tk32 and @winconway are helping me out with that, without them this whole process would've taken me yet more time! It's clear that Audioveek, Midi Tools, Atom v1, and now v2, would not have been the same without them.

    One last thing

    Now that I know release is coming, there's this one feature I've kept hidden, that I feel comfortable sharing now. And that's add-ons:

    Atom 2 has user-scripting support that lets you extend it with your own code, allowing you to do your own hardware scripting to add new controllers or completely change the behavior of supported ones (e.g. Launchpads), as well as overhauling the entire interface with custom styles for new colors schemes and even changing the entire layout. Programming is with a language similar to JS, and styling is done with CSS.

    You can share and import add-ons, so if there's adventurous folks among you that want to add support for their own controllers, or build new themes, you can, and they'll work everywhere and for everyone if you decide to share them. The extensibility surface area is extremely large, it's theoretically possible to even do crazy stuff like write custom arpeggiator or humanizer plugins; however, documenting and supporting this is a daunting task for me, so I'll start with just hardware control and custom theming officially supported for now (though If you want to go ahead and reverse engineer everything else, be my guest).

    Nice reveal. Looking forward to learning some more advanced scripting with Atom 2!

  • gregsmithgregsmith

    Wow @blueveek you are full of surprises! 😂

    I’m gonna see if I can code in some sort of native LK integration!

  • AAntonAAnton

    @blueveek congrats with your progress, looking forward to your app.

    Maye a new app with scripting? An app where one just could use scripting to control the synth apps, trigger audio loops and effects would be awesome and a big time saver.

    Something like apematrix but with scripting? No more typing in midi notes for synth apps, triggering midi patterns, automate synths and effects, set up midi effects, triggering sound loops, a chord pad here, an arp there ... Just everything in one place and controlled in a sane way, that would make it so easy to make sound/ music ...

  • blueveekblueveek
    edited March 2021

    @gregsmith said:
    Wow @blueveek you are full of surprises! 😂

    I’m gonna see if I can code in some sort of native LK integration!

    I haven't tested this, but it may be possible when talking to the standalone version of LK, since it's theoretically indistinguishable from an external piece of hardware as far as Atom is concerned. Same goes for any other app that has virtual MIDI ports. I'm happy to try making a demo prototype and help you out, DM me when it comes to that. For my own sanity, I'd really like to limit public scripting support to new or existing hardware controllers, and user themes, at least for now :)

  • blueveekblueveek

    @AAnton said:
    @blueveek congrats with your progress, looking forward to your app.

    Maye a new app with scripting? An app where one just could use scripting to control the synth apps, trigger audio loops and effects would be awesome and a big time saver.

    Something like apematrix but with scripting? No more typing in midi notes for synth apps, triggering midi patterns, automate synths and effects, set up midi effects, triggering sound loops, a chord pad here, an arp there ... Just everything in one place and controlled in a sane way, that would make it so easy to make sound/ music ...

    That's a very interesting idea for a host. I wonder what the audience for such an app could be.

  • CarnbotCarnbot

    That looks like a great additional feature, any customisation options increases the lifespan of an app :)

  • FloRi89FloRi89

    Atom 2 has user-scripting support that lets you extend it with your own code, allowing you to do your own hardware scripting to add new controllers or completely change the behavior of supported ones (e.g. Launchpads), as well as overhauling the entire interface with custom styles for new colors schemes and even changing the entire layout. Programming is with a language similar to JS, and styling is done with CSS.

    Bro, you kept the best thing for last, didn't you? That is an insane addition. I'm so looking forward to this.

  • CharlesalbertCharlesalbert

    I'm amazed. Thanks so much.

  • [Deleted User][Deleted User]

    Looking forward, @blueveek and congratulations. 🍾

    It is a privilege to follow your progress with the app and be witness of your generosity and dedication. Now remember to take a deep breath now and then.

  • david_2017david_2017

    Wow @blueveek that sounds great!

    If anyone needs someone with Launchpad Pro (Mk3) I could give it a go - would be cool to have this controller supported too

  • blueveekblueveek
    edited March 2021

    @david_2017 said:
    Wow @blueveek that sounds great!

    If anyone needs someone with Launchpad Pro (Mk3) I could give it a go - would be cool to have this controller supported too

    I would be very happy to guide you through the process. I bought a Pro for this purpose too, happy to work together on it.

  • FloRi89FloRi89
    edited March 2021

    @blueveek said:

    @david_2017 said:
    Wow @blueveek that sounds great!

    If anyone needs someone with Launchpad Pro (Mk3) I could give it a go - would be cool to have this controller supported too

    I would be very happy to guide you through the process. I bought a Pro for this purpose too, happy to work together on it.

    @blueveek
    I want to make a video about apps that support the LP Pro MK3, AFAIK this is only the third app that supports it out of the box (Launchpad and LK beeing the other ones).

    One thing that interests me is the "save to clip" button, that currently only works in Ableton. I wonder what that buttons sends, did you ever try it? The developers reference documents about every button, but leaves that out.

    Since all the other buttons are either MIDI or Sysex I was wondering if this button maybe sends a batch of midi commands. Furthermore since you are opening your scripting I was thinking if I can use that to implement this.

    Print 2 Clip into Atom 2 would be insanely cool :).

    If you need help with implementing anything for the LP Pro MK3 contact me over PM. I'm a programmer in my regular life and I wrote a few Mozaic scripts to controll the Launchpad and the Launchkey, so I know my way around the stuff that is documented in the developers reference.

    Edit: For the interested, print2clip currently sends whatever you have in the sequenzer to Ableton and saves it as MIDI there. That's really cool, because you can sketch something with the sequenzer and then send it to Ableton for fine tuneing.

  • horsetrainerhorsetrainer

    Thank you! :)

  • blueveekblueveek
    edited March 2021

    @FloRi89 said:

    One thing that interests me is the "save to clip" button, that currently only works in Ableton. I wonder what that buttons sends, did you ever try it? The developers reference documents about every button, but leaves that out.

    Since all the other buttons are either MIDI or Sysex I was wondering if this button maybe sends a batch of midi commands. Furthermore since you are opening your scripting I was thinking if I can use that to implement this.

    I'm extremely curious about this too. It should't be too hard to add a MIDI monitor in-between to check and see what the controller is actually sending over. If it's still MIDI, and not too obfuscated or some unknown Ableton thing, I see no reason why it couldn't be added in an Atom script.

    Generally, the nice thing about having hardware customization through scripting is that you don't need to be limited to the default functionality or behavior. Community-driven scripting is a thing, just look at what this guy got together for Bitwig, which is far beyond what "official" support offers http://mossgrabers.de/Software/Bitwig/Bitwig.html:

  • FloRi89FloRi89

    @blueveek said:

    @FloRi89 said:

    One thing that interests me is the "save to clip" button, that currently only works in Ableton. I wonder what that buttons sends, did you ever try it? The developers reference documents about every button, but leaves that out.

    Since all the other buttons are either MIDI or Sysex I was wondering if this button maybe sends a batch of midi commands. Furthermore since you are opening your scripting I was thinking if I can use that to implement this.

    I'm extremely curious about this too. It should't be too hard to add a MIDI monitor in-between to check and see what the controller is actually sending over. If it's still MIDI, and not too obfuscated or some unknown Ableton thing, I see no reason why it couldn't be added in an Atom script.

    Generally, the nice thing about having hardware customization through scripting is that you don't need to be limited to the default functionality or behavior. Community-driven scripting is a thing, just look at what this guy got together for Bitwig, which is far beyond what "official" support offers http://mossgrabers.de/Software/Bitwig/Bitwig.html:

    Yea absolutely! I would say the Bitwig integration is probably better then for Ableton itself :D. So far I'm doing everything with Mozaic, but you are right, I'll debug this tonight to see what that sends. If it's really midi or sysex it should be easy to loop over it and forward the result.

This discussion has been closed.