Hi!
There we go again.
I installed Ample Sound - Ample Bass U yesterday and started a project with it. (I guess, this U stands for "Upright").

But today, after opening the project, I got this:



I tried to reinstall everything, but no luck, still the same.

I installed:

1.- Ample Sound - Ample Bass Upright v3.5.0 WIN OSX
2.- Ample Sound - Ample Bass Upright v3.6.0 Update
3.- Ample.Sound.Ample.Bass.Upright.v4.0.1-R2R
4.- Ample.Sound.Activation.Manager.3.v1.0.0.Incl.Emulator.and.Keygen-R2R
5.- TEAM R2R Network Block Runtime v2.1.0-R2R

Numbers 4 and 5 are recommended to be installed in number 3 release.

Number 1 and 2 were downloaded from audiotools.in or some place of torrents, can't remember now. (Because if I'm downloading from rg or katfile it would take ages to get all the links).

I used the activation inside release number 3 and I think I followed the instructions from release number 4 correctly, but I cannot say for certain, they were a bit messy for me.

I don't know what I am missing, but I can't get it to work.

 

Spoiler: Source: Grok KI

What This Error Means in Bitwig Studio
The error message "Plugin host died: Could not read responses: End of stream: Broken pipe" is a specific issue encountered in Bitwig Studio, a digital audio workstation (DAW) used for music production. It indicates a crash or sudden termination of the plugin host process—the separate environment Bitwig uses to run third-party audio plugins (like VSTs, AU, or CLAP formats) safely, without destabilizing the main application. This error is common on macOS (due to the "Broken pipe" phrasing, which relates to Unix-like pipe communication failures) but can occasionally appear on Windows or Linux.

Why Does It Happen?

• Communication Breakdown: Bitwig communicates with plugins via inter-process pipes (streams of data). If the plugin process crashes, hangs, or fails to respond (e.g., due to a bug, memory overload, or incompatibility), the pipe "breaks," ending the stream prematurely. Bitwig interprets this as the host "dying."
• Common Triggers:
  • Faulty or Incompatible Plugins: Recently installed or updated plugins (e.g., Ample Sound Ample Bass U, as noted in user reports) often cause this. It could be due to version mismatches with Bitwig (e.g., Bitwig 5.x requiring updated plugin wrappers).
  • Resource Issues: High CPU/RAM usage, especially with sample-heavy plugins or large projects.
  • System-Specific Problems: Outdated macOS versions, permission issues (e.g., Gatekeeper blocking unsigned plugins), or conflicts with other audio drivers (like ASIO on Windows).
  • Bitwig Bugs: Occasionally tied to known issues in Bitwig's beta builds or specific plugin bridges.

This has been a recurring complaint in Bitwig communities, with spikes around new plugin releases or OS updates (e.g., post-macOS Sonoma/Ventura).

How to Fix It
Here's a step-by-step troubleshooting guide based on user reports and official advice:

1. Restart and Isolate the Plugin:
   • Close Bitwig and relaunch.
   • Open your project in a new, minimal session (no other plugins loaded).
   • Bypass or remove the suspected plugin (e.g., via the device chain). If the error stops, that's the culprit.
2. Update Everything:
   • Bitwig: Ensure you're on the latest stable version (check Help > Check for Updates). As of October 2025, Bitwig 5.2+ has improved plugin stability.
   • Plugins: Update the offending plugin to the latest version. If it's Ample Sound or similar, reinstall from the developer's site.
   • OS and Drivers: Update your macOS/Windows and audio interface drivers.
3. Reset Plugin Settings:
   • In Bitwig, go to Settings > Plug-ins > Rescan to refresh the plugin database.
   • Clear cache: Delete ~/Library/Application Support/Bitwig Studio/Plug-in Database (macOS) or equivalent on Windows (%APPDATA%\Bitwig Studio\Plug-in Database).
   • Run plugins in bridge mode (Settings > Plug-ins > Use Bridges) to isolate crashes.
4. System Tweaks:
   • Increase Resources: Close background apps; allocate more RAM to Bitwig if possible.
   • Permissions (macOS): Right-click Bitwig > Open (to bypass Gatekeeper), and ensure full disk access for audio apps in System Settings > Privacy.
   • Buffer Size: Increase your audio buffer size in Bitwig Settings > Audio (e.g., from 128 to 512 samples) to reduce CPU strain.
   • Safe Mode: Launch Bitwig with plugins disabled (hold Option/Alt on startup) to test.
5. Advanced Steps:
   • Check Bitwig's console logs (Help > Show Log) for more details on the crashing plugin.
   • If persistent, report it on the Bitwig Forum or Reddit r/Bitwig with your setup details (OS, Bitwig version, plugin name).
   • As a workaround, try running the plugin in a different host like Ableton or Reaper to confirm if it's Bitwig-specific.

Prevention Tips

• Scan plugins in small batches after installing new ones.
• Use plugin managers like Plugin Boutique or Waves Central for better compatibility checks.
• Back up projects before loading experimental plugins.

If this doesn't resolve it or you provide more details (e.g., your OS, Bitwig version, or the plugin involved), I can refine the advice further. This error is frustrating but usually fixable with isolation!

 

Last edited: Oct 3, 2025 at 6:00 PM

Hi, I currently have SC installed, and it works with my Bitwig 6. Yes, there were some errors, but please check again to ensure that everything is correctly installed.

 

I'm no Bitwig guru, but the error message points to the plugin crashing (duh), however this sounds like a Bitwig plugin hosting mode thing, what's your setting on that? It's in Settings > Plug-ins > Plug-in Hosting Mode.

I think it defaults to "per vendor", but I'm not too sure. I'd try "individual" first, then running it in the Bitwig process itself. Does the plugin work in other hosts? Standalone? Do other Ample Sound plugins work (if you have any)?

 

It's obvious it doesn't work. You've mixed three different releases, two legit ones with the R2R release, which works completely differently. Uninstall everything, do a deep clean, and install only what you need. If you opt for R2R, strictly follow R2R instructions in the NFOs.

 

Answering in order:

1. Restart and Isolate the Plugin:
   • Close Bitwig and relaunch. ✅
   • Open your project in a new, minimal session (no other plugins loaded). ✅
   • Bypass or remove the suspected plugin (e.g., via the device chain). If the error stops, that's the culprit. ✅
2. Update Everything:
   • Bitwig: Ensure you're on the latest stable version (check Help > Check for Updates). As of October 2025, Bitwig 5.2+ has improved plugin stability. ✅
   • Plugins: Update the offending plugin to the latest version. If it's Ample Sound or similar, reinstall from the developer's site. ✅
   • OS and Drivers: Update your macOS/Windows and audio interface drivers. ✅
3. Reset Plugin Settings:
   • In Bitwig, go to Settings > Plug-ins > Rescan to refresh the plugin database. ✅
   • Clear cache: Delete ~/Library/Application Support/Bitwig Studio/Plug-in Database (macOS) or equivalent on Windows (%APPDATA%\Bitwig Studio\Plug-in Database). ✅
   • Run plugins in bridge mode (Settings > Plug-ins > Use Bridges) to isolate crashes. ✅ I USED THE "INDIVIDUALLY" OPTION; DIDN'T WORK.
4. System Tweaks: (DON'T THINK I NEED TO DO THIS)
   • Increase Resources: Close background apps; allocate more RAM to Bitwig if possible.
   • Permissions (macOS): Right-click Bitwig > Open (to bypass Gatekeeper), and ensure full disk access for audio apps in System Settings > Privacy.
   • Buffer Size: Increase your audio buffer size in Bitwig Settings > Audio (e.g., from 128 to 512 samples) to reduce CPU strain.
   • Safe Mode: Launch Bitwig with plugins disabled (hold Option/Alt on startup) to test.
5. Advanced Steps:
   • Check Bitwig's console logs (Help > Show Log) for more details on the crashing plugin. ✅ Any log showed anything different to the message on bitwig itself (the one on the picture I posted).
   • If persistent, report it on the Bitwig Forum or Reddit r/Bitwig with your setup details (OS, Bitwig version, plugin name). Well... no point on doing this, since I'm using R2R software.
   • As a workaround, try running the plugin in a different host like Ableton or Reaper to confirm if it's Bitwig-specific. ✅ It works on Cantabile.

I'm no Bitwig guru, but the error message points to the plugin crashing (duh), however this sounds like a Bitwig plugin hosting mode thing, what's your setting on that? It's in Settings > Plug-ins > Plug-in Hosting Mode. ✅ I set it to by vendor, by plug-in and individually, nothing worked.

I think it defaults to "per vendor", but I'm not too sure. I'd try "individual" first, then running it in the Bitwig process itself. Does the plugin work in other hosts? Standalone? Do other Ample Sound plugins work (if you have any)? ✅ Yes, version 4.0.1 (R2R) loads without problems on Cantabile. Other Ample Sound plugins work, yes.

It's obvious it doesn't work. You've mixed three different releases, two legit ones with the R2R release, which works completely differently. Uninstall everything, do a deep clean, and install only what you need. If you opt for R2R, strictly follow R2R instructions in the NFOs.
Yes, I know you're right, but, again, dl'ing all those gigabytes on rg or katfile is really time comsuming. And I'm in France now, so it'll take forever, because I have to use a free VPN to be able to download, and depend on if that node of VPN has not been recently used, because, you know, you can only download a file every each 120min... And other times not even that, you directly find that the time limit has ben used... But I know you're right, mixing is no good for success.


Anyway, thanks to you all for your answers and suggestions. I'll take the advice of "not mixing releases" and keep up with the same releaser.

P.S.: I don't know if I mentioned, but, the plugin loads correctly when loading it from zero. If I create a new track and load the plugin there, it works. The problem is that it is not loading in the project, after saving the project, when I reopen the project. And if I load the plugin on the track I'm using it but it does not load, it LOADS correctly. So, again, could it be a matter of mixed releases.

 

Focus on this information. If the plugin loads in an empty DAW project and not in another, the problem is in the project.

Keep in mind, when you save a project, each plugin settings are stored with a "saved state". You should be able to open the project with either just that plugin bypassed or all plugins bypassed somehow. Remove the plugin from the project. Resave the project. If you can save a "fresh copy" of the project so the working version is saved as it's own thing, you may not have any carryover issues from the problematic one.

As already stated, see how you setup the project (or DAW settings) and it's plugin handling. Try the various sandboxing options.

Also, if you ever need to test something like this; get a copy of Bluecat's Patchwork. You can load the "problem plugin" using it as a wrapper in the project, but you can also launch Patchwork as a standalone application with your DAW closed. That can be a good way to either fix a preset, save a new INIT patch as the plugins default loaded settings, and so on.

Don't just start randomly installing and uninstalling stuff when a plugin will load in Patchwork. But if you do go that route, use Revo Uninstaller Pro to do it so you can do a monitored installation which will then know exactly what junk to remove/delete.

some AI about blocking loading plugins in Bitwig:

Spoiler

In Bitwig, there is no direct keyboard shortcut to load a project with all plugins disabled. The best method for troubleshooting problematic plugins is to use Bitwig's robust plugin management system after the project is open.
Here is the safest workflow for dealing with a project that crashes on load:

1. Delete the plugin cache: Before trying to open the project, fully quit Bitwig and delete its plugin cache. A corrupt cache can sometimes cause startup issues.
   • On Windows: Go to C:\Users\your_username\AppData\Local\BitwigStudio\cache and delete the vst-metadata file.
   • On macOS: Go to /Users/your_username/Library/Caches/Bitwig and delete the vst-metadata file.
2. Relaunch Bitwig and let it re-scan: Open Bitwig again and let it re-scan your plugins. This may take a moment but ensures the cache is rebuilt properly.
3. Open the project: Open the problematic project. Because of Bitwig's sandboxing feature, a single plugin crash should not bring down the entire project.
4. Manage plugins in the Project Panel: Once the project is open, navigate to the Project Panel (or press Ctrl+P on Windows or Cmd+P on macOS) and click the Plug-ins tab.
5. Identify and manage problem plugins:
   • Red square: A red square next to a plugin indicates it is missing. This is often the cause of crashes. You can use this information to decide if you need to reinstall the plugin.
   • Yellow square: A yellow square means there is a version conflict. You can tell Bitwig to ignore all version conflicts from the bottom of the plugin list.
   • Reload crashed plugins: If a plugin has crashed and its interface is replaced with a notification, you can click "Reload Plug-in" to restart it. You can also click "Reload All Plug-ins".
6. Deactivate the problematic plugin: Once you've identified the plugin causing the issue, you can deactivate it or replace it to get your project working again.

Worst case scenario, you can always try renaming or moving the problematic plugin somewhere Bitwig is not looking for it, like your Desktop. Then it should just complain about a missing plugin without crashing.

 

Last edited: Oct 3, 2025 at 7:35 PM

Thanks, @clone ! I'll give it a try and keep on investigating tomorrow. I'm worn out now from all day chopping timber for the fireplace. Thanks!