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
I got that impression from your last post that you think the problem is solved ... but I can’t confirm this for my case for example - and I also had the impression other users still report less performance stability compared to the situation “before” the update -
Sorry I tried that before and did it again ,just not working. Can you let me try the beta test version please?
As stated before in the thread by myself...
“Performance has unfortunately worsened here.
Device: iPad 2017 base model
IOS 14.3
I just made a project in NS2 using three instances of Model D 1.3.1. It played back at around 85% CPU with no crackles using the NS2 high latency buffer.
I then updated to Model D 1.3.3, rebooted my iPad and now the same NS2 project stays at 100% and completely crackles.”
Hate to say it but I get a ‘yah we’re done’ corporate messaging vibe. They probably made changes to benefit the majority of users moving forward on more recent and future devices but for those on ‘older’ devices (four years or more, or maybe base models?) they tried their best, but sucks to be us. Welcome to the future?
It is a new platform that has yet to mature in many ways. This reminds me a bit of how desktops were in the mid/late 90s where a computer was seemingly ‘out of date’ every three or four years. I recall issues with VST updates when they first started too. Loading up old presets and they sound all wonky, projects ruined etc. Anyway, dust more or less eventually settled there it seems.
I got a touchscreen monitor as a test for future tablet life. So far the Maschine software works not too bad as touch but there are a few sliders that are way to skinny. I hear Bitwig is good. Tried the demo on mouse/keyboard once. Maybe now that I have since wiped and reinstalled my computer I can try it again in touch mode.
Yes, the same here. For live use I'm use low latency, as possible. For example:
1.3.1- one instance @64 samples (with some other apps + AUM + Keystage = no problems, 60-80% of DSP everyting.
1.3.3 - one instance as the only app in AUM @64 = no way! works @128.
Model D as the AUv3, iPad 2018 (6th gen)
I think, this shows the difference like in previous comment..
Greetings
@MoogMusicInc
iPad Pro 12.9'' 2017, IOS 14.4.2
Buffersize 1024
1 instance 30-39%
2 instances 60-90%
3 instances 90->100% spikes
Where I before the updates could load 3 instances without any spikes , now it's limited to 2 instances.
Wish I never did the update.
Would be very sad if this would be the final result of this AUV3-CPU-Optimization-Update ...
@MoogMusicInc Is it?
And if its the final outcome ... that older devices not only do not benefit from this so called optimization but get a “downgrade” performance-wise instead - then this should have been communicated beforehand at least - so that a user of a such a device could have a made a conscious decision about updating or not ... at least ...
But lets not give hope here - maybe it can still get sorted out by Moog - I deeply hope so ,,,
Here is a video of the problem which I am facing with the update of Model -
IPad Pro 2017 12,9 - IOS 13.7
AUMSession - buffer: 1024
ModelD - Version 1.3.3.
Two instances of Model D running smoothly around DSP 30-45% with both AUV3-windows closed - as soon as I open the UI - I get spikes up to 110/120% and instant crackles
Video:
https://streamable.com/gzjc22
The interesting thing is - sometimes these UI-related crackles even happen at a DSP of around 80-90% (not in the video here - but maybe of interest for trouble shooting) - never experienced this with any other app ever.
Hi AudioGus,
That is in no way our intent. We're still testing with iPad Air 1 from 2013 and the performance there and on our other dozens of test devices, is back to before the oversight in 1.3.2. The sad reality is that it's impossible to actively test all possible combinations of devices and iOS versions, as well as DAW combinations. Once we update a particular device to a later iOS version, we can't get it back to an older version and test on that.
The reason why we communicated that it's safe to update, is that we actually backed out all the audio engine changes for v1.3.3 and went back to the audio engine of v1.3.1. Now there are other things that come into play, like the Xcode version (Apple aggressively makes us update that too with compiler changes), iOS version differences, specific iOS CPU heuristics that only occur is rare situations and often stabilize later, and so on. We're continuing to look into improving performance, but as mentioned, the changes have been reverted.
We've re-enabled the TestFlight link for 24 hours so that you can try it out. Please note that this is the exact same binary as Apple distributed through the App Store. Hope it works for you.
Hi Bon_Tempi,
Here's the behavior on our oldest iPad Pro 12.9 inch from 2015 (model ML0N2NF/A) running iOS 14.4.2. We don't have the 12.9 inch model from 2017 but have the one from 2018 (model MTEM2LL/A) and that one opens up a lot more instances in a stable fashion.
... and here's a video of the UI behavior on the same 2015 iPad:
https://app.box.com/s/xdihknbbwj8yrzprm4wnm22gzcfzy117
Can you please try offloading Model D and re-installed the latest version from the App Store?
iPad 2018, same problems with the new update. Reboot and re-installed.
2 instances, a few crackles, lagging and 95% CPU
3 instances, crackles everywhere.
Nop, is not working like before.
Can please you double-check the version number in the app?
Thanks for the clarification. I guess this can be chocked up to the continuously evolving nature of the platform. Not much Moog can do about that. Thanks for trying! Bye Apple!
@MoogMusicInc, kudos to you and your team. Really stand up response. Much appreciated.
Hi - thanks for getting back at me - and providing the informations about the behavior of your 2015model.
Really weird and irritating - don’t know what could cause such a difference - I even deleted Model D and set it up freshly - and I get the same result -
Basically not even a single instance of Model D is working correctly as soon as anything is added in conjunction to play a long with ... as this video shows:
Video:
https://streamable.com/hsib0w
Can this difference be caused by IOS 13 vs IOS 14?
Is there anything in the new versions of the app which requires in a mandatory way for IOS14?
Hi Bon_Tempi,
We've not changed anything in the supported platforms or targeted versions, nor added any code that would be iOS version specific. We just did another test with FugueMachine like in your test, on our 2015 iPad Pro and we can't get the audio to stutter, even when opening the UI of both Model D instances and FugueMachine, closing and opening continuously. The UI of Model D does get a bit sluggish being dragged around, but the audio is not impacted.
Could you provide the exact model number of your iPad? Maybe we have an alternative iPad in our collection with the same CPU characteristics.
We know this is not of much use for you, but we did another test with the 2018 iPad Pro 12.9 we have at 512 buffer size in AUM, and it also seems to behave just fine with the current App Store version of Model D :
https://app.box.com/s/65fu92ya6vornb8xwa7fzi9yypwcnoi6
@MoogMusicInc , I don't know if you have an Air2, if so can you test the sessions ?
other users mention the performance is worse know so I haven't update yet
Just have to say thank you Moog. As some here had already stated, one of the best communication on the Plattform. One reason why I love iOS music so much.
One could say that the current version behaves just fine on my 2017 base iPad. I mean it is usable, particularly when starting a project from scratch. The ceiling is just a little lower now. Previous projects that used Model D will now require a bit more CPU and that could push them into stuttering territory where they were not before. So the only option will be to now free up resources. This just reaffirms the iPad for me more as a disposable sketch pad, where the sooner audio is exported and moved to desktop, the better.
Good luck to you if you decide to move to Surface. I was thoroughly unimpressed with it.
Thanks for sending those sessions, we haven't got an Air 2 on iOS 12, but we'll test with iOS 14.4.2 and report back.
When you say “2017 base iPad” what does that mean exactly? Is that the 9.7” iPad with 32 GB of storage? And how much storage is left on the iPad? Do you have a lot of files? I have a Pro with 128 GB of storage, but less than 10 GB of space left. I definitely cannot run large files anymore until I get a new model to replace it.
duplicate post.
Moog FYI
Model D 1.3.3, all buffer sizes, iPad 2018 128 GB, iPadOS 14.4.2, crackles in both standalone and AU (3 instances in Zenbeats). No problems before updating.
Regards,
DMfan🇸🇪
Try increasing the “Preferred Audio Buffer Size” for that specific app via your iOS Settings.
Crackles regardless of buffer size unfortunately, tried them all. An app restart fixes it in standalone, but as soon as I use it as AU again the crackles start in standalone as well.
😔
Hmm. I presume you’ve also done a force restart of the device to clear out memory?