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.
App to filter MIDI CC messages to morph gradually, at a chosen speed
Imagine turning a knob that doesn't instantaneously change the filter cutoff (or any chosen CC parameter), but instead slowly opens or closes the filter until it hits the target value, at a specific speed set by the user (user definable, and controlling the speed of movement, not the amount of time). A kind of "smoothing" that allows for extremely slow changes. I'm after an app that can do this, a kind of MIDI filter, so that I can use a physical controller, and send the resultant "smoothed" CC values to external gear - in my case to control various parameters of an Octatrack.
Another example: I move the "volume fader" of a track down to silence, but because I've chosen a very slow speed, the track's volume takes 10 or so seconds to fade out, leaving my hands free to do something else while playing live.
I used to be able to set this up using FL Studio's internal XY controller object, but I don't want a laptop to be involved. Just wondering if there's an app that already allows for this.
Ideally I'd like to be able to do it without using Lemur or scripting.
Alternatively, I'm also interested in apps that allow for CC changes using physics objects, momentum, stuff like that.
Any help appreciated!
Comments
I could easily make you a Mozaic script that does that. Sounds useful.
When you say "momentum", do you mean outputting the current velocity of your CC change, rather than the position? TC-Data does that, and I have a mostly-finished Mozaic script that also does that.
Physicles and TC-Data would be two apps to look into, in terms of physics objects and momentum respectively.
Here’s one designed to do just that. It was made specifically with the iRig BlueBoard in mind, but doesn’t care what is sending it MIDI.
https://patchstorage.com/blueboard-switch-ramper/
By default it responds to CC 20, 21, 22, and 23. In the alternate “notes” mode, it reacts to notes 60, 62, 64, and 65 (C, D, E, F). These default inputs can be easily edited in the first section of code without any real programming experience.
Output CC’s default to 20, 21, 22, and 23 but can be changed from the UI without any programming.
BLUEBOARD SWITCH RAMPER v1.1
Responds to triggers from iRig BlueBoard, sending cc values out over a configurable ramp time. The two standard BlueBoard modes are supported: Mode 1 (Notes) and Mode 2 (CC’s), as selected by the bottom-right knob in Trigger Mode.
Toggle between Trigger and Settings mode by tapping the SHIFT button.
In Trigger mode, tapping the pads is the same as tapping the correspoinding BlueBoard button. The first tap will start sending from the Start value to the End value at the Ramp speed set for the pad. The A, B, C, and D knobs will turn to show the progress. The next tap will reverse the direction of travel. If a tap comes in before the end of the end point is reached, travel immediately reverses without reaching the end point. (Also, see “Looping” below.)
In Settings Mode first tap a swith to select it, then you can adjust the starting and ending limits for the cc values sent out for that switch. Ramp adjusts the time it takes to go from start to end. You can also set the outbound CC# and channel number here if needed.
Looping: In Settings mode, the bottom-right knob allows enabling Looping for the switch. If turned on, tapping a switch toggles looping on and off. The values will ramp up and down like an LFO until the next tap turns the looping off. Looping is disabled when Ramp time is zero. (See TIPs below.)
TIP: To bypass the plugin and send the BlueBoard messages to another app, set the bottom-right knob to the opposite of the mode the BlueBoard is running.
TIP: If you set Ramp to zero it makes the switch behave as a toggle. Normally the BlueBoard sends ON when the switch is pressed down and OFF when the switch is released. But with Ramp at zero each press with toggle between ON and OFF.
Credit for this script idea goes to @rcf on the AudioBus Forum.👍😎👏
I think it's worth having a dedicated script, without the trigger mechanism, so I created one that fits the "Imagine a knob..." aspect. But I like the BlueBoard script, and I'm sure I'll have a need for both at some point.
I called my script "CC Gradual Glide".
Edit: I totally forgot to add the MIDI input component. I'll fix it today/tomorrow, but for now, you can still connect your MIDI controller's outputs to Mozaic's knobs using AUM, so it is usable.
https://patchstorage.com/cc-gradual-glide/
"When CC Gradual Glide is placed between a MIDI input and a MIDI output, CC values will always change at a consistent pace, gradually moving toward the position you set.
Use the Channel I/O and CC I/O pads to access menus for editing Channel and CC inputs and outputs. When you’re finished setting up, tap the “Performance” pad.
In the performance menu, use the bottom right on-screen knob labeled “All” to set one speed for all four CC messages. Use the top right knob, labeled “[Cur] Speed” to change the top four knobs between showing the current CC value, and allowing you to set an individual speed for each of the CC messages.
Look near the top of the code, and you’ll see the SpeedRange and Interval variables. You can edit these if you’d like.
Set a lower number for SpeedRange to increase the maximum speed. Set a higher number to decrease it.
“Interval” affects how many times per second the current value is changed, and a new CC value is sent. Default is 20 times per second."
@handed If you have any suggestions regarding the layout or functionality, let me know.
Here's a screenshot:
Thanks @Skyblazer and @wim ... Plenty to investigate here. Trying to wrap my head around the Blueboard script. Thanks @rcf too. And @Skyblazer , thanks so much for cooking up the Mozaic script! Awesome that you set it up to allow separate speeds for separate CC values. Planning to check it out in practice soon. Really appreciate you going to the effort - hope it’s useful or inspiring to you as well.
Here’s the FL studio XY pad UI for reference - it’s hooked up to two values at once (X and Y obviously) per instance.
The bottom left “speed” is the relevant one. Looks like they’ve added acceleration and some advanced joystick controls since the early FL Studio I used all the way back then.
I used to have a screen full of these, maybe 10-12 instances, controlling a whole boatload of parameters, with the “level” for each parameter linked to a hardware controller. Great for slow, evolving performances with loads of parameters moving at once.
I looked at TC-Data and Physicle - not exactly what I’m after, but they both look very powerful, particularly TC-Data. Curious to know what else I might use it for...
@handed Ah, okay, I think I see how it works. I didn't see any YouTube videos on it, though I'm sure there's info on it somewhere. I can make an XY version, more similar to the inspiration. (And yes, technically, you could route any other XY pad to Mozaic's knobs to get the same effect with the current version.) Glad you like it so far.
I already had a rudimentary "proof-of-concept" version in my stash of unreleased scripts, so I was definitely planning to use it at some point. "Slow, evolving performances with loads of parameters moving at once" are exactly what I like to make, and I also usually do have a bunch of XY pads on the screen, rather than physical knobs connected. So if you come up with any other ideas involving XY pads and CCs, I'm always interested. And if you come up with an idea involving physics objects that works with Mozaic's minimal UI, I'd love to try making something like that.
So, the Level knob. Let's say the Level knob is set to 27, the Min is at 0, and the Max is at 127. Then it outputs values from 27 to 100? And when Level is set to its maximum, the full range of 0-127 is used? With the Level knob at its minimum, the coordinates are always (64, 64)?
In terms of the newer, potentially less essential features...do you know what they do? Maybe I'll feel like adding those at some point.
I guess "Tension" would maybe cause it to move more slowly at the beginning and end of the path? Acceleration would cause it to move more slowly at the beginning, and reach the "Speed" at the end? And the joystick...maybe the cursor returns to the middle when you release the mouse button, and the XY pad then changes the speed, making the the destination value determined by the "Max" and "Min" knobs rather than cursor position?
@Skyblazer Finally got a moment free and I’m testing your patch now. Thanks again! I’ll be in touch again soon.
@Skyblazer Thanks again - I have sent you a PM.