With the latest Steinberg VST3 SDK update (v3.6.7), VST3 plugins that are compiled against this SDK crash in Sonar, which did not crash with VST3 SDK v3.6.6 or earlier. These are VST3 plugins that also use the JUCE framework (v4.3.1).
 
The root cause seems to be that for plugin parameters that are marked as 'program change' parameters, the following function from the VST SDK is called from Sonar with a parameter ID as first argument instead of the parameter index:
 
vsteditcontroller.cpp, line 105:
tresult PLUGIN_API EditController::getParameterInfo (int32 paramIndex, ParameterInfo& info)
 
If the parameter ID (represented as int32) is out of bounds re the parameter array, the VST3 SDK v3.6.7 throws an error (while v3.6.6 did not). Both versions of the SDK however exhibit the problem of calls with the parameter ID argument being mixed up as paramIndex (the SDKs seem to differ in robustness of dealing with this issue).
 
Using the exact same code, other hosts do call the above function with the correct arguments so this seems a Sonar specific problem. Parameters that are not marked as program change parameters work correctly in Sonar.
 
The issue occurs for Windows (7) x64, Sonar version 23.2.0 Build 45.

This needs to be sent to someone who can help.

This needs to be posted in the problem reports forum.

Thanks for the report.  We'll check it out.  
 
Keith

Thank you Keith!!!

Holy moly.

Only slightly related. If you install the latest Stardock Fences on windows 10 x64, Production or Insider builds, it breaks plugin scanning. Nearly every plugin generates an error during auto scan.

djtrailmixxx Stardock Fences

i had to look it up (i only know stardock as a games publisher) so i'll save the rest of you the trouble https://www.stardock.com/products/fences/
not sure what could be happening to break plugin scanning?

Thanks again for the specific report with the VST3 program change param.
This is updated for 2017.04.
Tested with Melda PowerSynth demo which is now responding to the program change from the Inspector.
If anyone knows a synth that supports multiple program change params (i.e. for multiple midi channels) that'd be cool to check.  Melda supports a single unit with 1 program change param.
Thanks.
 
Keith
 

Hi Keith,
 
Thanks for looking into this and following up so quickly! 
 
As for testing: the plugin that initially revealed the issue was not a synth but a VST3 effect plugin. I've made that plugin available for testing purposes here:
 
www.toneboosters.com/downloads/Barricade_v4.1.2_win.zip
 
The crash can be reproduced as follows:
- Open a new project
- Add a new audio track
- Insert Barricade VST3 as effect on the track
 
We've made an update available as temporary fix (by reverting to VST3 SDK v3.6.6) that won't crash, but still receives the program parameter call with the wrong arguments:
 
www.toneboosters.com/downloads/Barricade_v4.1.3_win.zip
 
Let me know if you need anything else for testing.