No. You move the entire content of the folder "AU" into /Components folder. Then you do not have to change anything at all, because you are not moving the "AU" folder into that directory. Codesign each .component and you are done (or do them all at once).

 

Did anyone got Tiger and Jam working?

 

Not me. They weren't done correctly, apparently. So you could go in and try and edit them but you'd have to fix whatever is wrong. Some filenames have the T still in them, so there are possibly other errors in the XML files. It might be easier to just start over with the original r2r files and the demos to systematically create them rather than digging around for random errors.

 

Yes, I also had a Behringer mixer and sold it. You can do anything with digital, especially since artificial intelligence has entered the game.

Nebula is a good alternative. On Russian trackers, libraries can be downloaded for free

 

Last edited by a moderator: Apr 11, 2024

ok

 

Acustica plugins do not work in Rosetta mode, Giancarlo has confirmed this before. This doesn't seem to apply to their newer stuff (such as Pumpkin Pro, Midnight, Arctic) but it's best if you just don't combine Acustica and Rosetta, better safe than sorry ig

 

what about the ENG and AQU files? Do we keep them, trash em?

 

I trashed them. Got the N2S & the Folder from R2R, then just added the vst3 & xml files.

 

Last edited: Jun 19, 2024

and do we have to edit each XML?

 

I have a friend who gave me files for Tiger, Jam, Cardinal, Cream & stuff. So, I don't know, I just codesigned & they worked. Yesterday, I tried it myself for Aero. Just codesigned & no need to change anything in the xml, they work.

 

hmmmm idk what I did wrong, I have some legit and some R2R but I did all legit stuff on VM and transferred over, but then nothing was working in ableton. I had legit files in AU, cracks in VST3, idk where I went wrong

 

how do we block acustica from accessing the comp? Deleting Scorpion files? or something else? I'm kind of nervous to try again, dont want to get bricked

 

I have my doubts about aquarius. I didn't install it. I unpacked it using pacifist. I ran it after making a backup of the framework shall it tinker with it. I only installed Aero [which is free]. Then removed aquarius. It's a strange thing. It took 10 mintues to just boot up after getting information from the server...could have scanned my whole system by then. Well, my buddy don't do amps, so I had to drop my feet in the strange land, and yet I withdrew quick. He too once got a 24 hour ban. For the future R2R releases, I'll just be grateful to him & let him handle these things.

 

I just did my first restart after the aquarius thing now, It left cache & added a helper tool that runs in the background as a launch deamon. Bloody hell, can't these companies just not bother you and let you live a peaceful life. What help if your tool and surveillance gonna offer me. Bloody greedy bastards!

P.S. - Now my Aero doesn't output any sound. Had to replace it from a Back-up I made just in case something like this happens. Bloody nuisance.

 

Last edited: Jun 19, 2024

Yeah the no sound thing is what happened to me! I think for now I just have to stick with my Legit plugs, which is a bummer because I want more than a 15 or 30 day trial to see if a plugins is useful in my workflow

 

Did you have any luck getting these to work on Sonoma?

I am having an issue on M processor mac or Sonoma where the GUI elements at the very top (LOAD, SAVE, A/B, OPTIONS, etc..) are not appearing properly.

This works perfectly on Intel/Monterey and from recollection it was fine on M1/Ventura, but the GUI elements appear to be glitching (in Acustica and Nebula) on Sonoma. Went through every possible file it accesses via terminal and opensnoop across both computers and my guess is that the issue lies in the way Sonoma is handling access to the .dylib files. I am not sure what changed, but codesigning, batchmod, etc will not fix the issue.

Just wondering if the problem is unique or if others have experienced it.

 

I remember seeing someone mention this but I forget where. I do not see that it is an issue specific to your MacOS, because it would be mentioned by more users. Make sure you installed the framework correctly and codesign that just in case. The way I suggested previously to install, was to install Aquarius, login on it, download any free or demo plugin and install that. Then delete only the plugin and it's related files in your components or vst folder. Delete Aquarius. Then add the real plugins, and codesign them. Firewall them in.

You probably have forgotten steps you took to install them before, on other MacOS version. Screenshot your plugins folder with the common files and plugin specific folder showing in the image. Or you could try this, it will codesign every plugin on the machine, otherwise look through the thread and ask someone who is using Sonoma, I'm not:

cd /Library/Audio/Plug-Ins/

find . -name "*.bundle" -execdir sudo xattr -cr \;
find . -name "*.VST" -execdir sudo xattr -cr \;
find . -name "*.vst3" -execdir sudo xattr -cr \;
find . -name "*.component" -execdir sudo xattr -cr \;
find . -name "*.dpm" -execdir sudo xattr -cr \;
find . -name "*.bundle" -execdir sudo codesign -f -s - {} \;
find . -name "*.VST" -execdir sudo codesign -f -s - {} \;
find . -name "*.vst3" -execdir sudo codesign -f -s - {} \;
find . -name "*.component" -execdir sudo codesign -f -s - {} \;
find . -name "*.dpm" -execdir sudo codesign -f -s - {} \;

 

happens here as well. Funnily, it doesnt show up in LUNA that way so i cant really pinpoint what the problem is and why.

 

Interesting, perhaps it's DAW-specific. Using Ableton Live 12.1, will try on Luna to see if it mirrors your situation.

 

The compressor in your screenshot is not an Aqua, right? It is Cupwise for Nebula... little colorful logo under the left side meter. That would be a different issue as his with Ash.