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…4142444647…56

Comments

  • RajahPRajahP

    A great day for iOs music production... Thanks..

  • sloJordansloJordan

    Wooooo!!! So excited for this! And really cool about the scripting. I'm still trying to grasp the scope of that (in the long term), so is it possible to actually write scripts that could change the layout/sizes of the buttons or write scripts that effect the midi notes themselves? I understand in the immediate future its more about supporting hardware controllers / colours / simple things.

  • blueveekblueveek
    edited March 2021

    @sloJordan said:
    Wooooo!!! So excited for this! And really cool about the scripting. I'm still trying to grasp the scope of that (in the long term), so is it possible to actually write scripts that could change the layout/sizes of the buttons or write scripts that effect the midi notes themselves? I understand in the immediate future its more about supporting hardware controllers / colours / simple things.

    Yes, changing the sizes of buttons is possible for 2.0, as well as fonts, colors, defaults, and tons more. It really is something like "here's something that targets this bit, write some CSS in there", or "tweak these variables for easy theming", or "tweak this config file for different input defaults".

    In terms of coding, also yes. While the immediate future is about building seamless integration with hardware controllers, after the dust settles I plan to also enable (read: publicly document :smile:) the ability to script the clip itself (e.g. completely alter the notes to build an arpeggiator, turn notes into CC messages, and so on).

    For everything, you can edit the files on the iPad in an editor, and tap a button Atom to apply the changes. This is live, so you don't need to create a new project, it'll load the scripts in-place.

  • FloRi89FloRi89

    For everything, you can edit the files on the iPad in an editor, and tap a button Atom to apply the changes. This is live, so you don't need to create a new project, it'll load the scripts in-place.

    @blueveek
    That sounds perfect, I'm looking forward to trying that. I think you are really creating a great playground there.

  • wimwim

    @blueveek - patchstorage.com seems like a perfect place to share customizations and scripts. If that seems appropriate then the earlier in the process it’s set up the better.

  • blueveekblueveek

    @wim said:
    @blueveek - patchstorage.com seems like a perfect place to share customizations and scripts. If that seems appropriate then the earlier in the process it’s set up the better.

    Is this something I'd need to implement in Atom? Or is it like https://gist.github.com where people just post stuff?

  • wimwim
    edited March 2021

    @blueveek said:

    @wim said:
    @blueveek - patchstorage.com seems like a perfect place to share customizations and scripts. If that seems appropriate then the earlier in the process it’s set up the better.

    Is this something I'd need to implement in Atom? Or is it like https://gist.github.com where people just post stuff?

    It’s a bit like Github. No app coding involved.

    Mozaic, Drambo, and lots of other apps have sections on the site.

    Github is an option too of course but patchstorage is a bit less intimidating for non programmers.

  • lukesleepwalkerlukesleepwalker

    @RajahP said:
    A great day for iOs music production... Thanks..

    This, indeed. Just blew me out of the water again with the latest news, @blueveek !

  • auxmuxauxmux
    edited March 2021

    The scripting aspect looks immense, can't wait to try with my midi controllers.

  • tk32tk32
    edited March 2021

    You just need to contact the Patchstorage admin team and ask for a section to be added. We can help arrange that post-launch.

    As long as you can ensure at least 5 patches are added in the first few weeks they are happy to add a new category.

    (that's the basis on which I got the BM3 section created there - and the same happened with Drambo, Mozaic, NS2 etc.)

  • blueveekblueveek

    @tk32 said:
    You just need to contact the Patchstorage admin team and ask for a section to be added. We can help arrange that post-launch.

    As long as you can ensure at least 5 patches are added in the first few weeks they are happy to add a new category.

    (that's the basis on which I got the BM3 section created there - and the same happened with Drambo, Mozaic, NS2 etc.)

    That's perfect, thanks! This would be a good opportunity for me to build some templates and example scripts, e.g. "simple new controller", "modified launchpad", "integration with another app on a virtual midi port", "high-contrast theme"...

  • tk32tk32
    edited March 2021

    One small caveat...

    Deep testing of this scripting feature is above and beyond what I was able to offer as a beta/QA tester (both logistically and perhaps, intellectually), so you might need to suit-up before venturing forth and be prepared to fight a few dragons.

    We have an awesome dungeon master, however.

    ...and if you're passing by... I'm the level 3 Bard sitting under the tree in a stupor with a broken lute blankly murmering "so many possibilities... there are so many possibilities"

  • sloJordansloJordan

    @blueveek said:

    @sloJordan said:
    Wooooo!!! So excited for this! And really cool about the scripting. I'm still trying to grasp the scope of that (in the long term), so is it possible to actually write scripts that could change the layout/sizes of the buttons or write scripts that effect the midi notes themselves? I understand in the immediate future its more about supporting hardware controllers / colours / simple things.

    Yes, changing the sizes of buttons is possible for 2.0, as well as fonts, colors, defaults, and tons more. It really is something like "here's something that targets this bit, write some CSS in there", or "tweak these variables for easy theming", or "tweak this config file for different input defaults".

    In terms of coding, also yes. While the immediate future is about building seamless integration with hardware controllers, after the dust settles I plan to also enable (read: publicly document :smile:) the ability to script the clip itself (e.g. completely alter the notes to build an arpeggiator, turn notes into CC messages, and so on).

    For everything, you can edit the files on the iPad in an editor, and tap a button Atom to apply the changes. This is live, so you don't need to create a new project, it'll load the scripts in-place.

    Legittttt that is awesome! Is it possible to load scripts by default when first opening the auv3? Or load scripts simultaneously into all open instances of atom? i'm thinking about some kind of performance layout that hides a lot of the editing features and makes certain things larger like the Record button, or probability params, etc.

  • espiegel123espiegel123

    @tk32 said:
    One small caveat...

    Deep testing of this scripting feature is above and beyond what I was able to offer as a beta/QA tester (both logistically and perhaps, intellectually), so you might need to suit-up before venturing forth and be prepared to fight a few dragons.

    We have an awesome dungeon master, however.

    ...and if you're passing by... I'm the level 3 Bard sitting under the tree in a stupor with a broken lute blankly murmering "so many possibilities... there are so many possibilities"

    Maybe someone could start an ATOM 2 page on the wiki and people can share their wisdom there so it doesn’t get lost in threads...and info about the scripting can go there and get refined by the community.

  • FloRi89FloRi89
    edited March 2021

    @blueveek said:

    @tk32 said:
    You just need to contact the Patchstorage admin team and ask for a section to be added. We can help arrange that post-launch.

    As long as you can ensure at least 5 patches are added in the first few weeks they are happy to add a new category.

    (that's the basis on which I got the BM3 section created there - and the same happened with Drambo, Mozaic, NS2 etc.)

    That's perfect, thanks! This would be a good opportunity for me to build some templates and example scripts, e.g. "simple new controller", "modified launchpad", "integration with another app on a virtual midi port", "high-contrast theme"...

    O.K so I tested what the Launchpad sends on the "Print To Clip" button. Unfortunately it's nothing, no MIDI or SysEx. Seems that putting it into DAW mode isn't enough to enable this button, probably some undocumented SysEx that you have to send, or something like that. So it seems they want to keep this Ableton Exclusive for now.

    Edit: Next thing I'm going to do is document the communication between Ableton and the Launchpad :D, let's see what I can find there.

  • blueveekblueveek
    edited March 2021

    @FloRi89 said:

    O.K so I tested what the Launchpad sends on the "Print To Clip" button. Unfortunately it's nothing, no MIDI or SysEx. Seems that putting it into DAW mode isn't enough to enable this button, probably some undocumented SysEx that you have to send, or something like that. So it seems they want to keep this Ableton Exclusive for now.

    Edit: Next thing I'm going to do is document the communication between Ableton and the Launchpad :D, let's see what I can find there.

    Thanks a lot for looking into this, it's very useful info. I was fearing that could be the case. Perhaps Ableton integration uses programmer mode instead? Atom scripting can also enable that (it's all just code), it's just more grindy to reimplement some of the built-in functionality.

  • blueveekblueveek
    edited March 2021

    @sloJordan said:

    Legittttt that is awesome! Is it possible to load scripts by default when first opening the auv3? Or load scripts simultaneously into all open instances of atom? i'm thinking about some kind of performance layout that hides a lot of the editing features and makes certain things larger like the Record button, or probability params, etc.

    Yes, you can select which scripts to auto-load when opening, in every instance. You can have one theme and one configuration file selected exclusively, and any number of available controller scripts enabled.

    Your theming plans are quite drastic, and not something I ever considered or tested, but happy to guide you through and see what happens.

  • blueveekblueveek

    @espiegel123 said:

    Maybe someone could start an ATOM 2 page on the wiki and people can share their wisdom there so it doesn’t get lost in threads...and info about the scripting can go there and get refined by the community.

    I'm happy to support any kind of wiki like this. I'll make sure to at least build a corpus of simple examples, and document all available functions in the API.

  • PaulinkoPaulinko

    I think the decision to release Atom now is the correct one. Doing similar work for automation will not be an easy task and waiting for its release before Atom 2 would have been very frustrating for many of us.

    The addition of scripting support is a nice last minute surprise before release.

  • gregsmithgregsmith

    @blueveek said:

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

    I hoped this would be the case

    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 :)

    I’ll see how I get on. It’ll probably take me a while to get round to it anyway.

  • orandorand

    I realize the window for advice is over, but the sooner you release, the sooner you get real product validation with people’s wallets, not just with the length of this thread. 😄

    And, if the influx of cash is sufficient, it might just enable you to focus more exclusively on automation and everything else folks are asking for! Remember, money is what gives you the freedom to choose where you spend your time.

  • MrBlaschkeMrBlaschke
    edited March 2021

    @blueveek said:

    @FloRi89 said:

    O.K so I tested what the Launchpad sends on the "Print To Clip" button. Unfortunately it's nothing, no MIDI or SysEx. Seems that putting it into DAW mode isn't enough to enable this button, probably some undocumented SysEx that you have to send, or something like that. So it seems they want to keep this Ableton Exclusive for now.

    Edit: Next thing I'm going to do is document the communication between Ableton and the Launchpad :D, let's see what I can find there.

    Thanks a lot for looking into this, it's very useful info. I was fearing that could be the case. Perhaps Ableton integration uses programmer mode instead? Atom scripting can also enable that (it's all just code), it's just more grindy to reimplement some of the built-in functionality.

    @blueveek @FloRi89
    I don’t use Ableton, but from what i saw in some videos Ableton is able to paste the notes and stuff you played on a keyboard in the last unknown defined timeframe without recording it somewhere into a track. Some kind of live-tracking what you do and if you liked it just click this function and it pastes that onto a piano roll...like an ever growing history of incoming MIDI data...
    I don’t know the name for that function. But i am pretty sure that the button is for this data.
    So it is actually just temporary data in the memory of the computer that Ableton runs on.

  • wimwim
    edited March 2021

    @orand said:
    I realize the window for advice is over, but the sooner you release, the sooner you get real product validation with people’s wallets, not just with the length of this thread. 😄

    And, if the influx of cash is sufficient, it might just enable you to focus more exclusively on automation and everything else folks are asking for! Remember, money is what gives you the freedom to choose where you spend your time.

    That would be true if iOS music apps actually generated that kind of revenue. They don't.

  • blueveekblueveek

    @MrBlaschke said:

    @blueveek said:

    @FloRi89 said:

    O.K so I tested what the Launchpad sends on the "Print To Clip" button. Unfortunately it's nothing, no MIDI or SysEx. Seems that putting it into DAW mode isn't enough to enable this button, probably some undocumented SysEx that you have to send, or something like that. So it seems they want to keep this Ableton Exclusive for now.

    Edit: Next thing I'm going to do is document the communication between Ableton and the Launchpad :D, let's see what I can find there.

    Thanks a lot for looking into this, it's very useful info. I was fearing that could be the case. Perhaps Ableton integration uses programmer mode instead? Atom scripting can also enable that (it's all just code), it's just more grindy to reimplement some of the built-in functionality.

    @blueveek @FloRi89
    I don’t use Ableton, but from what i saw in some videos Ableton is able to paste the notes and stuff you played on a keyboard in the last unknown defined timeframe without recording it somewhere into a track. Some kind of live-tracking what you do and if you liked it just click this function and it pastes that onto a piano roll...like an ever growing history of incoming MIDI data...
    I don’t know the name for that function. But i am pretty sure that the button is for this data.
    So it is actually just temporary data in the memory of the computer that Ableton runs on.

    I think you’re referring to “Capture MIDI”, which is different from “Print to Clip”, which is a Launchpad Pro feature based on its sequencing capabilities and what @FloRi89 is looking into. Both equally cool features! However, implementing the latter seems to be a little bit more challenging, or at least we don’t know how it works under the hood yet.

  • wimwim

    @wim said:

    @orand said:
    I realize the window for advice is over, but the sooner you release, the sooner you get real product validation with people’s wallets, not just with the length of this thread. 😄

    And, if the influx of cash is sufficient, it might just enable you to focus more exclusively on automation and everything else folks are asking for! Remember, money is what gives you the freedom to choose where you spend your time.

    That would be true if iOS music apps actually generated that kind of revenue. Sadly, they don't.

  • espiegel123espiegel123

    @FloRi89 said:

    @blueveek said:

    @tk32 said:
    You just need to contact the Patchstorage admin team and ask for a section to be added. We can help arrange that post-launch.

    As long as you can ensure at least 5 patches are added in the first few weeks they are happy to add a new category.

    (that's the basis on which I got the BM3 section created there - and the same happened with Drambo, Mozaic, NS2 etc.)

    That's perfect, thanks! This would be a good opportunity for me to build some templates and example scripts, e.g. "simple new controller", "modified launchpad", "integration with another app on a virtual midi port", "high-contrast theme"...

    O.K so I tested what the Launchpad sends on the "Print To Clip" button. Unfortunately it's nothing, no MIDI or SysEx. Seems that putting it into DAW mode isn't enough to enable this button, probably some undocumented SysEx that you have to send, or something like that. So it seems they want to keep this Ableton Exclusive for now.

    Edit: Next thing I'm going to do is document the communication between Ableton and the Launchpad :D, let's see what I can find there.

    Have you tried to spy with the MacOS MidiMonitor.app it has an option to show everything sent to/from a driver. It should let you see any communication between the Launchpad’s two drivers and Ableton.

  • JumpercollinsJumpercollins

    @blueveek Will we have a Atom 2 user manual to read or is it built into the app?

  • krassmannkrassmann

    Will Atom 2 be a free update for the actual Atom? Can I buy it now and will be automatically updated?

  • wimwim
    edited March 2021

    @krassmann said:
    Will Atom 2 be a free update for the actual Atom? Can I buy it now and will be automatically updated?

    It will be a separate app. No automatic update.
    If I remember correctly, there will be a bundle for some period of time to give existing owners credit for Atom 1.

    [edit: yep, I remembered correctly, unless things have changed since then...]
    https://forum.audiob.us/discussion/comment/860936/#Comment_860936
    https://forum.audiob.us/discussion/comment/835582/#Comment_835582

  • ipadbeatmakingipadbeatmaking

    @wim said:

    @krassmann said:
    Will Atom 2 be a free update for the actual Atom? Can I buy it now and will be automatically updated?

    It will be a separate app. No automatic update.
    If I remember correctly, there will be a bundle for some period of time to give existing owners credit for Atom 1.

    Wow that’s generous. I’ll be skipping the bundle and paying full price. Seems crazy to get all this for free or even a reduced price.

This discussion has been closed.