Yeah, Im gonna go with the AAX is too new for AU12.5 but R2Rs version isnt or its been modified to work with 12.5.

 

The Pro version is available via "Friendly Sites" link.
I'll PM with a link.

EDIT: Of course, as you speculate, it seems unlikely that your problem is the old install, but it is a good tool , especially for those things you'd like to try but want to fully clean up if you decide against it.

 

Last edited: Jul 15, 2025 at 4:38 PM

does it open in any other DAW like Reaper?
that way you can rule out problem being specific plugin type/rescan or more broad issue, maybe with iLok licensing?

 

most people never bother to actually use Patchwork. they use it for loading plugins and testing, but PT users almost always say it "slows down their workflow". This kind of thing is a result of using Protools and "sister site versions" of plugins. If something works, then great; and if not, you already know why.

If you are almost always using Patchwork for one plugin, you can just load that plugin and save it as your user default; so that every time you open patchwork it has that plugin immediately loaded.

Depending on the changes with the individual plugin, per the changelog; I would just feel better about paying for something i'm using and supporting the developer. For about 30 seconds at least, and then I would reinstall the R2R version anyway.

I mentioned this earlier because he sounded confused which version Protools was actually trying to load, the old R2R install or the new legit one. The AAX in Protools should show the same version as the legit VST format plugin loaded in another host or Patchwork.

 

Yeah I sent them an email yesterday. But they will tell me to ask Avid about it, and Avid won't help me because I'm using AudioUtopia PT.
My friend runs the same plugin on his AU Pro tools without issues.

Yeah I had checked Hosts and Firewall, nothing is blocking it.

 

No, a friend of mine runs seventh heaven (same version as me) on his AU12.5 Pro Tools.
It should work.

 

Yeah I can open it fine in Pro Tools with a VST Host plugin (Patchworks). The VST3 works fine.

 

Thanks, I will try the Pro method that someone mentioned earlier.

 

Unfortunately installing the R2R version with Revo PRO, tracking the log and uninstalling did not work either.

 

I have never tried it but I can from my own experience say Total Uninstall has never failed me - yet - It doesn't mean it won't sometime, but so far, so good

 

Total Uninstall looks to be a similar "monitored install" premise and probably same results; but it can never hurt to check if you aren't buying anything to do it.

I think there is maybe some little detail derailing the process somehow. A duplicate copy of the AAX installed, some anomaly. I thought someone probably had already suggested flushing the plugin cache in Protools but I do not see that in any posts. here are steps from google:

Spoiler

Yes, you can force Pro Tools 12.5 on Windows to rescan all your plugins by deleting the AAX plugin cache file.
Here's how:

1. Close Pro Tools: Ensure Pro Tools is completely closed before proceeding.
2. Navigate to the Cache Location:
   • Open Windows Explorer.
   • Go to this path: C:\Users\%username%\AppData\Roaming\Avid\Pro Tools\.
3. Find and Back Up the Cache File:
   • Locate the InstalledAAXPlugIns file.
   • Important: Move this file to a safe location (like your Desktop) as a backup in case you need to revert the changes.
4. Restart Pro Tools: Relaunch Pro Tools to initiate a full rescan of all plugins.
5. Verify and Remove the Backup: If the issue is resolved and your plugins are appearing correctly, you can safely delete the InstalledAAXPlugIns backup file you created in step 3.

Please note

• After deleting the plugin cache file, Pro Tools will re-scan all of your AAX plugins, and the process may take several minutes depending on the number of plugins installed.
• Deleting this file will force a complete new plugin scan.

This process effectively "flushes" the plugin cache, ensuring Pro Tools rebuilds its plugin database and includes all your installed plugins during the next launch.

 

One of my posts had a link where that was part of the solution for a similar issue (but for Soundtoys instead). At this point, I would nuke Pro Tools, rename the AAX folder so that no plugins are picked up, then I would reinstall the DAW and Seventh Heaven just to see what would happen. If losing settings can be a problem, maybe create a restore point before doing all that.

 

I'm always reluctant to make those sorts of suggestions in a thread that has followed a less than systematic bunch of recommendations. Other than data corruption, bad hard disk, logging in as systemwide root and running a bunch of commands you don't know what they are, or malware; you should really be able to fix almost anything, theoretically. Time involved, diminishing returns and so on, make save and pave approaches start to make more sense; but admitting defeat by a plugin you just paid for would annoy me. I'd reinstall the R2R release and call it a day until I backed up. Runs faster, uses less memory, no ilok driver. Try again after a break from it.

 

The thing is that he mentioned having issues with the R2R:
"I had the R2R version of Seventh Heaven installed.
but after noticing it has issues, I decided to buy the real product."

Maybe it is not the R2R but something else (?)
It would be good if he elaborated on the issues.

 

Reinstalling might solve your problem.

1. Back up your data first.
2. Manually delete all files, including the registry.
3. Restart your PC.
4. Reinstall Pro Tools.
5. Install your purchased Seventh Heaven.

Delete following Folders:
C:\Program Files\VSTPlugins\LiquidSonics
C:\ProgramData\LiquidSonics
C:\Users\YourName\AppData\Roaming\LiquidSonics
C:\Users\YourName\Appdata/Local/Liquidsonics
C:\Windows\System32\R2RLS7HP.dll
C:\Program Files\Common Files/Avid

 

Last edited: Jul 16, 2025 at 9:05 AM

I wouldnt mind using the R2R version. but as many other people have complained about;
the right channel has volume jumps / cuts in and out with early reflections.
If you slide the early reflections all the way to the left, you can clearly hear it.

This is because R2R missed 1 layer of protection hidden deep in the code.
R2R never bothered to fix it, maybe because it was too time consuming for them.

 

I also want to say that I am very thankful for the effort you guys have put in.
I signed up just for this issue, and did not expect anyone to chime in to be honest.
Even though I have not yet found a fix, I am surprised by the amount of support on this forum.

Currently just waiting to see what LiquidSonics support has to say about this.

 

which precisely is why I recommend it to troubleshoot