Valhalla dsp vst mac os

ValhallaDSP — ValhallaDelay 1.0.6.0-WIN, 1.0.6.2-OSX VST, AAX, AU x86 x64 — дилэй

ValhallaDSP — ValhallaDelay 1.0.6.0-WIN, 1.0.6.2-OSX VST, AAX, AU x86 x64

Дата Выпуска: 05.2019
Версия: 1.0.6.0 WIN 1.0.6.2 OSX
Разработчик: ValhallaDSP
Сайт разработчика: valhalladsp.com/shop/delay/valhalladelay/
Формат: VST, AAX* (*MOD)
Разрядность: 32bit, 64bit
Таблэтка: присутствует (R2R)
Системные требования: Windows 7/8/10
Plugin formats: 32-bit VST2.4, 64-bit VST2.4/AAX*
OS 10.8/10.9/10.10/10.11, macOS 10.12/10.13/10.14
Plugin Formats: 32/64-bit VST2.4/AU
Размер: 20 MB

ValhallaDelay — классическая и современная система задержки и эхо.

Ленточная задержка, BBD, цифровая старой школы, смещение высоты тона — все в одном плагине. ValhallaDelay предлагает классику и расширяет ее до новых измерений с уникальными стилями задержки Ratio и Quad, режимом Ghost (который добавляет сдвиг частоты) и мощной диффузионной секцией, которая может создавать что угодно от размытых эхо-сигналов до эфирных ревербераторов.

ValhallaDelay имеет семь уникальных режимов задержки (Tape, HiFi, BBD, Digital, Ghost, Pitch, RevPitch) и пять стилей задержки (Single, Dual, Ratio, PingPong, Quad). Комбинируя режимы и стили, вы можете получить классические ленточные эхо-сигналы, задержки в стиле чипов Bucket Brigade, цифровые задержки старой школы, удвоители высоты тона, реверсированные задержки, неуловимый хорус. список можно продолжать и продолжать.

Мы потратили кучу времени на моделирование винтажных аппаратных задержек, но на этом мы не остановились.
Много мыслей было уделено элементам управления ValhallaDelay. Графический интерфейс имеет все необходимые элементы управления для такой универсальной задержки, оставляя при этом только нужные элементы управления, поэтому интерфейс является быстрым и простым в использовании. Все элементы управления находятся на одном экране — без скрытых вкладок или меню. Цель состоит в том, чтобы создать инструмент, который вы сможете быстро освоить, чтобы получить нужные звуки и выполнить свою работу!

ValhallaDelay has seven different delay Modes:

• Tape: Modeled after vintage tape echoes, with all the features and quirks that were loved in the old hardware.
• HiFi: A higher fidelity tape echo, where the ability to precisely sculpt the sound is in your hands.
• BBD: A dark, low fidelity bucket brigade delay model.
• Digital: A cleaner, higher bandwidth delay, with the ability to dial in digital dirt.
• Ghost: A Valhalla DSP original! Combines the tape model from the HiFi mode with frequency shifting and a unique diffusion algorithm, for sounds that will split your skull in two.
• Pitch: A digital delay with added pitch shifting. Perfect for micro-shifting vocals, adding harmonies to synths, creating vast shimmering soundscapes, or shrieking sounds that forever spiral upwards or downwards.
• RevPitch: Reverse pitch shifting! Everything that goes in, comes out reversed.

Five tape Styles, for controlling the number of delay voices:

• Single: Same delay length & modulation for left and right channels.
• Dual: Independent delay lengths for left and right channels.
• Ratio: The right channel is set to a ratio of the left channel, and the feedback of left and right channels is mixed. Perfect for sounds that slowly transition from delay to reverb-esque.
• PingPong: A delay that bounces between the left and right channels, with the ability to set the left and right delays independently.
• Quad: Models the multi-head tape echoes of the 1960s and 1970s, with up to 4 delay taps on tap.

• Delay lengths ranging from 0 msec to 20 seconds. Dial in choruses and flangers, slapback echoes, longer delays, or long Frippertronic loops.
• Sync the delay to the beat, with straight/dotted/triplet options. Or, control the length via milliseconds.
• Age control, for adjusting the artifacts of the delay mode. Clean and shiny, old and dusty, or anywhere in between.
• Powerful Diffusion section, that can be used to smooth out the attacks of delays, or can be an amazingly smooth and lush reverb in its own right. Up to 20 seconds of diffusion time possible!
• Era control, for selecting between different variants of the delay modes.

Источник

ValhallaDSP – Plugins Bundle [AU, VST, RTAS, MAC OSX][x32/x64]

ValhallaDSP – Plugins Bundle ( 45.3 MB ) contains

Minimum system requitment

– Mac OS X 10.6.0 or later
– PowerPC G5 or Intel Core processor
– 512 MB of RAM
– 70 MB of free hard drive space
– 1024 x 768 screen resolution
– Built-in audio interface
– Mac OS X-compatible MIDI interface/keyboard

Related posts:

Leave a Reply Cancel reply

Link Blocked By Antivirus

Some antivirus (like Avast) block links from Adf.ly short-link.

For access the links just disable your antivirus temporally.

Please Disable Your Adblock

For people who are having trouble accessing the links on our site, you can use The Universal Bypass addon for Chrome, Mozilla, and Edge.

But don’t forget that when you use this addon, you make us lose revenue from shortlinks, so please help us by not using adblock on our site.

Best regards : Admin

• Spectrasonics – Omnisphere 2 + Keyscape + Trilian + Stylus RMX (VSTi, RTAS, AAX, AU) [WiN-OSX x64] 1.4k views
• Spectrasonics – Omnisphere 2.7.0f, Keyscape 1.3.0f, Trilian 1.6.0f & StylusRMX 1.10.1e 2 – UPDATE (STANDALONE, VSTi, VSTi3, AAX) [WiN x64] 800 views
• WavSupply – All Kits Bundle – UPD (WAV, MIDI, OMNISPHERE, SERUM, GROSS BEAT, DUNE, ELECTRAX, SYLENTH1) 560 views
• Native Instruments – Plugins Bundle 2021.9 (VST, VST3, AAX) [WiN x64] 480 views
• Image-Line – FL Studio Producer Edition + Signature Bundle v20.7.2.1863 – RC4 [WiN x86 x64] 480 views
• Native Instruments – Kontakt 6.6.1 (STANDALONE, VSTi, VST3, AAX) [WiN x64] 480 views
• Plugin Boutique – Scaler 2 v2.4.1 (VSTi, VST3, AUi) [WIN.OSX x64] 480 views
• Waldorf – Waldorf Edition 2.2.2 (VSTi, VSTi3, AAX, NKS) [WiN x86 x64] 400 views
• Image-Line – FL Studio Producer Edition 20.8.3.2304 [WIN.OSX] 400 views
• Arturia – SQ80 V 1.0.0 – FiXED (STANDALONE, VSTi, VSTi3, AUi) [WIN.OSX x64] 400 views
• Klevgrand – Everything Bundle 2021.09.14 (VST, VST3, AAX, AU) [WIN.OSX x64] 320 views
• Arturia – V-Collection 8 v8.5.0 (STANDALONE, VSTi, VSTi3, AAX) [WiN x64] 320 views

Источник

Valhalla Super Massive

Downloads

Make some space.

ValhallaSupermassive has been designed from the ground up for MASSIVE delays and reverbs. Blow your mind and your music to new levels of consciousness and experience. Get ready for luscious clouds of reverb, otherworldly delays, swelling waves of feedback unlike any you’ve heard before.

All Valhalla plugins are self documenting, so just roll over the controls for the tool tip.

And, it’s FREE! No strings attached. Just click the download links and you’re ready to go.

New in 1.1.1: Two new reverb modes, Large Magellanic Cloud and Triangulum!

STOP THE PRESSES. New in version 1.2.0: Two new reverb/delay modes, Cirrus Major and Cirrus Minor!

BUT WAIT THERE’S MORE. Version 1.3.0 for Mac and Windows available. Intel and ARM builds available for Apple M1 computers. VST3 fixes for Studio One and FL Studio.

Downloads

Plugin UI

Modes

Overview

Gemini

Hydra

Centaurus

Sagittarius

Great Annihilator

Andromeda

Capricorn

Large Magellanic Cloud

Triangulum

Cirrus Major

Cirrus Minor

The MODE control is the most powerful Supermassive control, as the different algorithms have very different attack, sustain, and decay characteristics. For more details, head to the ValhallaSupermassive Modes blog post. Supermassive uses a variety of feedback delay networks, where each delay in the structure can be up to 2 seconds long. Combine these long delays with the unique WARP control, and the results range from echoes that slowly fade in, to cascading harmonic echoes, to lush reverbs, onwards to reverbs that decay way over the course of minutes.

This is the most “conventional” of the Supermassive modes. It has a very quick attack time, and a natural exponential decay. With the DENSITY parameter at maximum and WARP at 50% or more, you can get very smooth reverbs from Gemini. Turn down the DENSITY control, and the reverbs will become less dense as they decay away, which is nice for pointillistic effects.

This mode has a relatively fast attack time, and a very lush and long exponential decay. The Hydra mode is very sensitive to the DENSITY parameter. With DENSITY at 0%, Hydra can sound like a fairly simple echo. Turn up the DENSITY, and the echo density rapidly increases towards a complicated reverb/echo structure. The modulation can be very lush in Hydra.

A mode with a slower attack time, a shorter decay time, and a bit of “sustain” to the reverberation. The attack time in Centaurus is tied into the FEEDBACK parameter, with higher feedback values resulting in a faster attack (and longer decay). This slower attack can be used with lower values of WARP to create echoes that slowly fade in and out. Turn up the WARP parameter, and you have a reverb that slowly fades in, and hangs in space for awhile.

A reverb/echo with a VERY long attack time, depending on the setting of FEEDBACK. With FEEDBACK settings less than 70%, Sagittarius will slowly fade in, and fade out over a similar time period. Turn up FEEDBACK higher, and things will fade in more quickly and decay more slowly. Sagittarius can be viewed as having a fair degree of sonic “mass” or inertia: slow to get going, slow to go away. It is perfect for creating echoes that fade in over time, or massive slabs of reverberation with higher WARP values.

Similar to Centaurus, but MORE MASSIVE. Slow attack with a fair amount of predelay, and super long decay times.

A super massive variant of the Sagittarius mode. Very slow attack with a fair amount of predelay, and decay times that can range into thousands of seconds.

A more compact celestial object. Quick attack time, long decay time, and very low echo density. Even with DENSITY at max, Lyra spends a lot more time in the “echo” domain than the “reverb” domain. This can be really nice for spacey echoes that gradually diffuse over time.

A larger version of Lyra. Quick attack time, long decay time, and a medium size bowl of echo density. Useful for pointillistic reverbs, as well as for lush chorus effects.

A mode that can have VERY long initial delays with DENSITY set to zero, and the potential for looping delays or huge reverbs. The DENSITY control allows for extremely sparse reverbs when at 0%, or dense lush reverbs when set above 60%. Large Magellanic Cloud can be viewed as a cross between Centaurus and an oversized variant of the Lyra mode.

A delay mode that can act as a looper, as a gigantic lush reverb, or as a repeating delay with independent control over the individual repeats and the overall decay time. With the Triangulum DENSITY control at 0%, the result will be repeating echoes at 8X the displayed DELAY setting. DENSITY settings greater than 0% will introduce diffuse echoes at shorter delay lengths, that «fill in» the space of the longer echoes.

A lower density reverb/echo mode, with a mysterious pattern to the initial echoes. Ideal for sparse multitap delays, spacious echoes, and cold 80s reverbs.

Similar to Cirrus Major, but smaller and less dense. Strange repeating echoes, low initial density, significant predelay before the reverb. Turn up the size, turn down the density, and let the echoes evolve over time. Or crank up the density and turn down the size, for a perfect mid-80s digital room reverb.

Источник

FAQ / Installation

How do I download the plugins and authorize them with the keyfile?

• When you purchase a Valhalla plugin, the email you receive after the purchase includes a link to download the installer. Should you ever need to download it again, the installer files are in your User Account on the Valhalla site:

• Also in your User Account is the License keyfile (see the above image); this is used to authorize the plugin within your DAW. You need to SAVE this file to your computer; when you click the keyfile link to download it, your browser will save the .zip file that contains the keyfile. Once this is downloaded to your computer, double-click the .zip file to extract the keyfile. DO NOT try to open the extracted keyfile with any application, DO NOT double-click it expecting it to find an appropriate application with which to open it.
• Unzip the installer and run the Installer file for your plugin.

1. On macOS, the plugins will automatically install into the system VST, Audio Units and AAX folders
2. On Windows, you can choose whether to install 32-bit or 64-bit .dll files (or both) – pay attention to the VST installation directory as it may be different than the one your DAW is set to reference in its preferences.

• Now that you have installed your plugin, open your DAW and insert an instance of the plugin on a track; once you do this, you will see a message about finding your license to authorize the plugin:

• Navigate to the keyfile you have downloaded, select it and open it from the dialog box:

• Your plugin will now be authorized!

The plugin isn’t showing up in Cubase 9! What do I do?

Cubase 9 will sometimes refuse to recognize a VST plugin if both the 32-bit and 64-bit versions are installed. In order to fix this, you can remove or delete the 32-bit VST plugins.

On the Mac, you will want to delete:

• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaVintageVerb.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaRoom.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaShimmer.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaUberMod.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaFreqEcho.vst

Be sure to leave the files that have _x64 in their file names, as these are the 64-bit plugins.

On Windows, you will want to go into the directory where you keep your 32-bit VST files, and delete

• ValhallaVintageVerb.dll
• ValhallaRoom.dll
• ValhallaShimmer.dll
• ValhallaUberMod.dll
• ValhallaPlate.dll
• ValhallaFreqEcho.dll

The 64-bit versions have _x64 in their file names, so make sure to keep those.

Alrighty. I’ve just rescanned my Audio Units in Logic, but the plugin isn’t showing up. Are there any more weird, completely unintuitive steps I need to take in order to get my plugins up and running?

If you are using High Sierra (macOS 10.13) or Mojave (10.14), you should restart your computer after installing our plugins. Apple made some changes to High Sierra/Mojave that require a restart for some plugins to appear in DAWs (especially Logic…) after installation.

It sometimes takes more than one restart, too, so don’t get discouraged if it’s not found after the first one.

If that doesn’t work, this is where I lean on the expertise of Don Gunn, producer/mixer/drummer extraordinaire, and a long time user of Logic. Don writes:

If you are having issues with newly installed plug-ins showing up in
LogicX, it may be necessary to trash the AudioUnit cache and allow
LogicX to rescan your plug-ins when you restart the application. To do
this, follow these steps:

1. You need to access the Library directory in your User account; Apple
has hidden this since OSX 10.7, so to show the User Library, hold the
“Option/Alt” key on your keyboard while clicking the “Go” menu in the
Finder menubar. You will see the Library toggle between visible and not
if you alternately press/let go of the Option key.

2. Choose “Library”

3. A new Finder window will open with the User Library directory open.

4. Navigate to the following path: Caches/AudioUnitCache

5. In the AudioUnitCache folder is a file called
“com.apple.audiounits.cache”; you can trash this file or the entire
AudioUnitCache folder.

6. Restart LogicX and the application will rescan all of your installed
AudioUnit plug-ins.

I’ve followed all of the above steps, but the plugins aren’t showing up for me in Logic and/or Mainstage. What now?

First of all, try rebooting your machine. OS 10.13/10.14 (High Sierra/Mojave) often requires a reboot to recognize the new plugins.

You may need to rescan your Audio Units in order to have Logic/Mainstage recognize that a new Audio Unit has been installed:

– Open up the Audio Unit Manager (in the menu bar, select Logic Pro->Preferences->Audio Unit Manager).

– Click “Reset and Rescan Selection” at the bottom of the Audio Unit Manager window to rescan the Audio Units.

The installation failed on OSX, with the message “Installation Failed.” Now what?

Here’s a few hints:

– Turn off Gatekeeper. The current Valhalla plugin installers aren’t “signed,” so Gatekeeper will flag them. Here’s a few links on how to disable Gatekeeper for the installation:

– Try downloading the installer, right clicking on the .zip, and selecting “Open with Archive Utility.” Some older achiving programs, such as The Unarchiver, will balk at the installation scripts used in the Valhalla installers. The standard Archive Utility that is built into OSX seems to reliably work.

Help! My hard drive crashed! What do I do?

Sorry about that. Hard drive crashes suck! You should be able to download a new installer and your keyfiles from your Valhalla DSP user account.

I upgraded from Snow Leopard to Lion/Mountain Lion/Mavericks/Yosemite, and now your plugins aren’t working. Help!

This has happened a couple of times. Not all the time, but sometimes. If this happens, just use your .vkeyfile keyfile to reauthorize your plugins. You can download the keyfile and the latest installers from your Valhalla DSP user account.

Can I install the plugin on more than one computer? For example, can I put it on both a desktop and laptop machine?

You can install the plugin on as many computers as you own and personally use. None of my plugins “phone home” or rely on internet connectivity for protection, and are not locked to a specific machine ID. I strongly feel that customers should not be treated like potential criminals. Just be sure to remove the license from your computer when you sell that computer. In short, I trust you folks.

I have all my licenses on an iLok. Can I use an iLok to authorize the ValhallaDSP licenses?

Nope! I use PACE copy protection for my AAX plugins, because this is a requirement of AAX, but I don’t require iLok for any of my other plugin formats.

Do I need to uninstall the demo before installing the “full” version?

Nope! I would recommend running the full installer WITHOUT uninstalling the demo version. The “full” installer will overwrite the demo plugin, while preserving any presets and project settings that were created with the demo version.

Why can’t I unlock the demo version?

Copy protection stuff. It is a bit more annoying, but I figure that it is far less annoying than using challenge/response, a dongle, etc.

How do I unlock the demo version?

You can’t. The demo version is a dedicated, “hardwired” demo version, and can’t be unlocked. You need to install the “full” version from your user account, that you can download when you purchase the plugin.

My audio workstation machine isn’t hooked up to the Internet. Can I authorize/run the Valhalla plugins without a web connection?

Yes! As long as you have some way of moving the plugin installer and the .vkeyfile to your audio computer, you should be able to authorize and run the plugins. The Valhalla plugins don’t require an active Internet connection, and don’t “phone home” or send any information over the Internet during the authorization process, or at any time during their operation.

My older keyfiles have the suffix .xml. Will these work with the latest plugin updates?

Yes. I changed the name of the files from .xml to .vkeyfile, as a few computers will do weird things when downloading files with a .xml suffix. The files are essentially the same, and both the older .xml keyfiles and newere .vkeyfile keyfiles can be used to authorize the latest plugin versions.

What sort of copy protection do your plugins use?

I use an XML keyfile, which is posted to your user account as a .vkeyfile. No dongles, no challenge/response.

I just purchased the plugin, but haven’t received an email with the XML keyfile! When is this email going to be sent out?

See above. As of late December 2014, I no longer send out keyfiles manually (which could take up to 24 hours). Instead, your keyfiles and installer links are available in your user account immediately after completing your purchase.

Is there a video showing how to fix folder and disk permissions that happen for some OSX users when installing Valhalla plugins?

Yes! Click here for another great tutorial from Don Gunn.

Is there a video showing how to install and authorize the plugins?

Yes, courtesy of Don Gunn. Check it out!

I just bought a Valhalla DSP plugin. What happens next?

• • 1. Grab the .vkeyfile keyfile and download links from your account (i.e. click the My Account label in the upper right of this window).
  • 2. Save the .vkeyfile keyfile to your desktop. DON’T OPEN THIS. You’ll be using this in a future step.
  • 3. Click on the installer link (that works for your OS) in the email, and download the installer to your computer.
  • 4. Double click the .zip of the installer (to unzip it).
  • 5. Run the installer program.
  • 5a. WINDOWS ONLY: When running the installer, choose the formats (32/64-bits, VST/RTAS/AAX) that work with your OS and DAWs. Pro Tools will require RTAS (up through PT10) or AAX (PT11/12); all other DAWs use VST.
  • 5b. OS 10.13 / HIGH SIERRA ONLY: Reboot your computer after running the installer. For some reason, 10.13 often requires a reboot in order to recognize new Audio Units.
  • 6. Open your DAW (Digital Audio Workstation, i.e. the program that you record with and that hosts the plugins. Pro Tools, Cubase, Live, Logic, etc.)
  • 7. Go to the list of available plugins in your DAW, select your new Valhalla DSP plugin, and put it on a channel in your DAW.
  • 8. An alert window will pop up, asking you to browse to the .vkeyfile keyfile. Do this and click “OK.”

After this, your plugin should be registered!

Other FAQs in Installation

How do I download the plugins and authorize them with the keyfile?

• When you purchase a Valhalla plugin, the email you receive after the purchase includes a link to download the installer. Should you ever need to download it again, the installer files are in your User Account on the Valhalla site:

• Also in your User Account is the License keyfile (see the above image); this is used to authorize the plugin within your DAW. You need to SAVE this file to your computer; when you click the keyfile link to download it, your browser will save the .zip file that contains the keyfile. Once this is downloaded to your computer, double-click the .zip file to extract the keyfile. DO NOT try to open the extracted keyfile with any application, DO NOT double-click it expecting it to find an appropriate application with which to open it.
• Unzip the installer and run the Installer file for your plugin.

1. On macOS, the plugins will automatically install into the system VST, Audio Units and AAX folders
2. On Windows, you can choose whether to install 32-bit or 64-bit .dll files (or both) – pay attention to the VST installation directory as it may be different than the one your DAW is set to reference in its preferences.

• Now that you have installed your plugin, open your DAW and insert an instance of the plugin on a track; once you do this, you will see a message about finding your license to authorize the plugin:

• Navigate to the keyfile you have downloaded, select it and open it from the dialog box:

• Your plugin will now be authorized!

The plugin isn’t showing up in Cubase 9! What do I do?

Cubase 9 will sometimes refuse to recognize a VST plugin if both the 32-bit and 64-bit versions are installed. In order to fix this, you can remove or delete the 32-bit VST plugins.

On the Mac, you will want to delete:

• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaVintageVerb.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaRoom.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaShimmer.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaUberMod.vst
• Macintosh HD/Library/Audio/Plug-Ins/VST/ValhallaFreqEcho.vst

Be sure to leave the files that have _x64 in their file names, as these are the 64-bit plugins.

On Windows, you will want to go into the directory where you keep your 32-bit VST files, and delete

• ValhallaVintageVerb.dll
• ValhallaRoom.dll
• ValhallaShimmer.dll
• ValhallaUberMod.dll
• ValhallaPlate.dll
• ValhallaFreqEcho.dll

The 64-bit versions have _x64 in their file names, so make sure to keep those.

Alrighty. I’ve just rescanned my Audio Units in Logic, but the plugin isn’t showing up. Are there any more weird, completely unintuitive steps I need to take in order to get my plugins up and running?

If you are using High Sierra (macOS 10.13) or Mojave (10.14), you should restart your computer after installing our plugins. Apple made some changes to High Sierra/Mojave that require a restart for some plugins to appear in DAWs (especially Logic…) after installation.

It sometimes takes more than one restart, too, so don’t get discouraged if it’s not found after the first one.

If that doesn’t work, this is where I lean on the expertise of Don Gunn, producer/mixer/drummer extraordinaire, and a long time user of Logic. Don writes:

If you are having issues with newly installed plug-ins showing up in
LogicX, it may be necessary to trash the AudioUnit cache and allow
LogicX to rescan your plug-ins when you restart the application. To do
this, follow these steps:

1. You need to access the Library directory in your User account; Apple
has hidden this since OSX 10.7, so to show the User Library, hold the
“Option/Alt” key on your keyboard while clicking the “Go” menu in the
Finder menubar. You will see the Library toggle between visible and not
if you alternately press/let go of the Option key.

2. Choose “Library”

3. A new Finder window will open with the User Library directory open.

4. Navigate to the following path: Caches/AudioUnitCache

5. In the AudioUnitCache folder is a file called
“com.apple.audiounits.cache”; you can trash this file or the entire
AudioUnitCache folder.

6. Restart LogicX and the application will rescan all of your installed
AudioUnit plug-ins.

I’ve followed all of the above steps, but the plugins aren’t showing up for me in Logic and/or Mainstage. What now?

First of all, try rebooting your machine. OS 10.13/10.14 (High Sierra/Mojave) often requires a reboot to recognize the new plugins.

You may need to rescan your Audio Units in order to have Logic/Mainstage recognize that a new Audio Unit has been installed:

– Open up the Audio Unit Manager (in the menu bar, select Logic Pro->Preferences->Audio Unit Manager).

– Click “Reset and Rescan Selection” at the bottom of the Audio Unit Manager window to rescan the Audio Units.

The installation failed on OSX, with the message “Installation Failed.” Now what?

Here’s a few hints:

– Turn off Gatekeeper. The current Valhalla plugin installers aren’t “signed,” so Gatekeeper will flag them. Here’s a few links on how to disable Gatekeeper for the installation:

– Try downloading the installer, right clicking on the .zip, and selecting “Open with Archive Utility.” Some older achiving programs, such as The Unarchiver, will balk at the installation scripts used in the Valhalla installers. The standard Archive Utility that is built into OSX seems to reliably work.

Help! My hard drive crashed! What do I do?

Sorry about that. Hard drive crashes suck! You should be able to download a new installer and your keyfiles from your Valhalla DSP user account.

I upgraded from Snow Leopard to Lion/Mountain Lion/Mavericks/Yosemite, and now your plugins aren’t working. Help!

This has happened a couple of times. Not all the time, but sometimes. If this happens, just use your .vkeyfile keyfile to reauthorize your plugins. You can download the keyfile and the latest installers from your Valhalla DSP user account.

Can I install the plugin on more than one computer? For example, can I put it on both a desktop and laptop machine?

You can install the plugin on as many computers as you own and personally use. None of my plugins “phone home” or rely on internet connectivity for protection, and are not locked to a specific machine ID. I strongly feel that customers should not be treated like potential criminals. Just be sure to remove the license from your computer when you sell that computer. In short, I trust you folks.

I have all my licenses on an iLok. Can I use an iLok to authorize the ValhallaDSP licenses?

Nope! I use PACE copy protection for my AAX plugins, because this is a requirement of AAX, but I don’t require iLok for any of my other plugin formats.

Do I need to uninstall the demo before installing the “full” version?

Nope! I would recommend running the full installer WITHOUT uninstalling the demo version. The “full” installer will overwrite the demo plugin, while preserving any presets and project settings that were created with the demo version.

Why can’t I unlock the demo version?

Copy protection stuff. It is a bit more annoying, but I figure that it is far less annoying than using challenge/response, a dongle, etc.

How do I unlock the demo version?

You can’t. The demo version is a dedicated, “hardwired” demo version, and can’t be unlocked. You need to install the “full” version from your user account, that you can download when you purchase the plugin.

My audio workstation machine isn’t hooked up to the Internet. Can I authorize/run the Valhalla plugins without a web connection?

Yes! As long as you have some way of moving the plugin installer and the .vkeyfile to your audio computer, you should be able to authorize and run the plugins. The Valhalla plugins don’t require an active Internet connection, and don’t “phone home” or send any information over the Internet during the authorization process, or at any time during their operation.

My older keyfiles have the suffix .xml. Will these work with the latest plugin updates?

Yes. I changed the name of the files from .xml to .vkeyfile, as a few computers will do weird things when downloading files with a .xml suffix. The files are essentially the same, and both the older .xml keyfiles and newere .vkeyfile keyfiles can be used to authorize the latest plugin versions.

What sort of copy protection do your plugins use?

I use an XML keyfile, which is posted to your user account as a .vkeyfile. No dongles, no challenge/response.

I just purchased the plugin, but haven’t received an email with the XML keyfile! When is this email going to be sent out?

See above. As of late December 2014, I no longer send out keyfiles manually (which could take up to 24 hours). Instead, your keyfiles and installer links are available in your user account immediately after completing your purchase.

Is there a video showing how to fix folder and disk permissions that happen for some OSX users when installing Valhalla plugins?

Yes! Click here for another great tutorial from Don Gunn.

Is there a video showing how to install and authorize the plugins?

Yes, courtesy of Don Gunn. Check it out!

I just bought a Valhalla DSP plugin. What happens next?

• • 1. Grab the .vkeyfile keyfile and download links from your account (i.e. click the My Account label in the upper right of this window).
  • 2. Save the .vkeyfile keyfile to your desktop. DON’T OPEN THIS. You’ll be using this in a future step.
  • 3. Click on the installer link (that works for your OS) in the email, and download the installer to your computer.
  • 4. Double click the .zip of the installer (to unzip it).
  • 5. Run the installer program.
  • 5a. WINDOWS ONLY: When running the installer, choose the formats (32/64-bits, VST/RTAS/AAX) that work with your OS and DAWs. Pro Tools will require RTAS (up through PT10) or AAX (PT11/12); all other DAWs use VST.
  • 5b. OS 10.13 / HIGH SIERRA ONLY: Reboot your computer after running the installer. For some reason, 10.13 often requires a reboot in order to recognize new Audio Units.
  • 6. Open your DAW (Digital Audio Workstation, i.e. the program that you record with and that hosts the plugins. Pro Tools, Cubase, Live, Logic, etc.)
  • 7. Go to the list of available plugins in your DAW, select your new Valhalla DSP plugin, and put it on a channel in your DAW.
  • 8. An alert window will pop up, asking you to browse to the .vkeyfile keyfile. Do this and click “OK.”

After this, your plugin should be registered!

Источник