AU download contains folders instead of component package. What do I do? : )

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

I have a few of these, where the result from the disk image is a folder called name.component, and inside are the various folders that make up the guts of the AU (first "Contents", then within that one which is "MacOS" and one "Resources". I know nothing about programming : ) but I know enough that if I look into the package contents of a usual AU component that's what's inside.

So it's easy to control-mouse onto a package and "show package contents", but how do I do the reverse? Make a folder realize it should be a package? : )


Thanks!

S

MBP 10.7.5

Post

Have you tried contacting the developers' support?

Post

standalone wrote:Have you tried contacting the developers' support?
Yep, but I just hit the bump an hour ago, and I don't figure the author of a freebie AU will be responding until Monday so I figured I'd give here a shot : )

What I did learn is that to be seen as a wrapped up package it needs a "PkgInfo" doc in the Contents folder. I inspected a handful of other AUs and they all were identical, with just the text "BNDL????", so I copied these into where they were not. Whether or not that's a kosher way to do it I can't tell, but this does in fact turn them into component packages. However they're still the only AUs not recognized by apps.


It's not a big issue, but these two plugins, "Gain" and "Rider" from "Sound Consulting" would be useful if I could get them going. They're both from 2006 so that may be a factor with ML 10.7.5

Thanks,

S

Post

I'd be surprised if auval burped because of a missing pkginfo - have you tried just dropping them into your /Library/Audio/Plug-Ins/Components folder and seeing if it works?

If it is indeed a missing PkgInfo file, yes, they are just those 8 characters, so copy a file over from another AU.

But if they're not getting recognised... that's a different question.
Sounds as if the zip might have been corrupt, or you might have lost some files... is there an Info.plist?
Is there an <name> executable file inside the MacOS folder?
Is there a <name>.rsrc file inside the Resources folder?
(where <name> is the name of the au - or, <name>.component)
Edit: checked myself and they're fine.

Failing all this, if you're on 10.7, could it be that the AU is PPC only? Or that you're running 64bit?

Edit: Removed comment about ppc. There /does/ appear to be an intel version.
So, here on 10.6, they show up fine as .components, assuming I download from here: http://sounds.wa.com/audiounits.html

So, it looks like it's either:
- 10.7 being fussy about the PkgInfo
- 10.7 being fussy thanks to GateKeeper
- You're running a 64bit host, and it's not liking it.

Next step here, technically speaking, is to run auval from the terminal.

command would be: auval -t aufx BWsc ride (to test rider)
and see what it comes up with.
Might be that the folder state has been cached, and, having copied the PkgInfo, you'll need to drag the .component out of your Components folder onto the desktop and back again, to get finder to update.

Edit: Here on 10.6, auval fails with the following:
Checking parameter setting
Using AudioUnitSetParameter
Using AudioUnitScheduleParameter
ERROR: Buffer overun was detected when rendering

So... they need fixing (probably just a recompile with the latest AU SDK would get it), but Logic might let you use them as "unstable".

Dave.
[ DMGAudio ] | [ DMGAudio Blog ] | dave AT dmgaudio DOT com

Post

Dave,

Wow, thanks for the insightful response and all of your energy in looking into it. I emailed Sound Consulting at the address on the site and it bounced back BUT I now recognize Sound Consulting as the sig on one of the Metric Halo mailing list's prominent posters, Brian Willoughby, with a different email. So I'll email Brian and ask if he has a fixed version.

Thanks! : )


S

Post

DaveGamble wrote: Sat Nov 10, 2012 5:46 pm
If it is indeed a missing PkgInfo file, yes, they are just those 8 characters, so copy a file over from another AU.
This old post from the stoneage of digital has helped me today!

I had the same thing happening to me: some .component files were turned into folders instead of their usual packages, some weren't, who knows which update caused that. Copying the PkgInfo (which is in the first folder after you've opened "Contents" with the "show package content" command) into another component folder works. Just reload the folder and you'll see all your component-folders turn into regular, good ol AU files again!

MASSIVE THX! :clap:

Post

This command will set the bundle flag on a plugin that's turned into a folder and thus turn it back into a package:-

Code: Select all

sudo SetFile -a B /Library/Audio/Plug-Ins/Components/myplugin.component
(Obviously, you can just type the first part and then drag/drop your plugin file onto terminal).

SetFile is part of the Xcode command line developer tools.

Post

beely wrote: Sat Apr 16, 2022 9:51 am This command will set the bundle flag on a plugin that's turned into a folder and thus turn it back into a package:-

Code: Select all

sudo SetFile -a B /Library/Audio/Plug-Ins/Components/myplugin.component
(Obviously, you can just type the first part and then drag/drop your plugin file onto terminal).

SetFile is part of the Xcode command line developer tools.
Man thank you for posting that. Never could figure out why all my Arturia and SoundToys AudioUnits always showed up as folders or how to change them back. Just ran it on all my V8 Collection plugins and now gonna go fix up the SoundToys stuff, they're all back to bundles now!

EDIT: Odd worked great for the Arturia stuff but the latest SoundToys dont seem to react at all. They're still showing up as folders.

Post

mothra wrote: Sat Apr 16, 2022 3:30 pm EDIT: Odd worked great for the Arturia stuff but the latest SoundToys dont seem to react at all. They're still showing up as folders.
Same here (although it worked on previous versions).
There might be something else going on with these, I haven't looked into it as of yet...

Edit: It looks like these *are* correct packages (try double-clicking them!), just with a folder icon (so the wrong icon, basically) - which is easy enough to reset. Just fixed mine here.

Post Reply

Return to “Effects”