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.
Busted
Pretty much both IAA and Audiobus are busted, as In broke and damn near useless regardless of which device being used.
Any thoughts?
Comments
I stayed on ios 7 and everything still works. Are you using ios 8?
Busted, useless, broken?? Really? Minimal to zero problems on 8.1 here.
Agree with @thinds in as far as I seem to have less issues, less workflow problems and so forth, since 8.1 than I had just before -finally- deciding to upgrade.
iOS 8.1
Try simpler setups, if that doesn't work go back to standalone use of an app and copy and paste.
Really???..... I have no idea then. Audio Share as well. Apps drop out.
Sometimes all is good and sometimes not. 50/50. Well frustrating.
Yes, it is. We need to wait for apple to fix it.
It gets less wonky if I use less apps, like 2 instead of 5.
Yeah I'm having problems on 8.1
IAA works great inside of iMPC Pro.
Also apps work fine in both the input and effect slots of Audiobus. But once I insert Audioshare into the output slot I can't hear anything, though the meter in the recording window shows that there is a signal- just can't hear it..
@lala
Yup!!
I wonder who the idiot is that down votes stuff like this, just because you are surfing fine it doesn't mean everything is fine. Get a clue.
@CDB2 said:
that Sounds like a problem in audioshare ...
I don't use that, so no tips, u Need to talk to the developer of audioshare
r u on the latest version? I just looked there was a fix a month ago
A lil OT but I'm starting to be a bit paranoid about something physically breaking (dropping/battery etc) on my air 1 7.1.2. Everything is running flawlessly but should something happen (dropping in the toilet) I'd be screwed. Don't think I've been in a situation like this with gear before. I think I'll start looking for another air on 7 as a backup.
Just imagine telling the press that your band broke up because your ipad fell into the toilet!
@supadom said:
A light hearted observation from the perspective of risk mitigation....
You have do have a simpler mitigation strategy than buying a spare pad... Don't take the pad into the bathroom, risk eliminated. Just a thought
Cheers @Xen this piece of advice is no advice at all. Ipad in the toilet is an absolute necessity!!!!
P.s. Anyhow, just remembered that my 4yo has a mini retina still on 7. I just wasn't sure if I don't have to go to 8 in order to switch users but it seems like it shouldn't be a problem.
No issue here with AudioShare in either input or output on 8.1 AB 2.1.latest, Air 1.
I don't think it's "busted" overall, but things fail to work all the times for reasons I can't understand.
My #1 gripe is when I hook up an IAA app to either AudioShare or a DAW directly - the app will play no sound. Sometimes it even records data, but plays no sound. Stuff like that needs to just work - there's just too many hurdles like "BCKD AUDIO" defaulting "off" that seem to have no purpose other than to create problems.
Interesting. I wonder if I am perhaps a 'typical' user (as defined by Apple etc), by that I mean a regular schlub who doesn't reach as far as many of my brethren (and sisteren too) hereabouts. I'm certainly having less problems than before I upgraded, but then it's very possible that I tax my system less than many here do. Lucky for me (currently at least), but console yourself with the thought that perhaps I am attempting and achieving less interesting things...
Been doing some testing yesterday with the AB folks and an app dev that might lead to some eventual conclusions as to what the actual problem is - which appears at present to be an IAA issue (and hence an AB issue until IAA is fixed). It potentially affects everything that has been updated with the AB SDK 2.1 - so 7.1.2 apps as well as 8.X - and will likely not go away until Apple fixes it.
That's not to say everyone's experience is or has been the same. It will depend to some extent on the variety of apps one uses and in which combinations and on which power devices. Suffice it to say that what was working before isn't working now - on the same devices - and that that is something that got worse two months ago. The AB team is working hard on seeking a fix to it. Others are working with them to see the same result.
If you are not experiencing any problems on your setup, then, great! Make music ! :-) But many are and that continues to need addressing. Likely by a fix from Apple.
The safest most stable platform for iOS music making presently appears to continue to be 7.1.2 with older - non-updated-for-AB SDK 2.1 / iOS 8 - apps.
And in the setup detailed by @musicinclusive above, make sure you stay off WiFi as much as possible. Never going on it is the best choice. There are issues that crop up from WiFi usage.
Thanks for sharing this info @Musicinclusive and @AdamMatza1967.
To be perfectly fair, someone else (Ted) shared this video today - so - as I said above - not everyone is experiencing the problems depending on apps, combination, speed of device, etc.
A little OT but I loaded my set up onto my daughters mini retina and found the performance being a little sketchy. It runs but I had to up the buffer right away, stutters all over. I thought these two had the same specs.
Hard to explain. Wild guess, I use a system status app to make sure IAA didn't leave anything hanging around and I reboot before trying anything. When I load an effect I put it immediately in bypass mode if available then turn it on after the rest of the scene is loaded.
I also don't use the internal speakers. It's headphones or monitors for me.
None of this may mean a thing over this very puzzling issue. People I really respect have problems so I do not suspect user error, in most cases. But this stuttering, silence bug is so prevalent that maybe people overlook the obvious solutions that they used to try before this iOS 8 challenge hit.