Noel Borthwick [Cakewalk]
The button will be grayed out if the synth is a Transformer - patched inside a track effects bin instead of the synth rack. In that case you can't independently freeze the synth.

Hi, Noel. That was not the case in this project. All synths in the project were inserted normally (and IIRC I inserted them directly into the Browser Synth Rack). None were inserted into FX Racks/Bins.
 
Not sure what was up and I haven't been doing much synth stuff so haven't seen it again. The mute toggle trick fixed it so no biggie but still a little odd.
 
Sorry I don't have a recipe for you to replicate.
 
Cheers.

Toggling the mute butto has worked for me in the past.  I cannot give steps to reproduce, but it does seem to happen to SITs that have been frozen and then unfrozen.

Are you using EZDrummer 2?

Let me know when you all think this thread should be moved to the Problem Reports forum and I will do it.

I was not using EZD2.  I had 3 synths in the synth rack, AD2, CW SC (rapture patch), and Zebra.  All were added using the + add synth in the rack.  I had done a solo on an audio track which may be factor.  I'm unable to test to see if this was a factor at this time.  I did a save previous to the issue and then did some after tracking cleanup.  Prepping for mix phase.  Did a freeze of the CW SC syth and pop.

Hi, Konradh... no EZD2 on my project either.
 
The synths in my project are Cakewalk products or came with Sonar (AD2).
 
SI Bass, DimPro (these are the ones that had the greyd out freeze... but not all instances)
 
SI Strings, AD2, Z3TA+ 2 (no problems with these)
 
Cheers.
 
 

John
Let me know when you all think this thread should be moved to the Problem Reports forum and I will do it.

Your call, bud. However there isn't really a recipe and it could be intended behavior. I'm really not sure about this one. It seems "confirmed" but not in the usual defined by reproduceable steps procedure.
 
Noel seems to have seen this thread so may still be watching and already exploring/noodling away at the code.
 
I think perhaps the best bet would be if whomever handles the notifications to the Beta testers put this on their "Yo, keep an eye out for this issue" list so the project conditions can be figured out.
 
Of course not being a Beta tester I have no idea how that all works but I get the impression there is a rolling list of things to test, observe and report. I think this would probably be an "observe" type of situation.
 
Now that I know the "fix" it's of course no problem but that would have been almost impossible to figure out without the input here (which seems to have been a fluke discovery as it is... gotta love the hivemind, lol).
 
Meh... I have no idea what should happen with this thread so I'm just gonna sniff my own farts and let the adults handle it.
 
Cheers.

I have been watching this thread Beep in case I can help or do anything. At present I see no reason to move it. That could change at any time. Don't worry about it. 

@beeps - had you frozen and unfrozen the tracks that displayed this issue?

jb101
@beeps - had you frozen and unfrozen the tracks that displayed this issue?

Hi, jb.
 
Nope. I rarely Freeze anything. I was just attempting the synth Freezing because this was/is a particularly huge project so I wanted free up some resources before getting ultra crazy with some heavier duty FX on the final mix phase.
 
Cheers.