

So far, I have uninstalled Stutter Edit completely and reinstalled (currently using version 1.03 running as a 64-bit VST plugin). I'm trying to find the cause of this so that I don't have to go into the Plug-In manager on each session and reconfigure Stutter Edit to act as a synth. I have set that option properly within Sonar on both Stutter Edit plug-in files, however when Sonar scans existing plug-ins upon startup, it resets the values for Stutter Edit and clears the "Configure as synth" option, making it an effect once again. In order for this plug-in to work properly, it needs to be configured as a soft synth via the options in Sonar's Plug-In Manager. I'm having a problem with Sonar Producer Expanded resetting values in registry files for my plug-ins when scanning upon startup, specifically iZotope's Stutter Edit. IZotope Stutter Edit and Sonar Expanded - plugin scan resets registry values
