Michael Reynolds Posted May 18, 2021 Share Posted May 18, 2021 I have already posted about this issue in the Native Instruments forum but no one seems to be able to help me and it doesn't seem to be a problem others are experiencing with the latest version. Basically every time I load a project, if there were any instances of Massive X they would all be reset to init, meaning I lose all the work I've done tweaking each instrument. I only have this problem with Massive X but I'm wondering if there is a setting in Cakewalk that could be causing this information not to be saved. Any help would be greatly appreciated. Link to comment Share on other sites More sharing options...
Noel Borthwick Posted May 18, 2021 Share Posted May 18, 2021 @Michael Reynolds you share a reference test project that has this problem with instructions on how to reproduce it? Also are you running the latest version of Cakewalk? Link to comment Share on other sites More sharing options...
Michael Reynolds Posted May 18, 2021 Author Share Posted May 18, 2021 @Noel Borthwick Thank you for the reply. I'm sorry but I'm not sure what you mean by "reference test project". Should I upload my project here? Yes, I am using the latest version of Cakewalk and Massive X. This issue happens even if I only have a single track in the entire project, as long as that track is an instance of Massive X. Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted May 18, 2021 Share Posted May 18, 2021 Just now, Michael Reynolds said: @Noel Borthwick Thank you for the reply. I'm sorry but I'm not sure what you mean by "reference test project". Should I upload my project here? Yes, I am using the latest version of Cakewalk and Massive X. This issue happens even if I only have a single track in the entire project, as long as that track is an instance of Massive X. yes, can you please upload either the .cwp or a link to the project via dropbox/google drive, etc. You can also PM Noel and/or myself with the link with the details if you don't want to attach to the public thread. Link to comment Share on other sites More sharing options...
Renato Ventura Posted January 14, 2022 Share Posted January 14, 2022 (edited) I have the same problem when I open a project the massive x preset used before is reset to "Init" was the probòem solved? Edited January 14, 2022 by Renato Ventura not clear Link to comment Share on other sites More sharing options...
Klaus Posted January 14, 2022 Share Posted January 14, 2022 I can't reproduce that, Massive X presets and parameter changes are saved and restored when opening the project. I'm using the VST3 version of Massive X. Link to comment Share on other sites More sharing options...
TVR PRODUCTIONS Posted January 15, 2022 Share Posted January 15, 2022 (edited) This has been happening to me intermittently for years using Korg M1 and Roland JV. In fact it is happening right now using the M1. Every time I reopen the project, the sound I chose is gone and it defaults back to the default sound, Universe, which is over the top, reverb drenched lush sounds. The last thing I need for this song. Edited January 15, 2022 by TVR PRODUCTIONS Link to comment Share on other sites More sharing options...
msmcleod Posted January 16, 2022 Share Posted January 16, 2022 18 hours ago, TVR PRODUCTIONS said: This has been happening to me intermittently for years using Korg M1 and Roland JV. In fact it is happening right now using the M1. Every time I reopen the project, the sound I chose is gone and it defaults back to the default sound, Universe, which is over the top, reverb drenched lush sounds. The last thing I need for this song. Just tried it here with the Korg M1 (both with the plugin GUI open and with it closed). It's recalling the correct preset in both circumstances. Double check you've not got MIDI output enabled on any other VSTi's. If there's another MIDI or Instrument track routing to the M1 / JV that is set to program #0, this could be the cause. You should also check the input routing of the M1 / JV tracks. If they're set to OMNI or None and there's another track outputting MIDI with program change set to #0, this will also cause this issue if the M1 is the active track when loading. Link to comment Share on other sites More sharing options...
Michael Reynolds Posted January 20, 2022 Author Share Posted January 20, 2022 The only workaround I have found is to delete the Massive X folder at this file path before launching Cakewalk. You must do it every time before launching Cakewalk or Massive X will be reset again. C:\Users\owner\AppData\Local\Native Instruments Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted January 20, 2022 Share Posted January 20, 2022 7 hours ago, Michael Reynolds said: The only workaround I have found is to delete the Massive X folder at this file path before launching Cakewalk. You must do it every time before launching Cakewalk or Massive X will be reset again. C:\Users\owner\AppData\Local\Native Instruments This sounds like it's likely something specific to Massive X on your system. I just confirmed it loads normally on our end. If deleting a plugin settings folder/file fixes it for you, it's likely something you'll need to address with NI directly. Link to comment Share on other sites More sharing options...
TVR PRODUCTIONS Posted February 4, 2022 Share Posted February 4, 2022 On 1/16/2022 at 10:03 AM, msmcleod said: Just tried it here with the Korg M1 (both with the plugin GUI open and with it closed). It's recalling the correct preset in both circumstances. Double check you've not got MIDI output enabled on any other VSTi's. If there's another MIDI or Instrument track routing to the M1 / JV that is set to program #0, this could be the cause. You should also check the input routing of the M1 / JV tracks. If they're set to OMNI or None and there's another track outputting MIDI with program change set to #0, this will also cause this issue if the M1 is the active track when loading. I must be stupid because, as helpful as your post sounds, I am lost. I do not see any way to check midi out on my vsts. If I look in the pro channel, there is no midi outs there either. What am I missing? Link to comment Share on other sites More sharing options...
Sebastian Szpakowski Posted August 19, 2022 Share Posted August 19, 2022 @Michael Reynolds, were you able to find a solution? I've been experiencing the same thing on my brand new PC, with fresh installs of cakewalk and massive (all versions are up-to-date), with NI tech support we've been doing all sorts of installs/uninstalls/reinstalls to no avail... I found that if in the folder you listed I just delete content.db (before starting cakewalk) this does the trick too. Link to comment Share on other sites More sharing options...
Sebastian Szpakowski Posted August 27, 2022 Share Posted August 27, 2022 So, I think I found something, potentially a bug in cakewalk, related to the "EnablePluginCancelButton" as per "Cakewalk - Cakewalk Documentation - Cakewalk.ini" ... i.e.: a bug related to how some very complex plugins are initialized? I noticed that Massive X remembers the preset when it's the only track in the project... However, the more MIDI tracks I add, the more likely massive X is to "forget" and reset to init. Frustratingly enough there is not a simple number of tracks that throws everything off... I can only say more than 7 MIDI tracks, - more likely it is to cause issues... (I double checked, and this is not related to my other MIDI gear sending stray messages: I can turn everything off, and turn my cakewalk without any MIDI gear, and massive will still reset ... most of the time. This behaviour is seemingly related to number of MIDI tracks and how complex they are (i.e. in/out assignments vs omni) workaround: So with the EnablePluginCancelButton set to 1, in the property window of massive you now have a little VST "cancel" button in the upper right corner (next to the "pin", right below the close window button). (I saved my project with the massive x property window opened, prominently showing my preset - angelic sprites) I start cakewalk and re-open my project I see my original massive X preset briefly, (see top picture below) but massive resets to init X within a second, I then press that cancel button so massive X property window closes, when I reopen the massive property window again, magically, Massive X now reverts to the preset that was saved with the project originally... (i.e. un-resets itself...) Not sure if this is helpful... I'll send this to Cakewalk support and NI support to see if there is anything special that causes this reset behavior for Massive X Link to comment Share on other sites More sharing options...
Sebastian Szpakowski Posted September 2, 2022 Share Posted September 2, 2022 solution on my system, at least: Memory integrity toggle in windows 11. when it's off, massive X recalls program settings correctly. When it's on, massive X resets to init X upon loading of the project... Link to comment Share on other sites More sharing options...
abacab Posted September 2, 2022 Share Posted September 2, 2022 I already have that feature set to "Off" here in Windows 10. I wonder if that also could be an issue on this version of Windows? 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