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
Lol
Thanks @brambos
I hope the radar helps what’s going on in this pic. So weird, I mean clearly I’m using auv3 and went to open some more instances in another node and there are “no auv3 installed.”
@Model10000 Have you tried requesting the list of IAA, to see if it restores the AU list? This sometimes restores the icons, so it could work here too.
Thanks guys, I’m going to keep my eye out on it happening on saves and will also try and pull up some iaa after.
Apologies if this has been mentioned before as I haven't been following all the discussions on iOS 14 and AU icon issues, but I know there's lots of stuff about missing icons, but how about hosts showing the wrong icon?
A customer on iOS 14.4 sent me this screenshot showing my AU (MU Waverley) with the FAC Bandit icon.
This is in AB3. Anyone else seen incorrect as opposed to missing icons? Could it be some kind of messed-up cache thing?
It’s not just you. Weirdly, it seems to be just the FAC Bandit icon which goes icon squatting. Figures.
Thanks @Philandering_Bastard - weird or what? And the fact it's called Bandit and it's stealing icons... (insert conspiracy theory here)
I see that also, and I don't have Bandit installed. I assume it's a dummy placeholder because the app doesn't provide an icon of the required (very small) size. It might be provided by the app's application builder, returned by iOS, or simply thrown in by Audiobus.
@Michael, do you know anything about this? In the Audiobus AUv3 pick lists, some apps show this broken N icon. It's always the same ones. They're normal in AUM, but it doesn't require such tiny icons. I see it for LRC5, NA 808, and NA Analog Rack Phaser.
Ah, thanks @uncledave - OK, apologies for the confusion - I had been told this was the Bandit icon, but a placeholder would make more sense. Unless the AppIcon requirements have changed (iOS target version dependent?), all mine are present. I think your build will get rejected anyway if they're not all there.
I can confirm that LRC5 didn't have all of the various icon sizes in the assets catalog. I'm not sure why. Do any of my other AU's show up as having missing or placeholder icons in AUM? All the rest of mine that are released should have all the sizes filled in. LRC5 actually had its icon showing on my devices in Audiobus, but my devices don't cover all of the possible combinations of icons.
I wouldn't have expected the icons sizes I didn't include for LRC5 to be used for the AU icon. Though, Apple does seem to be changing what they do to get and return the icons for AU's.
Interesting. I'm using iPad 6, which has the classic 9.5" Retina display (1536x2048), with iPadOS 14.4. I also have CnSnP, PhaseDelayArray, and xTrem, all of which have icons in Audiobus. I tried to measure the icons I see in Audiobus, and they seem like 64x64 maybe. Here's my screen (lower resolution):
Edit: Checked icon size by tedious photo cropping. Looks like 64x64 to me.
Thanks for the confirmation. The icon situation is a little weird for AU's. The AU itself doesn't have an icon. It gets it from the container app. I hadn't included all of the notification, spotlight, etc. icons for LRC5 for some reason. All of the app icons were there, but the system must return some of the other icons in different situations.
You can't really tell which icon is being used from the selection list because it could be rescaled for the size needed by the view.
Looks like you have to provide all of the various different combinations of sizes and scales to be certain. It would be really nice if Apple would move to using SVG based icons as an alternative to the 20 something different sizes needed to cover them all now.
You can use pdf icons instead of all the bitmaps. I’m used to creating SVG icons, because I put a lot of interactivity into the SVG markup myself after the export (no automated export can make svg to my level of sophistication). When I had to do some graphics for an app I was disappointed to find out that apps can’t make use of my SVG and at the time I didn’t want to generate all the bitmaps (although Designer can do that in Export persona), but I was somewhat relieved that it could accept an export from Designer as pdf.
Weird, as I have all the Spotlight and notifications icons in my container app. 18 in total, counting the 1x, 2x and 3x variations. Having said that, I've done nothing to try and make the 20 pt ones "work" at that size.
Interesting. Do you have to make a different kind of asset catalog or do you drop the same pdf on each of the AppIcon slots?
I would have thought that would cover it. BTW, the more than 18 I mentioned above is including when you have to do the macOS icons as well. I'm playing with a SwiftUI based document app and there are even more to include because of all the different macOS icon sizes.
I really only try to do two different size categories, one for the larger icons and one for the smaller. I pretty much ignore the 16px and 20pt sizes as with my graphics skills they may as well be a single color blob.
I can’t remember how exactly it went, but I sat next to the person doing the Xcode and between us we found that it will accept either/or. What seemed to me to be happening is that if you’ve given it a pdf in the appropriate place, it then generates all the bitmaps from it anyway unless you tick some box telling it to actually use the vector information in the final app
I can’t remember the reference pages I looked up to help him through it, but it was something like this page: https://useyourloaf.com/blog/xcode-9-vector-images/ or something.
However, I’ve just noticed this: https://www.avanderlee.com/xcode/svg-image-assets/ Which means I can use SVG directly! Probably not on my colleague’s Xcode, as that is stuck on a quite old version at the moment (for the build system, some reason I don’t understand and aren’t interested in). Still, if it can take SVG I’m interested.
You can definitely use SVG in Xcode 12 now. I've been playing with it over the last few days. It's been added in because all of Apple's SF Symbol stuff is SVG underneath. Using asset catalogs of SVG is really easy. It works like any other asset. The SFSymbol stuff with SVG is also very slick because it makes your SVG work with size classes and weights that are compatible with the text in the app.
The easiest way to start using it is to get the SF Symbols app from Apple and then export one of the symbols to an SVG doc. All of the weights and stuff are help has layers in the SVG. Importing and exporting in Affinity Designer worked easily. Then you just drag the SVG into the assets catalog and it creates a resource that you can use in UIImage(named: ...) for example.
Oh dear. That's most definitely my bad. My audio unit data scooping robot went rogue and assigned a bunch of audio units to Bandit. I blame Bandit. Bandit definitely stole them. Fixed by hand, it should be sorted within a day when the local database cache reloads.
Thanks @Michael!
All this talk of icons reminds me of the time I started working for a company that had developed a financial app. I was gobsmacked to discover that the logos for all the banks they supported were baked into the app! So... new bank, or changed logo = new app release
It was one of the many things I ended up re-doing.
More a case of cowboys than bandit in this case
Good grief! I thot you were joking, but I just checked and the icons are normal now. Nice job.
Hi all,
still pretty new in this area, not that new in error making, head scratching etc.
I am not quite sure if this missing icon issue is related to my problem. I've got tons of auv3 apps on my ipad, and after the phase of hunting and collecting I finally wanted to use and apply them - starting in AUM (admiring the routine that Doug of SoundTestRoom and others show there twice to thrice per day).
The head scratching started immediately after AUM let me know that there are NO auv3 apps on my iPad (at least I see their icons and can start the stand alone versions). Audiobus also lets me know there are no AU apps. Which I don't believe, the AppStore invoices are very real. GarageBand, as far as I can judge it, also does not acknowledge the presence of all the tools. The only thing it shows is the advice to reboot my device if I don't see the expected apps.
I've rebooted the iPad several time in the past days, no change, no chance. iPadOS 14.41 installed, 9.7" iPad Pro.
As said, not sure if this issue is related to the missing icons drama described here. If not, please let me know, then I'll start a new thread.
FWIW, when I select InterAppAudio to add to a node in AUM and / or audiobus, I get a long list of apps and tools I can select.
My first thought is of course that I did something wrong or missed to enable something during setting up the habitat for the auv3 stuff.
Any ideas, anything I might try? In most cases, the error source sits on my side of the screen...
TIA for any help to get the thing where it belongs...
Cheers,
Ulli
Rebooting the iPad should fix this problem. First, are you sure you're really doing a full reboot? Some people aren't clear that this means fully powering off the device. If you didn't see the Power-Off slider and slide it to completely shut down then you may not have done a full reboot.
There's an even deeper reboot you can do. I think the process for your device is:
If you've already done a real reboot and the icons don't come back, that's really unusual.
Wim,
Due to my historic background starting in ~1967 on a Zuse Z22 (with a tube CPU) across CP/M, bitslice microcode programming and finally Win and some Linux, I was obviously indeed mistaken about what a boot means in the iOS world. (btw, I think booting is derived from the short piece of paper tape that was read by early machines to get the initialisation started, resembling a bootstrap, but that may be anecdotically transposed...) - in short, nope, just the several restarts after iOS updates (like right now the update to 14.4.2), looked like a reboot.
I'll try that next. BTW, on my old iPhone SE (first generation), AUM etc. work as advertised, (without a reboot, but I understand that is optional, on the will and decision of each device).
Thanks a lot for your prompt reaction and (hopefully) help. I'll let you know about the outcome. Cheers, have a nice sunday!
Ulli
I never thought I'd come across someone here that pre-dates my computer background by a decade.
I hope it helps. It should. 👍🏼
Yeaaaah! Suxxxessssssss! I owe you a double cold one. Thanks.
I used the vol + - pwr sequence.
Very good. Just played this game myself; only normal Power Off, though. But I wanted to point out that the only power cycle reboot that matters is the one after the AUv3s go missing. And they do just pop off at random. Your history of reboots installing updates is irrevelant for this.
I've realized that my limited sample of 2 AUv3 disappearances seem to be correlated with AppStore updating an app, triggering a jetsam event that restarted pkd. I wonder if anyone else has noticed AppStore update activity around the time of these events. I've turned off automatic app updates, so they only happen when I specifically check for them.
Good to learn something new. From https://discussions.apple.com/thread/251712150?answerId=253295764022#253295764022
A UI initiated restart [normal power off/on] causes the OS and App running-state to be saved prior to shutdown - and reloaded from the saved-state upon restart of the system.
By contrast, a forced restart [vol up, do, pwr] immediately terminates all processes; the OS to completely reinitialised upon system restart.