please read the rules, it will answer all your questions!

  • Get the best VPN on the market with 66% Discount!
Software, Mac OSX
Acustica Audio Camel 2023 macOS screenshot
macOS | DEC 2023 | 315 MB
Camel is a 4-plugin suite encapsulating the sound of 2 iconic British pro audio brands that have earned their reputations as industry leaders thanks to their technological innovations and achievements.



download from free file storage
click to show download links


download from any file hoster with just one LinkSnappy account
download from more than 100 file hosters at once with LinkSnappy.

comments

  Contributor 11.10.2014 7974 15556
+392775
Rapidgator | KatFile | Nitroflare
mirror
http://peeplink.in/01de40036077
Get Premium:
https://katfile.com/free269170.html
http://rapidgator.net/account/registration/ref/1854888
https://www.nitroflare.com/payment?webmaster=1349764
  Resident 21.06.2018 457 16063
+9325
  Member 19.08.2015 2 156
+38
I can't figure out how to install these plugins. I follow the instructions as close as I can, but get confused.
The component and vst files have additional files that I'm not sure what to do with.
The codesign instructions turn up a message that says "AMBER doesn't exist".

Can anyone help me out please? I really need it.
  Member 6.04.2014 70
+10
do both of these on each plugin but make sure you copy and paste the iCOMMON into each plugin directory, components, vst and vst3.

sudo codesign --force --deep --sign -

sudo xattr -dr com.apple.quarantine
  Member 24.04.2016 11
0
Have you installed the "Framework" part that's needed for all of the Acustica plugins?
It was posted here a few weeks ago.

If there is an extra folder called R2R, like this plugin has, all of the files inside the "Common" folder need to be copied to all of the VST VST3 and Component folders.

The problem is that the "instructions.txt" file is one generic one that they've used for all of these Acustica plugins. You need to adjust them for all of the files for each plugin.
Not helped by the fact they've called the "Components" folder "AU", which is wrong.

For this plugin the code you need to run is:

function prep() {
sudo xattr -cr "$1"
sudo xattr -r -d com.apple.quarantine "$1"
sudo codesign --force --deep --sign - "$1"
}
prep "/Library/Audio/Plug-Ins/Components/CAMEL x64.component"
prep "/Library/Audio/Plug-Ins/Components/CAMELCOMP x64.component"
prep "/Library/Audio/Plug-Ins/Components/CAMELCOMPZL x64.component"
prep "/Library/Audio/Plug-Ins/Components/CAMELEQ x64.component"
prep "/Library/Audio/Plug-Ins/Components/CAMELEQZL x64.component"
prep "/Library/Audio/Plug-Ins/Components/CAMELPRE x64.component"
prep "/Library/Audio/Plug-Ins/Components/CAMELPREZL x64.component"
prep "/Library/Audio/Plug-Ins/Components/CAMELZL x64.component"
prep "/Library/Audio/Plug-Ins/VST/CAMEL.vst"
prep "/Library/Audio/Plug-Ins/VST/CAMELCOMP.vst"
prep "/Library/Audio/Plug-Ins/VST/CAMELCOMPZL.vst"
prep "/Library/Audio/Plug-Ins/VST/CAMELEQ.vst"
prep "/Library/Audio/Plug-Ins/VST/CAMELEQZL.vst"
prep "/Library/Audio/Plug-Ins/VST/CAMELPRE.vst"
prep "/Library/Audio/Plug-Ins/VST/CAMELPREZL.vst"
prep "/Library/Audio/Plug-Ins/VST/CAMELZL.vst"
prep "/Library/Audio/Plug-Ins/VST3/CAMEL.vst3"
prep "/Library/Audio/Plug-Ins/VST3/CAMELCOMP.vst3"
prep "/Library/Audio/Plug-Ins/VST3/CAMELCOMPZL.vst3"
prep "/Library/Audio/Plug-Ins/VST3/CAMELEQ.vst3"
prep "/Library/Audio/Plug-Ins/VST3/CAMELEQZL.vst3"
prep "/Library/Audio/Plug-Ins/VST3/CAMELPRE.vs3t"
prep "/Library/Audio/Plug-Ins/VST3/CAMELPREZL.vst3"
prep "/Library/Audio/Plug-Ins/VST3/CAMELZL.vst3"
  Member 19.08.2015 2 156
+38
Do you have a link to the framework? I can't find it with the search.

Thanks in advance

Edit: Found it.
  guest -- 0
0
I was trying for a while to get these to work on my Mac M1, this was the comment that finally helped me to find the fix. I hadn't realized JammuAnd had posted a modified Nebula.framework, I had been using the one I already had from my Acustica product trials and hence why it wasn't working for me. Thank you for your comment. And thank Giancarlo for the 10% of his plugins that are ACTUALLY worth the time to download for free
  Member 27.02.2014 3 259
+129
you have to put bulk in VST/VST3/AU folder as they are in the downloaded folder. When there is an R2R > COMMON folder, you copy the contents as is.
It’s true that it’s annoying because it’s not tidy.
When everyone thinks the same thing, no one is thinking anymore !
  Resident 29.06.2010 123
+7
Hello everyone, the same thing happens to me too, I follow the instructions to the letter precisely but I can't, if you could help me I would be grateful thanks
  Member 2.12.2022 60
+3
Help please
  Resident 21.10.2011 11 836
+317
sure thing. Help needed.

The plugin has "white" background after installation.

1. do we have to include the VST3 files as well, even if we just want to use AU?
2. do we have to include that short commend Terminal line (starts with: sudo xattr -r -d com.apple (even if some don't us Logic?)

thanks!
  Member 6.04.2014 70
+10
do both of these on each plugin but make sure you copy and paste the iCOMMON into each plugin directory, components, vst and vst3.

sudo codesign --force --deep --sign -

sudo xattr -dr com.apple.quarantine
  Member 12.10.2013 4 199
+233
All of them work like a charm !!! Thanks a lot
  Member 5.05.2021 80
+10
Does AU work in M1 Mac?
  Member 20.05.2022 1 19
+76
yes, all AU worked for me so far on M1
  Member 21.10.2014 179
+21
Thanks JammuAnd for all of these new plug-ins!
  Member 27.02.2014 3 259
+129
Be carefull !

In the "COMMON" folder there are files named "_44, _48,_88, _96". These are the sampling frequencies supported by the plugin. If your project is not set to one of the frequencies supported by the plugin, it is possible that the DAW will crash or that the plugin will not work.

For me, if my setting project is 48khz, it tells me that the plugins are not authorized ! if i change to 44khz, it work !
When everyone thinks the same thing, no one is thinking anymore !
  Member 13.01.2021 58
+18
quote by Alex SOZZABe carefull !

In the "COMMON" folder there are files named "_44, _48,_88, _96". These are the sampling frequencies supported by the plugin. If your project is not set to one of the frequencies supported by the plugin, it is possible that the DAW will crash or that the plugin will not work.

For me, if my setting project is 48khz, it tells me that the plugins are not authorized ! if i change to 44khz, it work !

quote by Alex SOZZABe carefull !

In the "COMMON" folder there are files named "_44, _48,_88, _96". These are the sampling frequencies supported by the plugin. If your project is not set to one of the frequencies supported by the plugin, it is possible that the DAW will crash or that the plugin will not work.

For me, if my setting project is 48khz, it tells me that the plugins are not authorized ! if i change to 44khz, it work !

Hello Alex,
Thank you for this important information, which saves us a lot of time.

In my case : Mojave+LPX, and after reading some information, I'd like to add that it works with a sampling frequency twice the frequency of the project, eg:
The project is at 48k, so if you only have AA files at 96k it works! The plugin works internally at 96k, a sort of x2 oversampling.
  Member 19.08.2015 2 156
+38
I greatly appreciate the help, but none of this worked for me.

I have a new issue though. I wanted to test the trial version of Sienna Headphones, but somehow it doesn't work. (plugin not recognized by any DAW)

Is there a possibility that the previous terminal commands are preventing this? If so, is there a way to clear those commands?

M1 Monterey
  Resident 28.12.2022 6 367
+337
I get the plugins work on m1 Sonoma, Logic 10.81

but even if I copy the R2R decompressed Folder to the Components
i dont have any Luck with the Presets

maybe someone can help how to make the Presets work?
  Resident 4.07.2015 346
+39
Has anyone been able to find the manuals for any of these? Thx!
  Member 31.05.2021 9 151
+195
every plugins from this release doesn't let change the gui size, is there a way to fix this?
  Member 29.06.2020 8
+1
Open plugin-resize-close plugin-reopen
  Member 19.08.2015 2 156
+38
Update: Got everything working following Bradders' instructions in this thread.
  Member 29.04.2017 1
0
Does this work in pro tools?
  Resident 22.12.2022 205
+49
Thanks JAmmuAnd, would like to see more of this on the AA series

Spread the Word