Guys, R2R plugins do not derive from trials. We're not joking. These plugins derive from legit licenses. There's no point in cracking trials. The situation is different with Frequency Packs. Which are extras.

 

I think Ash Ultra and Midnight are getting a CPU fix tomorrow, so maybe an R2R repack or update to follow?

 

Okay that clears that up for me.

 

If you didn't installed the Acustica plugins yet (but already installed but didn't put in production) use VST2 plugins, as stated on one of the .nfo's if your workflow and DAW allows you to do so. Soon as i got this witch tip, my plugins loads very fast (faster than PA or Overloud, for example, that needs to check the license file) and with less sudden spikes on CPU than the VST3 plugins i had installed at the beginning. The overall CPU usage i think it's the same. Didn't noticed any difference and quite honestly i changed to VST2 ASAP when i got that tip from the .nfo, so really didn't tested. But the plugins are running with a OK consumption (on the same average of most algo plugins from Arturia) and FOR SURE less than legit ones if you use R2R framework as i do.

 

ok now seriously : )

Stevie, again thanks for this huge work.
I think that would be also useful to insert a list of the plugins that come with presets and which one dont (i didnt check, I rarely use presets, just seen many requests about this topic)

 

is there a performance difference AA vs R2 Framework?

 

Not to go too far off topic, but Giancarlo had a post about this topic in the facebook group yesterday, for anyone interested:

Spoiler: Giancarlo's post about wrappers

WRAPPERS!!

One of the first topics I'd like to address is the implementation of various plugin formats, as there seems to be confusion or a belief that we're hiding something. This approach has been transparent and discussed many times, but I understand that the details might have been lost over time.

At the core, we implement the VST2 format, which we plan to phase out. Our VST2 is the least potent and most bug-prone format we have. In our company, we build a single engine compiled in different versions, each based on varying components that extend functionality or implement formats. This modular approach is typical in software development, avoiding monolithic software construction.

For example, if a plugin's DSP core changes, there's no need to alter the connector (format). So, for an Audio Unit or VST3, the underlying code to be executed remains the same. This approach minimizes bugs significantly. When discussing wrappers, we are referring to a component we've developed internally. We don't borrow wrappers from other companies; instead, we build specific functionalities for each format and then integrate them with our product.

Our protocol allows different components, like VST3, to communicate with each other, accessing functionalities not present in VST2. This is also true for AAX. There's a misconception that a wrapper should simplify porting products, but that's not accurate due to our unique architecture. Our products are based on a singular engine with varying libraries. For example, when we updated our MAC code for VST2, VST3, and AU, we did so with native support for Silicon ARM architecture.

The transition to Silicon for Pro Tools products poses challenges as it requires updating to the latest engines and wrappers, potentially introducing new bugs. This necessity for comprehensive updates is why a modular approach doesn't automatically simplify the process. When updating, we need to address the entire product, including libraries, which might require debugging.

Lastly, our products are increasingly adopting a client-server architecture, evident in products like Modula. This architecture further separates the product into distinct components: the server handling DSP and the client managing user interface controls. An overarching component, often mislabeled as a wrapper, handles the implementation of formats like AU or VST3. Remember, VST2, our least potent format, will be phased out. While it's the simplest core and my primary debugging environment, the final user format can be quite different, requiring targeted debugging for each specific format.

I hope this explanation provides clarity on our approach to plugin formats and the underlying architecture.

Also worth noting that VST3 does a "true bypass" when not in use. E.g. In Studio One there's a "plugin nap" feature, which means the plugin essentially becomes disengaged and uses 0% CPU when the audio clip for the given channel that the plugin is on ends. It only works for VST3, not VST2, i believe

 

It's hard to believe his words. He's just not a honest person. Remember when we though that all that storage was because of the tech, as he said so? Giancarlo words doesn't worth a penny, if you see how much he lied (and lies). So... I don't know. FR

 

this is beyond my capability, you can always install only the VST2. It's recommended by R2R. About the VST3 being a wrapper, that's on AA.

there are mixed opinion about this but it seems like it's not just the full retail version missing the Frequency Pack which suppose to be downloaded separately. Will create a topic about Frequency Pack soon if I can.

a fix suggested by a member works. I updated the thread, try em out and see if it works for ya.

will add it soon.

 

Last edited: Nov 30, 2023

bro... color.. hahahhaha

 

I'll try it! And I'll let you know the results here.

 

Bug Report and Warning:
I opened a project with "ash" used and after loading the plugin it made a really loud noise, very dangerous for your hearing, I'm glad that my headphones weren't that loud! After loading another impulse and then the same again, it worked.

 

PLEASE report MORE ON THESE KIND OF BUGS:
report SO, DAW, if your DAW is legit, sample rate of the project, if using AA plugin VST3 and so on. Also report if you can reproduce the bug again in the same situation.

it's very very important, thanks!

 

@Stevie Dude
it seems that this page from AA site has direct links to manuals and plugin overviews, available quickly

https://www.acustica-audio.com/plugins-overview

it looks like a mess, Giancarlo's style lol it also needs time to load, but once done it seems to be pretty useful, maybe you wanna add this page if allowed

 

Guys, I've added [NOT CONFIRMED] to any ISSUE that haven't been verified. Sometimes, it could be my error, installation error or such, that kinda thing happens, so I thought it's better to have everything verified first and labeled them accordingly.

added to thread, waiting for others confirmation/verification.

I had the same experience with ASH ULTRA once during adding/removing while playing with it one the first day of release. It happened only once for me, I just assumed the plugin went crazy inside, removed and re-instantiate it, everything working great after. Haven't really used ASH ULTRA until today, only ASH, daily, no problem for now. It could be the plugin bug itself sometimes, but let's see if others are having the same problem first.

added to the thread.

 

Haven't tested this with AA factory presets yet, but rather than a fix, I have an alternative suggestion: I had plugins from other developers mute, not load the preset or crash the DAW completely when using a factory one. I'd normally circumvent this by simply taking a screenshot of the preset settings then reset to default (or reload the plugin) adjust them on my own by using the image as a reference and then save as a user preset with the same name (but with a number or a letter added at the end to create a new preset file and not overwrite the problematic original). If this works for you but the plugin had a lot of presets and with the method being tiring, I encourage you to cherry-pick your favorite ones and start with them. This will help you narrow the preset folder to a 'greatest hits' sort of list.

 

I think the huge spiking audio thing is just Acustica, not related to crack. It's happened to me too.

 

hey chief you are doing great, please just edit your responses
the @ work just fine in an edit

@Stevie Dude
the witches released a fix for Diamond Dyn. DS
Also confirming that AA mixed Trail and Full Licenced Versions.

The Problem is that AA Plugs see that as an error and Deactivate/Mute the Plugin
Forcing a crash

 

Last edited: Nov 30, 2023

9(

Yeah, I've noticed a theme with Acustica: A Lack of organization, and optimization. (And this is coming from a LONG time fan, and user of Acustica products).

The Acustica site is a mess... it's poorly organized and optimized. It takes FOREVER to load the images, its a symptom of the issue with Acustica, they undervalue the importance of ease of use, but over value the use of High-Res images.