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 Voltour and LoFi Clipper bad signal?

Hi,
Could anyone do a quick test and load one of the above apps in AUM to see if they get a “bad signal” message?
Also sometimes mutes audio in GarageBand when added to a track. Maybe issues in other hosts but don’t have any of those.
iPhone 12 iOS 17.2.1
Thanks in advance

Comments

  • Voltour works for me in AUM on a gen 1 ipad pro 12.9, ios 16.6.1. and i often use it in Drambo.

  • Ok that’s interesting, appreciate you checking.
    Could it be an iOS 17 problem? If anyone is on that and could do a quick check would be great

  • Voltour works in AUM on iPadOS 17.3 without problems here.

  • I’m on the last version of iOS 16 and it’s working fine for me.

  • Thanks for checking, just updated to 17.3 and am still getting the same issue.
    Assume it must be a phone problem then which would be bad news.

  • @Zerozerozero said:
    Thanks for checking, just updated to 17.3 and am still getting the same issue.
    Assume it must be a phone problem then which would be bad news.

    Yep I’m getting that error on my iPhone which is on 17.3 as well.

    Have you reported to the developer?

  • Ah ok, thanks for confirming. Yes, reported over a month ago, chased them today, they’re saying they can’t reproduce the error.
    Have sent video and will say others have confirmed now.

  • Dev has said they can’t reproduce error (they’ve sent a video showing this on their device) so there will be no fix and to try for a refund (had the apps a while so probably unlikely).
    If any other phone users have error would be great if they could message dev…
    Thanks

  • @Zerozerozero said:
    Dev has said they can’t reproduce error (they’ve sent a video showing this on their device) so there will be no fix and to try for a refund (had the apps a while so probably unlikely).
    If any other phone users have error would be great if they could message dev…
    Thanks

    I don’t use iPhone but do have the issue so will send them a message as well 👍🏻

  • @HotStrange said:

    @Zerozerozero said:
    Dev has said they can’t reproduce error (they’ve sent a video showing this on their device) so there will be no fix and to try for a refund (had the apps a while so probably unlikely).
    If any other phone users have error would be great if they could message dev…
    Thanks

    I don’t use iPhone but do have the issue so will send them a message as well 👍🏻

    Many thanks.
    It’s also broken in GarageBand.
    Really odd. I don’t know why it would work on Devs device but not others.

  • wimwim
    edited February 6

    Have you tried messing with different buffer sizes and sample rates? You can't explicitly set the buffer size in GarageBand but you can sometimes in AUM. Be sure that no other apps are open when you try to set the sample rate or buffer size.

  • @wim said:
    Have you tried messing with different buffer sizes and sample rates? You can't explicitly set the buffer size in GarageBand but you can sometimes in AUM. Be sure that no other apps are open when you try to set the sample rate or buffer size.

    I have but to no avail unfortunately.
    Done a few reboots/reinstalls.
    Managed to crash in Audiobus as well just now so that’s all of the 3 hosts I own. No other apps running at same time.
    Dev is also on ios17…no problems…..

  • @Zerozerozero said:

    @wim said:
    Have you tried messing with different buffer sizes and sample rates? You can't explicitly set the buffer size in GarageBand but you can sometimes in AUM. Be sure that no other apps are open when you try to set the sample rate or buffer size.

    I have but to no avail unfortunately.
    Done a few reboots/reinstalls.
    Managed to crash in Audiobus as well just now so that’s all of the 3 hosts I own. No other apps running at same time.
    Dev is also on ios17…no problems…..

    It may be particular to some devices but not others.

  • I guess so.
    Dev has iPhone 13 and I have 12.
    Not sure what @HotStrange has
    That would be quite an inflexible position to take if that is the case. Not being prepared to fix apps because dev has different device to customer.
    Hopefully it’s something else..

  • @Zerozerozero said:
    I guess so.
    Dev has iPhone 13 and I have 12.
    Not sure what @HotStrange has
    That would be quite an inflexible position to take if that is the case. Not being prepared to fix apps because dev has different device to customer.
    Hopefully it’s something else..

    if they cannot find a way to reproduce it, it can be difficult to fix. It might not be inflexibility.

    If few people have reported the issue it might also impact how much effort they are able/willing to spend.

    I had an issue and they initially wouldn’t look at it but a few weeks later after several other people reported it, they put more effort in and were able to address it.

  • Indeed. iPhone users a niche in a niche.
    Hopefully others might report.

  • I’m trying to recreate it to see but it’s not happening for me on iOS 17 on an iPhone 11 on 48k, 512 buffer

  • @Fingolfinzz said:
    I’m trying to recreate it to see but it’s not happening for me on iOS 17 on an iPhone 11 on 48k, 512 buffer

    Hmm, so working on 11 and 13 phone. Quite a specific bug.
    Thanks for testing 👍🏻

  • It works fine in AUM on the iPad Pro M2 (48 kHz, 128 samples, iOS 17.2) and the iPhone 15 (48 kHz, 256 samples, iOS 17.3).

    Is this “message” from Nembrini AU or the host?

  • Many thanks for testing.
    Message is “bad signal” in AUM.
    Also kills audio in GB when added to a track (see vid). I did manage to crash them in Audiobus as well I think adding them randomly to tracks.
    Seeming like iPhone 12 Pro Max might be prob 🤷🏼‍♂️

  • @Zerozerozero said:
    Many thanks for testing.
    Message is “bad signal” in AUM.
    Also kills audio in GB when added to a track (see vid). I did manage to crash them in Audiobus as well I think adding them randomly to tracks.
    Seeming like iPhone 12 Pro Max might be prob 🤷🏼‍♂️

    Check in settings->analytics to see if there are crashlogs for the AU and if there are , send them to Nembrini

  • @Zerozerozero said:
    Many thanks for testing.
    Message is “bad signal” in AUM.
    Also kills audio in GB when added to a track (see vid). I did manage to crash them in Audiobus as well I think adding them randomly to tracks.
    Seeming like iPhone 12 Pro Max might be prob 🤷🏼‍♂️

    I’ve tested Nembrini Voltour in GB on the iPhone 15 Pro Max, the first load with the default patch was without sound. As soon as I select the patch on Voltour, everything works fine, even if you select back to default.

    So there is something, for sure.

  • @espiegel123 said:

    Check in settings->analytics to see if there are crashlogs for the AU and if there are , send them to Nembrini

    Nothing there unfortunately but know where to look in future, thanks

    @Luxthor said:

    I’ve tested Nembrini Voltour in GB on the iPhone 15 Pro Max, the first load with the default patch was without sound. As soon as I select the patch on Voltour, everything works fine, even if you select back to default.

    So there is something, for sure.

    Thanks for check. All good info for dev. Sometime issue is minor as described and others (mostly in AUM) more severe.
    Cheers

Sign In or Register to comment.