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.
Animoog Z - 1.0.7 update breaks MIDI CC sending (1.0.8 fixes it!)
Animoog Z sends MIDI CCs for any hardware-mapped controls. In the original release this was buggy for toggle buttons, so it didn't always send CCs if you manipulated the buttons from hardware as well as software. This looks like it's been fixed. BUT...
Previously all of the CCs for mapped controls were sent when you changed presets, with the exception of the (buggy) toggle controls. Now the MIDI CCs for mapped controls are not sent when you change presets! Or rather, a very few of them are (with no obvious logic*), but most of them aren't. This is disastrous if you want your hardware (or other MIDI controller app) to reflect the current state of Animoogs controls.
Is anybody else seeing this?
(*Okay, I think the few CCs that _seem_ to get sent on a patch change are the LFOs and any controls that are bound to LFOs in the new patch's MOD matrix. So in fact they aren't getting sent on the patch change, they're getting sent by the action of the LFOs after the patch has loaded.)
Comments
Direct your comment to @MoogMusicInc. They are usually very responsive.
@MarkH - It would be helpful if you could detail how you know this. Have you verified this with a midi monitor placed directly after Animoog Z’s output?
I ask, because there is also the possibility that it’s the host, hardware, or controller app that is having trouble receiving or processing the information.
I have reported it through the official appsupport email.
Yes, I am using a Mozaic script to monitor the messages.
Are only controls have changed being missed between presets? Or are some that have changed being missed as well? Sorry, I would test myself rather than asking, but I have no time until tomorrow.
If I had time I'd also, try substituting Model 15 for Animoog Z. If I remember correctly, that one worked correctly. Again ... just an easy making sure that the test itself is working.
Lastly, if I had time, I'd test standalone vs. AUv3 instances to see if there's any difference.
Thanks for the ideas, but no joy. There is no difference whether I tweak some, all or none of the controls before changing presets. The CCs are sent correctly by Animoog (original version) and they were sent by Animoog Z before the update (I am using previously-saved AUM sessions). The behaviour is the same standalone as with an AU instance.
@MoogMusicInc all I want for christmas is to open Animoog Z and to have it always default to my prefered settings of MPE enabled and pitchbend settings where I want them and pressure mode on. It's very very very annoying to reset these controls every time it crashes or I open a new instance.
If you set these in the standalone version do they not default in new AU instances? The CC map does this, at least.
Here's a video showing what I mean.
Have you tried force restarting your iPad?
Hi MarkH,
We just released v1.0.8 that fixes this problem.
Moog is the greatest!
You just beat me to it
BTW, can you check it works for the Delay ping-pong toggle? That's the only one that still seems not to follow for me, although I need to double-check my settings before I'm sure.