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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
Ha! I'm proud of myself. Called it within reading the first three sentences of the initial post!
(about 5 posts before I finally realized the thread is four years old.)
Cables can do weird things like that. Working well on one device and not another. It could be simply that that the iPad6 needs to draw more power than the iPhone.
But ... the reason I dropped by is to suggest checking the input jack on the iPad. It's easy for dust or lint to get in them, causing poor connections that push a marginal cable past its limits. It might be worth shining a light in there to see if you can see any obstructions and to try blowing the port out with some compressed air.
Thanks for the update. 😊
Wow. How are you?
I have exactly the same problem happening to me very occasionally.
Pro 10.5 with Zoom U44 but generally AB restart cures it so not so sure it is the dirty plug’s fault but I guess it doesn’t hurt to lub that joint.
Just to clarify. The noise that creeps in and gradually destroys everything is kind of decimated delay sound? Is that it? Because this is exactly what happened to me.
First I thought it was ToneStack but then it’s happened without it in the chain. I’ve even gotten in touch with @Michael about it but it hasn’t happened since.
I also get over 200% on audiobus cpu meter while this is happening. It is some kind of feedback loop.
Here’s a video
https://drive.google.com/file/d/1-k-fUVXC8YZZUWRSC0tlzSs4zyusoUt1/view?usp=drivesdk
Yeah, in my setup it would start with a pop/crackle or two... then the audio would slowly get more and more distorted... until it was a "garbled mess"... but it's true if I left it long enough in this unusable state... it would often switch over into clear audio again but completely delayed (again totally unusable since the delay/latency is relatively huge... something on the order of 1 sec or such).
My setup uses the Apple USB3 Camera Adapter, and a lightning extension cable (I was actually using 2 in serial to add length to the cable), so I can have the iPad6 mounted higher up on a stand. So this setup worked fine for approx 6 or 7 months... even with the 2 lightning extension cables in series. I should mention they're probably not the highest quality... purchased on Amazon, but Apple doesn't make an official lightning extension cable, so there's not many good options. I've gone through a few of these cables now... it really should have been suspect from the start, but what would happen with the older cables when they'd fail, was simpler- the connection would totally break... or switch in and out.
In my setup, I'm near certain it's not a random lint or dirt in the port issue (though sure, I bet that might also cause this problem if there was an obstruction in the port), since it started happening VERY consistently at the end... happening the same over every session I started/restarted and over many days of connecting/disconnecting the iPad.
I'm fine. What a blast from the past to get an update to an Audiobus bug.
I'm sure you've already done this - but for completeness sake - the CCK ports should be checked for obstructions too.
If I understand correctly, the lightning cable must be for power, then you're connecting something to the CCK with a USB cable? You're sure the USB cable is good too I suppose (probably far less likely to fail than a 3rd party lightning cable and extension). I don't know how far you need to go, but there are fairly long lightning cables available. I've had good luck with Amazon Basics cables ... ymmv of course.
You could be right. I actually hadn't done this, as I'd never had a problem with it before (in the years since the beginning of iOS audio pretty much)... but I air-cleaned all ports for dust, isopropyl-d the connectors, and set up my system with the same cabling as before.... and... at least for the moment, it's working without the audio degradation! If it was a dust/lint problem, it was probably trapped in the Apple adapter area, since I more rarely need to mess with that connection.
I won't totally call it yet though... I had moved the suspect cable around quite a bit in the interim, and you know how defective cables can get... one position they're totally fine and another they just ain't.
The problem here... and why I want to use the lightning extension in the first place, is that it makes the setup simpler, less of an eye-sore (as only a single cable reaches up to the iPad on the stand), and reduces wear and tear on the Apple adapter (since then the adapter itself doesn't directly need to be plugged/replugged constantly into the device).
@wim have you in the past had this "garbled audio" problem then? Specifically, with clean audio for a while that slowly gets worse and worse?
Overall, I'm just crazy relieved it's not a problem with the iPad, interface, or software... and for future reference I know to check the cables for defects and their connections for obstructions. I still conceptually find it a little strange that the audio is totally normal for some minutes then slowly degrades like this, and that dust/lint or a degrading cable can cause this, but this has been made very clear to me now.
If I end up finding more fault with the cable, for example if the cable ends up in a different position and the problem clearly returns, I'll post the results here again, just so we can get at a resolution of whether this is a defective cable or port obstruction that causes this.
Hi @thenonanonymous - no, I can't say I've had the problem you describe, so anything I say is just guessing based on general experience with troubleshooting and signal strength, etc.
So, now I think I understand that the extension cable is between the CCK and the iPad. That makes more sense to me. My guess is Apple designed the CCK assuming that the signal path to the device would only be a few inches. If so, then it's possible it is just really sensitive to any signal degradation between it and the device.
The next most logical thing to try if it happens again is to temporarily use the CCK right into the device without the extension cable. If the problem doesn't come back, then you have isolated the problem. If it does come back, then you move on to the next most likely suspect. "Eliminating what it's not." is a slow but effective troubleshooting process.
Yeah that thought crossed my mind as well. I wasn’t sure if the extension cable was going to work when I first tried it... but it did work fine... for 7 months.
An update- the signal degradation came back yesterday using my old setup, therefore I can rule out the dust/obstruction issue. My next course of action will be to replace the 2 lightning extension cables with brand new ones and test that through time. I’ll update again later if I find out anything interesting, but as it is, I’m going to conclude that this whole slowly-more-garbled-audio issue was caused by a slowly degrading lightning cable.
The way to categorically rule it out is to temporarily not use extension cables at all. Even though it messes with the aesthetics, it will tell you a lot. If it comes back with that setup, then you know without a doubt that it's something else and won't waste money on cables you don't need. If it does, then you know where the weak spot is and can think about ways to improve that.
Coincidences happen all the time in troubleshooting. It can look for all the world like something is the cause, so you make a change and the problem goes away, making you sure you've found it ... but it was just a coincidence. The surer you can be that you've actually nailed down the issue, the better in the long run.
Just a suggestion.
@wim yes I’ve already tested without the extension cable, and the issue totally goes away (it’s going on 2 weeks of testing without fail).
I am greatly summarizing, leaving out many testing details in order to make this easily readable, in case anyone else runs into this problem and finds this thread.
Great. Thats good that the issue is definitively nailed down. 👍🏼
Nothin' worse than an intermittent problem.
Agreed. 👍