D16 Group updates all SilverLine Collection Plugins

[Larry Shelby]

D16 Group has announced that all SilverLine plug-ins have been updated.

The new versions are:

Antresol v1.2.0.

Decimort v2.2.0.

Devastor v2.2.0.

Fazortan v2.1,0.

Frontier v1.1.0.

Godfazer v1.1.0.

Redoptor v2.1.0.

Spacerek v1.1.0.

Syntorus v2.1.0.

Tekturon v1.1.0.

Toraverb v2.1.0.

Changes in all plug-ins:

Better compatibility with the latest macOS versions (Catalina and Big Sur for Intel based computers)*.

Interface unification across all products.

Fix for misbehavior of preset change alert.

Fixes of other so far reported and discovered issues.

Code maintenance.

Digital signature for installers and plug-ins (Windows and macOS).

(*) Due to Apple requirements for new macOS'es 32-Bit versions are abandoned in all new builds. In consequence new updates cannot be used in 32-Bit environment (DAWs) like Pro Tools 10.

There are also plug-in specific changes as well:

Decimort:

Fixed:

Problem with audio initialization (ducking-like artifact).

Problem with latency compensation for 48 kHz.

Devastor:

Fixed:

Problem with latency during initialization.

Crackles during first playback.

Crackles occurring for specific audio buffer sizes.

Fazortan:

Fixed:

Issues with Phase Shift for LFO's Random waveform.

Frontier:

Fixed:

Problem with Frontier on stereo bus fed with mono track (Logic Pro X).

Problems with latency compensation.

Godfazer:

Fixed:

Empty parameters shown for automation (Pro Tools).

Changed:

Font size for model selectors.

Factory Default skin set to Medium.

Added:

Hover Prev/Next buttons to move through Filter/Ensemble models.

Spacerek:

Fixed:

Latency compensation in higher sample rates.

Added:

Hover Prev/Next buttons to move through Reverb models.

Tekturon:

Fixed:

Problem with not working Delay Lines for bigger delay times under certain conditions.

Toraverb:

Fixed:

Issue with partial signal processing in Bypass mode on Pro Tools.

Problem with audible delay network adjustment during preset change.

https://d16.pl/effects

[Zo]

What is interface unification ? I stopped using those because they were to tiny ...

[Fleer]

It’s a gender thing. 

[TheSteven]

<sigh> Apparently the dev forgot to code in error handling to automatically select a default plugin size if none has been previously selected.

In Windows - all of the updated VST plugs will give you this error when you use them...
(no idea about on a MAC or with AAX versions)

Here's how to fix so that you don't get this error every time you try to use the plugin.
Open plugin and get past error message shown above by clicking on the OK button.

then

and repeat for every D16 updated VST you have installed.

I created a support ticket with D16 about this...

Edited February 4, 2021 by TheSteven

[TheSteven]

7 hours ago, Fleer said:

It’s a gender thing. 

OMG as if using plugins wasn't at times challenging enough - they now have genders?  Is this part of the VST 4.0 spec?
Will we need to address them by their proper pronouns to get support?
Are we going to have misogynistic and misandristic plugins that won't work together?
 

[TheSteven]

Got answers from D16 support but it was a complicated, time consuming mess.

Found simple fix:

In Windows File Explorer go to C:\ProgramData\D16 Group\[PLUGIN-NAME] \Skins
and then delete old skin files.

[TheSteven]

v2 plugins updated to 2.X.1

• Fix for skin error.

Per D16:
 

Quote

Our development team analyzed the problem and we found that if for some reason update installed cannot delete old skins (it happens occasionally unfortunately) the plug-in if finds the old skins (because ini file points to the old skin name) tries to load them up it shows the error. We made the fix for the problem and even if old skins aren't removed plug-in no longer tries to load them. The new version has just been made available in User Area. But if you've already resolve this issue there's no point in downloading the hotfix update.