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.

Patterning 3 LFO velocity modulation question …

flowtillaflowtilla
in General App Discussion

I’ve tried to get the lfo(s) to control the velocity of a pattern so there would be variation in the volume. However each time I add “LFO 1-velocity “ to the parameter layers menu , nothing I draw seems to effect the volume/velocity. Perhaps I’m missing something simple? Any help would be greatly appreciated. Thanks.

Comments

  • eveningjimeveningjim

    What space are you working in? AUM, Loopy Pro, Cubasis, etc?

    I don’t use Patterning specifically, but I have found that using something other than my drum sequencer as a “brain” (or clock, coming from modular mostly, this would’ve something like Pamela’s Pro Workout, but could also be a clock/tempo module).

    Here is theoretically how I would do it in AUM, where I work!

    #Modulating Patterning 3 Tempo with FAC Polyflo (or LFO app)

    If you want to use FAC Polyflo as the "brain" to generate generative or algorithmic tempo shifts and send that to Patterning 3, here are the two most effective ways to route them within AUM.

    **## Method 1: Modulating AUM's Global Tempo **

    In this scenario, AUM acts as the master clock. Since Patterning 3 follows the host, modulating AUM’s tempo shifts everything in sync.

    1. Route Polyflo to AUM Transport:
      • Open the AUM MIDI Matrix (the "toaster" icon).
      • Connect the output of FAC Polyflo to AUM MIDI Control.
    2. Assign CC in AUM:
      • Go to Menu > MIDI Control > Transport.
      • Find the Tempo parameter.
      • Tap it to engage MIDI Learn while Polyflo is sending CC data from one of its FLO(W) processors.
    3. Sync Patterning:
      • Ensure Patterning 3 is in AUv3 mode or has Host Sync/Ableton Link enabled so it follows AUM’s fluctuating BPM.

    **##Method 2: Direct Modulation via MIDI Learn **

    Use this if you want and LFO app (Polyflo) to modulate Patterning 3’s internal clock independently of the host.

    1. Route MIDI in AUM:
      • In the AUM MIDI Matrix, connect the output of FAC Polyflo directly to the Patterning 3 MIDI Input.
    2. Configure Polyflo CC:
      • In Polyflo, select a FLO(W) processor and set its destination to a specific MIDI CC (e.g., CC 20).
    3. Map in Patterning 3:
      • Open the Patterning 3 plugin window.
      • Navigate to Project > MIDI Input.
      • Find the Tempo control (located under Transport/Project settings).
      • Activate MIDI Learn and let Polyflo's signal bind to the parameter.

    It’s also worth noting that if Patterning 3 is receiving a master clock from AUM, direct CC modulation, its internal tempo might be ignored or overridden by the host clock, hence the theoretical callout.

    Method 1 is probably how I would approach it first. Maybe others have more hands on experience with Patterning. Good luck!

  • flowtillaflowtilla

    @eveningjim said:
    What space are you working in? AUM, Loopy Pro, Cubasis, etc?

    I don’t use Patterning specifically, but I have found that using something other than my drum sequencer as a “brain” (or clock, coming from modular mostly, this would’ve something like Pamela’s Pro Workout, but could also be a clock/tempo module).

    Here is theoretically how I would do it in AUM, where I work!

    #Modulating Patterning 3 Tempo with FAC Polyflo (or LFO app)

    If you want to use FAC Polyflo as the "brain" to generate generative or algorithmic tempo shifts and send that to Patterning 3, here are the two most effective ways to route them within AUM.

    **## Method 1: Modulating AUM's Global Tempo **

    In this scenario, AUM acts as the master clock. Since Patterning 3 follows the host, modulating AUM’s tempo shifts everything in sync.

    1. Route Polyflo to AUM Transport:
      • Open the AUM MIDI Matrix (the "toaster" icon).
      • Connect the output of FAC Polyflo to AUM MIDI Control.
    2. Assign CC in AUM:
      • Go to Menu > MIDI Control > Transport.
      • Find the Tempo parameter.
      • Tap it to engage MIDI Learn while Polyflo is sending CC data from one of its FLO(W) processors.
    3. Sync Patterning:
      • Ensure Patterning 3 is in AUv3 mode or has Host Sync/Ableton Link enabled so it follows AUM’s fluctuating BPM.

    **##Method 2: Direct Modulation via MIDI Learn **

    Use this if you want and LFO app (Polyflo) to modulate Patterning 3’s internal clock independently of the host.

    1. Route MIDI in AUM:
      • In the AUM MIDI Matrix, connect the output of FAC Polyflo directly to the Patterning 3 MIDI Input.
    2. Configure Polyflo CC:
      • In Polyflo, select a FLO(W) processor and set its destination to a specific MIDI CC (e.g., CC 20).
    3. Map in Patterning 3:
      • Open the Patterning 3 plugin window.
      • Navigate to Project > MIDI Input.
      • Find the Tempo control (located under Transport/Project settings).
      • Activate MIDI Learn and let Polyflo's signal bind to the parameter.

    It’s also worth noting that if Patterning 3 is receiving a master clock from AUM, direct CC modulation, its internal tempo might be ignored or overridden by the host clock, hence the theoretical callout.

    Method 1 is probably how I would approach it first. Maybe others have more hands on experience with Patterning. Good luck!

    Oh, I appreciate the detailed help, but I was referring to Patterning 3 's INTERNAL LFOs which don't need cc's configured. I thought of doing that as a work around in AUM but it shouldn't be necessary since there 2 built in to the app itself with multiple target destinations.

  • wimwim

    @eveningjim - if you're going to cut and paste AI answers, please have the courtesy to fact check them, or at least assure that they're responsive to the actual question being asked.

  • benkamenbenkamen

    @flowtilla hey! I also saw your message in my email just now, but I'll just respond here!

    The long and short answer is that I intended to implement this feature, didn't get around to it, and apparently forgot to cover my tracks. So it shows up for you as an option but I never wrote the code to actually connect the LFO to velocity. Oops! I promise to get to it. I've been taking a little coding break this month, but I will put it on my list of TODOs for the next update (or the one after that, depending!)

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • eveningjimeveningjim

    @wim said:
    @eveningjim - if you're going to cut and paste AI answers, please have the courtesy to fact check them, or at least assure that they're responsive to the actual question being asked.

    Sure thing boss!

  • eveningjimeveningjim

    Reminds me why I’ve spent so much time away from the loopy pro forum… real inviting crowd.

  • flowtillaflowtilla

    @benkamen said:
    @flowtilla hey! I also saw your message in my email just now, but I'll just respond here!

    The long and short answer is that I intended to implement this feature, didn't get around to it, and apparently forgot to cover my tracks. So it shows up for you as an option but I never wrote the code to actually connect the LFO to velocity. Oops! I promise to get to it. I've been taking a little coding break this month, but I will put it on my list of TODOs for the next update (or the one after that, depending!)

    @benkamen Thanks for responding . I’m thinking it would help it breath like human variation. I would love it as an update someday.

  • wimwim
    edited December 2025

    @eveningjim said:
    Reminds me why I’ve spent so much time away from the loopy pro forum… real inviting crowd.

    You're right. That was overly harsh and none of my business. Sorry about that.

    If it had just been a matter of misreading the question, no way would I have said anything other than "Sorry, I think you misunderstood the question." Or just have ignored it altogether. Just because the answer was AI produced (or seemed so) was no excuse to act any differently.

  • eveningjimeveningjim

    @wim said:

    @eveningjim said:
    Reminds me why I’ve spent so much time away from the loopy pro forum… real inviting crowd.

    You're right. That was overly harsh and none of my business. Sorry about that.

    If it had just been a matter of misreading the question, no way would I have said anything other than "Sorry, I think you misunderstood the question." Or just have ignored it altogether. Just because the answer was AI produced (or seemed so) was no excuse to act any differently.

    I appreciate that reply. This was not AI generated, but was AI assisted and edited, as I was trying to make it take my specific process and apply it to something else. But clearly should have been better read on my part.

    The crux of my answer was trying to explain how I use an LFO to clock utility (plugin) to manipulate clock/tempo much like I would in modular. No other answers at the time, so I was just trying to be helpful.

    Still probably best I not give potentially confusing answers that feel off topic.

Sign In or Register to comment.