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
Well, let’s hope they do fix it, quickly!
The more noise people make on social media, their forum, Amazon reviews, here, etc. the faster that'll probably happen.
I hope people are contacting Apple and reporting the issue.
Perhaps someone on Twitter could post something ?
Why? Even if the problem is with something Apple did, which I tend to doubt at this point, Line 6 has the much better path to the people at Apple that can help. It seems that Line 6 is aware of the issue now (even though they should have been during the beta and warned people like many other companies have). Really, it seems that the only thing people can do now is wait a bit for some more info to come out.
The reason for contacting both Line 6 and Apple is that oftentimes bug fixes get prioritized based on the number of customer complaints they have.
According to Line 6, the bug is in Apple's driver. That may or may not be true, but if it is, the more actual users that Apple hears from, the more they are likely to care. From past experience, both inside and outside Apple, if a developer reports an OS issue, the priority of addressing the issue is influenced the number of affected customers they hear from.
People should, of course, also contact Line 6. The amount of effort that goes into solving a problem is influenced by the number of people that express a need for a solution.
From what's been said in this thread, it really doesn't sound like it is with the audio driver. The work around of going through the powered CCK makes that seem unlikely. If it is a problem that Apple introduced, I'd guess it is more likely to do with current draw or something like that. But really, that's all pretty much baseless guessing on my part.
I agree with you that more complaints is good. I'm just suggesting that getting Line 6 and thus Yamaha (and every other subdivision of Yamaha) complaining to Apple more loudly is probably more effective. Put it this way, if just customers reported the bug to Apple and they couldn't cross correlate it to other similar devices and they didn't hear from Line 6 directly, there isn't much they could actually do about it. Even if it is a problem that Apple caused, they are going to have to solve it together.
13.1.1is available wonder if that one fixed anything. Cant test here for now.
From the update notes:
Downloading it now on iPhone SE, will report back later.
UPDATE: Still not working on iPhone SE or iPad mini 5 on 13.1.1.
Searching online I also can’t find a USB version of the Sonic Port cable, only Lightning. If anyone is aware of such a cable please share a link. Thanks in advance.
There is no usb cable for the sonic port. Only for the sonic port vx
Well line 6 haven’t changed the firmware on the sonic ports so it’s not something they have done, the problem is only evident in ios13 therefore logically it is a result of something Apple did. Apple have a perfect path to all users by fixing the bug they introduced in ios13.
Apple made a change in iOS 13. If they introduced a bug or exposed an already existing bug in the Line 6 firmware or software, we don't know. If the Line 6 software or hardware were doing something out-of-spec and the update exposed this, it's highly unlikely that Apple will do anything to fix it on their side.
More importantly, wherever the fault is, it's going to be Line 6 that has to initiate the debugging process. They are going to be in the better position to attach the debuggers to their hardware and trace where the issue starts. Apple isn't going to be able to do this. I'd imagine that Line 6 have already started doing this. The big question that I'd have is why didn't they do this during the beta process. And why, once the issue was discovered, and it was reported on their forum during the beta, didn't Line 6 put out a warning to its customers not to upgrade like every other vendor does when there are issues exposed at a major OS update.
Still waitin for Line 6 to react...
So far the only comments and deductions were made by their disapointed customers...
Has anyone that has the VX tried powering it with the included USB cable to a USB charger and then connecting it to the iOS device with the lightning cable?
Looking at the line 6 forum, it seems members reported the issue during beta
According to Line 6 forum, the issue was known at the beta stage and quite some time ago at that.. A developer has now joined the conversation over there.
@Wrecked Do you have a link to where line6 have joined their forum discussion?
Line 6 haven’t joined the discussion as far as I can tell. Here’s the link to one of the discussions
https://line6.com/support/topic/50210-sonic-port-ios-13-ng/
Thanks - what did you mean by a developer has just joined the conversation?
It seems an iOS app dev? joined in, last reply on page . I assume that what he/ she is?
Perhaps changing something in the settings of the Mobile Pod app might help.
Thanks but I dare not update to 13 at this time. There’s a Yamaha music school down the road from me, I went in sometime ago and they were using iPads etc. I may go down there tomorrow and ask the teachers etc about it, Maybe they can get through to Yamaha and report it. Do any of you think that’s an idea or a waste of time?
Line 6 told me they’d submitted a bug report to Apple and are waiting on a reply. That was back on Monday the 23rd. Maybe we could bomb the Apple support line: tel:1-800-275-2273 in the USA. Developers have an app to report bugs, I don’t have such.
Well that’s something positive I suppose. We’ll see. Well done for getting some info off Line6. Not to forthcoming by looking at their forum.
Been messing with sonic port into GarageBand IOS 12.4.1. I don’t use the mobile pod app a great deal but I was interested to see if it works. It appears it doesn’t as in IAA through GarageBand. It works as a stand-alone app. Also noted some odd behaviour when using sonic port as in cutting out, stoped working. Hard reset, worked then it went again, now back working.
Mobile Pod app crashes when Sonic Port is plugged in on iOS 13.1.1 on both iPhone and iPad.
On a side note, I just realized there’s no more search on my home screen...no settings seem to bring it back either. That’s an odd feature to remove.
About search: had the same issue a few hours ago, BUT found it is not gone! Just, on the home sreen: swipe your finger down from anywhere as long as it is not completely the top, and there is the search bar.
Edit: works also on other screens, so it is more easily available then it was in previous ios versions.
@Marcel Thank you!!! I thought I was losing my mind for a minute.
Anyone tried updating their IPhone?
Does Sonic Port work now with the latest IOS update ? How bout mobile Pod -which is sold with it-, Is it still broken?
I’ve checked their forum and Line 6 remains silent.
All I read is complaints and people trying to reach them without success.
The support from Line 6 is inexistant.
Why so?
It gives me the impression that they want to wash their hands of this.
You can’t lie to customers and sell them products which do not work anymore: That is ILLEGAL !
According to the line 6 forum the new update does not work with sonic port. And yes, the units are not fit for purpose and should be withdrawn immediately, including their other products that don’t work in iOS 13. I may get the irig hd2 but does that work with iOS 13?