jpetersen
Very strange one. Never had that problem.
I still have X3e installed and worked with it on 2 full CD projects.
 
 
 
The only difference I can see is I use Win 7 64bit SP1, you use Win 10.
 
 

So you have X3e Studio or Pro? Not that there should be much of a difference besides the bundled software, but I'm curious if this is more "Studio" related than "X3e" related.
 
I had Windows 8 until recently, same behavior. As I said above, this was a clean install on a new machine. 

Pro. I don't think Studio had the ProChannel.
Does it happen if you start a clean, "Normal" project, single audio track, pull up a node on the EQ, then close and re-open?
 
I ask because I wonder if a plug-in may be crashing on save before the prochannel EQ save code is reached.
 
So perhaps it's worth a try removing all plug-ins from the ProChannel (including from the Master and Metronome busses - why does the Metronome bus get plug-ins by default, for heaven's sake! :) )
 
I am puzzled that this bug should even be possible without other more dramatic things happening. But sometimes programmers are lazy and put a try-catch around code without doing any error handling in the catch part. So it can crash and you will never know.

If your Windows machine is connected to the internet, you might try disconnecting from the net and start shutting some things off (antivirus, wifi adapter, various background services that you don't need when disconnected from the net - just keep track of what you turn off so you can turn it back on once you connect back to the 'net). Before I took mine offline, the wifi driver would cause all kinds of headaches - and it was a fluke we found it. Might be worth a try if everything else comes up short.

Why on earth should that prevent saving (or recovering) only the project-specific ProChannel EQ settings?

jpetersen
Why on earth should that prevent saving (or recovering) only the project-specific ProChannel EQ settings?

There may be things going on in a functional area that has nothing to do with ProChannel EQ (or even in a process outside of Sonar completely) that only manifests itself to you there, no doubt caused by a wildly implausible chain of interactions.
 
Since in this case it seems that many other folks have not seen your specific problem and the fix provided by a Cakewalk associate has apparently not helped, and given that you are experiencing a number of issues in a product that most would agree was the most stable of the pre-Platinum X series releases, I would suspect a system issue of some kind.
 
In that spirit I would check the Windows Event Log for any curious failures or messages. Failing that, disable any devices/device drivers like internal audio or even Wi-Fi (as has been suggested) to eliminate them as sources of trouble. Whatever you do, do one thing at a time, preferably with a reboot in between steps, and evaluate the outcome.
 
I wish you good luck!
 
PS:
By the way, one thing that would really help is to make a short screen-capture video of you demonstrating the issue from a new project. Unlikely as it may seem, there may be some procedural issue in play here that will become obvious to those more experienced with the X series when seen in a video.

Thanks for the responses. The problem with any sort of "turn this plug off" diagnostics is that it seems almost random in timing. I'll open a project every day for a week and work on it, then one day it sounds rough so I look at the eq and it's flatlined. I can turn off a plug and when all is fine the next day, it doesn't tell me much because it might be 2 weeks before the eq zeros out. It's hit many projects but I don't think all of them.
 
According to Dean Capper above, I don't have the correct .dll for Prochannel. Nor do I know how to get it: when I deleted mine and re-did the X3e update, I ended up with the same "wrong" .dll again. 

There's no ProChannel-specific dll in C:\Program Files\Cakewalk\SONAR X3 Producer, so we can ignore that.
 
OK, it's random - or, to be more precise, it is not clearly repeatable.
And it does not occur in all projects, but we cannot be sure of that because all might fail given time.
And when it fails, it always flatlines the ProChannel EQ on ALL tracks, not just some tracks.
 
I'm assuming you have thought what the ones that fail have in common.
There really has to be something that is causing it (sorry for stating the obvious).

Thanks for responding. 

jpetersen
There's no ProChannel-specific dll in C:\Program Files\Cakewalk\SONAR X3 Producer, so we can ignore that.
 
 

Do you happen to know what the .dll version is in X3e anything? Mine is  1.2.2.246, Dean Capper said it should be 1.2.2.323. I have no idea if that matters, it's all I have to go on at the moment. 
 

OK, it's random - or, to be more precise, it is not clearly repeatable.
And it does not occur in all projects, but we cannot be sure of that because all might fail given time.
And when it fails, it always flatlines the ProChannel EQ on ALL tracks, not just some tracks.
 
I'm assuming you have thought what the ones that fail have in common.

 
All that seems correct. All eq-gone to flat line. Nothing sticks out as common or uncommon, my projects are really, really similar. They are all audio (at this point), very few plugs, all shipped with Sonar. I use the Nomad Factory reverb (ouch) and few few others. Boost 11 on the master, which I'll take off before I export for mastering. 
 
I'm not sure how many projects are affected, it would be hard to tell at this point. 
 
I eq-ed one this morning. Just opened it: EQ is flat. It's insane. It's unusable. 
 

jpetersen
There's no ProChannel-specific dll in C:\Program Files\Cakewalk\SONAR X3 Producer, so we can ignore that.

It was Dean Capper from Cakewalk who suggested that you might have the wrong dll, so I would suggest if it is still incorrect and you can't find the right one it is certainly worth following up with him.

tenfoot

jpetersen
There's no ProChannel-specific dll in C:\Program Files\Cakewalk\SONAR X3 Producer, so we can ignore that.

It was Dean Capper from Cakewalk who suggested that you might have the wrong dll, so I would suggest if it is still incorrect and you can't find the right one it is certainly worth following up with him.

Thanks, I plan to. I'll file a fancypants report and all. I'm trying to make sense out of it and I can't: the X3e update gave me a "new" .dll that's exactly the same as the old one. I'm at a loss as to how that can be. 
 
How bout this: Does anyone here use X3e? If so, could you do me a huge favor and check what version of the Prochannel .dll you have?? Thank you.