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
It is. It works well with the included midi fx such as modulate. You can take one LFO and map it to multiple parameters across different plugins. This makes it useful even if your synth of choice has a mod matrix already. Also it means you can reuse your mapping in any patch for the VI instead of you having to redo your work for each patch you want it to work on.
I’m finding uses for it even without an external controller. You can even for example draw the controller data into the region in the piano roll editor — or have it p-lock style from the pattern editor — and transform it from there to multiple parameters and multiple plugins.
And you can have multiple scripters on each channel. It’s up to you to ensure they’d don’t clash with each other though :-)
Yeah, it's super lightweight and flexible. Better than the workaround of Max devices I use in Ableton which bog down the CPU.
Updated the demo project in the OP to include an instance of Alchemy that has the performance pad X and Y parameters pre-mapped.
It's not possible to select "Y" as a target on the iPad otherwise.
Let me know if you find it useful :-)
Thanks a lot!
You’re a great person!
Aw shucks... Thanks :-)
This is great, thanks for sharing. Maybe I’m missing something, but why can’t I use MIDI Learn on the controllers/inputs section? I am only seeing that option for the targets. Doesn’t it make more sense to open up an input slot, turn a MIDI knob on the controller, and set the target using the Logic UI?
This got buried so fast, so much activity lately. @klownshed am I just misunderstanding how to use your plugin?
Cool stuff, I didn’t even know Logic on IOS did scripting.
It shows I have much to learn about being a bit more efficient with controller setups.. not having to redo it every project etc.
I will give it a try later, thanks!
So I have a AKAI MPD with 4 banks of midi values for its 8 knobs…
i change..
Line 24: var TOTAL_TARGETS = 8
To..
Line 24: var TOTAL_TARGETS = 32
With logical memorable use, a bank for ADSR, a bank for OSC pitches amd shapes. Abank for filter control and a bank for LFO control… save a chain setup for each favourite synth and im cooking on gas!
Thanks for this! Has anyone been able to get it working with Turnado? It won’t learn midi parameters, if I assign the target to cc1, cc2 etc (the default Turnado midi) some work and some don’t. In fact, the Turnado midi only really seems to work in AUM, it doesn’t work in Logic or Loopy so I’m wondering if it’s the app itself. Is anybody able to test it?
Not in the use case I made it for. I have a little controller with 8 knobs that go from CC12 up and I don't keep changing the MIDI ins. Also I use it to map things like Rozeta LFO and that works pretty well as is.
The target mode needs to be how it is; Without this built in method you couldn't choose different parameters from different plug-ins within the channel.
There is code in the script to enable MIDI learn. I had it working fine with one source/target pair but it wasn't worth the scripting effort for me to expand it to work reliably with multiple source/target pairs as I always tend to use the same CC inputs anyway.
So yeah. I built it this way is this is the way I wanted it to work. It's just a free script I shared. It doesn't come with support
Turnado doesn't work, no. Sugarbytes don't appear to have implemented the assignments in auv3s.
It doesn't appear to respond to normal CC values either. The main knobs are assigned CC1-8 per default but they don't respond to MIDI as far as I can tell.
Tornado Automation works if you choose specific parameters, but automating CC values doesn't.
Also, it doesn't respond to automation writing from the UI (i.e. set to "Touch" or "Latch" it won't write automation data from the Tornado UI).
TLDR I think Tornado needs an update to work fully in Logic. Manually drawing in automation is a workaround.
Thanks so much for the info! It’s pretty disappointing and I hope @sugarbytes update their app.
Specific reason you want to us Turnado? Since Logic has build-in multiFX. StepFX and PhatFX are particularly nice. Both include XY pad and more.
You can set up the MIDI script to control both StepFX and PhatFX from the same MIDI controller (hardware or virtual)... Map a couple of knobs to XY pads in each plugin with different Min/Max (invert them to make one go the other way) for some OTT fx or be more subtle and have one controller turn up the saturation on phat FX whilst controlling a different parameter in Step FX at the same time.
Just what I’m used to! I’ll try Logic’s effects, thanks!
I’m guessing midi scripter is a Logic Pro only tool?
Yes, it's basically a JavaScript container that can be used in Logic.
Pretty awesome. I wonder if there are more scripts like this.
Super lightweight compared to stuff like Max for Live.
Hey this is really cool. Thanks for making this and continuing to work on it.
@klownshed thank you for making available your controller mapper script. I’m trying to set it up using MIDI velocity to control AU parameters down the line but it seems unresponsive (while it is responsive/works with CC1 for instance). Do I have to do something extra for velocity?
It does work, use the preset “Map Controllers”. The other cc to Param 4 might not work, I think I had that set to filter the inputs to avoid them being used elsewhere, which is ok for cc but not velocity. The Map Controllers preset passes velocity through. It does work. I’ve just tested it.
Thank you! I used one of the other mapper scripters and it’s working now!
Cool. The other ones are useful when you don’t want the cc controller you’re using to be passed on down the chain, but for 99% of the time the main ‘Map Controllers’ script is the one to use.
Hmmm that one does not seem to be in the project I downloaded from this thread…
@pruddo — Try this
Still so awesome @klownshed thanks man
Super!
I just tried this out and it’s a stellar work. Works perfectly with my Kory nano studio keys. You just need to add a midi monitor to see what CC the knobs are sending and assign on the inputs. Very easy and intuitive . Thanks @klownshed 🙌
It does make you wonder. Why are we missing this crucial functionality in Logic?. We have to resort to some hacky workaround when there’s obviously no technical impediment to implement controller mapping.
It’s a similar case to the hack I employ to modulate FX on an audio track (using a dummy instrument track with sidechain, since audio tracks can’t host midi FX)…. Things that are perfectly doable but have no direct or UI access to.
Controller support in the Mac version is really good so hopefully things will improve on iPad. Coincidentally, I made this script originally to use on the Mac as it made it easy to load up a pre-configured instrument and I also often wanted one controller to control multiple targets which this script lets me do.
There's a hack you can use to use midi and pattern regions in an audio track to modulate audio fx. you won't be able to use midi fx in the track but you can send midi. I use it to automate fx using the pattern editor, p-lock style and it's great for that.
To do that, you need to make additional tracks that point to the same instrument, which (obviously) requires a tacky workaround! To do that, first duplicate (or make) a midi region that has 2 or 3 note pitches in it and drag it to an empty area of your audio track. Logic will try and tell you you can't do that, but it work. Then select Convert->Split by Note Pitches and you have multiple audio tracks that all point to the same track. Delete all the midi regions.
Now, create a new Pattern region in a midi track and drag that into one of the new empty audio track lanes. You can add rows that automate anything in the plug-in chain. If you se the Automation mode of the row to "Latch" you get parameter lock style stepped automation, but you can also set it to "Slide" and it will then smooth out the transitions so you can put steps in to get a nice curve (i.e. if you want to go from 0 to 127 but curve slower over the first part, put a step in at step 1 at 0, another at say step 16 at 127 then you can put a step in at say 13 at 50 and it will ramp from 0-50 over the first 13 steps then from 50 to 127 over the last three).
It takes an extra couple of steps but it's awesome having pattern region fx automation on an audio track.
If you want to use LFOs to modulate fx you can do it but you'd have to write the data first into a midi region (just record the output of a MIDI LFO and drag that into the free audio lane).
The cool thing about automating using regions is you can copy/paste them, loop them etc. for all sorts of cool modulations.
For example, make midi region that's one bar long. Use region automation and draw in curves that modulate the volume like a fake sidechain. Then drag that into your free audio track lane and loop it and you have instant sidechain fx just using volume. You can also obviously automate anything like that. Being able to drag the midi regions into an audio track makes it far more convenient for looping fx.
This example shows a MIDI pattern region on an otherwise empty audio track that is effectively the same audio track as the lane above it. The MIDI region is automating delay feedback on an audio track using the pattern editor.
This is crazy powerful stuff when you get your head around it and can be like Elektron on steroids.
@klownshed Thanks for these tips and explanations.