Blackmagic Forum

I'm seeing an issue where my Valhalla Room reverb plugin will just stop working. I apply it to a clip and choose a preset and it simply doesn't do anything (I can test this by choosing a really large space). Sometimes it works, sometimes it doesn't - I was just doing a test to see if there was a difference between the VST and Audio Units versions where I applied the VST version to a clip and it did work, then I removed it, tried the AU version and it didn't work, then applied the VST version again and it didn't work either. This is happening with both VST and AU versions in Resolve 16.1.2, 16.2, and 16.2.1.

Anyone else seeing this?

Is the described behaviour limited to Clip-based processing or is this also an issue on Busses?

Is the issue limited to Valhalla Room or is the behaviour also experienced with other VST and AU plugins?

Thanks Reynaud. I'm only doing it on clips, and I have a pretty minimal selection of plugins (RX7, evaluation versions of Fabfilter C, Q and R and a couple other things) since I don't want to shell out money for plugins only to find that they don't work properly in Resolve (and IME that's not something that should be taken for granted). But I have not seen this happen with any of the other plugins.

I'll try it on a bus to see if that makes a difference but workflow-wise a clip effect is much preferred, I'm adding it to a hard effect to fit it into the space and tying up a whole track for that isn't really practical.

Also, the problem is actually worse than I initially reported - I relaunched Resolve to see if that would fix it and it did (as in, Resolve did apply the reverb), but when I switched presets it did this thing it's done before where I'll hear nasty feedback and each time the clip plays the feedback gets worse (by the third time it's necessary to quit Resolve).

The weird thing is that sometimes (and until recently, pretty much all the time) it just works fine. Meaning, the exact same clip in the exact same timeline works fine. And I know other people here use it and recommend it.

Did this ever get resolved? I am having the same problem where I apply ValhallaRoom and get feedback. I have used it 100s of times, and it just suddenly started with a particular clip. I don't think it has anything to do with the clip, and I've updated the .vst, so I'm at a loss what to do.

Thanks!

mlavanish wrote:I apply ValhallaRoom and get feedback

Is the issue isolated to ValhallaRoom?

You may need to discuss with the ValhallaDSP developers and have them test their plugin within Resolve.

For what its worth same issue happening still. Will contact DSP if anyone else has please let me know what you find, would like to use these plugins within Davinci.

Currently using Valhalla Room 1.6.3 VST on DR 17.1.1 with no issues on a Mac 10.15.17

I'm also using Valhalla Room 1.6.3 VST on DR 17.1.1, but in my case applying Room to a clip means the clip will stop outputting any audio, even if the plugin is disabled/bypassed. Also, the VST and VST3 versions won't even show up in the Effects Library.

Works fine in Logic and Ableton Live and Final Cut X.

VST 3 does not work in Resolve.

Charles Lyons wrote:Also, the VST and VST3 versions won't even show up in the Effects Library.

On macOS both the AU and VST2.4 versions load correctly in 17.1.1 - Resolve's Preferences > Audio Plugins indicates if an error is present.

Note that if the “Filter Effects by Track Type” preference is enabled in the Mixer's Additional Options (3 dots) menu, then plugins that only support 2 channel IO will not be listed on multichannel Mixer Channels and Busses.

The VST is showing up today, is reported as loading successfully, and is playing audio correctly. I didn't change anything from yesterday, just relaunched Resolve (again). I don't have any multichannel audio tracks either. This kind of erratic behavior is disturbing.

The AU also reports as having loaded correctly but continues to mute the audio completely, even when disabled/bypassed.

I don't use VSTs in general so I haven't been paying attention to which platforms support VST3 and which don't. Which means that even if the VST loads and behaves correctly from now on it doesn't do me much good, because I have many instances of the AU effect in multiple timelines which I would have to go through and manually replace.

I've contacted Sean at Valhalla, hopefully he's able to identify the cause of the problem. Again, I don't have this issue in any other hosts.