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
it seems not only BramBos but generally the lighter weight synths are doing OK in AUM, I can load ten instances of Viking for example but only a few of Kaspar
Audiodamage stuff is incredibly light though. My air 2 can do 12 of phosphor but the pros stumble at 4. I just hope it all gets sorted soon
Just bought a 10.5", running 10.3.3 and was getting worried reading this thread! This was a quick test in Auria; 10 instances of Phasemaker, 3 of Laplace, 1 Tines, and 6 Lyra (Grind on one of these Lyra tracks, and Quatromod on another). Also had four instances of AudioReverb on sends, all actively processing. Each of the 20 tracks was playing back the identical MIDI data. CPU was running pretty high, but no crackles or glitches. I'm happy with that as, in all honesty, I would probably be freezing or bouncing tracks in normal use on anything with 20 tracks of instruments!
Doing the same test with iSEM instead of Phasemaker, iPad Pro 2016 9’7” 256 GB: the upper limit falls to only 10 tracks inside Auria Pro before it becomes unusable. Since iSem is a behemot, I think that’s expected and actually a great result. Cheers!
Your 9.7 isn't the same gen. The issues only apply to a10 CPU. No need to test more.
Should this AU issue be in a separate topic from this one
problem with latency and digital noise?Just a suggestion, but perhaps we should stick to the latency problem in this thread> @drez said:
Yes. Please.
WTF?! I'm happy to drop this altogether and stop wasting time with this. Someone asked several posts ago if anything else has progressed. I reported I hadn't noticed any more issues with noise and latency now that I'm a couple weeks in. @gonekrazy3000 asked about the AU usage, so I did what I thought was going to be a quick test as a favor since he's helped me out before.
So there. I'm out. My 10.5 serves all my needs just fine. Maybe someone else with a 10.5 pro and has the time to beta test all this can take over from here.
Buh-bye, good luck and cheers
Nothing wrong with pointing out a thread that is going in a different direction than the topic. Your work has not been in vain, but simply suggesting that it goes to a dedicated thread. This way people would see the topic and go
Oh yeah, I'm having AU issues in my ipad pro as wellinstead of not finding it because its in a thread aboutlatency and digital noise. Appreciate your efforts responding with testing the AU issue, so I was suggesting it not go to waste 10 pages into a thread that has nothing to do with the topic. This AU issue sounds like it will be multiple pages worth of responses so it seemed like the right forum etiquette to suggest. I guess I was wrong, so do what you want /shrug.Ahhh!
A new beta of iOS 11 just arrived!
Beta 6... Hope it can bring me back Beatmaker 3 and Auria Pro on my new iPad Pro 12.9”...
Are you upgrading? Or is anyone brave enough to test? Looking forward to results. Nice to see this thread active again btw. Been using my K-mix interface lately with no problems btw, just to update my situation.
BM3, Auria and Audiobus still crash in beta 6.
Fuck fuck fuuuuuck!!
Still unable to execute both Beatmaker 3 and Auria Pro.. :-(((((((((
>
If it's of any comfort all the crash-logs will be forwarded to the Apple _and the app developers
But since iOS11 is not 'final' yet do not expect any instant fixes...
(At least one of the BM3 developers has iOS11 installed on one of the test-devices so I trust that once iOS11 is 'final' it will work properly).
FYI/Update: mentioned earlier in the thread that the only evidence of any "latency" I was experiencing lately on my 2-week old 10.5 Pro, was a very slow lag using a stylus with the graphic app ArtRage.
This evening they updated ArtRage to specifically address this on new Pro iPads. I just updated the app and it's indeed been fixed. No lag/latency.
So, I'm no longer experiencing any latency or noise/crackles, etc. at all anymore. The AU loading issue appears to be software related.
I still get the latency and audio degradation all the time
The restart replug can get me maybe an hour until it starts again
Buying a nice audio interface soon but honestly for me This has stoped me from going full force on music right now. Hoping iOS 11 rollout goes smooth and this shit gets fixed. I seem to maybe have the issue more than others tho.
I'm starting to think the 10.5 pro doesn't have whatever problem is affecting the 12.9. You can clearly run 2-3 times more Au/iaa than the new 12.9 can.
I can run a seemingly infinite number of AUv3 in AUM, so this isn't exactly accurate.
Are you on the 2017 12.9 ? If so what iOS ? Which au ?
and which iOS?
I think they're about the same
he can run upto 6 instances of quatromod without bombing out in AUM. meanwhile the 12.9's struggle with more than 3. its not a question of power. its something in the code.
Unfortunately it looks like it is a question of power, or rather, AU memory limits interacting with the enhanced graphics in the pros (a bigger problem with the higher resolution 12.9). See the other thread:
https://forum.audiob.us/discussion/20439/trouble-starting-several-au-instances/p3
I've posted this information several times already.
Chris Randall of Audio Damage has stated that these issues are caused by 'RAM allocation bugs'
I spoke to Chris personally a couple of days ago and he also said the same thing.
His words about the iPad Pro 2 - 10 and 12inch
"My friends in the business are of the general mind that the 12.9” is a bit of a dog, and that Apple pushed the platform a little too far. (That’s why I didn’t get one to begin with.) So I’ll be honest; I’m not going to lose sleep over this. I just stacked 30 AD plugs in AUM on a Mini 2. Of course, the CPU meter was pegged and crackling like a bitch, but they all still worked. This is going to turn out to be a RAM or GPU issue of some sort, related to how JUCE plugs are built and are thus something I’m almost certainly not going to be able to do anything about it. The best I can say is that I’ll have a look at it and poke around in the allocation, and maybe come up with something."
About the hardware...
"The graphics architecture is the same, but it has to push almost twice as many pixels (3.3 million versus 5.9 million.) So that’s a lot more math that has to happen on the same hardware, and a lot more RAM being vampired from places it’s actually needed for something besides doing screen animations at 120Mhz. Like, I say, hosting audio plugins. Just as a for-instance. So a 12.9 will be noticeably less capable than a 10.5 at the same tasks.
But all that said, this smells like a firmware problem to me and is almost certainly RAM-related. Hopefully, Apple will acknowledge and fix it. iOS 11 is just around the corner, and it has a full AUv3 rewrite, so hopefully, the problem will be solved for me.
Could this possibly be helped by lowering the screen refresh rate?
Didn't work for me.
For me on 10.5" its definitely something to do with the way jack connections are understood by software or more precisely, as somebody mentioned, firmware. No problem in iTrack dock (Lightning connector).
iPad Pro 12.9 1st gen user here. I've had the same issues with the headphone jack on my device for two or three months. Doesn't just occur in audio apps either.... YouTube does it. Switching apps makes it stutter horribly and sends CPU cycles through the roof in AUM… This is a leased device and still has AppleCare active. Should I pursue exchanging it or is it the OS?