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.

Nembrini apps bug when used in hosts.

13»

Comments

  • @flo26 said:

    @uncledave said:
    From @Rodolfo 's tests, it looks like these tones may be related to the buffer update frequency. A test in another host (AudioBus, GarageBand?) might show whether the effect is due to AUM or the Nembrini AUv3 implementation.

    Yesterday,i’ve Tested this in Audiobus and auria, and had the same results

    I have performed a bunch of tests and the issue is easy to reproduce. I hope that they will address it. Their desktop versions don't have it. Most of their IAA versions don't have this issue either. But it doesn't seem like they are interested in it.

    @NembriniAudio does not seem to consider this issue worth looking into. I hope they will change their minds. In some cases it isn't noticeable, but in some it really is. And that low frequency content will muddy up a mix.

    With some amp settings, one doesn't notice it so much but in some cases it can be pretty distracting. The pitch of the hum is proportional to the buffer size and is independent of the input signal's content. Sending a sine wave sweep through it and looking at a spectrogram makes it clear.

    The Mac versions of their plugins don't exhibit this behavior at all. They are very clean.

    Anyway, below are spectrograms that demonstrate the issue. These were created by running a sine sweep from 600 hz to about 2200 Hz through MRH810 with these settings.

    Here is the output of their MRH810 Mac version

    This is the MRH iOS version as an AU with a buffer of 256. You can see the hum (the horizontal band that doesn't change as the sine wave sweeps).This is at about 150 Hz.

    This is the the spectrum analysis of the IAA version. This is much better. It does not have that 150 Hz hum. There is a very low frequency band a bit below 50 Hz (?) but I can't hear it. The Mac version doesn't have it at all.

  • @espiegel123
    A week ago there was an update to fix a DC offset bug.
    That didn’t fix this issue?

  • I’ve gone amplitube and gen labs road.
    I really love the sound of nembrini apps,but i can’t stand this hum anymore😉.
    It is always there( clean or distorted sound).
    Several of their apps have the same problem.
    f they fix it Then, i will use them again.

  • @CracklePot said:
    @espiegel123
    A week ago there was an update to fix a DC offset bug.
    That didn’t fix this issue?

    @CracklePot said:
    @espiegel123
    A week ago there was an update to fix a DC offset bug.
    That didn’t fix this issue?

    No,it did not.

  • @flo26 said:

    @CracklePot said:
    @espiegel123
    A week ago there was an update to fix a DC offset bug.
    That didn’t fix this issue?

    @CracklePot said:
    @espiegel123
    A week ago there was an update to fix a DC offset bug.
    That didn’t fix this issue?

    No,it did not.

    Dang.
    It sounded like they found the buzz.
    Maybe a different buzz, then.

  • @CracklePot said:

    @flo26 said:

    @CracklePot said:
    @espiegel123
    A week ago there was an update to fix a DC offset bug.
    That didn’t fix this issue?

    @CracklePot said:
    @espiegel123
    A week ago there was an update to fix a DC offset bug.
    That didn’t fix this issue?

    No,it did not.

    Dang.
    It sounded like they found the buzz.
    Maybe a different buzz, then.

    @NembriniAudio seemed receptive to my initial report and I sent them some examples and an AUM project to simplify reproducing. But I received a message that demonstrated that they had not understood my report (perhaps I had not documented it clearly enough). When I tried to clarify and provide more information, I received a message that gave me the impression that I was wasting their time with a trivial issue.

    I have to say that I was puzzled by the response. The IAA app doesn't have the issue for the most part and the AU clearly does. Since it is directly proportional to the buffer size and not the frequency content, it seems like it must have something to do with how the buffer is loaded when running as AU.

  • Did this get fixed?

  • @OscarSouth said:
    Did this get fixed?

    Yes. Last year. Not long after the post you responded to.Thatnews made it into other threads about the issue but I guess not this one.

  • Good to know! Thanks!

Sign In or Register to comment.