[Solved]Bug: Fairlight 17.4: Why some VST 3 are not working?

Solved on 17.4.2
I have put SPL IRON on a music track on Fairlight.

i went on PLay: nothin!not any indicator was working and the plugin was in the reality excluded
The same for FabFilter Pro Q3. No audio in.
Same thing with iZotope Ozone ...

is there something specials, should I consider with Farilight, in order to get them working?

You are not the only one. When opening DVR17.3 projects containing FabFilter Q3 on 17.4, it crashes the app. I had to revert to DVR17.3

There have been several threads started since 2 days ago on this forum, and we guess BMD is working on DVR17.0.1 to solve those issues.

TO me the app doesn't crash. Just doesn't work at all.
It's opening and no signal is through.

Similar to iZotope: the signal is through but not any changes when I change any parameter.

Hence:; there si not compatibility with VTS3s if it's behave so

I did notice with the upgrade to 17.4.1 that some of the VST3 are working now.
Q3, Izotope are working . SPL IRON not at all. Other ones yes but some not yet.

[Peter Chamberlain]

Please list the ones that you find don't work with as much detail as you can so we can evaluate if its our or their implementation of the VST3 spec.

Peter, I have the following VST3 plug ins that show status 'Failed to Load':
Drawner S73
Red 2 EQ
Red 3 Compressor
Saturation Know
TSAR-1 R Reverb
Tube Delay
The same plug-ins load fine as AU effects

Please list the ones that you find don't work with as much detail as you can so we can evaluate if its our or their implementation of the VST3 spec.

Hi Peter

The one I re-tested yesterday and it was not working: SPL IRON, Mäag Audio EQ4 and I tested now: all the ones Plugin Alliance (so far)

The other ones I complained in the topic (FabFilter Q3/Q2, iZotope), from the 17.4.1 are working.

I've just installed the SPL Iron VST3 and it is working fine in 17.4 on Windows.

As an aside, I do like the alternative red UI.

To me no one of the plugins of Plugin Alliance is working. on 17.4 as well as on 17.4.1

it means: they are opening, but not any audio signal through.

Here it is: opened but not any signal through.

And they are all activated of course

Bart, all my Plugin Alliance VST3 plug-ins work without issue.
These are my VST locations.

VST Locations.jpg (70.52 KiB) Viewed 3342 times

And here is SPL Iron happily working on the Master Bus.

SPL Iron VST3a.jpg (759.33 KiB) Viewed 3342 times

Are you using an up to date version?

The same as mine ones. But to me: they don't work (viceversa in any DAWW they work perfectly).
So the only one impacted is DaVinci.

And yes I always and constantly update everything. I don't like to work with old versions of anything.

The Plugin Alliance VST3 plugins are without issue on macOS (along with the VST2.4 and Audio Units formats).

I have the following VST3 plug ins that show status 'Failed to Load'

Are the VST2.4 versions of the problematic plugins loading correctly?

Manually delete the VST3 configuration file to force a rescan:
Users/Home/Library/Preferences/Blackmagic Design/DaVinci Resolve/Fairlight/Effects/VST3Configuration.xml

Do the problematic VST3 plugins load correctly after a rescan?

Hi Reynaud

you have Mac.
I have Win.

2 different architectures.

As many Mac users are experiencing issues with last versions of DRS (see another topic in which they are lamenting these https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=149514) but not me, it's possible that Mac users are tno experiencing this issue.

It's a fact that the Plugin Alliance won't work at all on my machine and DRS.

I'd like to add that vst compatibility among the various developers in the DAW world is a perpetual battle. If this is Resolve's first version to support vst3, I'd generously buffer my expectations for full functionality.

I'm guilty of jumping in quick too but early-adopters seem to often deal with initial bugs.

It's a fact that the Plugin Alliance won't work at all on my machine and DRS.

You need to determine the cause of the issues on your system as Charles Bennett, who is also running Windows, indicates that Plugin Alliance VST3 plugins are without issue.

Can you confirm that the VST2.4 versions of the Plugin Alliance and iZotope plugins are without issue on your system?

SPL Deverb Plus (Plug Alliance) and iZotope RX 6 both VST3, work fine here too on Windows, for what it's worth.

It's a fact that the Plugin Alliance won't work at all on my machine and DRS.

You need to determine the cause of the issues on your system as Charles Bennett, who is also running Windows, indicates that Plugin Alliance VST3 plugins are without issue.

Can you confirm that the VST2.4 versions of the Plugin Alliance and iZotope plugins are without issue on your system?

I have only VST 3s

The few VST 2s I have are not PA.

What determine the malfunctioning? DRS of course since it's the only one platform i which these VST3s are not working and since it has VTS3s as "new entry" so: potentially buggy.

My Plugin Alliance/Brainworx VST2.4 plug-ins work as they should as well.

My Plugin Alliance/Brainworx VST2.4 plug-ins work as they should as well.

Goof for you indeed

But you have VST 2.4

And i said: VST3.

To me it's a bug like this: viewtopic.php?f=21&t=146975
where all said it isn't and then: it was.

Let's waiting for another version, hoping they can target this.

Bart, I've already said that Plugin Alliance VST3s are no problem. I was expanding on what Reynaud said about whether VST2.4 plug-ins from Plugin Alliance were working.

Bart, I've already said that Plugin Alliance VST3s are no problem. I was expanding on what Reynaud said about whether VST2.4 plug-ins from Plugin Alliance were working.

Ah ok, sorry

Solved on 17.4.2 So: it was a real bug. Greatly solved! Thank you BMD

I am also having problems running VST3 plugins with 17.4.2 (build 8). I have several plugins from FabFilter (Pro Q2, Pro L, Pro MB, etc.) and most are not responding well or at all to control changes. For example, the Pro L (a brick-wall limiter) gain control won't 'catch' and affect anything unless I turn it way up or keep wiggling the control as I play the timeline. Then, I can't seem to turn it back down.

When I revert back to VST2.4 versions of the same plugins, they seem to work.

Jeremy re-download and install 17.4.2. It had a very quick build update because of vst problems and is now build 9.

Thanks Charles for the tip. I just downloaded and installed build 9. Unfortunately, I'm still having the issue with FabFilter ProL, where the gain setting doesn't 'catch', same as before. I guess I'll have to stick with the V2.4 VST until this really is fixed.