[SOLVED] Waves V16 plugins scanned (VST3) but most are now in the excluded bucket

[Glenn Stanton]

updated to v16 and when scanning, i've had a couple of errors asking to disable or enable (the Wave v13 seems to be a frequent one) and the v16 scanning seemed to be ok, then i got a "VST Loop Error".  i ignored that, when i look into the VST FX, many were missing, checking them with excluded button marked - many of the v16 are there. 

i'm guessing this might be a Waves issue, but then my NI Komplete Kontrol scanned them without issue (maybe NI isn't doing a robust a check?)

 

Edited Monday at 06:26 PM by Glenn Stanton

[Glenn Stanton]

note - i selected  "enabled" all the Waves FX in the excluded bucket and re-ran the scan for all failed and all existing plugins. no errors and no excluded. so must have been a one time thing... weirdly the VSTScan.log file didn't show the v16 Waves DLL being scanned...

one additional note - i removed the plugin catalog XML and asset XML files for Next and re-ran the scan because i was getting something like 10 copies of plugins and failures to load.

the Next plugin catalog reset did not do anything useful hence removing them. once the new scan was complete - all neat plugins list again and all working.

Edited Monday at 06:55 PM by Glenn Stanton

[Billy86]

Your mention of Komplete Kontrol caught my eye. I’ve worked with Kontakt, but I’m a newbie at KK.  

I’ve got an NI Session Guitar loaded into Komplete Kontrol. I’m using Auto-Chord in the key of F. The song modulates twice, a half-step  each time, so from F to Gb, and Gb to G. I’m trying to automate the key change to avoid 3 separate instantiations of the VSTi. KK makes the key change parameter available in an automation lane, but I can’t figure out how to make it happen. I arm the track, and write-enable the automation lane, hit record, make the move with my mapped Nektar Impact 25+, but all it does is change the key of the Session Guitarist instrument. I start at F, move to Gb as the record function is running when it hits the spot for the key change, but it doesn’t change the key at the spot I make the move. It simply changes the key of the Session Guitarist instrument. Visually, it looks like the move hasn’t been recorded; usually I can see the envelope nodes being written  when i record and automate something.  Any ideas what I might be doing wrong? Thanks.

[Glenn Stanton]

i really only use the Komplete Kontrol when i'm playing live or composing, i just use Kontakt in the DAW. for the Session Guitarist instruments, you can use key switches (selective MIDI notes usually lower or higher than the instrument range) to change parameters

--or--

use articulations (which are typically the same MIDI notes but with some options) as there is an articulation track and it also makes things easier. you can create your own articulations or in some case purchase them (or maybe some folks have freebies). there is a huge package "Babylon" which has articulations for hundreds of products and instruments, i had bought an earlier version several years ago as it had a lot of the instruments i use already built.

[Billy86]

Hi. Thanks. Yes, have the Babylon articulation package, but haven't dived much into it. Very familiar with keyswitching in Kontakt, but I don't think the "change key" parameter when you're using Auto-Chord is available. From what I've been able to find, you have to go through Komplete Kontrol wrapper to access it.