Doesn't look like R2R is going to fix Desert soon or anytime for that matter. Has anyone come up with some fixes for the issues it has ?

 

Graphite VST3 dont work (black screen crash)
Win 10 all DAWs

But VST2 works right ...

any idea ?

 

Last edited: Sep 22, 2024

I tried on Win 11 and Reaper 7, both VST3 and VST2, and it crashed Reaper consistently. I gave up

 

Works fine as VST2 here, win 23H2: Cubase 13, Reaper, Studio One 6.6.2, Studio One 7.

 

Thanks. It must be something on my end. All my other AA plugins work but not this one. Very weird. I'll see if I can figure it out.

 

Need to be very careful about the "common" files, and were they go.
So im not the only one with VST2 only, thanks for the info !

 

what's the latest word with these plugins with regard how acustica are dealing with cracked plugin detection? banning accounts? temporarily? permanently? if all applicable cracked files are removed before running aquarius, is aquarius still able to pick something up? logic tells me no, but I've seen scare stories of aquarius aggressively scanning your hard drive and OS?

 

I DL'ed Graphite after reading ItsFine post. I was curious.

I installed as vst3 only...works perfectly. And is a very, very nice piece of software.

Reaper/Win10

 

Aquarius scan AA products. And your legit account can be banned from this scan.
Automatically and FAST.
Of course, you can contact them, remove the culprit product and tell them to recover your account.

But i would not "play" with AA on this side
If they don't want/don't have time ...

Basically, AA push us "all legit" or "all pirate"
And so, they push third party creators along with them

 

i have a friend who is running them both, side by side. Cracks, and legit. Cracks are stored in a different VST3 folder than the system one. As far as i know, aquarius only checks the system folders. Im not sure about nebula tho.

 

Was the potential security risk ever explained? I recall reading something a while ago, I think part was from an nfo, alluding to a potential backdoor into customers pc that could be exploited by hacker or AA themselves.. Maybe I'm talking shit or misinterpreted.. Sure I read something along those lines though.

 

There are a couple of AA plugins I’d like to buy, but I refrain to do so because they can’t coexist with R2R. Honestly, that’s just AA’s loss of revenue: instead of buying those I actually use in the long run, I don’t buy none at all…

 

Sadly, it is too risky for now to use both legit and scene.
That's why i said it is probably pushing ppl all NON legit ...

No risk and no money lost.
Yes, it is stupid ... but that's how Giancarlo is leading AA since day one.

 

Has anyone found anything glaringly wrong re: OCEAN yet?

 

Everything seems fine but loading presets its too slow

 

Cross-posting in this thread because I'm stumped regarding a black GUI when launching Jade VST3 on Wavelab. Do you guys have any hints ?
I'm willing to paste the Acustica Framework files in my System32 folder but do I have to overwrite the existing ones there ? Should I do a backup before doing so?

Help with Acustica Installation

EDIT: I'm a dumbo, I previously added the environment variable by adding a new line in System variables. I added the line "C:\Program Files\Acustica\Framework" to the PATH entry and now everything is working okay.

 

Last edited: Jan 23, 2025

Hello everyone, I have a few questions I’d like to ask, and I hope someone can help me out:

1. At a 48kHz sample rate, does Pink’s compressor also need to run with oversampling in MetaPlugin to achieve the correct compression response? I saw someone mention earlier that the lack of 48kHz sampling has a significant impact on the Pre section—does it also greatly affect the compressor’s behavior? I didn’t notice any obvious issues when loading Pink’s compressor directly in PluginDoctor.
   
   
2. If I want to move away from the R2R version and return to my previous legitimate license, what’s the safest way to uninstall the R2R version? I’m really worried that if I switch back to the official version, my account might get banned.
   
   
3. I recently learned that oversampling can introduce pre-ringing and post-ringing artifacts. I think I can hear the transient differences caused by oversampling—have you noticed this as well?
   

 

Please uninstall the product and delete all associated files. Restart your PC and reinstall your legal version.

 

Spoiler: The AI Help:

TL;DR:
Yes, oversampling can improve Pink's compressor accuracy, but it’s especially critical for the Pre section rather than the compressor itself. The compressor can still sound and behave fairly accurately at 48kHz, but certain nonlinearities (like harmonics or aliasing behavior) may not be fully captured without oversampling.

Deeper Breakdown:
How Acustica plugins work:
Acustica Audio's plugins (like Pink) use dynamic convolution and load huge sampled impulse responses of analog gear. These are sensitive to sample rate, input level, and aliasing artifacts. When run at lower sample rates (like 44.1kHz or 48kHz), nonlinear components (like saturation or harmonic distortion) can alias more noticeably—especially in the Preamp and sometimes EQ sections, where harmonics are more prominent.

Pink’s Compressor:

• The compressor section in Pink is based on sampled analog dynamics behavior, but it’s less sensitive to sample rate than harmonic-rich parts like the Pre section.
  
  
• That said, aliasing can still occur, particularly when the signal level is hot and the gain reduction is intense—because those conditions can provoke harmonics or intermodulation distortion.
  

Why oversampling helps:
When you wrap Pink in DDMF MetaPlugin and engage oversampling:

• You're running the plugin at a higher internal rate (e.g., 2x, 4x, etc.), which pushes aliasing artifacts further above the Nyquist limit.
  
  
• This helps preserve more accurate nonlinear behavior, especially in the Pre section.
  
  
• For the compressor, the benefit is more subtle—but it can improve transient accuracy and reduce potential aliasing on fast attacks or when driven hard.
  

PluginDoctor Testing:
When you test Pink's compressor in PluginDoctor:

• It may not reveal problems unless you're driving it very hard or analyzing the harmonic/aliasing response closely.
  
  
• PluginDoctor itself may not account for dynamic behavior over time or level-dependent distortion curves, which are crucial to Acustica plugins.
  

Final Verdict:

• Pre section = definitely benefits from oversampling (big difference at 48kHz vs. 96kHz).
  
  
• Compressor = not essential, but still beneficial with oversampling if you're chasing the cleanest, most accurate behavior.
  
  
• If you're working at 48kHz and want the most faithful sound, running Pink in MetaPlugin with 4x oversampling is a solid idea—especially if you use the Pre or are pushing the comp hard.
  

Want help setting up oversampling in MetaPlugin for Pink?

Source: AI

 

The AI answer above is wrong and has nothing to do with why you need to oversample Pink. The reason to oversample Pink to 96k is because there are no programs/vectors for 48k and 88k. So you either run 44.1k in your 44.1k project, 96k in your 96k project, or you 2x oversample your FX chain in your 48k project so that the chain is now running at 96k, so Pink can run through the 96k program/vectors.