Originally Posted by idoru97214 ➡️

That's fair. He is very impressed with himself. Lol

Originally Posted by Ringthane ➡️

My only technical issue with 821 is it's essentially one flavor. A great flavor, but limited. I have issues with their pricing and pre-order "Masterpiece" marketing too but I think I can overlook that when a product is great (which they are).

My broader issue is with Ziad... the way he spoke to/treated Jantex in the thread is beyond his typical self-congratulatory/regard/aggrandizement. He can keep his plug ins. Y'all are welcome to spend your $ how you see fit, no judgment here.

Tape and Taupe: I have a bone to pick with up AA as well (who pissed me off this Easter, lol?). Taupe is nearing 7 years old, Pink is turning 5 y.o. next month. They really, really need an update.

Originally Posted by olshalom ➡️

m3 ultra, 32core, 256 GB unified memory:

I'm running multiple times into a annoying memory issue with any aqua plugin.

I've done multiple test projects.
By reaching a unified memory load of about 45 GB, with each opened instance memory loading get's slower and slower. To me it looks like exponential.

Tested in vanilla REAPER and logic pro installs.
Same behavior for both DAWs.
Sequoia 15.4.1 and 15.3.
No problem found with System Diagnostic.

Why is it needed to load the exactly same vectors/samples multiple times into memory for the same kind of instances?
Why these are not shared by multiple instances?


Related to a specific test project in REAPER:

4 instances of {StrawPre, Teal, SandUltraEq, SandUltraComp} on each track.

CPU utilizing meters inside REAPER, activity monitor and istats start to max out at about 60 tracks (=240 instances). Aqua's are reporting wrong values, while REAPER's core percent per track is pretty accurate.

I maxed it out with 900(!!) aqua plugin's running on 225 tracks by adjusting buffer settings inside REAPER for having no dropouts and snappy graphics fully utilizing all 32cores. 165GB of unified memory. That's insane!

BUT !!:

It took FOREVER to duplicate tracks.

At a certain plugin count (about 600, I guess) aqua graphics start to break.
Meters do what they want.
Eq graphics in ultra versions do not respond properly while knobs still respond and adjustments take place in the audio.
Opening a plugin's GUI works properly in an acceptable amount of time. Even with 900 instances.

loading such a project takes FOREVER. To be precise 3 hours and 47 minutes. :-)

Also checked REAPERs performance by loading kontakt libraries with total over 50 GB of memory.
No such issues. Loading times are excellent.
It seems REAPER performs great about this.

Anybody could replicate?
@ Giancarlo and Acustica, could you replicate or ever tried aquas on that kind of a computer?

Originally Posted by zaphod ➡️

We have a lot of projects in the works, and we’ll try to make this one happen too

Originally Posted by zaphod ➡️

I understand you have a lot of RAM, but we’re not doing anything unusual on our end. I’m also not sure that all available RAM runs at the same speed—there might be differences that affect performance. Or bottlenecks. We are using standard calls

Originally Posted by Ringthane ➡️

My backordered M4 should be here in a week so I will holler with any findings.

Originally Posted by djshiny ➡️

i just got my m4 max setup on friday. Still installing stuff, but have started doing initial testing. Ive so far found Acustica plugins have a bit better performance on my Max than on my M1 Ultra. There is a definite noticeable improvement. i havent done an exact numbers test yet, but to me it feels like 15% improvement, maybe more.