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.
Audiolayer update v1.6.6 displays 2 entries in NS2 bug (SOLVED)
Hi - I have a weird issue with the latest AudioLayer update (5th June 2022 v 1.6.6): in NS2 there are now 2 auv3 instrument entries:
The version selected in my current project is unable to be loaded:
If I select the other version then that loads ok (although with no patch loaded) and I can load patches in to it if I use Audiolayer’s own browser - but I cannot load patches saved with NS2’s patch browser (of which I have a fair few as that is my preferred method of saving patches) - clicking on a patch always flips the selected version to the version that will not load.
I’m running on iPhoneXR on IOS14.8 - have rebooted my device twice since Audiolayer auto updated. I have also refreshed the internal NS2 patch database (this removed a number of Audiolayer patches ☹️)
Any advice appreciated or if anyone could point me towards an @ or an official bug reporting site (as I have a deadline looming).
Many thanks 🙏
Comments
Does it only show two entries in NS2 or other apps (AUM etc) as well?
Just checked AudioEvolution & there’s only 1 instance there - although I have no AE projects where I have an instance of Audiolayer loaded from before the update (or ever actually…) in case that makes a difference:
I have just tried opening a brand new project in NS2 but there are again 2 instances & the same problem with its patch browser.
I think it is pretty safe to assume nothing in NS2 has changed… 😉
Then it could or most likely is an iOS issue...
I've got only one AudioLayer in NS2, iPadOS15.5.
As far as I know the iPhone XR supports iOS15.5 so I see no reason NOT to keep it up-to-date...
@attakk . We've seen some problems lately where a dev has changed the AUv3 AudioComponentDescription in an update. This identifies the AUv3 and the presets saved in the host. One reason for doing this has been to achieve compatibility with MacOS; apparently it has certain character requirements not imposed by iOS. In KQ Dixie, the dev retained the old ID as deprecated, and added a new one. Some other devs haven't been so cagey. You might check with @VirSyn to see if this is the problem.
This isn't much help for your deadline situation. You may just have to repair your projects.
Many thanks for checking.
This sounds very much like it could be it as selecting the working version of Audiolayer and then attempting to load a preset for it automatically switches the chosen instance to the non-working (ie not found) version.
Now - how to repair the project: not sure how to go about that as these presets were only ever saved in NS2’s patch browser.
If @VirSyn could shed some light on whether there might be an easy way or if this is something that may have been missed but could be fixed easily? I note the update was specifically for Apple Silicon (which is a little frustrating if I’m honest - note to self: turn off automatic updates when deadlines are approaching… 🤦♂️)
Ok - looking at the patch file NS2 produces, this is one that loads to the incorrect instance:
I then saved a new blank patch with the working instance (this one reloads to the correct version) so I then compared it to the “broken” patch file - I see 3 differences:
The case is different here:
And the numbers are different here:
… and here:
I suspect I need to change 1 - or all - in the “broken” file to match but before I start tinkering does anyone know with authority if only 1 needs changing, and if so which? @VirSyn : any help you can provide is more than appreciated here 👍
(I’m guessing on the s=“3176” myself, but who knows?)
Stupid, untechnical, pleb question, but given that not everyone is experiencing this (neither Samu or I are reproducing it for example), have you tried deleting and freshly installing the app? I only ask because Harry said on another thread this was needed for some other unrelated issue after an update (possibly on a different product. The specifics escape my memory).
@attakk Nice work there. The update for "Apple Silicon" is def the sort of change that may require changing the ID. My personal guess for the fix would be the capitalization in the PITypeID. Maybe that VRSN has to exactly match a string registered by the dev.
@attakk Sorry about the problem, it's definitely the capitalisation of the developer name "VRSN". This was needed because on Apple desktop at least one character must be in capital letters. As a brute force solution I already uploaded a new version having two audio units, one labelled "*deprecated" which should not be used in new projects. Only old projects will call this automatically. Let's pray Apple review team is fast today...
Awww, man - I’m sorry to have caused any panic!
I’d literally just - through experimentation - worked out that it was the capitalisation that was the issue (ie I’ve just got a patch to load after a bit of trial and error!) so if worst comes to worst I can go through and manually update the others in this project if Apple do decide to sit on their hands.
I don’t really ever open projects other than the current one so it shouldn’t really be a problem for me, but that said it’s handy to know this will provide a fix for those projects should I ever decide or have the need to.
Many, many thanks for your time - and everyone who provided help & ideas along the way 🙏🙏👍