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 2 is now available

1…4647495152…90

Comments

  • rs2000rs2000

    @blueveek Glad you like it 😊

    Not being a trained musician, I have difficulty using the scales. Don't get me wrong, for all the great musicians here it's certainly a no-brainer but I'm composing just by ear and I know exactly which notes I need within an octave. Now how do I find that matching scale, if it even exists? Scroll through the list and read through every single key?

    Let me suggest and ask you for the following like it is done in some other apps too:
    How about adding a small one-octave keyboard above the scales list which will show all notes of the currently chosen scale highlighted.
    Now we can either choose a scale from the list or (which would be much, much faster for me) just add or remove notes by tapping keys on that mini keyboard and be free to define any scale, at least such that fit into one octave 😉

  • blueveekblueveek
    edited April 2021

    @rs2000 said:
    @blueveek Glad you like it 😊

    Not being a trained musician, I have difficulty using the scales. Don't get me wrong, for all the great musicians here it's certainly a no-brainer but I'm composing just by ear and I know exactly which notes I need within an octave. Now how do I find that matching scale, if it even exists? Scroll through the list and read through every single key?

    Let me suggest and ask you for the following like it is done in some other apps too:
    How about adding a small one-octave keyboard above the scales list which will show all notes of the currently chosen scale highlighted.
    Now we can either choose a scale from the list or (which would be much, much faster for me) just add or remove notes by tapping keys on that mini keyboard and be free to define any scale, at least such that fit into one octave 😉

    My workflow is usually the other way around: pick a scale and noodle around to see if I like it. However, I'm not claiming it's "better", and I know this doesn't fit well for the opposite way of doing things where you noodle around and want to pick a scale afterwards.

    Something much better can be done here. I won't say exactly exactly what for now, but expect a huge update to how scales work, which doesn't just include 'custom scales' ;)

  • rs2000rs2000

    @blueveek Oh I get it, I remember some apps to provide "scale from selection" which would be just as great 😉

  • mbncpmbncp

    @tk32 said:
    What's happening here? You forgot to include an explanation :)

    Just Mozaic scripts that converts to note and back to CC. I'm surprised it works pretty well. B)
    Off course you lose some cool features of Atom like scales, transpose,.. but it's easy to separate from standard notes and have two clips, either before of after recording.
    The scripts are not very smart, could support some user functions and make it easier to add more CC
    "Enjoy" :
    https://forum.audiob.us/discussion/44710/mozaic-script-to-record-cc-pw-as-notes-and-back-to-normal-1-0-beta#latest

  • GdubGdub

    Update out !!

  • gusgranitegusgranite

    @blueveek said:

    Celebrating one month since the launch

    Exactly one month ago, on March 15, Atom 2 was released. Thank you all for being early adopters.

    Version 2.0.5 is now released, and should make its way to your country's store shortly. It includes the following:

    • Enabled iOS 13 compatibility for Launchpad controllers.
    • Added nonuplets, undecuplets and tredecuplets for quantization, swing, and general editing, in addition to triplets, quintuplets and septuplets.
    • Added 39 new scales, grouped by their main mode, and including all of their corresponding modal flavors, for a total of 74. All scales are sorted with music theory in mind and ordered by their respective modal brightness, from “bright or happy” to “dark or sad”. The new scales include Double Harmonic, Persian, Neapolitan Minor, Neapolitan Major, Flamenco, Enigmatic, Octatonic Whole-Half Diminished & Half-Whole Diminished, Major Hexatonic & Minor Hexatonic, Whole Tone, Augmented & Six-Tone Symmetric, Prometheus and Tritone scales.
    • Added Program Change clip triggers, available in the advanced launch settings.
    • Added auto-routing support for the Akai MPK Mini 3 controller, which also serves as a simple example hardware script for adding your own custom routing.
    • Added receiveCC, receivePitchBend and receiveProgramChange, in addition to receivePolyphonicAftertouch and receiveChannelAftertouch, to the scripting sandbox.
    • Fixed an issue where controller scripts in would sometimes connect to the same ports twice.
    • Added a “Disabled Animations” configuration that reduces motion.
    • Added a “Reload UI” button for quickly reloading the configurations and styles.
    • Revamped configs, styles and scripts menus, now with icons, sorting and helpful tips for getting the most out of user extensions.
    • Now preventing accidental dismissal of the manual view when tapping on the background.
    • Now presenting doorhanger menus modally, disabling input for the background.
    • Better performance when opening various menus like Scales.
    • Fixed sliders also scrolling containers, and "Process" toolbars appearing incorrectly on narrow screens (e.g. on iPhone in vertical mode)
    • Layers now sorted by track.
    • Default quantize toolbar strength now depends on the top-level quantize button.

    Killer! Great work, @blueveek 👊🙏

  • NimboStratusNimboStratus

    What is the recommended approach if you want to build up a piece of music with sections.

    1. Multiple clips - if so then how to trigger in order?
    2. One huge atom clip?

    Thanks

  • blueveekblueveek
    edited April 2021

    @NimboStratus said:
    What is the recommended approach if you want to build up a piece of music with sections.

    1. Multiple clips - if so then how to trigger in order?
    2. One huge atom clip?

    Thanks

    Definitely #1. You can build a whole song this way, and it's fairly straightforward (though "modular easy", not "cubasis easy").

    • Use a master Atom sequencer to sequence the clips.
    • Set all your other Atoms to "hold" mode and disable "thru" for the easiest way to have them trigger.

    See this great demo @tk32 made a while back. The purple Atom that's shown is the master arranger, that turns all of the other clips on and off. There's also a neat little trick in there where it's set at 0.5x tempo, so all of the song parts are twice as long.

    @tk32 said:
    There is no special tricks involved, but for convenience I have all my player Atoms set to Hold mode so that the patterns only play while the sequencer notes are sustained (and then un-launch afterwards).

  • gregsmithgregsmith

    @blueveek said:

    Celebrating one month since the launch

    Exactly one month ago, on March 15, Atom 2 was released. Thank you all for being early adopters.

    Version 2.0.5 is now released, and should make its way to your country's store shortly. It includes the following:

    • Enabled iOS 13 compatibility for Launchpad controllers.
    • Added nonuplets, undecuplets and tredecuplets for quantization, swing, and general editing, in addition to triplets, quintuplets and septuplets.
    • Added 39 new scales, grouped by their main mode, and including all of their corresponding modal flavors, for a total of 74. All scales are sorted with music theory in mind and ordered by their respective modal brightness, from “bright or happy” to “dark or sad”. The new scales include Double Harmonic, Persian, Neapolitan Minor, Neapolitan Major, Flamenco, Enigmatic, Octatonic Whole-Half Diminished & Half-Whole Diminished, Major Hexatonic & Minor Hexatonic, Whole Tone, Augmented & Six-Tone Symmetric, Prometheus and Tritone scales.
    • Added Program Change clip triggers, available in the advanced launch settings.
    • Added auto-routing support for the Akai MPK Mini 3 controller, which also serves as a simple example hardware script for adding your own custom routing.
    • Added receiveCC, receivePitchBend and receiveProgramChange, in addition to receivePolyphonicAftertouch and receiveChannelAftertouch, to the scripting sandbox.
    • Fixed an issue where controller scripts in would sometimes connect to the same ports twice.
    • Added a “Disabled Animations” configuration that reduces motion.
    • Added a “Reload UI” button for quickly reloading the configurations and styles.
    • Revamped configs, styles and scripts menus, now with icons, sorting and helpful tips for getting the most out of user extensions.
    • Now preventing accidental dismissal of the manual view when tapping on the background.
    • Now presenting doorhanger menus modally, disabling input for the background.
    • Better performance when opening various menus like Scales.
    • Fixed sliders also scrolling containers, and "Process" toolbars appearing incorrectly on narrow screens (e.g. on iPhone in vertical mode)
    • Layers now sorted by track.
    • Default quantize toolbar strength now depends on the top-level quantize button.

    Congrats 🙌

    I hope all our requests aren’t keeping you up at night 😂

  • vasilymilovidovvasilymilovidov

    i’m sure this was asked before but i can’t find it - is it possible to change patterns with cc messages?

  • NimboStratusNimboStratus

    @blueveek said:

    @NimboStratus said:
    What is the recommended approach if you want to build up a piece of music with sections.

    1. Multiple clips - if so then how to trigger in order?
    2. One huge atom clip?

    Thanks

    Definitely #1. You can build a whole song this way, and it's fairly straightforward (though "modular easy", not "cubasis easy").

    • Use a master Atom sequencer to sequence the clips.
    • Set all your other Atoms to "hold" mode and disable "thru" for the easiest way to have them trigger.

    See this great demo @tk32 made a while back. The purple Atom that's shown is the master arranger, that turns all of the other clips on and off. There's also a neat little trick in there where it's set at 0.5x tempo, so all of the song parts are twice as long.

    @tk32 said:
    There is no special tricks involved, but for convenience I have all my player Atoms set to Hold mode so that the patterns only play while the sequencer notes are sustained (and then un-launch afterwards).

    OH! This is JUICY! Thank you!!!! :-)

  • blueveekblueveek

    @vasilymilovidov said:
    i’m sure this was asked before but i can’t find it - is it possible to change patterns with cc messages?

    Restricted to the beta for now. The next version will include this. And if you're using Drambo, it'll happen automatically to follow the pattern in the host. There's a full overhaul of how patterns behave in the works.

  • espiegel123espiegel123

    @blueveek : it would be great if double-tapping the number of measures gave one a chance to type in a number of measures.

  • NimboStratusNimboStratus

    @tk32 said:
    @gregsmith here’s a reminder of my demo vid that showed one Atom being used to trigger all the others - therefore acting as a pattern sequencer.

    There is no special tricks involved, but for convenience I have all my player Atoms set to Hold mode so that the patterns only play while the sequencer notes are sustained (and then un-launch afterwards).

    Cannot get this to work. I have two atom2s running. First one has c1 note. 2nd one has first atom as midi source and got it set to launch note c1. First atom plays c1 note but second atom2 doesn’t launch. Any ideas? Thanks

  • blueveekblueveek

    @NimboStratus said:

    @tk32 said:
    @gregsmith here’s a reminder of my demo vid that showed one Atom being used to trigger all the others - therefore acting as a pattern sequencer.

    There is no special tricks involved, but for convenience I have all my player Atoms set to Hold mode so that the patterns only play while the sequencer notes are sustained (and then un-launch afterwards).

    Cannot get this to work. I have two atom2s running. First one has c1 note. 2nd one has first atom as midi source and got it set to launch note c1. First atom plays c1 note but second atom2 doesn’t launch. Any ideas? Thanks

    C1 or C-1?

  • tk32tk32
    edited April 2021

    I can create a simple setup and share the AUM project here....

    Gimme a few mins.

    Edit: yes C-1 (negative 1) can easily be misread as C dash 1 , when in actual fact you want C1

  • blueveekblueveek

    @tk32 said:
    I can create a simple setup and share the AUM project here....

    Gimme a few mins.

    Maybe also post it to patchstorage?

  • tk32tk32
    edited April 2021

    @NimboStratus

    Here’s a very simple template with only the sequencer and 3 instances. I’ll make a more advanced version for PatchStorage

    https://www.dropbox.com/s/bjadtv47ro3uzau/Template - Atom2 sequencer.aumproj?raw=1

    The triggered clips are all set to HOLD mode and have the note triggers C1, D1 and E1 respectively. I also disable Thru input on each of the triggered clips so the trigger notes are never passed through as MIDI notes.

    Note - if you are building this template yourself you must also remember to route the sequencer clip into each of the triggered clips so that they receive notes from the trigger sequence.

  • NimboStratusNimboStratus

    Ah yes guys c-1 is not c1! Thanks

  • tk32tk32

    And here is the same template uploaded to PatchStorage:

    https://patchstorage.com/atom2-internal-sequencer-template/

  • xorxor

    @blueveek said:

    @xor said:
    I was playing around with a matrix of Atom 2’s in AUM and started thinking about sequencing them with a master sequence. Then I thought that I’d like to include some Drum Computer pattern changes too. Then I realized that I’d quickly run into unintended midi messages going the wrong au’s if I tried to sequence it all from the same master atom.

    Do I need one atom to sequence other atoms and then a second for dc and then a third for aum (just thinking ahead for when atom gets automation support)? Basically an entire lane for master timeline-level sequencers?

    You can disable "Thru" from each clip's menu in the top-left corner to make sure these triggers are 'swallowed' by each individual atom controlled by the master sequence. I pondered also making this automatic for the Launch note/cc/pc, but I've heard mixed opinions about it. What do you think?

    I was actually talking about how you can’t really have a single master atom if you need to control other au’s like drum computer or aum because you risk them interpreting each other’s inputs. You can get lucky and not have any fixed overlapping midi but there are au’s like dc that have fixed midi assignments for things like pattern change.

    I’d already found thru mode when configuring the other atom instances to be controlled. I gotta say that configuring 8 instances to

    • select launch note
    • Disable thru mode
    • Enable gate mode
      Wasn’t the most enjoyable though not sure if there is anything better I could think of.

    One thing I did run into was needing two different launch modes at the same time though. While “composing” I found myself needing to manually launch multiple clips concurrently but was unable to since they were in gate mode and my timing and lack of equal finger lengths made it impossible to get them to start even reasonably in sync with each other or the rest of the song that was playing. Having gate mode for midi input and launchpad, with the normal launch quantum behavior, for manual launching would be perfect.

    I discovered that composing on the timeline is, well, difficult. I could never get aum’s scrub to work well, I’d inevitably scrub past where I was on the timeline and then when backing up I never saw the now-playing vertical bar go backwards in atom. Also, when I would start playing again it, of course, wouldn’t start a drone whose only event was on bar 1. I don’t know if there’s any way for atom to control aum’s song position but that would be ideal.

    Should editing an event after it has started work? I was trying to extend the duration of a section (on the master timeline) but it ended at its original scheduled time rather than its new time.

    +1 to separate x/y zooming. Also to allowing more bars to be displayed. Don’t need beats on the master timeline (in this particular instance) so have the grid quantized to whole notes but it’s still taking up more horizontal space than really needed. This would also be a great time for folded custom scales. I have each track’s launch note starting on c an octave apart but only have three clips per track at the moment. It’d be nice to have a scale of c-f that caused f#-b to be hidden so I could see all my tracks.

    Today as I was reading the 2.0.5 release notes (yay for layer sorting) that timeline level automations (volume) are going to be an instance where you’ll need one per atom, or at a minimum, one for a group of atoms that can share the same exact automation. I guess thinking about these as one-per-track makes sense.

    Thinking about automation, is there any consideration being given to automation probability? Say on a clip where a pitch bend has a 10% chance of not happening or the amount of modulation varies from one play through to the next? If there’s a mod wheel on both a clip and a “track” what’s going to happen?

    Some random thoughts:

    • is there a 0.25 tempo hidden in there between 0.2 and 0.3?
    • Any reason that tempo goes to 0 but the au param only goes to 0.5?
    • Any thoughts on quantizing the tempo au param to make it easy to change tempo to exactly 0.25, 0.333, 0.5, 0.666, 1, ...?
    • Have you considered shared patterns so changes in one are reflected in all shared instances?
    • Have you thought about fwd/rev playback to turn a loop into a kind of arp?

    Atom is a great app and keeps getting better. Like many, looking forward to automation. Here’s hoping for a month of weekends. ;-)

  • tk32tk32
    edited April 2021

    @xor said:
    I gotta say that configuring 8 instances to...

    • Select launch note
    • Disable thru mode
    • Enable gate mode
      ...wasn’t the most enjoyable though not sure if there is anything better I could think of.

    Perhaps do it once and save the AUM project as a template?

    ...better yet, do what I did and share it on patchstorage

  • mbncpmbncp
    edited April 2021

    @blueveek
    All my global variables and other related question was just to find some workarounds
    My keylab88 is a pretty cool controller, 8 pads, a bunch of labeled buttons, 9 knobs, 9 faders and a 32 char display that I can send text to.

    The only problem is that it is dumb and not only as it can't do much more than sending either sysex, CC or Notes when I press one of the buttons, but it will send data on 2 different ports, sometimes sending the same values. :#
    In a JS script I need to watch for both, but currently there is no way for the script to know if that note on came from the record button (mackie protocol) or a standard keyboard note.

    One option is to create a "bunch" of scripts with just one in and one out, having a Mozaic scripts dealing with sending back to right script (virtual midi port).

    But it would be so much easier that an Atom JS scripts knows which port sent "that" OnNote.. and that the script could send some midi to a specific port.

    With Drambo you may want that sometimes events get sent only to the active track, sometimes to Control (mapping) and to save settings in current project, sending some data to a Mozaic script that will work as a storage unit.

    Ok, all that to say that to say that I (and probably others) need a port ID for incoming midi and one for output.

    Would function onNoteOn(pitch, velocity, channel, timestamp, portID) {} and emit([..], portID) make all previous script`s unusable ?

    I can understand that you focused on the Launchpad, but even If I might get one (though no room , "no money"), being able to press a button with one hand while playing a chord, and the other using some slider or wheels would be impossible. (Ok, I'm pushing it a bit, but I really do that :)

  • SynthiSynthi

    @tk32 said:

    @rs2000 said:
    Just purchased Atom 2 btw.
    Sorry for the dumb question - how can I edit pitch bend and modwheel in a pattern?

    Pitchbend and Modwheel support will arrive with the automation upgrade.

    i.e. not yet supported

    So no “blackbox” récord /playback before the full automation upgrade????

  • NimboStratusNimboStratus

    @tk32 said:

    @xor said:
    I gotta say that configuring 8 instances to...

    • Select launch note
    • Disable thru mode
    • Enable gate mode
      ...wasn’t the most enjoyable though not sure if there is anything better I could think of.

    Perhaps do it once and save the AUM project as a template?

    ...better yet, do what I did and share it on patchstorage

    Legend! ;-)

  • SynthiSynthi

    @mbncp said:
    Just figured out how to send text to my keylab essential keyboard controller :) B)

    Anyone with a keylab ?
    I'm thinking about using :

    cat/char, Preset button :     Track Select prev/next
<-, -> arrows  :                Slot selection prev/next
<<  >>    :                      Pattern selection (if we ever get a function for it)
The stop button :                  Clear current pattern (dble-click or long press)
Play/Pause             
Record button :                   Arm
Loop 
Save :    ~~Not sure but while holding the save button, hit one of the pads, and it would assign it to that clip~~
Save state of all running clips is more interesting or optional.
Being able to send text to the controller is a big plus, can do a lot with a few controls

Text would show current track, slot and clip state, or info

    just ideas
    Too bad we can't use the big wheel. @Arturia >:)

    Keylab 61 here! How is working that script??

  • tk32tk32

    @Synthi said:
    So no “blackbox” récord /playback before the full automation upgrade????

    I definitely didn't say that.

    See here for Blueveek's most recent general update on future features...
    https://forum.audiob.us/discussion/comment/941259/#Comment_941259

  • mbncpmbncp

    @Synthi said:

    @mbncp said:
    Just figured out how to send text to my keylab essential keyboard controller :) B)

    Anyone with a keylab ?
    I'm thinking about using :

    cat/char, Preset button :     Track Select prev/next
<-, -> arrows  :                Slot selection prev/next
<<  >>    :                      Pattern selection (if we ever get a function for it)
The stop button :                  Clear current pattern (dble-click or long press)
Play/Pause             
Record button :                   Arm
Loop 
Save :    ~~Not sure but while holding the save button, hit one of the pads, and it would assign it to that clip~~
Save state of all running clips is more interesting or optional.
Being able to send text to the controller is a big plus, can do a lot with a few controls

Text would show current track, slot and clip state, or info

    just ideas
    Too bad we can't use the big wheel. @Arturia >:)

    Keylab 61 here! How is working that script??

    Keylab 61, do you mean this one or the essential?

    I'm on an essential, but it shouldn't be too complicated to adjust, though I would need some info.

    What could it do ?
    I would say what ever you want.
    Like select a clip (using track and slot numbers). Then using the play, record buttons.
    Action that can be done in an atom js script are a bit limited, but so far you can play, arm/disarm, .. a clip .. you can see the features here (look for launchScene as :
    https://github.com/victorporof/atom

    Normally it's just a question of assigning a control from your keyboard to an atom function, but if you have a lot of tracks, slots we need to know who to talk to. That's where the LCD is very handy, we can see which track and slot we're are talking with.
    We can also use the pads to select a specific track/slot..use the record button (or another one) to record on that clip.
    And off course a script can do multiple function, like stop a clip, make a copy(pattern) clear it and start recording again.

    It could even add new Launch modes :) Hit and release a pad quickly and it behaves like the Launch pad style, or hold it longer than a second(or whatever) and it will act like the Hold mode ( @blueveek s'gonna kill me :# )

    Also one thing that is very interesting with Atom, is that you can use your keyboard normally, sending the MIDI to your host, then to Atom like you would do with any plugins. But Atom can also get the MIDI directly from your controller, you could just tap a pad, hit the record button, and it would record that clip even if your host is set to receive midi on another track or better not set to receive any MIDI from your keyboard at all.

    All that to say that's it's a bit up to you, we have buttons, we can do certain things, if you have ideas, please share :)

  • MrBlaschkeMrBlaschke

    @mbncp said:
    It could even add new Launch modes :) Hit and release a pad quickly and it behaves like the Launch pad style, or hold it longer than a second(or whatever) and it will act like the Hold mode ( @blueveek s'gonna kill me :# )

    That sounds interesting. Mind sharing a snippet?

  • dokwok2dokwok2
    edited April 2021

    My iPad is an Air 1: highest available OS is 12.x. I bought the bundle (maybe on my iPhone) and figured I would at least get Piano 1 with that, and maybe 2 later. Yesterday I was able to install “an older version” of 2 on my Air 1. So far so good, though the interface feels a little sluggish. Very pleased to be able to import, export MIDI now.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025