Audio DSP – Sonnoxplugins Oxford, consisting of:
Sonnoxplugins Oxford Elite Collection Native 1.0
EQ 1.8.1 – 5-band parametric equalizer with low-cut and high-cut filters.
Inflator 1.7.1 – clipper-limiter.
Limiter 1.3.3 – compressor-limiter.
Reverb 1.2.1 is an algorithmic reverb with flexible settings for early and late reflections, which has a phase modulation function in the late reflections block, which creates “live” tails.
SuprEsser 1.2.1 – de-esser without delay.
SuprEsser LL 1.2.1 is a deessor with low latency linear phase filters.
SuprEsser HR 1.2.1 – deessor with long delay linear phase filters.
TransMod 1.5.1 – transient processor.
Sonnoxplugins Oxford Restore Suite Native 1.0 – restoration filters
De-Clicker 1.1.0 – elimination of pops, clicks, crackle artifacts.
De-Noiser 1.1.0 is a denoiser with noise profile learning.
Sources:
Sonnoxplugins.Oxford.Restore.Suite.Native.v1.0-air
{HOW TO “INSTALL” THIS PACKAGE USING SymLink Installer .CMD FILES?}
################################################### ##############################
This release is intended for trial testing.
Support the Producer if you liked the software
and intend to use this software in commercial production,
in accordance with the Producer’s license agreement.
################################################### ################################
The “installation” steps are in curly braces.
Explanations (read only if necessary) are highlighted in spoilers (or in triple square brackets in the txt file attached to the distribution).
[WHAT IS SYMLINK (SYMBOL LINK, SymLink)?]
Link Shell Extension
schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
en.wikipedia.org/wiki/Symbol_Link
[IS IT POSSIBLE TO DO WITHOUT INSTALLATION USING THE .CMD FILES OF THE SymLink Installer?]
Yes. SymLink Installer CMD files are optional,
you can just copy the files according to the folder names inside the ..\C\ folder,
and also pay attention to the presence or absence of *.reg registry files, keygen … etc. inside the package.
{HOW TO “INSTALL” THIS PACKAGE USING SymLink Installer .CMD FILES?}
Despite the following long text, the point is simple:
a) remove some folders left over from old versions of the program being installed, if any;
b) run only one .CMD file;
c) by specifying the DAW scanning path for VST2 plugins (C:\Program Files (x86)\VstPlugins) start the DAW and use it;
d) register if required.
Details are below.
{0} {Preinstallation of required system software}
Optionally install
[addon] Microsoft Visual C++ 2005-2008-2010-2012-2013-2015 Redistributable Package x86 & x64
forum.oszone.net/thread-145766.html
{1} {Proper unzipping of the package}
Extract (using the 7zip archiver) the contents of the distribution from the .exe file to any disk for permanent storage – so that you do not delete it later *,
for example, to the folder:
d:\Sonnox\
– not deep into nesting folders and without Cyrillic.
* To ensure the operability of SymLink Installer .CMD files,
MOVE, DELETE, RENAME ANYTHING IN THE DISTRIBUTION CONTENT IS UNACCEPTABLE.
{2} {Preliminary cleaning of possible “remains” of earlier versions of the package}
Check for the absence of folders in the places where symlinks will be created (if folders are left, symlinks will not be created).
For this you can, !!! after saving the developments (presets, etc.) !!!,
uninstall (or delete if there is no uninstaller) previously installed plug-ins,
and also delete the remaining (if any) after uninstallation [Folders of the final location of the package contents]:
[Folders of the final location of the package contents ]
The content of the package is located in the folders listed below (“C\” means the system drive – “C:\”).
To successfully create symlinks, before running the SymLink Installer .CMD files, you need to make sure that these folders do not exist.
The “-” symbols in front of the paths below indicate which folders are not needed for x86 systems.
C\Program Files\Sonnox Oxford Plugins\Presets\Native
C\Program Files (x86)\VstPlugins\Sonnox Oxford Plugins
ATTENTION! As a rule, the use of Cyrillic during registration and in the name of the user folder (Current User Name) leads to the impossibility of registration and normal operation of the software.
ATTENTION! If the name of the system drive differs from “C:\”, you need to pay attention to the attached registry files (if any in this package) and correct the name of the system drive in them to the required one.
{3} {Actually “installation”}
For instant installation based on symlinks,
run the required * .CMD as administrator (depending on the bitness of Windows 7 (and higher)),
and if necessary, change** the path to VST2 in .CMD files.
* [WHICH .CMD FILE SHOULD I RUN?]
In this particular case, .CMD files are Windows command files
that create symlinks or delete symlinks or real folders.
SymLink Installer files:
– SymLink Installer.cmd – creates symbolic links to folders and files from the ..\C\ folder.
SymLink DeInstaller files:
– SymLink DeInstaller.cmd – removes symbolic links to folders from ..\C\ or !!! normal folders !!!.
Service files:
– Existing Folders.cmd – the existence of folders according to the list from the [Folders of the final location of the package content] item;
– FoldersList.cmd – creates a list of folders inside the folder ..\C\;
** [HOW TO CHANGE VST2 PATHS IN SymLink Installer .CMD FILES?]
You can avoid changing the paths in batch files for the VST2 plugin format described below
if you specify an additional scanning path for VST2 plugins in the DAW settings: C:\Program Files (x86)\VstPlugins,
or place a symbolic link to the folder C:\Program Files (x86 )\VstPlugins inside the folder where you usually have the rest of VST2,
for example, all your VST2 plugins 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 (x86 )\VstPlugins.
If the specified location is not suitable for one reason or another, then you can edit the paths for creating symbolic links in CMD files.
For example, in x64 Windows file MKLINK.cmd can be replaced (using any text editor):
cmd /c mkdir “%PROGRAMFILES(x86)%\VstPlugins”
cmd /c mklink /j “%PROGRAMFILES(x86)%\VstPlugins\Sonnox Oxford Plugins” “%~dp0C\Program Files (x86)\VstPlugins\Sonnox Oxford Plugins “
For example, on the lines:
cmd /c mkdir “%PROGRAMFILES(x86)%\Steinberg\VstPlugins”
cmd /c MKLINK /j “%PROGRAMFILES(x86)%\Steinberg\VstPlugins\Sonnox Oxford Plugins” “%~dp0C\Program Files (x86)\VstPlugins \Sonnox Oxford Plugins”
Or, for example, to strings (using absolute paths instead of relative ones – %PROGRAMFILES(x86)% or “%PROGRAMFILES%):
cmd /c mkdir “C:\Program Files (x86)\Steinberg\VstPlugins”
cmd /c MKLINK /j “C:\Program Files (x86)\Steinberg\VstPlugins\Sonnox Oxford Plugins” “%~dp0C\Program Files ( x86)\VstPlugins\Sonnox Oxford Plugins”
Or others required specifically in your individual case.
The “formula” of the command for creating symlinks – MKLINK – is as follows:
cmd /c MKLINK /j “Y” “X”
– that is, cmd /c MKLINK /j – the command to create a “mirror” (imaginary, virtual copy) in the form of a folder ” Y” (“symlink destination”) to the real folder “X” (“symlink source”).
In this case, in the parameters of the MKLINK command, only the address of the “Y” folder changes.
Similar changes (if necessary) can be made in other .CMD files.
{4} {Final step}
Installation is complete, next, you need to open your DAW,
specify an additional scan path for VST plugins in the DAW settings: C:\Program Files (x86)\VstPlugins
, and perform an update plugin scan.
See above for more: [HOW TO CHANGE VST2 PATHS IN SymLink Installer .CMD FILES?]
{HOW TO REGISTER A PACKAGE?}
Note:
Sonnox Oxford Plugins preset bindings are registered in the registry using
*Windows Sonnox Plugins.reg
