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
@iamspoon I managed to recreate what you described: two Hammerhead instances with the same beat, only one processed with Tails, going out of sync (Tails reports no latency). Interestingly, selecting a buffer size in AUM (even the same one already selected) fixes the issue for me: the beats are in sync again and Tails reports the latency. Can you give this a try?
@trickyflemming this happens to me consistently every time I insert a new instance, maybe there's something to investigate here. Another plugin with latency (AU3FX:Push) reports it right away without having to reselect the buffer size.
Came to report that the AUM switch buffer size or starting the playhead after switching fixes it for me. I assume you’ve been more thorough, so it’s prob the buffer size selection and can confirm that your way works in AUM, for whatever technical reason.
thats the first daw that i go and check every app that i buy because it my main use daw, and they all do show there and all of them go by UA before their names….
and about the cpu, you can look at this screenshot that the cpu it all over place, and tails its there by it self no other auv3 fx or instruments in there just Tails by it self, hopefully it can get fix because this has become my favorite ios reverb for iphone, not only because it sounds texture but because all its special features, and i do got all the reverbs for iphone but tails its the one for me
it would be perfect to have an LFO or two on LoFiAf
@SLPGroundSoundMusic when you say that the CPU is all over the place are you referring to the
LATENCY 100.0 mswarning? The CPU meter itself doesnt seem unreasonably high@oat_phipps yeah I noticed that the transport sometimes fixed latency reporting but wasn't repeatable for me, unlike the buffer size setting which always worked
also it would be great to have LFO on Needlepoint to automatically control few things and with some type of a 8 bar step sequencer that can automatically activate and deactivate the spindown and broken buttons for example at which ever step on the sequencer
actually it be all over the place, but because it was a screenshot it took right there here is another two screenshots and like i already mention there is no other auv3 fx or instruments in there !
also needlepoint has the same problem, it comes and goes and when that happens even the virtual record that is spinning stars to go in slow motion when the cpu starts to go on red, and thats also with just needlepoint by it self with no other auv3 fx or instruments
me
and if look at the screenshot cpu meter you can see the red line, which it’s actually keeps jumping back and forward, and im just testing it with NS2 Slate startup drumkits and thats it
At lower settings the randomiser, in Silo anyway (haven't checked the others) seems to work like a mutator i.e. it adds randomness within a range of current parameter settings, for numerical values anyway.
Not sure what DRIFT PREVENTION is, though it might keep the values within a certain range of the starting value, rather than a more Brownian, or "random walk" type randomisation where the value can eventually end up far from its starting value, even if it does so in small steps.
I think it defaults to 5 which is very low on the scale available so it would appear to work like a mutator.
this is just needlepoint the on the slate fx slot and no other auv3 fx or instruments on there
Ah yes, maybe! So I guess there are a few things worth reading the manual for that aren't covered by tool tips after all!
can the developer make LoFiAs a bit bigger for NS2 i really enjoy it, plus it not that bad on cpu as Tails and Needlepoint but it is to small to see and for adjusting the buttons
Did not read the whole thread, but the latency will soon by fix I guess? Was on my way to buy a couple of apps.
@SLPGroundSoundMusic understood! That does look like too much of a CPU hit
To be honest, I was looking forward into diving into the manuals to see if I could learn a little more how they work, but the manuals ARE the tool tips gathered on one page, that’s it. Which is totally cool, each parameter is clearly and tersely defined and the tooltips themselves are so well done it’s nice to not have to switch screens for a manual at all. Just a lament from one of those dudes who really likes manuals and cares about that stuff. It used to be (and still is fun!) to glean bits and pieces here and there where & when available instead of having no base to begin with and cracking a general Music Coding for Dummies book and reading from excruciating beginning to end.
There is a low latency mode coming from Tails for sure, quoted from the dev.
Based on their timely beta update schedule, I imagine they will also sort out anything that can be sorted on their side re: latency in a pretty timely manner. As I recall, there was a Drambo problem (due to it not having latency compensation? Or something) that was causing some of the earlier reports.
But if it’s the sort of thing that’s gonna drive you crazy, then just wait. The sales prices last through the new year til January 2.
I'm not entirely sure I understand what you mean. You're saying that if a plug-in adds latency, it won't matter whether it's in use or bypassed? That's interesting. I can't actually think of another plug-in where this has happened in AUM, so I have nothing to compare it to.
Yes, exactly. A simple test for me is using a guitar input and AU3FX:Push which can be configured with up to 100ms of lookahead, but other limiters, compressors or transient shapers with lookahead exhibit the same behavior. Enabling or disabling the plugin doesn't affect latency, while removing the node outright does.
I love Silo - this is such a powerful tool for a wide range of effects and it’s a lot of fun to explore and mess around with it and come up with a wide range of different sounds,
However, it seems to be a real battery guzzler. In about an hour of use in AUM, I realised my battery had dropped from 100% to 22% and this is very unusual even with sets with a whole bunch of apps.
In my experience of this happening with other apps, this seems to be more to do with the display of the GUI e.g. refresh rates, or whether the entire GUI is redrawn at the screen refresh rate or whether it’s just the region.
I tend to find that high CPU demand doesn’t tend to drain battery as much as it causes CPU spikes. Apart from one time when CPU went up to 85% in AUM (with everything cranked up), it’s not adding more than about 20-30% to AUM processing (on an iPad Pro 2017), I don’t think it’s a CPU thing, but more likely to be to do with the GUI.
I will test and compare battery drain rates with the GUI open vs GUI closed and see if that’s what it is.
Is anyone else finding battery draining more quickly than usual with any of these apps?
Don’t need to be clunkin up the joint. Map the knob or draw automation curves depending on your DAW. Surely this can’t be that much of a hassle
can i map the knobs and draw automation for auv3 in Nanostudio2 ?
Oof, sorry about that one. The developer had great intentions and a road map and everything, then he jumped in a space shuttle and flew off and that was that. Sorry about that; I would’ve liked it, too. But generally, that is a DAW based thing.
If you are willing to work with audio, try apeMatrix by apesoft. You can presto change-o add an LFO to ANY mappable parameter on any instrument or effect app in like 2 seconds. If you already knew this, then sorry. And sorry we all got short-stuffed on NS2.
same here, i actually noticed it more with needlepoint, i guess because it was the app that i was spending more time with checking out the presets and playing around with the knobs, when i started using it my battery was around 70% and around 25 minutes later my battery was already at 20%
yes i already knew this, that is way i say that it would be really cool to have an lfo in lofiaf
because even though ns2 developer got lost or maybe the shuttle got hit by some comet or just maybe he crash a tesla satellite on the way to space, which is probably the reason why twitter lost its feathers, but anyway i still enjoy ns2 work flow and everything about it, but maybe some other developer can travel to space and find the blip secret coding transcript blipping around somewhere in space, so he or she can bring back home the coding like ET so we can all keep getting stuff with some more ns2 creativity…. wouldn’t you agree ?
Yeah I feel pretty confident they'll fix these latency issues in Tails and Silo.
Right, that is a good point, and thanks for the heads-up on the bundle. Not just UA, there are other apps I want as well, like Tal. I passed up on Tal last BF when the price was lower, but now suddenly I want it.
RE latency ... the first time I tried Silo in AUM there was noticeable latency, but after restarting AUM, it seemed back to normal. I am running at 1024 buffer size on an older iPad Pro so some latency is noticeable, esp with percussion.
However, I've also had this scenario with other plugins, where a significant latency disappears after restarting AUM, or perhaps the iPad in some cases.
Not sure if this is related to the latency scenario others have described?
@trickyflemming Loving these plugins ... esp Silo so far ... definitely on the purchase list.
Is the battery drain something that could be looked into? In my experience with similar scenarios it seems to be GUI rather than audio processing related in my experience, but you know your code
My battery drained from 100% to about 40% in 40 minutes which is very unusual for my setup, even with very plugin heavy setups, if my CPU load is too high I will get CPU spikes/audio dropouts but not battery drain at this rate.
The AUM set in question only had 3 plugins: Silo, Pure Piano and SB Drum Computer, the latter two of which never cause battery drain issues for me.
Thanks