kei masumoto Posted October 10 Share Posted October 10 Starting with SONAR version 31.09.038, I’ve encountered an issue where a specific VST2 instrument plug-in resets its settings upon application startup. I installed the Core Plugins at the same time as this update—could that be related? The behavior reproduces with plug-ins such as TAL-BassLine. Since TAL-BassLine is deprecated by TAL Software, I apologize in advance if submitting this question is misguided. Link to comment Share on other sites More sharing options...
Wookiee Posted October 11 Share Posted October 11 @kei masumoto can you expand on what you mean by "reset"? Link to comment Share on other sites More sharing options...
David Baay Posted October 11 Share Posted October 11 14 minutes ago, Wookiee said: can you expand on what you mean by "reset"? I can confirm this happens with TAL Bassline, and it was brought up with another free VSTi recently. These synths somehow get reset to default parameters on re-load while the preset name continues to show the previously selected patch but with a dirty flag (asterisk). I don't have CbB on this machine, but it doesn't happen in Platinum (the dirty flag gets set, but the preset parameters are persisted on reloading). I've reported it to the Bakers. Link to comment Share on other sites More sharing options...
Wookiee Posted October 11 Share Posted October 11 @David Baay is this related to zero controllers or is it reading the bank and patch parameters from the MIDI track. Which means they need to be populated to stop this occurring. Just my two Triganic Pu's thought. Link to comment Share on other sites More sharing options...
David Baay Posted October 12 Share Posted October 12 7 hours ago, Wookiee said: is this related to zero controllers or is it reading the bank and patch parameters from the MIDI track. No, I checked; disabling zero controllers did not help. And the MIDI was my own - only note messages. Link to comment Share on other sites More sharing options...
Promidi Posted October 13 Share Posted October 13 I have had this happens sometimes with Native Instruments: Massive X. When loading some Sonar projects with Massive X, the Massive X preset reverts to the init preset. For this specific issue, I have found that the workaround (at least in my case) is to set the following file to read only. %LOCALAPPDATA%\Native Instruments\Massive X\content.db Link to comment Share on other sites More sharing options...
sjoens Posted Monday at 08:39 AM Share Posted Monday at 08:39 AM On 10/11/2025 at 8:14 AM, David Baay said: These synths somehow get reset to default parameters on re-load while the preset name continues to show the previously selected patch Sounds like the opposite of how Cakewalk (Sonitus?) plugins work. Preset stays intact while the name reverts to nothing or default name. Frustrating when I don't remember the exact preset. Link to comment Share on other sites More sharing options...
Amberwolf Posted Monday at 09:41 PM Share Posted Monday at 09:41 PM 12 hours ago, sjoens said: Sounds like the opposite of how Cakewalk (Sonitus?) plugins work. Preset stays intact while the name reverts to nothing or default name. Frustrating when I don't remember the exact preset. I make a new preset for each track or bus with the project name, track/bus name, and then what i called the preset. (at leasdt, enouigh of each to get the idea across to myself so if I have to match that "sound" somwhere else i know what i need to pick. Link to comment Share on other sites More sharing options...
sjoens Posted Monday at 10:03 PM Share Posted Monday at 10:03 PM Backup those presets. If you ever need to reinstall Sonar stuff they may disappear. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now