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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
After enter into edit mode, tap on fader and go into “value change”, then find your target and parameter.
For the slider add an action. There are parameter change actions . Choose that action. The action includes a target where you choose the AU and parameter.
I know this is different subject than originally started, and I feel not comfortable to expand this more, but still I don’t fully understand so, can ‘I try last question and I maybe ‘I will understand final conclusion?
Yes, auv3 should be not able to see core midi, but fortunately they see, and we have great support for controllers in atom2, LK, and also LoopyPro indeed allow to send via core midi outside from auv3.
So LoopyPro has access to this ports.
Question is can be LoopyPro controlled by launchpad in auv3 mode or not yet.
In LK we can disable this or enable. I like to have this in LoopyPro also. Please simple answer and I will live with what is possible now.
When Loopy is running as an AU, it does not look for control devices. So, the automated device mapping that happens when it is a host doesn’t happen.
I have no idea if adding this is planned. You might want to create a topic for this or add the suggestion to the Loopy Road Map page.
Thanks, I got that far, and can choose fundamental as a target, but can’t actually see any of fundamental’s parameters. I can send out ccs on various channels but what am I sending them to? How do I see fundamental’s exposed parameters in loopy? This part I don’t get yet
Thank you.
About controlling parameters of synths, I appreciate work Janosax did, but look Gravitas, he is playing live, and this is most important, rest is background. So when needed he call gui screen of instrument, controller, effect and dial directly. No too much mapping , even if possible. Maybe it is solution to have so many options and not be under pression to constantly map everything in constantly changing setup like ours?
Of course it is good to have full 10cm motorfader 14bit for any auv3 parameter…. Or not. How mobile is this setup then?
Oh never mind, I think I found the way now, thnx
https://roadmap.loopypro.com/improvements/p/support-launchpad-automap-under-auv3 @Michael thanks is advance!
Definitely the best option I found so far, but have not yet been able to get the very, very fine control I’m looking for in manipulating the low frequencies. Even using a huge knob and even adjusting the cc range to, say, just the lower half. Still, it’s enough to let me see already that I definitely need to look into using loopy as a host more 👍👍
Don’t do this with cc’s.
This has nothing to do with cc’s or midi
Well if I drastically adjust the range I can get control over those very low frequencies. Pretty cool
This is exactly what I did. Yes I shouldn’t have called it cc range. Just ‘range’. Thnx
This probably has to do with how the AU scales the parameter values. It might not use linear scaling.
Ultimately still getting better control from just using the knobs in fundamental itself though. Even limiting range to something like just 0-0.05. I’m sure for most cases though these loopy sliders etc will work very well
Thanks for honest information.
Just to check - if I had midi designer pro 2 (which can send 14-bit midi / nrpn), I would need to host fundamental 2 in apematrix if I wanted to send those nrpn messages to fundamental, right? Because AUM can’t receive nrpn, and fundamental standalone has no midi learn, so no way to access the parameters. Is that correct? Also, I saw that tc-data can apparently send 14-bit midi, but there is actually no mention of it in the manual. Can anyone confirm either way? Cheers
That’s weird, it should be doing that! I will investigate
Thank you, and If I good remember, earlier this works! I mean, probably (but for sure error is on my side) something was broken with one of updates, I think about 3 months ago…. My mistake that I didnt ask about this then. I hope it will be easy to fix, and not time consuming.
Works perfectly controlling osc freq of auGENx 🤷♂️
My guess, AuGenX accounts for the scaling of the parameter change values and Fundamental doesn’t.
I think the issue arises from the fact that the function in fundamental’s oscillators seems to be exponential.
@Michael : does Loopy Pro look at the AU flag : kAudioUnitParameterFlag_DisplayLogarithmic ? I wonder if the Gavinski mentioned up-thread about Fundamental's frequency control is Fundamental not setting that flag or Loopy not taking it into account.
It does. That doesn't necessarily mean there isn't a bug there though...
Normally, osc frequency adjustment is logarithmic: equal steps in the control produce equal multiples in the frequency value. So, for example, each octave (factor of 2) covers the same distance on the control. I don't have fundamental, but I suspect the problem is that the frequency scale is linear. That means the control distance from 50 to 100 Hz is the same as the distance from 10,000 Hz to 10,050 Hz. It makes 10,000 Hz the middle of the control range, so the last octave covers half the range, and the first octave is miniscule.
It is possible that Fundamental does not set the flag that lets hosts know the control values should be logarithmic. (See my question to Michael a post or two up).
Exactly. I was about to say the same thing. Or perhaps Loopy Pro does not implement it.
I ran into this some years ago with Audiobus and the filter cutoff in the Viking synth. At that time, Michael remarked that he had not implemented the log scaling option for AUv3 parameters. I just checked that scenario, and it's still not implemented in Audiobus.
Do you know for sure that Viking sets the flag that lets the host know to use logarithmic response? @Michael: i have no idea if viking sets the flag, but i can confirm that in Loopy if one makes Viking's filter cutoff the target of a slider that things are wonkie. I have no idea if Viking isn't setting the flag or Loopy isn't scaling right.
This was totally my fault – I messed up the param curve. Fix is forthcoming.
Yep, I broke it in a recent update! Fix is on its way.
Fundamental works like this - it gives very fine control over the lowest frequencies and less so over higher frequencies. So for example moving the knob up from 1 Hz to its mid point (12 o’clock) takes it to about 1500 hz. The final 50% of rotation of the knob covers the area between 1500 and 15000 Hz, so it is definitely not linear.
I think the issue arises from the fact that the function in fundamental’s oscillators seems to be exponential. > @uncledave said: