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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Animoog Z trying add simple lfo to swipe the filter, but the value jumps wildly when pressing keys.

So I cleared all modulations. I disable the filter envelope, then disable the keyboard trigger mode on the lfo 1. Then I set lfo 1 to swipe the filter frequency slowly and it does so when holding a key down, but when I trying to press a series of keys the frequency jumps around randomly?????? I do not understand what is causing that. I don't get what I'm doing wrong? This happened too when trying to modulate the bit crush parameter as well.

Here is a video

You can see the LFO 1 swipes the filter just fine when holding down the key, but then you can see the modulator indicator (the green ring around the filter frequency knob) jumping around randomly as I keep retriggering the key.

Here is a video of the result I want, using cubasis 3 micrologue

The LFO swipes the filter smoothly either while holding down the keys or when constantly triggering them.

Here are the settings for modulations and LFO I'm using on animoog Z, dunno if there is something I can change so it behaves like micrologue LFO?


Comments

  • I see what you mean. I tried with the LFO rate set to be slower, to see more clearly how it works, and it looks like the position of the LFO is being set to a random position when it's not set to 0 with the KB TRIG parameter, and the speed of the LFO is always set to be moving quickly; it's never at one of the "curves", never near the top or the bottom of the sine shape, but instead always on a straight section. There's no way to have the LFO moving completely unaffected by the keyboard, so that it affects all of the voices in the same way. Instead, every voice has a different value for its current "filter frequency" at any given time.

  • @Skyblazer said:
    I see what you mean. I tried with the LFO rate set to be slower, to see more clearly how it works, and it looks like the position of the LFO is being set to a random position when it's not set to 0 with the KB TRIG parameter, and the speed of the LFO is always set to be moving quickly; it's never at one of the "curves", never near the top or the bottom of the sine shape, but instead always on a straight section. There's no way to have the LFO moving completely unaffected by the keyboard, so that it affects all of the voices in the same way. Instead, every voice has a different value for its current "filter frequency" at any given time.

    this is so strange.... I just reopen the same project with the same patch and now it is acting a bit more like I would want to, it now does not jump to a random point, but rather when your lift the finger of the key it jumps to the middle of the modulation range (the center of the green ring) then when you press again it jumps to the point that the LFO would have reached at that point in time. Then I realized that was happening because the AMP ENV had 0 release so when the sound cut offs the LFO resets to the middle of the modulation range, so I increased the release and now it works similar to the micrologue......

    In conclusion I think it was bugged and reseting the cubasis session fixed that, but it also seems like the animoog LFOs automatically reset to the middle value of their modulation range when there is no sound playing.

  • @Nimgwen It's definitely a bug. I just reopened Animoog Z, and it restored the state of my unsaved preset, as it's supposed to...but this time, the keyboard has no effect on the phase or speed of the LFO, the way I expected it to work the first time.

    For me, the amp env release only seems to impact the visual indicator of the LFO's position; even with amp env release set to 0, the LFO is unaffected by the keyboard.

    It seems like, even when KB Trig is off, the keyboard was resetting some aspect of the LFO, until I exited the app and returned to it. I'll try exiting again, selecting a preset, and then making a new preset, and I'll see if that allows me to reproduce the bug.

  • Yes, the bug appears to be with the KB Trig parameter.

    Problem: KB Trig for LFO 1 is not fully "Off" until you exit the app and return to it.

    Steps to reproduce:
    1. Create a new preset
    2. In the MOD tab, disable all of the modulation.
    3. Attach LFO 1 to the destination "Filter Frequency".
    4. Toggle the KB Trig for LFO 1 to "Off".
    5. Go to the FX tab, and observe the behavior of the LFO indicator dot on the Filter Frequency parameter when pressing the keys.
    6. Exit Animoog Z, remove it from the backgrounded apps, and open it again. Repeat step 5.

  • edited May 2022

    @Skyblazer said:
    @Nimgwen It's definitely a bug. I just reopened Animoog Z, and it restored the state of my unsaved preset, as it's supposed to...but this time, the keyboard has no effect on the phase or speed of the LFO, the way I expected it to work the first time.

    For me, the amp env release only seems to impact the visual indicator of the LFO's position; even with amp env release set to 0, the LFO is unaffected by the keyboard.

    It seems like, even when KB Trig is off, the keyboard was resetting some aspect of the LFO, until I exited the app and returned to it. I'll try exiting again, selecting a preset, and then making a new preset, and I'll see if that allows me to reproduce the bug.

    You are right, the release on the amp env was not causing the LFO to jump the frequency. I was confused cause I was hearing clipping, but that was the 0 release, because I disabled the filter and I could hear the clipping and it went away with increasing the release, so that clipping sound was being caused by the amp env itself. The LFO seems to be working ok now and it's just the visual that shows it go back to the middle when the sound cuts off. If you can find how to reproduce the bug that would be useful to send it to the animoog devs.

  • I listed the steps to reproduce above, and I sent them an email.

Sign In or Register to comment.