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

1626365676890

Comments

  • Thanks for the MPE update @blueveek - seems to work great on a very quick trial, and now there's a way for us MPErs to sequence on iOS.

    Please consider everyone's pleas for you to add IAPs - I'd love to pay more for this stunning app

  • @blueveek said:

    @Stuntman_mike said:
    So to explain…
    I like to create a pattern then trigger a blank pattern to record another pattern for things like chord progressions or variations of the original drum pattern all in one go. Basically a jam session of sorts then go back and pick out the best bits. I would like to use my sustain pedal to trigger blank patterns. I am able to accomplish this with LoopBud because I have created a custom CC layout for my Launchpad where all 64 pads trigger patterns. I setup multiple LoopBuds with 64 patterns total then trigger a pad anytime I want to record a new pattern. I feel like Atom 2 could surpass this workflow by adding a trigger for blank patterns.

    Gotcha. So you want to use a single operation to create a new empty pattern, because you want to use a single CC source for it. Whereas the 'duplicate active' and 'clear active' operations in Atom are distinct and require two inputs.

    I don't think it's that big of a deal to add an 'add empty' pattern command, I'll look into it.

    Awesome, you’re the best @blueveek!
    Thank you 🙏🏻

  • @ErrkaPetti said:
    @blueveek - WTF WTF WTF - do you ever sleep (I’ve said it before)??

    Yet another update of Atom 2 Piano Roll - wow!!!

    Now it’s time for some expensive IAP so we can support you with more cash! Or, perhaps we can make something in common Atom-lovers?

    Good point, maybe a IAP tip jar…

  • Great app loving the versatility!!!

    Is there a way to midi input chords in step mode so the notes line up?

  • @wexy said:
    Great app loving the versatility!!!

    Is there a way to midi input chords in step mode so the notes line up?

    This is something I wonder as well...

    The 'logic' most step-entry sequencers use is to advance the playhead once all notes are released and/or rest/tie is added (quite often using the sustain pedal or 'tab' key or in the case of iOS/iPadOS sequencer an on-screen rest/tie button).

    I'm pretty sure this is somewhere on @blueveek 's to-do list already.

  • @blueveek said:

    I think it’s now easy for anyone to make a demo which proves that rhythm and pitch are actually the same thing, which was a mind-bending realization when I first learned about it.


    Perfect 5th - Rhythm Becomes Pitch...

  • So cc pattern switching doesn’t seem to change the piano roll. Could this be exposed in midi parameters down the track?

  • @wexy said:
    Great app loving the versatility!!!

    Is there a way to midi input chords in step mode so the notes line up?

    No, I'm still trying to figure out the best heuristic to use for this. Atom 1 used debouncing, which meant that notes clumped together in a very short time spans were treated as chords, but this could fail in some circumstances, so I opted out of that for now. I think @Samu's suggestion of using a stack and once all the off's are popped, then the cursor advances, could work well.

    @wexy said:
    So cc pattern switching doesn’t seem to change the piano roll. Could this be exposed in midi parameters down the track?

    If by this you mean that pattern switching plays patterns but doesn't focus them, then this is deliberate on my part. With the Drambo integration, I didn't want patterns to suddenly switch out of view when the song advances. However, I do realize that sometimes this may be needed when recording multiple takes for example (though I still recommend that you consider using multiple instance for this – you get neat Launchpad integration, and an insane amount of additional per-clip trigger options).

  • edited May 2021

    @Samu said:

    @blueveek said:

    I think it’s now easy for anyone to make a demo which proves that rhythm and pitch are actually the same thing, which was a mind-bending realization when I first learned about it.

    You can go even higher than 999bpm. Try maxing out the tempo in the host and also multiplying the 999bpm by 10x or 100x in Atom. You'll get self-oscillating periodicity for bizarro-experiemental weirdness (assuming that the instrument can handle that – e.g. Poison202 never disappointed me).

  • How can I use the new automation feature? I can't work it out for the life of me. P.s. I would like to join the chorus of those saying @blueveek should be cashed-up somehow. Maybe an IAP for something, or maybe just a 'tip jar' of varying amounts?

  • @blueveek
    This is how I would like A2 to work with Cubasis (first track), ignoring the host loop, more fun ahead :)
    Tried a bit every settings but A2 will always reset the clip on loop.
    https://youtu.be/hMJyjNvDQFI

  • @blueveek said:

    @wexy said:
    Great app loving the versatility!!!

    Is there a way to midi input chords in step mode so the notes line up?

    No, I'm still trying to figure out the best heuristic to use for this. Atom 1 used debouncing, which meant that notes clumped together in a very short time spans were treated as chords, but this could fail in some circumstances, so I opted out of that for now. I think @Samu's suggestion of using a stack and once all the off's are popped, then the cursor advances, could work well.

    @wexy said:
    So cc pattern switching doesn’t seem to change the piano roll. Could this be exposed in midi parameters down the track?

    If by this you mean that pattern switching plays patterns but doesn't focus them, then this is deliberate on my part. With the Drambo integration, I didn't want patterns to suddenly switch out of view when the song advances. However, I do realize that sometimes this may be needed when recording multiple takes for example (though I still recommend that you consider using multiple instance for this – you get neat Launchpad integration, and an insane amount of additional per-clip trigger options).

    Yes I want to focus the piano roll so I can edit directly when I switch patterns via cc
    If I could focus pattern via cc as well that would be awesome

  • @blueveek said:

    You can go even higher than 999bpm. Try maxing out the tempo in the host and also multiplying the 999bpm by 10x or 100x in Atom. You'll get self-oscillating periodicity for bizarro-experiemental weirdness (assuming that the instrument can handle that – e.g. Poison202 never disappointed me).

    Yeah, I've noticed, can we get a way to type in the value?
    It takes a while to swipe all the way to 100x :wink:

    Ruismaker also works pretty well when it comes to accurate timing.

    It's this kind of experimental weirdness that gets me going but drives those around me nuts :smiley:

  • edited May 2021

    Bizarro-experiemental self-oscillating weirdness

    (jump to 0:30)

    Weird ambient tempo drones at 99900bpm

  • @mbncp said:
    @blueveek
    This is how I would like A2 to work with Cubasis (first track), ignoring the host loop, more fun ahead :)
    Tried a bit every settings but A2 will always reset the clip on loop.

    Me too. Like I said in this comment, this only happens when the start loop brace in Cubasis is at 0. The behavior is correct when other parts of the host's timeline are being looped.

    I'm considering working around this issue in Cubasis, but it would sure be great if Cubasis didn't "lie" about the song being stopped when it's looping back to 0.

  • @blueveek said:

    Bizarro-experiemental self-oscillating weirdness

    (jump to 0:30)

    Extremely cool Victor 👋👋

  • @blueveek said:

    I'm considering working around this issue in Cubasis, but it would sure be great if Cubasis didn't "lie" about the song being stopped when it's looping back to 0.

    Have you notified @LFS about this 'bug'?

  • @Samu said:

    @blueveek said:

    I'm considering working around this issue in Cubasis, but it would sure be great if Cubasis didn't "lie" about the song being stopped when it's looping back to 0.

    Have you notified @LFS about this 'bug'?

    It's good that you used quotation marks there, because I'm not sure it should necessarily be categorized as a bug – it's one of those situations where it can be reasonably argued that it's up to the host's interpretation what tell AUs when the playhead loops back to 0 (even though it's still playing or looping). It's also possible that without this behavior, some AUs might break and others won't, and that it was added by necessity. My interpretation and wish is that it shouldn't say that it's "stopped", but realistically, it's probably easier for me to work around it than for @LFS to ensure that changing this behavior doesn't break the plethora of other plugins that exist.

  • edited May 2021

    @blueveek said:

    It's good that you used quotation marks there, because I'm not sure it should necessarily be categorized as a bug – it's one of those situations where it can be reasonably argued that it's up to the host's interpretation what tell AUs when the playhead loops back to 0 (even though it's still playing or looping). It's also possible that without this behavior, some AUs might break and others won't, and that it was added by necessity. My interpretation and wish is that it shouldn't say that it's "stopped", but realistically, it's probably easier for me to work around it than for @LFS to ensure that changing this behavior doesn't break the plethora of other plugins that exist.

    Ok,

    One 'related' thing that bugs the bejeezus out of me is that when using count-in in Cubasis it seems to send 'start/play/whateva' to connected apps/plug-ins before the count-in has actually finished?!
    (Apps that follow playhead are not affected by this but apps/sequencers that rely on the transport running are).

    Seems like Atom 2 is affected by this as well...
    My current solution when using external sequencers is to disable count-in.

    Count-In (Pre-Roll) in AUM works perfectly so this is definitely a Cubasis issue...

    Cubasis seems to be on sale again so maybe this time we'll get an actual update :smiley:

    Cheers!

  • @blueveek said:

    @mbncp said:
    @blueveek
    This is how I would like A2 to work with Cubasis (first track), ignoring the host loop, more fun ahead :)
    Tried a bit every settings but A2 will always reset the clip on loop.

    Me too. Like I said in this comment, this only happens when the start loop brace in Cubasis is at 0. The behavior is correct when other parts of the host's timeline are being looped.

    I'm considering working around this issue in Cubasis, but it would sure be great if Cubasis didn't "lie" about the song being stopped when it's looping back to 0.

    I'm unable to try on my very old MBA, but Mozaic isn't sending me a stop on loop.
    What I see is that Atom will sync with the host timeline. If I move the loop by one bar, it still resets but at next bar.
    I'm not saying it's wrong, it's just that it would be neat to have the option that the clip plays without repositioning it's play head on host loop.

    host    123412341234..
    Atom    123451234512..
    
  • @blueveek said:

    Bizarro-experiemental self-oscillating weirdness

    (jump to 0:30)

    Weird ambient tempo drones at 99900bpm

    @Gavinski said:

    @blueveek said:

    Bizarro-experiemental self-oscillating weirdness

    (jump to 0:30)

    Extremely cool Victor 👋👋

    Extremely! The even crazier thing to think about is that each one of those individual Poison notes has it’s own set of oscillation (synthesis) that was brought up to audio rate to begin with to produce the single “note”.

    It’s like “Audio Rate-ception”

    Or “Yo dawg, we heard you like some audio rate, so we put some audio rate in your audio rate...”

  • Any plans to develop the magic clipboard further.
    I think it would be great to be able to name the clips and then save them into folders building up a library of sorts. Maybe show or hide the midi note view...

  • @audio_DT said:
    How can I use the new automation feature? I can't work it out for the life of me. P.s. I would like to join the chorus of those saying @blueveek should be cashed-up somehow. Maybe an IAP for something, or maybe just a 'tip jar' of varying amounts?

    What automation would you like to record? Do you have a midi controller with pitchbend to test? Or KB-1 app? Just let Atom2 record what you do and it will play back the automation you record. You just can’t see it or edit it. You can delete just the automation though and re-record it (under Patterns)

  • @gusgranite said:

    @audio_DT said:
    How can I use the new automation feature? I can't work it out for the life of me. P.s. I would like to join the chorus of those saying @blueveek should be cashed-up somehow. Maybe an IAP for something, or maybe just a 'tip jar' of varying amounts?

    What automation would you like to record? Do you have a midi controller with pitchbend to test? Or KB-1 app? Just let Atom2 record what you do and it will play back the automation you record. You just can’t see it or edit it. You can delete just the automation though and re-record it (under Patterns)

    Can you not automate CCs yet? I do have KB-1, but I was under the impression it was possible to automated CCs?

  • @audio_DT said:
    How can I use the new automation feature? I can't work it out for the life of me. P.s. I would like to join the chorus of those saying @blueveek should be cashed-up somehow. Maybe an IAP for something, or maybe just a 'tip jar' of varying amounts?

    Yep. I'd really like a tip possibility like in Piano Motifs or something similar.

  • edited May 2021

    @audio_DT said:

    @gusgranite said:

    @audio_DT said:
    How can I use the new automation feature? I can't work it out for the life of me. P.s. I would like to join the chorus of those saying @blueveek should be cashed-up somehow. Maybe an IAP for something, or maybe just a 'tip jar' of varying amounts?

    What automation would you like to record? Do you have a midi controller with pitchbend to test? Or KB-1 app? Just let Atom2 record what you do and it will play back the automation you record. You just can’t see it or edit it. You can delete just the automation though and re-record it (under Patterns)

    Can you not automate CCs yet? I do have KB-1, but I was under the impression it was possible to automated CCs?

    This first update means it only records automation. You can’t draw it in or edit it. YET...

  • @Samu said:

    @blueveek said:

    It's good that you used quotation marks there, because I'm not sure it should necessarily be categorized as a bug – it's one of those situations where it can be reasonably argued that it's up to the host's interpretation what tell AUs when the playhead loops back to 0 (even though it's still playing or looping). It's also possible that without this behavior, some AUs might break and others won't, and that it was added by necessity. My interpretation and wish is that it shouldn't say that it's "stopped", but realistically, it's probably easier for me to work around it than for @LFS to ensure that changing this behavior doesn't break the plethora of other plugins that exist.

    Ok,

    One 'related' thing that bugs the bejeezus out of me is that when using count-in in Cubasis it seems to send 'start/play/whateva' to connected apps/plug-ins before the count-in has actually finished?!
    (Apps that follow playhead are not affected by this but apps/sequencers that rely on the transport running are).

    Seems like Atom 2 is affected by this as well...
    My current solution when using external sequencers is to disable count-in.

    Count-In (Pre-Roll) in AUM works perfectly so this is definitely a Cubasis issue...

    Cubasis seems to be on sale again so maybe this time we'll get an actual update :smiley:

    Cheers!

    Hi samu.
    In regards to the pre-count issue, i did report it and it has been acknowledged by Lars and his team. A fix will surely come but don’t know when.

  • So…. I almost hate to ask as you work so hard. But do you ever see a midi preview option like there is in Helium??

    Thanks for the hard work.

  • @Paa89 said:

    Hi samu.
    In regards to the pre-count issue, i did report it and it has been acknowledged by Lars and his team. A fix will surely come but don’t know when.

    Thanks! It's really driving me nuts...
    For onscreen-keyboard playing I prefer pre-count but when it affects recording sequencers it's a kinda wtf moment.

    I will surely compare the midi-timing between Atom 2 and Cubasis 3 when the Cubasis update drops ;)

    Cheers!

  • @blueveek said:

    Bizarro-experiemental self-oscillating weirdness

    (jump to 0:30)

    Weird ambient tempo drones at 99900bpm

    Cool! would this even be possible to transmit midi notes at audio rate over an external midi cable?

    This was actually the first thing i did when downloading atom2 (though i did not think to go to self oscillating levels), as a test to check for stuck notes, and was so impressed when there were none even at ridiculous speeds.

Sign In or Register to comment.