Hi audio friends,
I unzipped an Installer.pkg plugin with Keka, getting a new open folder with all its content.

Then I deleted the VST.pkg, VST3.pkg, AXX.pkg (leaving the AU, Content, Resources folders and the [TOC].xml and Distribution files inside).

I'm doing this because to get a much smaller new only AU Installer (saving tonnes of GB on HD... I only use AU) but unfortunately, when I tried to add .pkg to the folder and revert it to its initial Installer state, ta-da... the file was corrupted and no longer worked. Surely that's not the right procedure...

So I'm asking you file gurus what is a correct and simple procedure to get a working and installing file from that folder? Please, simple instructions...

Many many thanks for your help and attention.

 

Last edited: Jul 31, 2025 at 6:21 PM

Maybe it’s as simple as open the original installer, then if it lets you choose which formats to install, pick au? Otherwise you can just delete the other plugin formats manually or use the audio plugin uninstaller from wide blue sound. No need to rip open the package to single out the desired format

 

I know that... but, having thousands of .pkg installers, I wouldn't save hundreds of GB on my hard drive when I archive them afterwards.

 

Spoiler: Source: Grok KI

Creating a working Audio Unit (AU) installer from an extracted plugin folder is tricky because macOS .pkg installers are structured archives with specific metadata, signatures, and scripts that don’t survive simple extraction and re-packaging. When you unzip a .pkg file with a tool like Keka and modify its contents, you break the package’s integrity, which is why your attempt resulted in a corrupted installer. Below is a simple, step-by-step guide to achieve your goal of creating a smaller, AU-only installer while keeping it functional. Since you’re not a developer, I’ll keep it non-technical and straightforward, using accessible tools.

Why Your Approach Didn’t Work

• A .pkg file is not just a folder with a .pkg extension. It’s a bundle containing files, metadata (like Distribution and [TOC].xml), and often code-signing information that macOS verifies during installation.
• Deleting components (e.g., VST.pkg, VST3.pkg, AAX.pkg) and trying to re-package the folder disrupts the installer’s scripts and signatures, causing it to fail.
• macOS expects AU plugins to be installed in specific locations (e.g., /Library/Audio/Plug-Ins/Components or ~/Library/Audio/Plug-Ins/Components), and a proper installer ensures this placement with correct permissions.

Simple Procedure to Create an AU-Only Installer
Since you want a minimal AU-only installer to save disk space, the easiest approach is to manually install the AU plugin by placing the .component file in the correct folder and verify it works in your DAW (e.g., Logic Pro, Ableton Live). If you really need a .pkg installer for distribution or repeated installations, you can create a new one using a free tool like Packages. Here’s how to do both:

Option 1: Manual Installation (Simplest, Recommended)
If you only need the AU plugin to work on your system, skip creating a new installer and manually install the .component file. This saves space and avoids complex packaging.

1. Locate the AU Plugin File:
   • In the extracted folder, navigate to the AU folder (or similar, depending on the plugin).
   • Look for a file with a .component extension (e.g., MyPlugin.component). This is the actual AU plugin.
   • If the .component file is a folder (not a package), see the “Fixing Folder vs. Package Issue” section below.
2. Copy to the Correct Folder:
   • Open Finder and press Cmd + Shift + G to open the “Go to Folder” dialog.
   • Enter /Library/Audio/Plug-Ins/Components (for system-wide access) or ~/Library/Audio/Plug-Ins/Components (for user-only access) and click Go.
   • If the folder doesn’t exist, create it: Right-click in Finder > New Folder > name it Components.
   • Copy the .component file into this folder.
3. Set Permissions (if needed):
   • Right-click the .component file, select Get Info, and ensure your user account has read/write permissions.
   • If you’re installing to /Library/Audio/Plug-Ins/Components, you may need admin privileges. Enter your password when prompted.
4. Rescan in Your DAW:
   • Open your DAW (e.g., Logic Pro, Ableton Live).
   • For Logic Pro: Go to Preferences > Plug-In Manager, click Full Audio Unit Reset, and wait for the scan to complete.
   • For Ableton Live: Go to Preferences > Plug-Ins, ensure “Use Audio Units” is enabled, and click Rescan.
   • Verify the plugin appears in your DAW’s plugin list.
5. Test the Plugin:
   • Create a new track, insert the AU plugin, and test it to ensure it works.
   • If it doesn’t show up, double-check the file path and ensure the plugin is compatible with your macOS version and DAW (e.g., 64-bit, Apple Silicon compatibility).

Pros: No need for a new installer, saves disk space, quick and simple. Cons: Not ideal for distributing to others or reinstalling frequently.

Option 2: Create a New AU-Only .pkg Installer
If you need a distributable AU-only installer (e.g., for multiple machines or sharing), use the free Packages app to create a new .pkg file from the extracted AU contents. This requires a bit more effort but ensures a proper installer.

1. Download and Install Packages:
   • Download Packages from http://s.sudre.free.fr/Software/Packages/about.html (free, macOS-compatible).
   • Install it by dragging the app to your Applications folder.
2. Prepare the AU Plugin:
   • Ensure the .component file is in the extracted AU folder.
   • If the .component file appears as a folder, fix it (see “Fixing Folder vs. Package Issue” below).
   • Optionally, include any Content or Resources folders if the plugin requires them (check the plugin’s documentation).
3. Create a New Project in Packages:
   • Open Packages and choose File > New Project.
   • Select Raw Package (simplest for basic plugin installation).
   • Name your project (e.g., MyPlugin_AU_Installer).
4. Add the AU Plugin to the Package:
   • In the Payload tab, click the + button to add files.
   • Select the .component file and any necessary Content or Resources folders.
   • Set the Destination to /Library/Audio/Plug-Ins/Components (system-wide) or ~/Library/Audio/Plug-Ins/Components (user-specific).
   • Ensure permissions are set to Owner: root, Group: wheel, Permissions: 755 (Packages sets this by default).
5. Configure the Installer:
   • In the Settings tab, set a meaningful Identifier (e.g., com.yourname.myplugin.au).
   • Optionally, add a Read Me or License file in the Presentation tab for user instructions.
   • Skip code-signing unless you have a Developer ID (most personal use doesn’t require it).
6. Build the Installer:
   • Click Build > Build and choose a location to save the .pkg file (e.g., MyPlugin_AU_Installer.pkg).
   • Packages will create a new .pkg file containing only the AU plugin.
7. Test the Installer:
   • Double-click the .pkg file to run it.
   • Follow the installation prompts (may require admin privileges).
   • Verify the .component file is installed in /Library/Audio/Plug-Ins/Components or ~/Library/Audio/Plug-Ins/Components.
   • Open your DAW, rescan plugins (as in Option 1, Step 4), and test the plugin.
8. Optional: Create a Disk Image for Distribution:
   • To make the installer user-friendly, create a .dmg file:
     • Open Disk Utility (in Applications/Utilities).
     • Go to File > New Image > Image from Folder, select the folder containing your .pkg file, and save it as a .dmg.
     • Choose read-only format for distribution.

Pros: Creates a reusable, distributable installer that’s AU-only, saving space compared to the original multi-format installer. Cons: Requires extra steps and a third-party tool.

Fixing Folder vs. Package Issue
If the .component file appears as a folder (not a package), it’s likely missing a PkgInfo file, which macOS uses眼友

Fixing Folder vs. Package Issue (continued)

macOS uses to identify it as a bundle. This is a common issue with some plugins, as you’ve encountered. Here’s how to fix it:

1. Check the Folder:
   • Right-click the .component folder (e.g., MyPlugin.component) and select Show Package Contents.
   • Look inside the Contents folder. You should see subfolders like MacOS and Resources, but the PkgInfo file may be missing.
2. Create or Copy a PkgInfo File:
   • Find a working .component file from another AU plugin (e.g., in /Library/Audio/Plug-Ins/Components).
   • Right-click it, select Show Package Contents, and copy the PkgInfo file from its Contents folder.
   • Paste the PkgInfo file into the Contents folder of your problematic .component folder.
   • The PkgInfo file should contain the text BNDL???? (exactly 8 characters). If you can’t copy one, create a text file named PkgInfo with this content using a text editor like TextEdit.
3. Convert the Folder to a Package:
   • Open Terminal (search for it in Spotlight).
   • Run the following command, replacing MyPlugin.component with your folder’s name:
     text
     
     sudo SetFile -a B /Library/Audio/Plug-Ins/Components/MyPlugin.component
     
     
     
   • Alternatively, drag and drop the folder into Terminal after typing sudo SetFile -a B , then press Enter.
   • Enter your admin password when prompted.
   • This sets the bundle flag, turning the folder into a proper .component package.
4. Verify the Fix:
   • The folder should now appear as a single .component file in Finder (not a folder).
   • Move it to /Library/Audio/Plug-Ins/Components or ~/Library/Audio/Plug-Ins/Components and rescan in your DAW.

Note: You need Xcode Command Line Tools installed for the SetFile command. If you don’t have it, macOS will prompt you to install it when you run the command. Alternatively, copying the PkgInfo file alone may suffice in some cases.

Tips and Troubleshooting

• Check Compatibility: Ensure the AU plugin is compatible with your macOS version and DAW (e.g., 64-bit, Apple Silicon support). Check the developer’s website for details.
• Permissions Issues: If the plugin doesn’t appear in your DAW, ensure the .component file has correct permissions (right-click > Get Info > ensure your user has read access).
• Gatekeeper Warnings: If macOS blocks the plugin due to security settings, right-click the .component file, select Open, and allow it to bypass Gatekeeper.
• Rescan Plugins: Always rescan plugins in your DAW after moving or fixing files. Some DAWs may require a restart.
• Backup Original Files: Before modifying or deleting files, back up the original extracted folder to avoid losing data.
• Disk Space: Manual installation (Option 1) is the most space-efficient since it avoids packaging overhead. The .pkg installer (Option 2) adds some overhead but is still smaller than the original multi-format installer.

Why This Works

• Manual Installation: Directly placing the .component file in the correct folder bypasses the need for an installer, ensuring macOS and your DAW recognize the plugin.
• Packages App: This tool creates a new, valid .pkg file with only the AU component, preserving the necessary metadata and structure for macOS to install it correctly.
• PkgInfo Fix: Adding the PkgInfo file and setting the bundle flag restores the .component folder as a proper macOS bundle, making it recognizable by DAWs.

If you run into issues (e.g., plugin not appearing in DAW, permissions errors), let me know the specific plugin, macOS version, and DAW you’re using, and I can provide tailored troubleshooting steps. Also, if you want to share the installer with others, let me know if you need more details on distributing the .dmg file securely. Hope this helps, and happy music-making!

 

Use Suspicious Package: https://mothersruin.com/software/SuspiciousPackage/

You can export any file out of the pkg file. Sometimes if there is a problem with an installer, you just skip the installer entirely, and put the files where you want them.

It's one of the most useful Mac free utility programs for "unofficial" installers. You can even use it to see where "missing" presets have been incorrectly installed, because you can look at the entire directory structure of an installer's payload. It does not nag or do any of the more really annoying things that Pacifist does.

For "stripping" either the Intel or ARM slices of a binary, you want to use the command lipo in terminal. The result is what is known as a "skinny" binary, which can be made from any U2B release. Hence the command name.

It takes some serious talent to make a multi-billion dollar computer technology look retarded. Nice AI work there about an OS you have never even used before there buddy.

 

Last edited: Jul 31, 2025 at 7:29 PM

not sure to understain correctly, do you end up with Three Separate .PKG in a single folder after unzipping?
if that's the case, just keep the AU.pkg and thrash the rest (including the folder).

 

Aha aha ha aha ha ahah ah... It's not as easy as you think.
If you do what you say (and I did), you get a corrupted file that no longer works and you lose presets and other necessary things for a reliable and complete installation.

 

Last edited: Jul 31, 2025 at 10:43 PM

This does not get any easier:




A more complicated PKG file will have xml files, pre-install and post-install scripts, and other files. Trying to re-create packages is not what it is for. But you could easily export all the files and stick them in a highly compressed archive.

If you want to actually re-assemble the pkg file, something like this is your basic idea:

Spoiler

Requirements:

• macOS command line tools
  
  
• Access to Terminal
  
  
• pkgutil, productbuild, and optionally codesign

✅ Steps:
1. Expand the .pkg
If you haven’t done this already:

bash
pkgutil --expand /path/to/original.pkg /tmp/pkg-working

2. Modify contents
Navigate to /tmp/pkg-working and make changes:

• Delete or modify files in the Payload (inside package components in *.pkg subfolders).
  
  
• Remove unwanted components entirely (e.g., an unwanted package inside a metapackage).
  
  
• Optionally clean up scripts (preinstall, postinstall) in each sub-Package.

If you need to extract/modify the payload (the actual files to be installed):

bash
cd /tmp/pkg-working/component.pkg
mkdir payload
cd payload
cat ../Payload | gunzip -dc | cpio -i
# make changes here
# then reassemble:
find . | cpio -o --format odc | gzip -c > ../Payload

You can also skip this if you're just deleting full components or metadata.

3. Rebuild the .pkg
If it’s a flat component package:

bash
productbuild \
--identifier "com.example.package" \
--version "1.0" \
--scripts /tmp/pkg-working/component.pkg/Scripts \
--root /tmp/pkg-working/component.pkg/payload \
/path/to/new.pkg

If it’s a distribution (meta) package with multiple components:

bash
pkgutil --flatten /tmp/pkg-working /path/to/new.pkg

Optional: Sign the package
If you want to avoid Gatekeeper warnings (for distribution):

bash
productsign --sign "Developer ID Installer: Your Name (TEAMID)" \
/path/to/new.pkg /path/to/signed.pkg

But this is your real problem:

 

Last edited: Jul 31, 2025 at 10:31 PM

Thank you all for your examples and advice.

I admit I thought – given how easy it was to expand the Installer with Keka – that it would be simpler to re-compress it... just as I do with my .epub e-books (I own over 5,000 books and I open/decompress them, correct them, change photos and covers, insert chapters, change fonts and formatting and much more, then finally save/compress everything quickly).

Instead, it's very complicated to quickly recreate a customised AU-only Installer, especially having to do it for the enormous number of .pkg files I own.

You all are precious friends who are always there with your help.

 

Last edited: Jul 31, 2025 at 11:18 PM

Why do you need thousands of plugin installers? Other than free stuff that no-one archives anyway, you can easily find 10-20 years worth of releases from Sister Site on multiple other sites, and even more obscure stuff on torrent sites. They are all mostly small archives anyway, for applications and plugins. You would probably be better off just using a more high compression archive format like 7zip for the extracted installers as they are. It will not help much if you have them already compressed as zip, etc.

Look at one of the "Common" folders from an R2R Acustica plugin. Those were crazy. Some better solution to your problem very likely already exists. I've never seen anyone want to do this.

 

Actually I'm a serial hoarder of everything I love (girls included).

Yes, I use 7z to compress files.

If you change computers, have a system crash, a hard drive suddenly dies or you're installing for a friend... you need all the installers available instantly.

If you start searching at that moment because you don't have them to hand, you can be sure it will take weeks before you find everything online again (I've experienced this in the past)... that's if you're super lucky and manage to find 'everything' you need.

Fortunately, I've never used Acustica plugs. The best solution would be (as it used to be) different installers for each type of plug (VST, AU, etc.), but I understand that this would perhaps take a lot of time for those who create the cracks.

Maybe I should learn to use Time Machine, but since I spend more time writing songs, I haven't done it yet... perhaps that would help?

 

Last edited: Aug 1, 2025 at 10:01 AM

Time Machine backup would absolutely be the best way to deal with the entire thing. But without it, installing everything over would take longer than actually re-downloading all of it. You can add 50 torrents to download at one time, but only install them one at a time. Also, I never reinstall "everything" again, unless from a Time Machine backup. It's the perfect time to get rid of all the stuff you don't actually use by just not adding it back again until you really need it. I only keep the archives like you are doing with the really big items, because they are the most data to download again. Searching would not take weeks or even days, because it would all be from one place.