Arturia – FX Collection v1.0.0 – R2R – NO INSTALL, SymLink Installer (VST, VST3) [WiN x64]

By | April 9, 2020

 


Year / Date of Issue : 19.2.2020
Version : 1.0.0
Developer : Arturia
Developer’s site : Arturia
Format : VST / VST3
Bit : 64bit
Tabletka : cured | R2R
System Requirements :
Win 7+ PC: 4 GB RAM; 2 GHz CPU.
1GB free hard disk space
OpenGL 2.0 compatible GPU
Microsoft Visual C ++ 2019 Redistributable Package (x64)


Description : An inspirational suite of software effects that combine the legacy of the music industry with futuristic features and unrivaled sound quality with an intuitive workflow. Enhance your music with the perfect effect for every task.
Add. Information:: VST3 plugins are in the same folder as VST2. This is logical, convenient and correct.
The textures were taken from the distribution from VR Team, which reduced the size by 60% and accelerated the launch.

Structure

3 Compressors:
Comp VCA-65 v1.1.0
Comp FET-76 v1.1.0
Comp TUBE-STA v1.1.0
3 Delays:
Delay ETERNITY v1.1.0
Delay MEMORY-BRIGADE v1.1.0
Delay TAPE-201 v1.1.0
3 Filters:
Filter M12 v1.2.0
Filter MINI v1.3.0
Filter SEM v1.2.0
3 Preamps:
Pre 1973 v1.2.0
Pre TridA v1.2.0
Pre V76 v1.2.0
3 Reverbs:
Rev INTENSITY v1.0.0
Rev PLATE-140 v1.1.0
Rev SPRING-636 v1.0.0

 


Installation :

A) SAVING OPERATIONS, delete folders left over from previous installations;
B) run SymLink Installer.cmd as administrator (if you need to change the path to VST2, see below)
C) launch DAW by setting the scan path C: Program Files VstPlugins, scan for new plugins.
In the case when “manual” registration with keygen, patch, etc. is required, everything necessary will be in the REG folder

{0} {Preinstall the required system software}
The following must be installed in the system:
Microsoft Visual C ++ 2005-2008-2010-2012-2013-2019 Redistributable Package x86 & x64

{1} {Proper package unzipping}
Run .exe or open the package file with the 7-zip.org archiver (without using drag and drop),
extract its contents to any drive for permanent storage *,
not deep in the nesting of folders, briefly by name, from letters, numbers, spaces, underscores, periods,
without other non-literal characters, without Cyrillic and other national alphabets

* For the correct operation of symlinks, MOVE, DELETE, RENAME ANYTHING IN THE PACKAGE IS UNACCEPTABLE.

{2} {Removing traces of other versions of the package}
{2.1} ATTENTION! Save the operating time (presets, etc.) of the deleted.
{2.2} Uninstall (or uninstall if there is no uninstaller) previous versions of the installation.
{2.3} Check the absence of folders in the places where the symlinks were created (IF FOLDERS ARE LEFT, THEN SIMLINKS WILL NOT BE CREATED)
and delete the folders remaining after uninstalling.

What is a symlink?

A symlink (a symbolic link, in the case of a folder, the required type of symlink is Windows Junction Points) is a special type of link to a folder or file that is accepted by programs that read them as a regular folder or file, although the real data source may be on a different drive.
https://www.youtube.com/results?search_query=Link+Shell+Extension
Link shell extension
schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
en.wikipedia.org/wiki/Symbol
ATTENTION! Removing a symlink does not delete the folder that this symlink refers to.
ATTENTION! Removing something when entering the symlink folder leads to a real deletion of the deleted one.

Is it possible to bypass SymLink Installer without .CMD files?

Yes. SymLink Installer CMD files are optional
you can simply copy files according to the folder names inside the folder .. C ,
and also pay attention to the presence or absence of * .reg registry files, keygen … etc. inside the package.

How to change VST2 paths in .CMD files of SymLink Installer?

The change of paths in .CMD files described below for the VST2 plugin format can be omitted,
if in the DAW settings you specify an additional path for scanning VST2 plugins: C: Program Files * VstPlugins,
or place a symlink on the C: Program Files * VstPlugins folder inside the folder where you usually have the rest of VST2.
For example, all the VST2 plugins you have are located in the folder C: Program Files * Steinberg VstPlugins,
then inside this folder a symbolic link is made to the folder C: Program Files * VstPlugins.
If the specified location does not fit, then you can edit the paths for creating symlinks in the CMD files.
For example, in the SymLink Installer.cmd file, you can replace the lines (using any text editor):
cmd / c mkdir “% PROGRAMFILES% VstPlugins”
cmd / c mklink / j “% PROGRAMFILES% VstPlugins SWAM” “% ~ dp0C Program Files VstPlugins SWAM”
cmd / c mkdir “% PROGRAMFILES (x86)% VstPlugins”
cmd / c mklink / j “% PROGRAMFILES (x86)% VstPlugins SWAM” “% ~ dp0C Program Files (x86) VstPlugins SWAM”
for example, on lines:
cmd / c mkdir “% PROGRAMFILES% Steinberg VstPlugins”
cmd / c MKLINK / j “% PROGRAMFILES% Steinberg VstPlugins SWAM” “% ~ dp0C Program Files VstPlugins SWAM”
cmd / c mkdir “% PROGRAMFILES (x86)% Steinberg VstPlugins”
cmd / c MKLINK / j “% PROGRAMFILES (x86)% Steinberg VstPlugins SWAM” “% ~ dp0C Program Files (x86) VstPlugins SWAM”
or for example, to strings (using absolute paths instead of relative (% PROGRAMFILES (x86)% or “% PROGRAMFILES%)):
cmd / c mkdir “C: Program Files Steinberg VstPlugins”
cmd / c MKLINK / j “C: Program Files Steinberg VstPlugins SWAM” “% ~ dp0C Program Files VstPlugins SWAM”
cmd / c mkdir “C: Program Files (x86) Steinberg VstPlugins”
cmd / c MKLINK / j “C: Program Files (x86) Steinberg VstPlugins SWAM” “% ~ dp0C Program Files (x86) VstPlugins SWAM”
Or others required in specific circumstances.
Similar path changes (if necessary) should be made in other .CMD files.

How does the MKLINK symlink team work?

MKLINK Help:
ss64.com/nt/mklink.html
ab57.ru/cmdlist/mklink.html
To create a symlink, the folder in which it is created must be created in advance.
Example:
cmd / c mkdir “C: Program Files Steinberg VstPlugins”
This command creates a real folder “C: Program Files Steinberg VstPlugins”, preparing the possibility of creating a symlink inside it.
Example of creating a symlink command:
cmd / c MKLINK / j “C: Program Files Steinberg VstPlugins MyFolder” “% ~ dp0C Program Files (x86) VstPlugins MyFolder”
The command creates a symlink named MyFolder inside the folder “C: Program Files Steinberg VstPlugins”,
at the same time, a link to the source folder is stored inside the symlink – “% ~ dp0C Program Files (x86) VstPlugins MyFolder”.
% ~ dp0 – instead of this code, when executing a .cmd file, the full path to the folder from which the .cmd file is launched will be substituted.
cmd / c – call code for the command processor for executing batch files.
/ j – the key to create a symlink to the folder, not to the file.
ATTENTION! Removing a symlink does not delete the folder that this symlink refers to.
ATTENTION! Removing something when entering the symlink folder leads to a real deletion of the deleted one.
In some cases (for example, Ableton 10 on Windows 10), instead of the mklink / j command (creates Junction Points), mklink / d (creates a Symbolic Link) should be used.
Why in the SymLink Installer.cmd file you should replace * meetings of the text mklink / j with mklink / d, in the lines for creating symlinks for VST2 format, or replace all meetings.
* Using Notepad ++ (calling the replacement dialog – Ctrl + h).

Why can’t I see presets?

In some DAWs, presets do not work correctly and db.db3 is not updated. Licenses behave the same way. This is a bug of Arturia. In ripper, everything is OK.

[Distribution updated]
Fully compatible with conventional installation Arturia – V Collection 7
Fully compatible with Arturia – V Collection 7 [NO INSTALL]
Fixed bug scanning plugins on some versions of Win10

Leave a Reply

Your email address will not be published. Required fields are marked *