Marc Wielage wrote:The Waves plug-ins packages are pretty widely used: They have sales every often on the bundles - in fact, I picked up the Diamond package for about $500, which was a bargain given that it normally goes for well over $2000. IZotope is also a phenomenal set of tools, many of which help enormously in taming problematic dialogue and keeping levels optimized: Resolve is not an approved host for Waves. Shame too because right now the Diamond package is only 259.00 bucks (from 2,999.00) which is just bonkers. Marc Wielage wrote:The Waves plug-ins packages are pretty widely used: They have sales every often on the bundles - in fact, I picked up the Diamond package for about $500, which was a bargain given that it normally goes for well over $2000.
IZotope is also a phenomenal set of tools, many of which help enormously in taming problematic dialogue and keeping levels optimized: Resolve is not an approved host for Waves. Shame too because right now the Diamond package is only 259.00 bucks (from 2,999.00) which is just bonkers. Robert, I believe Waves and 'all' VST 2 plugins work in 14.
Apr 29, 2016 - RX is a powerful audio editor that DaVinci Resolve users can use to get better. How to use RX as an audio editor with DaVinci Resolve 12.
(I don't think VST 3 versions work.) Here's a YouTube video of someone using Waves in 14. I can report that most of the Diamond series do not appear in Resolve 14 and some that do actually crash Resolve. I think most support AAX, so they work very well in Media Composer (which is why I took the chance - MC is my main NLE still).
Not sure why most don't show in Resolve. A bit disappointing on the Resolve front. Maybe someone else will have different results. One thing to note is that Waves plugins do not sit in the Program FIles Steinberg VSTPlugins folder, just in the Program FIles VSTPlugins so you have to tell Resolve to look there as well. Also - Waves uses an interesting approach where only a couple of DLLs sit in the VSTPlugins folder and these somehow link to the actual plugins installed elsewhere. Anyway - for $259 yesterday ($999 today) that was a pretty good set of plugins for Media Composer.
I wish I had better news for Resolve users. If anyone with Waves plugins has a different experience, please post. Steve Alexander wrote:Glenn - are you referring to all plugins that came with the Diamond bundle? Also - did you have to tell Resolve where to look for those plugins and if so, were did you point to? Thanks Hi Steve, For sure but have used even more on my or other Resolve rig, ( i have a much wider range of plugins. Got it al a long time ago from a good college who quit his mixing job for close to nothing.) So far the only plugins that sometimes need a bit of massage are the multichannel (5.1) plugins (are a bit order sensitive ), but even those work fine.
![Davinci Resolve Audio Plugins Davinci Resolve Audio Plugins](/uploads/1/2/3/9/123928621/577323954.jpg)
Have yet to find one that does not work. Multichannel compression/limiting/reverb/image shaping, all good. And none that crash resolve Not all load as AU + VST, but the few i dont see as AU i see as VST and visa versa.
Regarding location, as besides waves i have lots of other plugins, and not al liked in the past or still Resolve (mainly old 32 bits dont work), i put them (a copy) in a separate directory, just for Resolve. In settings you can specify a (or multiple) custom directory(s), so i drop a copy of the vst/au in there and if it does not work/crash resolve i can easily take it out.
Nothing in there will affect my general VST/AU setup for my other DAW's (Reaper/Ableton/and now defunct protools which i ditched for Reaper). As you are on windows, things will likely look different so can not comment on that. Also the trick with the extra vst dir may or may not work as subtle although i did see in earlier discussion that something like that is also possible for windows, but due to the registry your mileage may vary. I'm just going through the process of dropping these Diamond bundle plugins on to tracks on the edit page. Most seem to 'work' (no idea if delivery would work) - the only crash so far was EMO-Q4-Mono when I dropped it on a stereo track (most mono effects don't crash if you accidentally drop it on a stereo track but this one does). Others that crashed: REQ n Stereo/Mono (there are several of these) But most seemed to work in as much as they would show their interfaces and have some effect on the audio played back trough my speakers. Sometimes a VST effect would apply and appear to work but then if you clicked on the track header later to show the properties (to bring up the VST UI again) Resolve would crash.
But mostly not. This is really as much testing as I care to do for now. That was a pretty well spent $259. Thanks to Glenn for pushing the issue (had you not stated emphatically that all was good with the Diamond bundle and more I probably wouldn't have pursued this - at least not today).
Going to collect my commission at Waves now Take you time to play with these VST's. It's really good stuff in there. You got a great deal as is so much more expensive this stuff normally. Even if 50% would not have worked, you still have a great deal I tent to only use them via the Fairlight page btw, much more user friendly to drop on the right track / monitoring etc without to much fiddling, not sure if makes a difference technicaly but guess it should be the same stability wise. As Fairlight evolves so will the support for more advanced function in some of the plugins, like side-chaining, which is not active yet in Resolve (in both the internal fx and vst). But was presently surpriced that multchannel stuff mostly works, which is sort of essential for post work. Anyway, have fun man!
Robert James wrote:Resolve is not an approved host for Waves. Shame too because right now the Diamond package is only 259.00 bucks (from 2,999.00) which is just bonkers. Yes, I bought the Diamond package when it went on sale. (I literally paid about $2K for this same package 10 years ago in another life as a Pro Tools mixer/editor.) All the Plug-Ins come up for me just fine in Resolve 12.5 and 14. I just double-checked Resolve 12.5 and yes, you can drop any Waves Plug-in on top of a clip and it will apply. It takes a few seconds to go out and load the control panel, but it does work.
This is for the Diamond 9.2.6 package. I also have most of the Nugen plug-ins, and those appear to work as well: I have not tried them in Fairlight yet, but hope to once I wrap a couple of projects. There are many plugin developers and thousands of plugins available for many tasks, so which ones are good to have really depends on what you personally need.
The plugins I have are from Waves (no problems so far using these in Resolve, and they have sales more often than not), iZotope (RX6, although I prefer to use the standalone editor, and Neutron), ToneBoosters (I only use the De-Esser) and Valhalla DSP (reverbs). You can get trial versions for most plugins, so just download those and see if they suit you. Wouter Verwijlen wrote:There are many plugin developers and thousands of plugins available for many tasks, so which ones are good to have really depends on what you personally need. The plugins I have are from Waves (no problems so far using these in Resolve, and they have sales more often than not), iZotope (RX6, although I prefer to use the standalone editor, and Neutron), ToneBoosters (I only use the De-Esser) and Valhalla DSP (reverbs). You can get trial versions for most plugins, so just download those and see if they suit you.
I can't get Resolve 14 to even see my VST plugins, the same ones I'm using in Sound Forge. I have Waves and Izotope plugins installed - checked the folders and, yup, the plugins are there. When I direct Resolve to the folders, it doesn't see the plugins, so no option to enable them. Can anyone help? I installed Waves h-reverb (AU and VST versions) in Resolve 14. Resolve doesn't recognise the VSTs. The AUs appear in the list, though, and in the compressed view, they work perfectly.
When I switch to the expanded view, the view sits on top of the compressed view instead of below it and the controls do not work. Reverting to the compressed version calls up a document in Preview and the plug-in crashes. I got on to Waves support and they told me they don't support installations on DaVinci. Anyone any ideas, please? Thanks for that Peter.
But I'm afraid I omitted to mention I'm on an iMac (32/latest Sierra) Plugins are in Library/Audio/Plugins/VST or Component. Resolve won't pick up H-reverb VSTs.
H-reverb AUs work, sort of. When I go into expand mode to use the advanced features the expanded screen loads over the original one and jams the whole thing up.
Actually that's not quite true - I have one clip, just one, where it works perfectly. I've examined all the settings but can't for the life of me see any difference. Waves won't help as they don't support DaVinci. PeterMoretti wrote:This is not good at all. Both Waves and Izotope do not officially Resolve. That's a big issue, as they are ubiquitous in post.Not so sure that is altogether true.
Waves and iZotope are often mentioned on forums due to these options being some of the cheapest paid options, but both still remain very much entry level options. Majority of my audio specialist colleagues (involved with film, television programming, music releases, and audio restoration) aren't Waves or Izotope plugin users, and therefore do not have these options installed, as they are always better served by more specialised and refined options.
I haven’t required a Waves plugin on a session in well over a decade. Update: iZotope's RX7 Advanced plugins, are much less resource intensive than the previous versions of the same plugins, and are now actually usable on a Resolve Timeline with little penalty. Much improved performance and stability within Resolve 15 as both Track and Clip-based effects - and if RX plugins misbehave, there is always the Cache or Bounce Audio Effects options.
RX7 Advanced plugins are still not nearly as resource efficient as Sonic's NoNoise and Cedar Studio plugins, and these options still provide much more transparent results than RX 7 in day to day workflows. IZotope RX's real (often overlooked) strength is still the standalone audio editor, the processing modules and plugins are really additional fluff on top of that core functionality. John Paines wrote:There have a few reports, including mine, that RX6 plugins are not reliable, at least on Windows. One or two may work, or at least work well enough that you won't notice any defects. More than, including more than one application of NR, will likely cause pre-echos, loss of sync, etc. These artifacts will be retained in any renders.These are issues related to latency and delay compensation, and have been the case since Izotope released RX version 2 in 2007 with certain modules as plugins. Try NRWhich settings are active within the Spectral DeNoise module?
The Adaptive mode in Spectral De-noise uses a significant amount of memory and computational power. For a more efficient form of adaptive noise reduction, try the Adaptive mode in Voice De-noise, which is designed to be highly efficient and zero-latency.
Voice De-noise has been specifically designed to provide high efficiency, zero latency adaptive noise removal when inserted on a track in your DAW or NLE. The Spectral De-noise plug-in is far more resource intensive and uses higher latency. A: is the least CPU intensive process and is suitable for real-time operation.
B: is more CPU intensive and has more latency, but can still run in real-time on most machines. C: is a very CPU intensive algorithm and can only run in real-time on faster multicore machines. D: The speed of algorithm D is similar to algorithm C.
It's easy enough to test. Try NR, de-crackle, de-hum, de-clip. That's usually enough to do it. Izotope's Notes on Latency: iZotope plug-ins use complex DSP, which can create audible latency. During playback, this can result in a delay or offset to a single track's output, which can put a track out of sync with the rest of a mix.
Make sure the 'Enable delay compensation'. feature is enabled in the Options/Preferences window. This option is available in the General section under 'Latency' or 'Delay Compensation.'
. Note that this feature reports the exact offset in samples to the host application. The host itself will need to compensate for the offset.
Make your host's delay compensation feature is enabled. This will usually be available in the preferences window or an options/settings menu. If your host application does not support Delay Compensation, you can still manually adjust your track to compensate for the offset. The current offset is available in the 'Latency' or 'Delay Compensation' section of the Options/Preferences panel.
I do not think that Resolve 14.x provides the required full latency compensation in its native implementation, and it certainly doesn’t provide any options within the application Preferences related to Delay Compensation, so manual compensation is required. My suspicion is that the Fairlight Accelerator card is required for full latency compensation, as hinted at on the Resolve marketing pages.