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
Definitely, I'd say. The Acoustic, Metallic and Richard Devine packs are all better than any of the new IAPs at first glance.
In agreement. The IAPs from Animoog are still worth buying to transfer over to Animoog Z. The underlying synth engine is pretty much unchanged (the Z axis is just another modulation source which is the equivalent of an LFO where you get to draw the LFO shape. The core of the synthesis is still 8 wavetables blended in the Y axis (a hybrid form of vector synthesis). I thought maybe that Moog might have taken the opportunity of the new version to improve the filter seeing as Animoog was created at a time when iOS devices were a multitude of times less powerful, but I suppose they decided against it for backward compatibility.
Funnily enough, I’m finding it hard to understand why Animoog Z is so much more processor-hungry than Animoog. Even though Animoog Z has (up to) 4x the polyphony, any imported presets are 4 note poly or mono (the majority of the Animoog Z presets are 4 note polyphonic or mono too, inclusive of the IAPs). The graphics routines shouldn’t tax the app too much and if they were responsible for the increase in processor overhead, you would most probably notice a peak on the orbs page which should drop off when viewing the other pages.
If you’re using all 16 notes of polyphony and all 10 modulation slots that definitely has the potential to increase CPU load significantly, but there’s no real need to push Animoog Z to that extent as it’s very expressive already. Increasing polyphony to 16 voices will definitely help with voice stealing on chords with long release times, but it’s a pity that an 8 voice mode wasn’t offered too, or even better, that the user was able to choose the number of voices that are reserved (as is the case with e.g Korg Odyssei)
I have a feeling that further optimisations are going to be possible over time which will reduce the processor load. The performance vs efficiency core utilisation on older devices is very interesting, I wonder if there’s anything programmatic the Moog team can do to prioritise performance cores as they update the app.
@MoogMusicInc : Animoog Z sounds great and it seems to take MUCH longer to load and display its interface than any other AU instruments I have (and I have a lot). This is on an iPad 6 with iOS 15.1.
Hmmm. I have your exact configuration, and it takes 4 seconds from tapping the icon to ready. This is on the default preset, as installed. Are you maybe loading a lot of timbres, or something? Or do you feel that 4 seconds is a long time? BTW, I'm doing this without much else loaded, so the app is not fighting for memory.
It takes about 8 to 10 seconds to load its interface on my iPad. It takes about 2 seconds for Layr or Model 15 or other hefty AUs to show their interface on my iPad in AUM. It sometimes takes considerably longer for me.
Yes, that is long; I wonder why? I tried a few others that I have. They ranged from 2 seconds (KQ Dixie) to 5 seconds (the venerable Music Studio). So my observed 4 seconds for Animoog Z is right in the window. Do you have hardware attached, controller or audio interface? That might explain the extra time.
No hardware attached -- and it is even true after a hard reset.
I’m assuming the UI is contributing a bit to the longer loading times
I think so -- it seems suboptimal -- the CPU use spikes crazily when the u.i. draws (on top of it being super slow on my iPad).
So excited about this app, Animoog is a favorite and this is an amazing improvement! Thanks @MoogMusicInc !
After playing with it I do have a question I couldn't find an answer to in the manual:
What does the Z axis actually do to the sound? I picked a few of the new Timbres and did an experiment drawing a line on the "floor" of the box and in the same place up at the "ceiling" and it sounds identical, seems like it should sound different using the Z axis?
Also wondering if the Z axis has an effect on legacy Timbres imported from old Animoog or only the new ones?
FWIW - about 4 seconds. iPad 8 / iOS 15.1
Fwiw, here is a video of a few different synths loading and displaying their interfaces. Note that I am talking about the time for the AU to display its u.i. not the initial load time of the AU into AUM. Here are Animoog Z, Moog Model 15, Factory, Continua. Animoog takes about 8 seconds from the time its node is tapped till the u.i. finishes drawing. All of the others display the u.i.s almost instantly. This is after a fresh reboot (hard reset):
It isn't something that prevents me from using Animoog Z, but I think it could use some attention/optimization.
Yeah I noticed that as well. I expect they'll improve it as Model 15 went through quite a lot of optimisations after release.
Luckily it's just the gui and not the audio/midi which is frozen, but it is a bit annoying.
I’m seeing roughly 2 seconds for AZ interface to appear in AUM. 🧐
Do you mean you it takes 2 seconds in the video or that it takes 2 seconds on your device? If you mean the latter, what device are you using? Is that for the first time that the u.i. loads? For me, the first time that the u.i. loads takes longer than it will, if the window is closed and opened again.
On my device - iPad 8 / iOS 15.1. About 4 seconds standalone. About 2 seconds for AU to display UI in AUM.
Has anyone talked about Animoog Z being a AUFX as well?
Have you tried using it for that yet? I was unable to get it to affect anything, oddly enough.
Thanks for the feedback from everyone.
@jonmoore @Wrlds2ndBstGeoshredr
Animoog Z is a joy to program and play … e.g.
All with with the usual Moog polish and usability. Apart from being an expressive it’s the little things e.g. that there is an Overwrite and a Save As option for patches (take note Fabfilter and many others - we don’t want to type the patch name in each time we save an update).
Did you turn on Process Input in the settings?
If you don't turn that on then the input is used for recording audio input in the timbre editor
Thanks, I’ll give that a try!
@espiegel123 On my iPad Pro 10.5 / IOS 14.8 Animoog Z takes about 4-5 seconds to open its UI in AUM - a lot longer than other AUv3s. Sometimes after changing window size and closing Animoog Z, the next open will also take that long - but normally reopening of the Animoog Z UI happens instantly.
Moog z glitches as you move around screen but so does Koala. Maybe because the original code were iaa? Its the only reason I can think of. Cpu also 60+ percent but goes to 40+ percent if you add another moog z? Also have to switch to regular midi from mpe. For external keyboards to connect. Then back to mpe.
Here. Not so bad but is it because they were iaa code? Seems to be when an app goes over the app. It will just strobe or feel magnetic. Same with koala.
I had to redesign my BCR2000 overlay
(Unfortunately Animoog Z's broadcast of CCs appears buggy, so the control synchronizing doesn't work as well as it did in the old version
)
Think of it as another modulation source.
X: runs through the 16 wave co-ordinate positions within the wavetable that’s at the X,Y Orb position.
Y: selects which of the eight wavetable slots are played according to the X,Y Orb position.
Z: is effectively a freeform LFO (it’s a pity that you can’t view the x/z plane orthographically, as this is the form the LFO takes).
The envelopes and Orb rates have a bearing as to how much of the orthographic Z form is utilised along the X axis.
The modulation slots on the Mod page allow you use the Z Orb’s position to modulate a range of other Destinations (including any of the 3 LFO’s, which is more useful than it seems as it enables you to create a hybrid LFO form which features less predictable non-linear value modulations).
Seeing as there’s no actual sound source on the Z axis, any sound source crossfading only applies to the X and Y co-ordinate positions.
Cool midi map