stxx
What is the disadvantage of disabling the 64 DP?

Rather than rehash the discussion from about this time 2 years ago when toggling the 64bit DPE was the temporary solution to different issue, I would suggest running tests to determine if there is an audible difference.

Hi Allen,
 
Basically 64 bit DP allows the synth and other plugins that support this to pass through full 64 bit audio. There are some headroom benefits to this setting, however fidelity and quality should not be that different. You would get more fidelity benefit from using the Upsample on Playback or Upsample on Render options on the plugin UI (top LH corner windows menu). 

 
The short answer is that 64-bit DP is analogous to entering all values to the penny in your tax return and not rounding to dollars until you've calculated the final sum vs. rounding each value to the dollar when you enter it, and adding the rounded values.
 
With the higher resolution, $100.51+100.51 becomes $201. Without it, you get $202. 64-bit DP gives a more accurate sum when adding a bunch of 32-bit sample values and then fitting the result back into a 32-bit range.
 
It's questionable how audible this is in the real world, but mathematically it's more precise; a penny saved is a penny earned. 

So in the end the question is....   Will there be a fix for the CSS issue?  For now when I use it I can uncheck 64 DP, use the nice new feature of recording the synth diectly to audio to track and then disable or remove the CSS  and then going back to 64 DP.
 

Well I replaced my csc with Rapture session and a new dynamic to my song...:( 

stxx
So in the end the question is....   Will there be a fix for the CSS issue?  For now when I use it I can uncheck 64 DP, use the nice new feature of recording the synth diectly to audio to track and then disable or remove the CSS  and then going back to 64 DP.
 

Sorry for the inconvenience. Yes we have a fix for this issue that is currently being regression tested. We will release an update very soon. Some other synths like sylent also exhibit this issue so its not specific to CSS. In fact the problem is not directly synth specific at all.
 
The reason it was not noticed is that it depends on the double precision setting as well as the synths ability to support double precision. We test a lot of combinations of scenarios but its impossible to test every synth with every permutation of project states. If we did that it would take months for even the most trivial of features to be released. 
Anyway a fix is on the way...