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
I have an MPK mini and it has these pressure sensitive tabs. They send a continuous pressure signal. (Is that what they call aftertouch?) The 8 pads of Mononoke are automatically mapped to the 8 drum pads on the controller. So far so good. Any way I can use the pressure signal of the controller's pads to modulate the volume of the pad I'm pressing? Analogous to moving the finger up and down on the touchscreen pad?
I was thinking if I can use the pad pressure signal to control volume and the 8 knobs on the MPK to control the pitch of the 8 voices, I'd have full control transferred to the MPK and one person could play mononoke while another person is doing other stuff on the touchscreen...
Also, something odd happens when you press a pad on the controller and use pitch shift. It doesn't shift the pitch like you'd expect it to but it instantly makes the active pad an octave (or so) lower, and it stays that way as long as you keep the pad pressed. No matter in which direction you move the pitch shift.
@dobbs If you mean that little Akai MPk controller, I don’t think the pads will do what you want. They send a single velocity value per hit, but not a continuously changing Aftertouch data stream.
You would have to repeatedly hit the pad to simulate Aftertouch, but then you get all the unwanted note/off messages.
As far as the pitch/mod stick goes, it is programmable if you have access to a computer and download the Akai utility. My guess is the stick might be programmed weirdly to get that octave drop you describe.
I have the MPK mkii. If you have the newer one (mkiii), maybe it has Aftertouch on the pads. If it does, it seems like you might still need to check the setup using a computer and that Akai utility. You could also try Midi monitoring the controller on iOS, but the Akai utility is so much easier if you have access to it.
The specs on the MPK mk3 list the pads as "velocity and pressure sensitive," but what that means specifically isn’t clear from the online info.
It's the MPK mini MK3. It sends a NOTE ON with velocity info and then a continuous stream of signals labelled PRESSURE, I see it in midispy. But Mononoke only reacts to the NOTE ON velocity but not the pressure signal. Any way I can maybe rewire this with something like MIDIflow to react to the pressure?
The pitch bend does exactly what it's supposed to do in every other synth. In midispy I see the signal labelled as PITCHBEND. Only in mononoke it creates this sudden drop. Which in itself is kind of a cool feature as the sudden drop creates some weird resonance/noises as well
@dobbs That sounds like one could re-map the pressure data stream to the CC needed by Mononoke - could have a look with MidiSpy what kind of midi event is send exactly ?
Regarding the PitchBend, in MidiSpy can you have a look at the exact bend values send by the device ? I suspect that perhaps a quite low value is send (center is 8192, min is zero, max is 16383) and other synth only bend by 1 or 2 semitones, while Mononoke probabbly bends 2 octactes like MPE. If its the case that maybe PB value of zero is send, then the conversion script would just need to ‚rescale‘ the pitchbend value.
Ohhh duhhh, i completely forgot that mononoke has midi out, I can just record the mononoke output and look at it.... why didn't i think of that sooner...
Pitchbend from the AKAI sends signals ranging from 0-127. Yeah if mononoke's pitchbend value goes up to 16383, that would explain it...
I am trying to use Mononoke as a MPE controller on iOS 10.3.3 and I have this problem
Can anyone else confirm?
Oh.. that doesn't look right at all. I haven't seen that happen before. Does that only happen in Audiobus?
I don't have any iOS10 devices anymore so I can't test this myself unfortunately.
It happens only on Audiobus, indeed
Of course I can test anything, it means a lot if it can work on this device since every other I own is too small for my hands
How can I help in order to make it work? It's the only MPE app I own which runs on iOS 10.3.3
I sent an email to Audiobus support with no reply regarding this issue
How else can I get help? I paid for both of these and expect them to work
I can assure you that Mononoke works. I've tried to reproduce the problem but I can't get it to glitch like your screenshot in any host and on any device.
Unfortunately I don't have any iOS10 devices. The oldest device/version I have is on iOS12. But on that one there is no issue either. I suspect it's an iOS10 thing, perhaps in combination with Audiobus specifically.
Yea I’ve never seen this. If you can update your device I would do it.
@bichuelo
To check if this bug is related to Audiobus, you could try to load Mononoke AUv3 in Garageband, AUM or apeMatrix, BM3 or whatever AUv3 host you additionally have installed on your device. (Garageband is free IIRC)
Which device are you using ? Perhaps other AB users with the same device can comment if its running with their IOS (ie IOS version dependend bug)
Update: this app is amazing I’ve been using it heavy since day 1!
It resizes a little weird but hey, that’s my only complaint
I particularly love how I can mirror the notes from the left side on the right side but get different "voices" from them, which provides incredible results when you combine the two sides/hands
It can't be done. I just bought it even though is an old 4th gen iPad. My first one with a big screen, since I'm used to my mini 3
This has been the only issue so far, and there are plenty of apps which are 100% compatible. Got it for less than $120!
Does the problem also occur when running Mononoke standalone? The standone also uses the AUv3 plugin internally, so if that runs ok there’s a relatively big chance that the issue is with Audiobus.
Might have missed this but is this a reoccurring issue, have you tried a turn off/turn on the device. If so you can also try to delete the app (backup any user presets) and reinstall it. Those two options fix a lot of issues.
It works perfectly fine standalone. Indeed, I think it's an Audiobus issue. And it's not only the GUI which is messed. The app doesn't work at all when used as an AUv3 inside it. Not with it's own sound engine, nor as a MIDI controller
I installed Garageband as @_ki suggested and it does work inside it. But I ain't got a clue on how to get rid of the native piano keyboard it has, so the pads are very small. I am unaware if it can be used as a MIDI controller, a function I do want to use. Mind you, on iOS 10.3.3 the latest Garageband version that runs is 2.2.2 and it currently is in 2.3.10
Thanks, I just did this and it made no difference whatsoever
MIDI controller features are only available on iOS11 and higher, because that’s when Apple added MIDI output to the AU standard.
So that’s unfortunately something that neither I nor Audiobus can fix.
@Michael
Alright, but there must be some kind of workaround. I have been able to use both SP Link Edition as well as Animoog by loading them as MIDI, then sending messages to the computer successfully from that device, running iOS 10.3.3
Those are standalone apps, so they don't have to rely on the Audio Unit framework for MIDI output. In Mononoke the internal MPE keyboard is part of the AU plugin - even when run in standalone mode - so it's not possible to have MIDI output on iOS10.
Unless Apple change that there's no workaround for it.
Actually, I'm not using them like that, but _within _ Audiobus.
Animoog needs an IAP in order to send MIDI from the standalone mode but not when used as a plugin, which is the way I use it, without its own audio engine running...
Audiobus supports Audiobus (IAA) plugins and Audio Unit (AUv3) plugins. Audiobus/IAA apps are essentially standalone apps that route audio to eachother using a clever networking protocol. But they're still standalone apps.
Animoog is a really old app, predating the Audio Unit standard, so I'm not surprised it works well on a 2012 iPad with iOS10. No matter how you load it, it will always be standalone - which means it can send MIDI using the normal CoreMIDI technology, or Audiobus' proprietary MIDI bus.
Mononoke uses the newer Audio Unit (AUv3) standard. Audio Units can not use CoreMIDI directly. They have to output MIDI to the app that is hosting them, and the host is then responsible for routing this MIDI to CoreMIDI. The plugins can not do this themselves. When you run Mononoke 'standalone', you're actually running a miniature host-app which loads a single instance of the Mononoke plugin in fullscreen mode.
Originally Audio Unit plugins couldn't even output MIDI at all. This is a feature that was added to the standard in iOS11. Which is why there is no possible workaround to get MIDI out of Mononoke (or any other AU plugin) unless you're on iOS11 or higher (this is also mentioned in the App description).
lol this aged like a fine wine 😂
Hhahaha that’s a gem you dug up there
Alright I think I understand, thanks for the detailed explanation!
So, if I can't use the big iPad for sending MPE from Mononoke (something I still can with my old iPad mini 3), I'd still love to use it inside Audiobus along with more plugins. How can this be fixed? Audiobus support never replied my emails...