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.

"Tap to fix" with ICA4+, Apogee Quartet

13»

Comments

  • HarroHarro

    Also notice that since last week iConnectivity released some software updates:

    • iConfig (for PC and Mac) version 4.2.5
    • Windows driver 4.11.0
    • firmware 1.1.2 for iCA4+ (beta)

    See release notes on the resp. pages on https://www.iconnectivity.com/downloads

  • CarnbotCarnbot

    I always have my ica4+ at 44.1/24

  • gatzschegatzsche

    With 44.1/24Bit I can reproduce the issue now too.

  • nytjadensnytjadens

    I also run at 44.1/24 does this put us closer to a fix?

  • gatzschegatzsche
    edited May 2017

    After having done some more investigation: It has nothing todo with 24/16bit or 44.1/48kHz. The real reason was, that I rebooted my device holding both, Home and On/Off Button. If I do this and connect the iCA4+, the error happens, no matter what sample rate and bit depth has been set.

    Here is a workaround that works for me:

    1. Disconnect iCA4+
    2. Reboot iDevice by holding both, Home Button + On/Off Button
    3. Launch Audiobus
    4. Wait 4s
    5. Connect iCA4+
    6. Launch apps --> Everything connects fine, iCA4+ is working.

    Can you confirm, that everything is working, if you connect the iCA4+ after having launched Audiobus?

    I'm still working on a fix for this issue ...

  • gatzschegatzsche
    edited May 2017

    Hi guys,

    I have found and implemented a workaround which fixes the issue, at least for the iCA4+ setup I have here at my desk.

    Could you guys install the latest version from TestFlight and tell me if the iCA4+ issue has gone for your setup?

    If you have not a TestFlight invitation for Audiobus, you can subscribe here:
    https://audiob.us/testing

    Thanks heaps,
    Gabriel

  • gonekrazy3000gonekrazy3000

    @gatzsche said:
    Hi guys,

    I have found and implemented a workaround which fixes the issue, at least for the iCA4+ setup I have here at my desk.

    Could you guys install the latest version from TestFlight and tell me if the iCA4+ issue has gone for your setup?

    If you have not a TestFlight invitation for Audiobus, you can subscribe here:
    https://audiob.us/testing

    Thanks heaps,
    Gabriel

    will test as soon as i can :)

  • gonekrazy3000gonekrazy3000

    @gatzsche whatever magic you did with this update is amazing. the ica4+ works pretty much with no issue now when connected to a pc and my ipad simultaneously. ab3=>aum=>multi outs=>ableton works perfectly.

  • gatzschegatzsche
    edited June 2017

    @gonekrazy3000 said:
    @gatzsche whatever magic you did with this update is amazing. the ica4+ works pretty much with no issue now when connected to a pc and my ipad simultaneously. ab3=>aum=>multi outs=>ableton works perfectly.

    Wow, that sounds good! Thanks for that feedback.

  • gonekrazy3000gonekrazy3000

    @gatzsche said:

    @gonekrazy3000 said:
    @gatzsche whatever magic you did with this update is amazing. the ica4+ works pretty much with no issue now when connected to a pc and my ipad simultaneously. ab3=>aum=>multi outs=>ableton works perfectly.

    Wow, that sounds good! Thanks for that feedback.

    It used to be that I had to disable my sound card in ableton first. Started Audiobus and then Reenabled it in ableton otherwise Audiobus would not work properly at all. Now it's flawless even if my pc is already using the device. That was pretty much my main gripe and you guys fixed it :)

  • nytjadensnytjadens

    Does this also fix the Apogee Quartet problem?

  • gatzschegatzsche
    edited June 2017

    @nytjadens said:
    Does this also fix the Apogee Quartet problem?

    I have not an Apogee Quartet here, but it might be possible that I have fixed the Apogee Quartet issue too.
    Do you have access to the TestFlight version? If yes, could you check if the Apogee issue is fixed also?

  • nytjadensnytjadens

    How do I get access?

  • gatzschegatzsche

    @nytjadens said:
    How do I get access?

    Enter your email here: https://audiob.us/testing.

  • MunibeastMunibeast
    edited June 2017

    The latest beta seems to work at first glance. I haven't had much time to do a lot yet but most apps seem to be loading fine with the interface connected now. ToneStack still has issues loading and usually gives the "tap to fix" error. Starting it outside of AB before adding it seems to do the trick but the first try usually just crashes it... Amplitube and BiasFX load fine but don't bounce back to AB afterwards. Not a big deal. So something is still wrong with ToneStack in AB3 with ICA4+. Otherwise it's looking good.

  • HarroHarro

    Yes, Tonestack needs a AB3 fix, although it's working ok as INPUT in AB3 (on my iPad Air 1 - latest IOS + iCA4+), but I also get the Tap to Fix error when it's in the EFFECT slot and sys 1 is INPUT.

    BTW. Shouldn't these guitar-apps (BIAS FX and Tonestack in particular) also be MIDI Recievers? They are not (yet?), while they have extensive midi (learn) parameters...?

Sign In or Register to comment.

© Vanilla Keystone Theme 2025