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.

Dear AUv3 plugin devs, please make parameters/values/units open for DAWs like AUM and Loopy Pro

What about following idea?
A website would be good: put a list of all currently available AUv3 plugins and show status of these have already access to inbuilt parameter integration* or not.

*function name, parameter, value, unit

I think this would give a more professional / serious touch for iOS/iPadOS DAWs and give more attention by plugin devs to make parts of their API open for DAW devs.

And I assume this would help also innovative makers of cool MIDI Controllers like from Intech Studio, PirateMIDI, Electra One, etc.

Something like https://isapplesiliconready.com/ but for AUv3 plugins. Instead of "IsAppleSiliconReady" maybe something like "IsAUv3openAPIready" or similar.

This website would just boost plugin selling for devs I believe. And some other plugin devs (which have not implemented open inbuilt parameter integration yet) will see: „Ah!, some other devs already doing this! I think I will work on this too.“

To have full access to function name, parameter, value, unit would help making AUM and Loopy Pro more professional. That would mean that canvas elements like fader and knobs (AUM and Loopy Pro are working on that) would not have inaccurate and vague feeling of moving them. No longer profane 0-100 or 0-127 (MIDI) but full 32-bit parameter values and its units. I mean, just look over what the newer TouchOSC version can do. And for very long time some users also using Lemur. Next level now. So users can see exactly what parameter value and unit they are dialing in.

What do you think about?
Just an idea.

Comments

  • I think this is a pretty great idea, especially when I think about the times I've bought a nice synth only to discover I can't control it inside NS2 automations.

  • It would be nice for parameters to always be exposed with well defined units and sensible ranges, but it's been more than two decades that I've been thinking that and there's still a ton of plugins being written with parameter ranges of 0-127 or 0-1 with no units. I think there are a couple of reasons for this. One is that lots of plugins are written with cross platform libraries that don't emphasize clean useful parameter ranges and units (or responses like linear, log, exponential, etc.). The other is that there is still a MIDI mentality. That feeds into the first reason.

    As a note, there are two different things in the AU that are related to what you are asking for. The first in the way an AU defines and configures its parameters in the parameter tree. This is where the things like the names, ranges, units, and responses are configured. The second is a function that the host can call on the AU called parametersForOverview(withCount count: Int) This is where the AU tells the host what the parameters are that the host might want to directly expose to the user. I'm pretty sure that this is where AUM determines which parameter to use on the knob next to the AU node for example.

    Another thing to consider is that an AU can mark a parameter as something that shouldn't be exposed by the host directly as a writable by the user. There are some parameters where having a direct potentiometer like control over them will break the algorithm. So, it is valid to not always expose a parameter for automation or direct control.

Sign In or Register to comment.