Hello all and thanks for taking the time to read my query on the problem I am experiencing.

Ableton 12.1.10 is running well with no issues except the one this thread will be discussing.

The Audified all-plugins bundle listed here installs fine and runs fine. The problem arises when I try to remove a loaded plugin from an Ableton Live session (delete). Then the entire session crashes.
Ableton Live 12.1.10

Audified Complete Effects Bundle v2025.6.16 by a certain TeamCubeAdooby:

Audified 1A Equalizer v1.0.2
Audified GK Amplification 3 Pro v3.1.5
Audified Linda IronVerb v1.0.2
Audified MixChecker Ultra v1.0.1
Audified RZ062a Equalizer v2.1.4
Audified RZ062b Equalizer v2.1.4
Audified U73b Compressor v3.1.4
Audified U78 Saturator v2.1.3
All plugins are of the VST3 (x64) variety.

PS. This bundle mentions something about AppID being the same as previous release. I am unsure what is meant by this. I figured that if it is something important that must be manipulated using some other app, it would be mentioned more thoroughly.

These plugins require Microsoft Visual C++ libraries to be installed.

What they recommend:
Microsoft Visual C++ 2015-2019 Redistributable
v14.32.31332.0 (x64)

What I have installed:
Microsoft Visual C++ 2015-2022 Redistributable
v14.44.35208.0.0 (x64)

This is due to the fact that it seems this newer library supersedes the one recommended by the Audified bundle.

The computer in question is:
Windows 11 24H2 (OS Build 26100.4351)
Ryzen 9 7845HX (12 cores)
32 GB RAM

All plugins load and function properly, but when removing a plugin (delete) the Ableton session locks up and crashes.

I am having no other issues on the machine in question, Ableton related or otherwise.

Any help would be appreciated, even if someone is only able to report that they are having the same issue.
The same goes for anyone successfully running these plugins, especially if you are running them fine with the same versions of Ableton and/or VIsual C++ Redistributable.

 

Which buffer size do you use in live?
Actually I have a similar problem with a plugin.
It crashes also.
But only on 512 samples and more.
In 256 samples everything is fine.

 

Brillliant! I seem to have found a solution to the crashing.

I was using the default MME\DirectX setting, which seems to require 4096 samples or it just crackles. I am using integrated Realtek Audio.

I now switched to Realtek ASIO (will have to look into other ASIO drivers later) and when I set the sample rate at 384 samples, I can seemingly use all these plugins and remove them without causing a crash.

Thank you so much for the idea. I was thinking in all other directions but this one.

I will note that (I am pretty sure) it still crashed if I put the sample rate too low on Realtek ASIO, but 384 is fine. I'd probably set it higher if the slider wasn't so particular about which values it will take. 384 looked "nice and binary" and is in the 256-512 area ;)

Now to see if this changed has caused problems elsewhere.

Thank you so much for your reponse. You've been a great help!

UPDATE: Hmm. Still having some crashes using the plugin. Testing heavy combos now. At least it is not ALWAYS crashing on removal, like before. Will keep testing.

 

Last edited: Jun 29, 2025

Might be a problem with the release and not your DAW/settings. Happens in Reaper as well and has happened with previous TeamCubeadooby releases too. I'm almost certain there were (a couple?) re-releases last time before the crashes stopped. (I only use GK AmpPro.)

 

Try the most reliable one from Team R2R:

Audified 1A Equalizer v1.0.2 READ NFO-R2R
Team R2R | 2025.06.22 | 25.6 MB

 

I should probably have mentioned earlier that I did try an earlier release by R2R, because I trust them. Exactly the same result. It's just weird to me that these are the only problematic plugins for me at the moment. And it's ALL Audified plugins. (Why not just one, or some? This fact had me seriously questioning the Visual C++ dependencies.)

 

Then I would expect a lot of reports of this very problem, but I have found none.

If you read above, changing the audio driver did have a positive impact, but there seems to be some lingering issues under certain circumstances. I am currently looking into it (mainly playing around with buffer size)

As a side note: This solution sorta makes sense to me because on my previous machine, where I also used Audified (but older versions) plugins, I never had an issue. However, I believe I used FL ASIO in Ableton.

 

The problem is usually the individual plugins, closer to "almost always". The first thing I would do would be to use Revo Uninstaller Pro to clean up your system while uninstalling them, since you had R2R vesions installed, and then these. Update the Visual C++ dependencies if you can. But everything else you are using which relies on those dependencies would "almost always" also exhibit problems too. If you think you would find some reports of problems with a DAW, the reports of problems with a Visual C++ release from Microsoft would be 1000 times that.

You included a lot of information, but am I just missing the audio interface you are using? You are mentioning a lot about which ASIO driver you are using but not which interface you are using it with.

Before all this, did you read the nfo file from R2R Mixchecker release? It's about LexActivator and contains some pretty funny other info. I think it was the first public mention of TCD's Bypass Everything Technology (TM)

You are probably trying to fix something you cannot fix yourself.

And then about the bundle you have now installed:

Spoiler

A witch says,

* Our release uses less resource than original, especially when you run the
multiple instance. This also soves minor Audified's license between the
threads.
* LexActivator emulator is injected to the plugin, which returns valid license
information to the software and handle callback system. It also avoids
writing broken data to the registry (LexActivator's bug).


We checked their latest release called
"Audified.Complete.Effects.Bundle.v2025.6.16-TeamCubeadooby"

* Direct memory leak in calloc still exists (TCD Bypass Everything Technology)
* Acess violation crash still exists (TCD Bypass Everything Technology)

Those 2 issues are already pointed out in the last NFO but not fixed at all.
We are often asked about if TCD improved the quality of their releases or not.
This fact explains everything.

 

Last edited: Jun 29, 2025

I am using the integrated Realtek audio interface on the laptop. Incidentally, I also used Realtek on a previous machine without issues. But again I want to emphasize that the versions of those Audified plugins (on the old laptop) are most likely quite a bit older and most probably R2R versions, as I tend to stick to R2R whenever possible.

No, why would I?

Oh... That's why...

I actually installed the TCD bundle twice. First, and then it would crash on exit, as per the problem in this thread. I uninstalled TCD and installed R2R U73b compressor and U78 saturator from R2R, which also happened to be the version released prior to the ones in the TCD bundle. To my amazement they behaved the exact same way. So I uninstalled those and went back to TCD to "fiddle with them" and here we are.

It seems nobody else on the sister site reported problems with the TCD release, so I figured they had it working and something was wonky on my system. But then the most likely culprit, other than broken plugin, would be that my C++ libraries were somehow incompatible. But now that you point out that R2R message I am confused why the R2R versions exhibited the same issue...and I am not seeing anyone else reporting it.

 

the reason I suggested using Revo to uninstall and cleanup, is because when you install and remove applications and plugins; they almost always leave some kind of remnant files. When you install a release from any Team, and then a different one, switching back and forth like that; even if both releases would work perfectly on their own, you could even still run into some issues. R2R even write that as step 1 in most of their installation instructions, and they even mean their own prior releases you have installed. Unraveling the problem with anything becomes way more difficult.

I can't say why you are not seeing reports or reviews from other users about the plugins. Maybe they are just not worth the headache when there are so many other options with less bugs and problematic DRM. You could go through the list you have installed, and get recommendations for replacements for each one from other PC users, and very likely end up with better sounding plugins.

 

Thanks for sharing your experience with R2R. Plugin crashes are often due to programming errors, and frequently they're graphics issues. OpenGL issues are very common. There have also been cases where it was Microsoft-related.
Ultimately, it's the manufacturer's responsibility to ensure their products work.

If you install this latest version, you should be able to rule out Visual C++ issues.
Visual C++ Redistributable Runtimes All-in-One June 2025
Latest June 9, 2025
https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/

Ableton works best with 256 samples. You can start with 512, then 256, then 128!
If it still crashes, I'd look for an alternative to Audified. Crashes are annoying and time-consuming.

Optimizing Windows for Audio
https://help.ableton.com/hc/en-us/articles/209071469-Optimizing-Windows-for-Audio
How to avoid crackles and audio dropouts
https://help.ableton.com/hc/en-us/articles/209070329-How-to-avoid-crackles-and-audio-dropouts

EDIT - R2R says

We checked their latest release called
"Audified.Complete.Effects.Bundle.v2025.6.16-TeamCubeadooby"

* Direct memory leak in calloc still exists (TCD Bypass Everything Technology)
* Acess violation crash still exists (TCD Bypass Everything Technology)

Those 2 issues are already pointed out in the last NFO but not fixed at all.
We are often asked about if TCD improved the quality of their releases or not.
This fact explains everything.

 

Last edited: Jun 30, 2025

Usually the post on any software drop is filled with bug reports if they are present, even more obscure bugs like synths failing to save preset if user has performed "action A". So, I am surprised to see none under this one. Had me feeling this was a "me problem".

I am going to uninstall using Revo and do a clean. I already took a look in RegEdit and the plugins have very few entries in their most obvious keys. Going to give the R2R versions a go after that to satisfy my curiosity.

The plugins are still crashing. I don't know if I just got lucky with one session and changing sampling rates working a few times.

Also ran another test because I was thinking "maybe other users are not deleting these plugins from their session and therefore not experiencing the problem." So I tried something new: Inserting an Audified (TCD) plugin and quitting Ableton. Crash. So, someone should have experienced that, but maybe thought "my Ableton is crashing now, for no reason."

As far as I know, these are very popular plugins. Well, at least the U73b compressor and U78 saturator are. They are also very nice quality (to taste). Slate offers a U73B as well, but...

On my older laptop I had "every" plugin imaginable. I was testing. But now I will stick to Fabfilter and some "special sauce" plugins and these are two of those.

We'll see how it goes.

 

Last edited: Jul 1, 2025

R2R is the best there is in my experience. Can't recall having an issue with any of their releases. Which puzzled me when their version of two of these plugins failed similarly. Led me to believe the problem was on my end and TCD was fine too. But no...

Your comment inspired one more test, however. Since my laptop has both integrated and discrete graphics, I tried switching between them to see if one had an OpenGL issue. Turns out it crashes no matter which GPU I use.

I have this installed since before these plugins got me questioning the compatibility with this newer one. Only because the NFO talks about the older 2015-2019 VC++ redistributable. Thinking it's most likely fine and not the problem.

I have mine set to 384 samples with Realtek ASIO at the moment. The interface for their driver is slider controlled with increments of 24, making for "awkward" looking numbers.

Yeah, but I am pretty sweet on that U73B and U78. But, obviously, if it's not working then it needs to go.[/QUOTE]

 

Definitely, which is why I looked on another site where you can see all the other related (same team and dev) releases on the same page of your search results. When you can see the completed download numbers vs bug reports, you can have a very good idea when something is a "me problem" which is usually something about your own system. When hundreds of people try something and no-one or almost no-one comments with problems, the problem is on your end a huge portion of the time. The best start is to always begin with a clean installation of a known-working release.

About the Visual C++ runtime, I did get this little chunk of info from chatgpt:

Spoiler

If an app specifically asks for v14.32.31332.0, it will still work perfectly with v14.44.35208.0 as long as it doesn't do a version check based on the exact number (which is rare and discouraged by Microsoft).

That is a very specific possible issue, which others would have also encountered. But you could always track down the superseded v14.32.31332.0 and try it.

GPT found file:

Spoiler

Here’s an official spot where you can download version v14.32.31332.0 of the Visual C++ runtime:

• On GitHub, the v14.32.31332.0 build (x64) is linked from this community-supported gist that references the official Microsoft download URL:
  https://aka.ms/vs/17/release/VC_redist.x64.exe microsoft.com+10gist.github.com+10learn.microsoft.com+10
  

That aka.ms link is a permalink hosted by Microsoft, pointing to the official Visual Studio 2022‑era runtime corresponding to version 14.32.31332.0. You can use it to fetch the exact build:

• x64 download: https://aka.ms/vs/17/release/VC_redist.x64.exe (v 14.32.31332.0)
  

✅ TL;DR

• v14.32.31332.0 is a legitimate, official build from the Visual Studio 2022 (17.2.5) branch .
  
  
• The provided aka.ms link is maintained by Microsoft and points directly to that specific version.
  
  
• You can download the x64 installer using the link above—no need to rely on third-party sites.
  

 

Last edited: Jul 1, 2025

Ok. Just uninstalled the TCD bundle using Revo with a full scan to get all remnant files and registry entries.
Installed this release from sister site: Audified.U73b.Compressor.v3.1.3-R2R
It behaves the same way and crashes on deletion or if present in a session when closing Ableton.

This is so weird. It must have something to do with not being able to release the hooks in the audio chain.

Also tried using MME\DirectX in 16-bit 44.1K as well as my default 24-bit 48K. The Realtek ASIO driver doesn't let me switch from 48K.

Oh well. This sucks. Not only is this annoying because it doesn't "just work." It makes me question why this seems to be a problem on my setup when everything else works beautifully.

At this point I just want to know I am not the only one having this issue. A "me too!" would be great or at least an overwhelming number of responses telling me they are using it and it is perfectly fine.

 

Hi @Wired, it seems other users don't have any crashes.

I think it's related to your Realtek ASIO. I would recommend the following:

ASIO4ALL is a freeware universal audio driver for Windows which supports ASIO.
https://de.asio4all.org

Setting up ASIO4ALL (Windows)
ASIO Buffer Size = 256 Samples
https://help.ableton.com/hc/en-us/articles/115000204630-Setting-up-ASIO4ALL-Windows

 

Three people on the sister site confirmed they have the same issue with the latest release, similar number of reports for most past releases. Including me and you, that's five just for this one.

Wish I could tell you which release I had previously installed that fixed it, but I don't remember - been a while since I used Audified stuff. May have been the R2R one.

Probably. Agree with clone - likely not something you can tweak away on your end.

Sister site comment: "always been this way" - can confirm, all the way back to the first bundle release I installed.

Can also confirm that legit Audified plugins do not crash for me.

Did you double check that your DAW is really loading up the R2R version? Maybe you still have copies of TCD's U87 on your disk and your DAW happens to load that one over the R2R one.

 

Ok, lots of questions in the queue to answer, but for now:

I think I have finally solved this. At least with the R2R version I am currently using. Of all things, it seems to be connected to the HiDPI setting in Ableton. I had it switched off for some reason I cannot remember, but IIRC it was some plugin looking strange and buttons being in the wrong place and not responding. With HiDPI switched back on I have not manage to make it crash a single time.

Seems strange that this would affect a plugin unloading and bringing down the application, but that seems to be the culprit.

Now I need to decide if I am going to try to install that TCD bundle. I only really wanted two of the plugs, but ... we'll see.

Will update if I was just VERY lucky and managed to unload the plugin multiple times in multiple instances.

Just to be very clear for posterity:

I had Settings-> Enable HiDPI Mode set to OFF when it was crashing. Switching it to ON seems to have solved the issue.

 

UPDATE:

The issue is not solved. The crashing is back. I have no idea why it was working fine when I reported changing my HiDPI setting. I was loading and unloading the plugin like crazy and it never crashed. I truly believed I had this one figured out. Turns out that wasn't the case. Now I am stumped. It crashes every time I use it now.

Thought: what 'else' was different when it was working? Clean install. Not working. Change audio settings (ASIO). Not working. Change HiDPI and not a single crash in something like 20 runs. Leave it alone for a few weeks. Doesn't work.

 

Thanks for the update. Probably best to stop looking for patterns at this point.