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.

Channel Bleed- Audiobus/BIAS FX/LoopyHD setup

edkelleredkeller
in General App Discussion

Greetings all,
I have a question about channel bleed which just began appearing in my setup a couple months back. Seemingly after a software or iOS update- not sure. Here are the details of my rig:

Guitar playing, single input. Audio interface is Audient iD4, using bus power and USBA toC cable, which has worked fine. This is running into an 11" iPad Pro, with the most recent iOS updates.

Software setup /signal path is:
Audiobus, one audio path, input software is BIAS FX [version 1] and output is LoopyHD.
I typically use a 12 loop setup in LoopyHD.
All software is updated to most recent versions.

The Audient iD4 controls gain on the system- it's not available in Audiobus or LoopyHD.
[I had previously used an Apogee Jam+, with general success- but had issues with gain consistency and the Audient, for many months, seemed to have solved that. I kept the Apogee as a backup for gigs. Just noting that with the Apogee, gain control in SOFTWARE was still possible and this caused issues when adjusting both the hardware and the software]

So here is what has been happening. I seem to be able, on a per session level, to get my guitar signal to where I want it in the meter in BIASFX. This registers at a good level in my tracking in LoopyHD. I usually record a bit quieter, to avoid clipping, as especially with switching from low gain to high gain parts in the compositions/performances, and using an eBow, I can get a lot of layered signal too quickly.

Lately, what I've seen happen seems to be a channel bleed. It happens more with high gain guitar patches; I'll switch on a few gain pedals or switch from a clean Matchless ampsim to a Rectifier, and suddenly I'll be hearing crosstalk on the new loop I'm recording, and sometimes it even seems that previously recorded loops are bleeding into the NEW LOOP.

Now, Positive Grid is sunsetting BIASFX version one, and I do have version two, but the rig setups do NOT all transfer smoothly to BIASFX2, so I haven't moved my rig to the newer software. So I can't yet test if this is all an artifact due to BIASFX version one updates being discontinued. That might be the problem.

But I'm writing to ask if anyone has any insights into this, has had similar issues, has solutions?

Thanks a bunch. If screenshots of my setup are helpful, I'm happy to post em.

CHEERS
Ed Keller
https://thermalhowl.bandcamp.com/

Comments

  • wimwim

    Yes, I think screenshots are needed.

    I don't see any possible way there can be channel bleed caused by an app. It almost has to be something about the audio routing.

  • SamuSamu

    I recall getting 'bleed-thru/crosstalk' using the ancient Behringer UCA-202.
    When output was maxed from apps I could record the bleed thru even when nothing is connected to the inputs.
    It's was at low level around -65-70db range but still very annoying.

    When I use latency free monitoring on my UR-242 I sometimes forget it's turned on.
    It's happened with loopback as well and I wonder why everything gets doubled...

    I've not checked the crosstalk setting on the interface but it could be that the high levels are pushing it into audible levels...

  • edkelleredkeller

    Wim, Samu, thanks so much. I'll post screenshots this weekend.

    Samu, I have a sneaking hunch that the Audient iD4 is responsible. It is the first version of that interface but that came out within the last couple years- it's quite modern. I'm not using it connected via a camera connection kit, tho- I have an iPad pro with usbc, so i'm going direct and powering the interface via usbC. My battery drain is acceptable for gigs lasting under and hour and general use.

    All this though to say, that the iD4 has a control for monitor mix, and I suspect that this could be the culprit. Either interfering with monitor input setting in Loopy- or, cranking up the input gain on the hardware itself.

    Screenshots to follow. I'll also A/B test my setup with the old Apogee interface.

    Thank you again! Ed

  • espiegel123espiegel123

    @edkeller said:
    Wim, Samu, thanks so much. I'll post screenshots this weekend.

    Samu, I have a sneaking hunch that the Audient iD4 is responsible. It is the first version of that interface but that came out within the last couple years- it's quite modern. I'm not using it connected via a camera connection kit, tho- I have an iPad pro with usbc, so i'm going direct and powering the interface via usbC. My battery drain is acceptable for gigs lasting under and hour and general use.

    All this though to say, that the iD4 has a control for monitor mix, and I suspect that this could be the culprit. Either interfering with monitor input setting in Loopy- or, cranking up the input gain on the hardware itself.

    Screenshots to follow. I'll also A/B test my setup with the old Apogee interface.

    Thank you again! Ed

    This sounds like you might have monitoring on in multiple apps and possibly also the interface. For instance, you don't want to monitor the input from Loopy if the audio stream also has the Bias FX audio audible via another path.

  • edkelleredkeller
    edited February 2021

    Hi all, quick update. I spent many hours trying different cables, interfaces, isolating software, and I think i have found the solution. @espiegel123 your comment on monitoring set me on a path. I spent some hours last night trying to disable monitoring on all the apps. It was a challenge tho as it's not obvious; only LoopyHD in my signal path has an obvious monitor function. Audiobus doesn't, BiasFX doesnt.

    Recall, my signal path is: guitar>id4 interface mk1>usbc on ipad pro 11">audiobus>BiasFX inside audiobus>LoopyHD as output for my looping DAW.

    I could reproduce channel bleed with high gain guitar amp sims. I rebuilt my rig setup inside Audiobus a few times, reread the manual, and it occurred to me that maybe handling this in the MIXER part of audiobus- which I'd never needed to use- might be a way forward. **So- I simply SOLOED the single channel I have running in audiobus. **

    Now, in LoopyHD, I can run really high gain guitar amp sims either early in the recording session, or later, and there seems to be no track bleed at all. I've done 5-6 sessions in the past two hours, and crossed fingers, it seems to be fixed.

    Now, why this NEVER HAPPENED in the past 6+ years I've been using this setup, I have no clue at all. But I assume that as it started recently, it has something to do with the ios14 update... and maybe something to call Michael's attention to. [ @Michael , have a quick look at this if you can!]

    Thanks so much for your thoughts. If it breaks again I'll jump back in here.

    Super best, Ed

  • uncledaveuncledave

    @edkeller Suggest you edit your last post to tag it @Michael , so he might notice it and take a look.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025