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

1525355575890

Comments

  • @blueveek said

    I know you're just teasing, but just FYI, there's no way for me to reply to TestFlight feedback, Apple doesn't provide this mechanism in the developer portal. I'll have another look to see what's happening with velocity-based pattern switching and will fix this in the next version.

    :D I'm not surprised
    And for us there's no way to see our previous post, and if you get low on ram it will just close and you'll loose everything you where typing. Given the price apple could do a little better :smile:

  • Does Atom offer multi midi out(bus) like Helium?

  • edited April 2021

    @Johnny89 said:
    Does Atom offer multi midi out(bus) like Helium?

    You simply need a separate instance of Atom2 for each bus and then configure MIDI routing in the host app accordingly. There are actually many advantages to separating MIDI buses in this way, and it won't harm CPU/RAM use (trust me).

    The only possible downside to this multiple instance approach is that some hosts can start to look a bit disorganised - but I believe this was already becoming a problem -- prior to Atom2 -- that host UIs should attempt to solve (e.g. a zoomed-out view in AUM).

  • edited April 2021

    @galmandsværk said:
    One more question (sorry...): is there a reason why colouring the Atom icons in AUM makes them a muddy colour instead of e.g. bright yellow like when I colour other plugins? For the sake of a quick overview, it would be great to be able to keep e.g, both my drum app and the Atom that controls it in the exact same (bright) colour.

    I want this option to i hate that dark color that it forces on, i like em bright! I like to pick the color and not have to choose it from the clip color

  • wait is this a thing? if so how do you access it ?

    Slice to patterns" is the MIDI equivalent for chopping audio into multiple samples and triggering them. The way I see people using this is recording one (longer) melody, slicing it up into separate pattens, and then playing each bar/sub-pattern in varying orders. Mayhem!

  • edited April 2021

    @eross said:
    wait is this a thing? if so how do you access it ?

    Slicing to patterns can be done in a few ways in the current version:

    Either:
    1. Duplicate a pattern a few times, and
    2. Use 'crop to loop' in each pattern.

    or:
    1. Copy selections into the magic clipboard.
    2. Add empty patterns and paste into them.

    In the next update, I'll combine the two steps from either approach into a quicker 'add pattern from loop' button, and I'm thinking something like a 'bars to patterns' would also be pretty cool.

    As a reminder, for quickly using crop to loop or crop to selection, here's a few shortcuts:

    • Double-tapping in the ruler will snap the loop markers to the closest bar.
    • Tapping in the ruler outside the loop brace will snap the loop to the closest bar as well.
    • Long pressing a selection will snap the loop markers to that selection.
    • Long pressing the loop brace in the ruler will select all notes within that time range.

    Take a look at the universal gestures section in the manual to learn more about them.

  • Is there an updated manual for this? I am trying to wrap my head around the 1 instance of Atom in AUM controlling all the tracks with different clips/patterns. Also trying to understand the whole Atom/Drambo thing everyone is talking about. I LOVE these modular apps with basically open world freedom, but damn do I get confused and overwhelmed with them.

  • edited April 2021

    @slicetwo said:
    Is there an updated manual for this?

    See https://forum.audiob.us/discussion/comment/945153/#Comment_945153

    This takes a while because it's pretty much all volunteer work. We're not a company, this isn't profitable when compared to the amount of work required to keep things running, and (for now) we're just doing stuff in our free time because we love it.

    I am trying to wrap my head around the 1 instance of Atom in AUM controlling all the tracks with different clips/patterns. Also trying to understand the whole Atom/Drambo thing everyone is talking about. I LOVE these modular apps with basically open world freedom, but damn do I get confused and overwhelmed with them.

    In Drambo, you can either create an Atom before the MIDI-to-CV module on each track, or follow @echoopera's approach and create your Atom tracks in the mixer view. Switching patterns in Drambo will also switch patterns in Atom, with Drambo as the master and Atom as the slave. In AUM, this would be relatively similar, and you'd use an instance per track. In both cases, you can use another Atom, StepPolyArp (or your DAW, like what @MisplacedDevelopment has done with NS2) to create song arrangements.

    For more info, see my replies here, my quick demo from yesterday, and some of the templates over at patchstorage.

  • So Sorry I might have missed this...... so many cool updates and other shiny things that distract me. @blueveek is there a way for you to audition the midi before import like the new 4pockets app? I would love that so much!!!!

    Also is there a way to trigger the patterns to play on next bar or wait 4 beats etc... instead of immediately?

    Thanks so much I need to gift some more of this away!!

  • @blueveek said:

    @slicetwo said:
    Is there an updated manual for this?

    See https://forum.audiob.us/discussion/comment/945153/#Comment_945153

    This takes a while because it's pretty much all volunteer work. We're not a company, this isn't profitable when compared to the amount of work required to keep things running, and (for now) we're just doing stuff in our free time because we love it.

    I am trying to wrap my head around the 1 instance of Atom in AUM controlling all the tracks with different clips/patterns. Also trying to understand the whole Atom/Drambo thing everyone is talking about. I LOVE these modular apps with basically open world freedom, but damn do I get confused and overwhelmed with them.

    In Drambo, you can either create an Atom before the MIDI-to-CV module on each track, or follow @echoopera's approach and create your Atom tracks in the mixer view. Switching patterns in Drambo will also switch patterns in Atom, with Drambo as the master and Atom as the slave. In AUM, this would be relatively similar, and you'd use an instance per track. In both cases, you can use another Atom, StepPolyArp (or your DAW, like what @MisplacedDevelopment has done with NS2) to create song arrangements.

    For more info, see my replies here, my quick demo from yesterday, and some of the templates over at patchstorage.

    I’ve started a thread to record my DAW experiences https://forum.audiob.us/discussion/44865/using-atom-2-in-different-daws

  • @blueveek said:

    @slicetwo said:
    Is there an updated manual for this?

    See https://forum.audiob.us/discussion/comment/945153/#Comment_945153

    This takes a while because it's pretty much all volunteer work. We're not a company, this isn't profitable when compared to the amount of work required to keep things running, and (for now) we're just doing stuff in our free time because we love it.

    I am trying to wrap my head around the 1 instance of Atom in AUM controlling all the tracks with different clips/patterns. Also trying to understand the whole Atom/Drambo thing everyone is talking about. I LOVE these modular apps with basically open world freedom, but damn do I get confused and overwhelmed with them.

    In Drambo, you can either create an Atom before the MIDI-to-CV module on each track, or follow @echoopera's approach and create your Atom tracks in the mixer view. Switching patterns in Drambo will also switch patterns in Atom, with Drambo as the master and Atom as the slave. In AUM, this would be relatively similar, and you'd use an instance per track. In both cases, you can use another Atom, StepPolyArp (or your DAW, like what @MisplacedDevelopment has done with NS2) to create song arrangements.

    For more info, see my replies here, my quick demo from yesterday, and some of the templates over at patchstorage.

    Mad respect! Thank you. So when you say all your clips in one instance, that doesn't mean that, using AUM as an example, I can have 1 instance of atom with different melodies for 3 tracks, I'd still need 3 instances of Atom, 1 for each individual track? If that's the case, I am definitely missing something with the clips thing. How are clips different from patterns?

  • edited April 2021

    Here's my attempt at a quick explanation for @slicetwo (and anyone else)

    • Patterns in other apps (say, in Helium for example) are locked in sync together. That means the bassline, melody and drums can never be separated or controlled individually.

    • A Clip (which in this case is a term specific to Atom2) is an individual instance of the app which can be triggered, re-triggered, stopped, mixed and matched independently - and this is particularly fun when done with a compatible controller - or with another Atom2 instance acting as an 'orchestrator' node. Note - If you want all of your clips to remain in locked sync that's obviously possible too.

    And just to add to your confusion... each Atom2 clip can have an unlimited number of sub-patterns which you can manually switch between (via MIDI notes, CC, program change or velocity) - and some apps such as Drambo will automatically advance these 'sub-patterns' when you switch scenes.

  • edited April 2021

    @blueveek

    Man, you’ve really got a beautiful thing here. I tried out a quick session when I got home from work last night (late!) and with leaving everything default, I had a couple different patterns switching back and forth with Drambo’s pattern functions; WOW! This is going to be amazing when I have some time to really get into it!

    Thank you so much!

    I only lasted about 10 minutes on the couch before I was out like a light, but I think I had a dream about Atom2. It was this elaborate project where I had all of Atom’s exposed parameters wired up to things in Drambo, like the Record, Launch, and Play Pattern buttons, all of them. I had it recording, playing, launching itself and it soon became its own living and breathing thing.

    It ended up taking over everything in my house, kicked me to the curb, and the last thing I remember seeing was Atom2 and my GF heading to the bedroom with the door slamming in my face... wtf Atom?

  • @blueveek said:

    thinking something like a 'bars to patterns' would also be pretty cool.

    this B)

  • @tk32 said:
    Here's my attempt at a quick explanation for @slicetwo (and anyone else)

    • Patterns in other apps (say, in Helium for example) are locked in sync together. That means the bassline, melody and drums can never be separated or controlled individually.

    • A Clip (which in this case is a term specific to Atom2) is an individual instance of the app which can be triggered, re-triggered, stopped, mixed and matched independently - and this is particularly fun when done with a compatible controller - or with another Atom2 instance acting as an 'orchestrator' node. Note - If you want all of your clips to remain in locked sync that's obviously possible too.

    And just to add to your confusion... each Atom2 clip can have an unlimited number of sub-patterns which you can manually switch between (via MIDI notes, CC, program change or velocity) - and some apps such as Drambo will automatically advance these 'sub-patterns' when you switch scenes.

    A-HA! Thank you. That makes sense. So CLIP is one instance of the Atom app, a PATTERN are all the various melodies/etc. within each CLIP/APP. So with all that cleared up, what is the whole thing about having all the CLIPS in one instance that is in this update? Did it mean that we could CONTROL all the other CLIPS/Apps from one instance?

  • edited April 2021

    @slicetwo not quite

    Atom2 still expects you to create one instance per channel/bus/instrument, but within that instance can be an unlmiited number of pattern variations.

    here's a real world example...

    Let's say you have three tracks in your host: drum, bass and melody.

    If you use Atom2 you will need a separate instance of the app for each of the 3 tracks, but... each 'clip' can also have an infinite number of sub-patterns that can be selected using lots of different techniques (the only limit is your imagination).
    You can also create multiple Atom2 clips per track, and this is particularly cool when using something like a Novation Launchpad controller, as each clip can be assigned individually to the pad grid, and these can be assembled into 'scenes' just like in Ableton, and can also be mixed and matched freely as a live jam.

    If you are sequencing your drum, bass and melody tracks via a combined MIDI sequencer (like LK or Helium) you only need one instance of that sequencer, and each of the 3 patterns in it will be routed out to a separate MIDI channel (eg drums on channel 1, bass on 2, etc). However, there is a cost to pay in terms of flexibility when everything in a single app, and using a single app to sequence multiple channels means that app will never be able to support MPE in the future (which requires all 16 MIDI channels for each track).

  • And each clip can have its own tempo multiplier/divider? And individual lengths? Is there per-clip swing?

    This reminds me of the Octatrack's sequencer.

    With multiple Atom clips running, each with different lengths and time signatures, how tight is the timing in AUM?

  • edited April 2021

    @ocelot said:
    With multiple Atom clips running, each with different lengths and time signatures, how tight is the timing in AUM?

    The timing is exceptionally tight. Trust me, we really bomb tested this during the beta.

    During testing we even discovered and calculated the amount of drift present in Ableton Link (which AUM depends on) but Blueveek was able to overcome this with some ingenious code that manages to keep Atom2 in perfect lock sync at all times.

    It's all the little details like this - like how Atom2 unloads it's UI when not needed to save resources, and the amazingly powerful undo/redo buffer code - that really separate Atom2 from a lot of other plugins, even though you'll never see these things mentioned in the release notes.

  • @tk32 said:
    @slicetwo not quite

    Atom2 still expects you to create one instance per channel/bus/instrument, but within that instance can be an unlmiited number of pattern variations.

    here's a real world example...

    Let's say you have three tracks in your host: drum, bass and melody.

    If you use Atom2 you will need a separate instance of the app for each of the 3 tracks, but... each 'clip' can also have an infinite number of sub-patterns that can be selected using lots of different techniques (the only limit is your imagination).
    You can also create multiple Atom2 clips per track, and this is particularly cool when using something like a Novation Launchpad controller, as each clip can be assigned individually to the pad grid, and these can be assembled into 'scenes' just like in Ableton, and can also be mixed and matched freely as a live jam.

    If you are sequencing your drum, bass and melody tracks via a combined MIDI sequencer (like LK or Helium) you only need one instance of that sequencer, and each of the 3 patterns in it will be routed out to a separate MIDI channel (eg drums on channel 1, bass on 2, etc). However, there is less control and flexibility with this method, and using a single app to sequence multiple channels means that app will never be able to support MPE in the future (which requires all 16 MIDI channels for each track).

    That makes a crap-ton more sense than anything else I have read about this. Thank you so much. So if you want to use a launchpad, you WOULD need multiple instances for one track, as the LP doesn't control the patterns IN each instance, yeah? But you could, theoretically, control the patterns in one instance with another controller, letting the LP control the CLIPS without needing multiple Atom Apps loaded up for each track. Am I understanding this correctly?

  • edited April 2021

    @slicetwo

    Yep. Up until the most recent update you had to have a separate clip for each separate pattern.

    This update has just opened the 4th dimension.

    by the way, it's theoretically still possible to have your one launchpad controlling both clip launching AND pattern selection. Here's one possible scenario (of many)...

    The pads on your launchpad select which clip is playing, and the velocity you hit the pad with determines which of that clip's many different sub-patterns is selected.

    Mind bending!!

  • so there’s no confusion i’m gonna state the obvious - one instance of atom plays patterns one at a time. there’re no nested patterns inside one instance that you send to different instruments. you just switch patterns inside each instance. there. just in case.

  • @tk32 said:
    @slicetwo

    Yep. Up until the most recent update you had to have a separate clip for each separate pattern.

    This update has just opened the 4th dimension.

    by the way, it's theoretically still possible to have your one launchpad controlling both clip launching AND pattern selection. Here's one possible scenario (of many)...

    The pads on your launchpad select which clip is playing, and the velocity you hit the pad with determines which of that clip's many different sub-patterns is selected.

    Mind bending!!

    Good lord. This is all so insane. Thanks!

  • @tk32 said:
    Here's my attempt at a quick explanation for @slicetwo (and anyone else)

    • Patterns in other apps (say, in Helium for example) are locked in sync together. That means the bassline, melody and drums can never be separated or controlled individually.

    • A Clip (which in this case is a term specific to Atom2) is an individual instance of the app which can be triggered, re-triggered, stopped, mixed and matched independently - and this is particularly fun when done with a compatible controller - or with another Atom2 instance acting as an 'orchestrator' node. Note - If you want all of your clips to remain in locked sync that's obviously possible too.

    And just to add to your confusion... each Atom2 clip can have an unlimited number of sub-patterns which you can manually switch between (via MIDI notes, CC, program change or velocity) - and some apps such as Drambo will automatically advance these 'sub-patterns' when you switch scenes.

    Can you upload a ‘session’ for us dummies?

    Thanks..

  • btw hirajoshi scales are really fantastic

  • edited April 2021

    @tk32 said:
    @slicetwo

    Yep. Up until the most recent update you had to have a separate clip for each separate pattern.

    This update has just opened the 4th dimension.

    by the way, it's theoretically still possible to have your one launchpad controlling both clip launching AND pattern selection. Here's one possible scenario (of many)...

    The pads on your launchpad select which clip is playing, and the velocity you hit the pad with determines which of that clip's many different sub-patterns is selected.

    Mind bending!!

    Cool. How do I set something like up? I actually was thinking about using a knob on a LCXL to scroll thru patterns. Is this possible as well?

    UPDATE: I did a test to set a LCXL knob to switch patterns. Works fine.

    But, I also use LCXL knobs to control Probability and Swing. These settings affect the selected/checked Pattern, but do not affect the Pattern that the knob scrolls to. The scrolled to Pattern plays, but the Probability and Swing params do not get applied. (Hope this is clear). Any ideas?

    2nd UPDATE: I saved the AUM project and now the Probability param works with all Patterns. Cool.

  • edited April 2021

    @carvingcode said:
    Cool. How do I set something like up? I actually was thinking about using a knob on a LCXL to scroll thru patterns. Is this possible as well?

    Yes. In your particular case, assuming you’re using AUM, I'd say the easiest thing to do is map that knob to the 'Play Pattern' parameter. It goes from 0-15 to make it easier for live performance (just like the tempo parameter is similarly clamped for example), but I may consider expanding the range if that's not sufficient for most people.

  • edited April 2021

    Here's a link to a little Drambo project file using 4 instances of Atom 2. In order to get the full experience, you'll need the following synths:
    . Model 15
    . Factory
    . Pure Piano
    The project also includes the Random Note generator @bcrichards helped me to craft last year...so feel free to use that elsewhere in your compositions...just save it out as a Midi Rack for later use.

    Hope you enjoy the track :wink:
    When it opens, if you have all of the above synths, just hit Play and enjoy the groove :blush:

    Sample:

    File:
    You can download the Project file from the Youtube Description as well...

  • edited April 2021

    Agree about the auditioning.

    I leave it on all the time, but sometimes get a shock when group selecting a large number of notes. :D

    My suggestion was for audition to ignore multiple notes at the same pitch, or to cap at 10 total notes. I think it's already on Blueveek's big fat Trello list :)

  • about drawing notes - would really like an option to ‘repeat after 1, 2, 3, 4... notes’

Sign In or Register to comment.