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.

AU Parameter Change Recording - Question for Devs

espiegel123espiegel123
in General App Discussion

Recently, there was a discussion (elsewhere) in which a developer of an audio and midi recording app explained why AU parameters can't be recorded in their app if an AUv3 isn't reporting touch start and stop information. Without the information, they said that they would have to be constantly recording the state of every parameter whether changed or not.

My question is this: is that true? Cubasis seems to do a pretty good job of recording AU parameter changes with its automation recording.

I was wondering if devs of AUv3 can share some insights. Are there OS calls that allow AU parameter changes to be detected if the AU doesn't share touch information?

@j_liljedahl @brambos

Comments

  • brambosbrambos
    edited January 2020

    As far as I know this isn't true. None of my plugins report start/stop and their parameters are recorded nicely in most hosts.

    I think the start/stop notification from the GUI is a bit of a hack. A plugin could technically change its parameters without requiring interaction with the GUI (e.g. Mozaic can do that).

    The right way to do it is to install KVO (key-value-observers) on the Parameter Tree of the plugin, so the host will get notified when changes occur. No need to constantly record the state of every parameter.

  • espiegel123espiegel123

    @brambos said:
    As far as I know this isn't true. None of my plugins report start/stop and their parameters are recorded nicely in most hosts.

    I think the start/stop notification from the GUI is a bit of a hack. A plugin could technically change its parameters without requiring interaction with the GUI (e.g. Mozaic can do that).

    The right way to do it is to install KVO (key-value-observers) on the Parameter Tree of the plugin, so the host will get notified when changes occur. No need to constantly record the state of every parameter.

    Thanks, Bram!

Sign In or Register to comment.