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.
Does Apple still do any kind of QA on their updates?
Rant, ignore! But I find it quite astounding. Just updated my 2017 iPad Pro 9.7" from iOS 15 to iOS 16 (no jailbreak, no odd stuff, plenty of ressources free, not a lot of apps installed)
1) the "onboarding" screen freezes when tapping "Next" without any kind of feedback
2) some new "Developer Mode" has to be activated to be able to run your own apps
2a) how this ominous mode can be activated it elusive, as in the "Settings" app there's 0 results for "Developer Mode"
3) after the forced reboot after "Developer Mode" activation, the keyboard doesn't come up at the password prompt (years old bug)
3a) but NEW: the keyboard doesn't even come up when tapping in the password field.
4) after another reboot, the keyboard finally comes up when tapping into the password field.
5) another attempt at launching my own apps again brings the "Developer Mode required" error
6) diving into "Settings", "Developer Mode" has magically turned itself off again. Turning back on and trying another reboot.
7) after the reboot, ANOTHER dialog appears asking me if I REALLY REALLY am 100% sure that I REALLY want to activate "Developer Mode". I confirm.
8) I have to enter my password AGAIN (this time though, the keyboard works and does come up automatically! Stunning)
9) Trying to launch an app again. It works, but audio is crackly during UI updates. Maybe this has to do with the background processing after an update.
10) Web Audio is essentially unusable, extreme crackling as soon as there's any kind of display update activity
Yeah I mean... I'm frustrated anyway recently but I do find it odd for the richest company on earth to have these kinds of QA problems with their main software platform!
Comments
But...but...new emoticons to play with! (probably). Hooray!
I froze my iPad on 13 ages ago where everything now always works, guaranteed, no disturbances, and it's all I need to produce what I want.
What annoys me these days is that my stuff like this can be broken and rendered useless by OTHER people at any time, out of my control. Back in the day, you bought something, a tool of any kind, you looked after it and it continued to work exactly as it was meant to for many years. The only way it could be broken was if you lent it out to a stupid Gorilla or were heavy handed with it yourself.
Now stuff relies on a host within a host within a host, all being maintained (or not!) by too many other people who have to keep fiddling with their stuff to keep up with all the other people constantly fiddling with their stuff in an effort to still keep everything working, when in fact it worked fine enough in the first place.
Yes, 12 new emoji! First line in the ChangeLog! (no kidding)
Regarding the constant updates: Yeah, that's another one of those "illnesses" of the past few decades that I don't fully grasp.
I mean, progress is good and quick progress is better I suppose, but it's evident that software makers have come to rely on "ah we'll just ship an update when stuff breaks" a bit too much and quality control has suffered as a result.
In the past, software HAD to be shipped (on physical media, at a huge cost!) essentially bug-free because there was simply no feasible way to get even a minor update to customers. So there was loads of testing and quality control.
This was arguably better than the current approach because less updates ALWAYS means less breakage, even if the updates are "supposed" to only contain bugfixes. Fix one bug, add another... you know how it goes.
Where it's even funnier is in the realm of programming languages. Those now essentially also get updated daily like underwear. Like, "This script requires Python > 3.4.19 but < 3.5.3". WHAT? Same with "Swift". This is a tad ridiculous.
A programming language also doesn't have the problem of having to adapt to a changing landscape. Programming is a relatively "static" art form, so it doesn't need to be "updated" all the time. When a programming language like Python or Swift keeps releasing updates by the day, it just smells like "bad design" (OR "feature creep"!).
Design it well ONCE, then let it be a standard for decades (like, I dunno, C!)
For anyone else suffering from the Web Audio issues:
You can force Webkit (the engine running Web Audio) to use a larger buffer size, which obviously increases latency but mostly mitigates the crackling issues in web audio apps.
To do so, make sure all audio apps (both web and native) are closed, then launch one which supports setting the buffer size (like AUM), set a large buffer, make sure the audio hardware is in use (in AUM for example, add a hardware input to a channel and mute it), then open the website.
It appears Apple has found if they include new emoji in updates they can get people to update more often. They wouldn't do it every large update otherwise.