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.
AUM and pedalboard-like presets?
Have any of you succedeed in doing this? WITHOUT loading a whole new aum file?
Example
Preset a: has overdrive, Tonex on preset a, delay_
Preset b: has compressor, tonex on preset b and reverb
Preset C: no tonex, just reverb and volume boost
And so on
I thought "bus are the way", but i did not find a way to activate something AND deactivate something else with the same program or control change
Any ideas?
Comments
Use a script to implement the logic. Send the script output to MIDI Control, and use it to solo the different channels. Check Patchstorage for suitable Mozaic scripts.
Hey Uncledave, you mean
if i press PC0, it translate to cc0 cc1 cc2 and cc3?
Is that right? Which kind of script should i search for?
If this is your question, you need Mozaic first, as a plugin in AUM.
https://apps.apple.com/us/app/mozaic-plugin-workshop/id1457962653
And then you need to code a simple script that transforms a single incoming midi message into messages to multiple destinations. It is more easy than is looks like, and on patch storage there are a lot of examples.
https://patchstorage.com/platform/mozaic/
I got this, but, for example: how would you implement the bypass on/off feature?
Example: i have 1 channel strip, with 3 sends.
first preset would be "overdrive engaged, chorus engaged, reverb unengaged".
Second would be "od engaged, chorus unengaged, reverb engaged".
Third something else.
The only command i am aware of in AUM is "bypass". That cycles trough active and off.
If i use Bypass, and try to move from a preset with reverb on to another one with reverb off, it will mess up and invert.
How would you deal with this?
Maybe you can create 3 channels in AUM, clones of each other.
And you dial in your preset om each channel.
With Mozaic you build a switch that mutes (or set volume to zero) of AUM channel B+C, A+C, or A+B, and unmutes A, B, C at the same time. You can mute output of the separate channels, or mute the input if you use a bus for this.
So with this you have 3 presets.
I say "maybe", I have not checked this myself.
This could be an option but it would need to
have multiple sessions open maybe, but using buses would be doable.
The problem would be: how do i mute/unmute AND maybe switch plugin preset?
This is quite tough to do. Looks like it really needs to be addressed from AUM creator in a native way!
You would set Mozaic up so that Mozaic listens for some particular midi event to to recall a pedalboard setup and sends out midi to AUM’s midi control to set things up as you want.
My great problem is that Bypass is triggered by an event, right? Well, i have no possibility to switch ON with cc1 and switch OFF with cc2 (for example).
There is a logical problem here. If i have plenty of snapshots, if i ask to switch on a chorus that was already on, it will switch OFF instead!
This is the biggest problem.
I don’t understand. You don’t need a different cc# for on and off.
Yes i do.
Simple scenario.
I have 3 preset. preset a with chorus on, preset b with chorus on, preset c with chorus off
I am on preset C. So chorus off.
I choose preset A, so i send Bypass to the chorus to engage it.
Then choose preset B. I send Bypass again (cause it needs chorus on), and instead of engaging, it disengages it (cause there is just one Bypass command in AUM)! It should do nothing instead.
Got it?
Can you show a screenshot of the MIDI Control setup for your chorus? You might have it setup to Cycle mode
The problem lies right there, in fact.
If i cycle that, the "switch on" command for preset A will switch chorus on.
But if i hit preset A again, or switch to preset B for example (that switches chorus on aswell), the "chorus on" command will switch chorus OFF instead
If there was an "effect on" and "effect off" command in AUM, it would have been possible. But there is only Bypass (for as far as i know!)
Maybe I don’t understand how you have set things up.
I just tested and if I have a cc mapped to bypass and cycle is off, sending 127 will turn bypass on regardless of the previous state and sending 0 will turn bypass off.
GREAT! THIS WAS THE MISSING BIT!
"I just tested and if I have a cc mapped to bypass and cycle is off, sending 127 will turn bypass on regardless of the previous state and sending 0 will turn bypass off."
I am used to use program changes as "standalones", never thought of CC.
So in AUM 0 to 63 turns effect off and 64 to 127 on!
Will try with Mozaik now (this is unfortunately not as simple as it looks for me), cause this involves a lot of scripting.
Do you think the extra expensive Midi Designer could help me in this in a more streamlined way?
Here is a video demonstration:
Btw, if you don’t want to use Mozaic or Streambyter as your go-between to set up presets , there is a new plugin that may work for you:
https://forum.audiob.us/discussion/55160/midi-messenger-new-free-app#latest
Lovely, really
People like you make internet a better place!
Last question, i swear. I guess i got the nested if statement. You defined constant at the top
@OnPadDown
if LastPad = 0
SendMIDICC midichan, bypassCC, on
elseif lastpad= 1
SendMIDICC midichan, bypassCC, on
elseif lastpad= 2
SendMIDICC midichan, bypassCC, off
endif
@End
is fine. but is writing this way
if LastPad = 0
SendMIDICC 01, 20, 127
SendMIDICC 01, 19, 127
SendMIDICC 01, 21, 0
SendMIDICC 01, 23, 127
SendMIDICC 01, 24, 0
fine too?
In this example, i would like to send 5 different midi cc, all of them on channel 1. 19 20 and 23 activate the bypass, 21 and 24 deactivate.
Am i right?
(as i re-read: it is better to use constant, as u did, to have better readability. But is the "multi message" syntax right?)
@steponme : you can send however many CCs you want for each case. I was just sending one to demonstrate that you only need one CC per bypass that you need and that it won't matter what the state is.
The syntax is right. I set it up to be triggered by pad touches, but you could also set it up in a midi receive block to trigger the presets based on Mozaic receiving a MIDI event from your pedal board.
You don't need to use constants (they are really variable being used as constants) but I find that it makes things more readable and easier to change. for example if you change the CC# that you want to use for something, you only have to do it in one place.
Cool. I think i will use the 16 pads layout in Mozaik and just use the "learn" feature, to control those pads with a ultra cheap Mvave Chocolate
Thanks buddy, a group of guitarist will love this. Should i have the time to do a video, i will undoubtfully credit you!
Just for future readers. The easiest (but most expensive way) is Midi Designer App, that has presets built in