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.

An experiment: Loopy Pro automation through DC biased audio clips

edited March 2 in Loopy Pro

As far as I know parameter automation has not been implemented into Loopy Pro - yet. This is a way how parameters can be automated with a workaround:
As far as I can see, all audio is routed DC coupled in Loopy Pro. This means that it is possible to store non or slowly changing parameter values inside the audio clips. This solution uses a Drambo module to convert MIDI CC messages, that can come from a widget or an external controller into an audio signal that is recorded into the clip. On playback the same module is converting audio back to MIDI CC messages that can be used to trigger actions in LoopyPro.
One big advantage of this method is that the automation curve is visible on the Doughnut.
WARNING and DISCLAIMER: I take no responsibility for people frying their gear by sending these heavily DC biased signals to their audio interface.
A ZIP containing both a LoopyPro and a Drambo Project can be found on Patchstorage:
https://patchstorage.com/loopy-pro-parameter-automation-with-drambo/

Comments

  • @catherder said:

    As far as I know parameter automation has not been implemented into Loopy Pro - yet. This is a way how parameters can be automated with a workaround:
    As far as I can see, all audio is routed DC coupled in Loopy Pro. This means that it is possible to store non or slowly changing parameter values inside the audio clips. This solution uses a Drambo module to convert MIDI CC messages, that can come from a widget or an external controller into an audio signal that is recorded into the clip. On playback the same module is converting audio back to MIDI CC messages that can be used to trigger actions in LoopyPro.
    One big advantage of this method is that the automation curve is visible on the Doughnut.
    WARNING and DISCLAIMER: I take no responsibility for people frying their gear by sending these heavily DC biased signals to their audio interface.
    A ZIP containing both a LoopyPro and a Drambo Project can be found on Patchstorage:
    https://patchstorage.com/loopy-pro-parameter-automation-with-drambo/

    You would need to convert the audio to cc. Loopy has an amplitude follow action that can map clip amplitude directly.

  • @espiegel123 said:

    @catherder said:

    As far as I know parameter automation has not been implemented into Loopy Pro - yet. This is a way how parameters can be automated with a workaround:
    As far as I can see, all audio is routed DC coupled in Loopy Pro. This means that it is possible to store non or slowly changing parameter values inside the audio clips. This solution uses a Drambo module to convert MIDI CC messages, that can come from a widget or an external controller into an audio signal that is recorded into the clip. On playback the same module is converting audio back to MIDI CC messages that can be used to trigger actions in LoopyPro.
    One big advantage of this method is that the automation curve is visible on the Doughnut.
    WARNING and DISCLAIMER: I take no responsibility for people frying their gear by sending these heavily DC biased signals to their audio interface.
    A ZIP containing both a LoopyPro and a Drambo Project can be found on Patchstorage:
    https://patchstorage.com/loopy-pro-parameter-automation-with-drambo/

    You would need to convert the audio to cc. Loopy has an amplitude follow action that can map clip amplitude directly.

    Thanks for the suggestion. That works too. I only notice that the values are translated differently. In my test the “drambo translated” slider moves at a consistent speed but the one controlled by the envelope following action in a more exponential accelerate / decelerate manner.

Sign In or Register to comment.