Thanks for the video, I see what's happening. But I can't reproduce, and believe me, I've tried. What version of Z3TA+ 2 are you using? I'm testing with 2.2.3.43. 
 
My spidey sense tells me this isn't a SONAR issue but a Z3TA+ 2 issue. Try setting the Amp release control to MIDI Learn, have it learn something, then tell it to forget...maybe the parameter needs to be reset in some way. I really can't think of anything else since I can't reproduce...sorry.

Thanks for checking this out!  

Now you see I am not going nuts! lol
 
I am using Version 2.2.3 (not sure what is after the 2.2.3 - i am using the "About Page" to see this.)

I am unsure who's problem it is really.  I have had this issue with other softsynths as well.  It *MIGHT* have something to do with the way Sonar is freezing and unfreezing too.
 
Problem is, its not just the AMP Release...its many other parameters... some I can't even figure out. 
 
Ive had this probem so many times over the years, it is so frustrating honestly.   There are previous threads on the issue, none have ever come to a resolution.   

How can I move this thread to the Bakery?
 

No you're not crazy, but not being able to reproduce the problem means I don't have any more options. I also don't think Cakewalk will be able to do anything until they have something reproducible.
 
At this point probably the only way to get a resolution is to trim the project down to only the Z3TA+ 2 track, and see if the problem persists. If so, send the project to Cakewalk along with info on your OS and system. If it doesn't, then there's some kind of interaction going on, which really complicates troubleshooting. I guess at that point, CW would need the entire project to figure it out.
 
I don't think you can move a thread to the Bakery, it's a different platform. I was hoping the video would provide something that would give a hint on how to reproduce, but it seems like "what you see is what you get."
 
A thought - have you tested your RAM lately? I had a very similar problem with a Mac where calling up a file would have weirdnesses that I swear weren't there when I saved it. I tested the RAM and it checked out fine. But then a Mac-savvy person pointed out that the only correct way to test the RAM was from the Mac's command line interface. When I did, the test did indeed catch a bad RAM stick. After replacing it, the random weirdnesses disappeared.

Yea its really weird, I can't reproduce this in a brand new project!
I wonder if it is something to do with MIDI CC Data in other synth tracks.  
Let me ask... if I have MIDI CC#58 say controlling something in another synth written in its own PRV controller lane, could that effect MIDI CC#58 in this Z3TA+2 instance?   
Can MIDI CC# data from one track be controlling another?

I will check RAM, but I've had issues like this on different machines.  Plus I dont experience other weirdness, but you never know.
 
 
 

SilverBlueMedallion

gustabo
Why aren't you saving the patch before freezing?

 
because I didn't expect the product to be broken and change my synth sounds.

anyway, actually I do all the time and it is annoying!  How is that any sort of resolution?
 
It's time this gets FIXED.

It's a "cover your own @ss" resolution.
I've had this happen before, but rarely and infrequently.
Can't reproduce what you're experiencing so it's hard to fix what does appear to be broken without some regularity or accurate recipe.

I recently had a weird freezing issue with NI Pro Session Horns. I had initially froze it as it takes up an extraordinary amount of memory. On 16gbs of ram, I was up to 90%. So I froze and the next time I loaded the project, no sounds from it. I unfroze it and the re-froze it and it seems to be okay now...weird.

I know people hate when I suggest workarounds, but...
 
Couldn't you render the audio rather than freeze, then archive the synth track? More work, but it would eliminate freezing as a problem. 
 
And now I'm really grasping at straws, but what happens if you increase the latency? I had to bounce some Pro Tools stuff so I could create something suitable for SONAR, but had to increase latency to 1024 samples before it would bounce reliably.

Anderton
I know people hate when I suggest workarounds, but...
 
Couldn't you render the audio rather than freeze, then archive the synth track? More work, but it would eliminate freezing as a problem. 
 
And now I'm really grasping at straws, but what happens if you increase the latency? I had to bounce some Pro Tools stuff so I could create something suitable for SONAR, but had to increase latency to 1024 samples before it would bounce reliably.

 
Yes I could render the audio, however, I may not be done with it.   I can't commit my synth parts until ALL synth parts are recorded.   
 
I tried the latency test... didn't work.

a little something of interest here...
 
it has NOTHING to do with freezing the track!

I just saved my project, re-opened it, and that AMP-release and other parameters are the way they are as if I froze it!