I just froze a synth in S2 and the frozen track literally is 200ms later than the unfrozen synth.
 
The synth was played in S2 but the track was ported from 8.5.  Nevertheless, this is not a cosmetic or a workflow issue.  It's a musical issue and it's not acceptable to me.
 
I've frozen other synths and didn't have this problem.  So it's an intermittent problem, the worst kind.
 
I'll come back with the first major revision and check it out.  CW sure has it's work cut out for it!  There's a lot of great things about this software.
 
Ian
 

'Just tried the same with a project ported from S 7 and it froze in time and in place, with no problems.  Just for balance.  I don't know how long you've been with X2, but you really should give it some time to grow on you.  I felt the same way you did for a while, then I really kind of got used to X1 and now with X2, I don't even feel comfortable in previous versions of Sonar anymore.

It's not perfect.  It crashes on me with no chance of recovery sometimes.  I'm learning to Save a lot.  But it's so far beyond S 8.x.  Give it a chance.

Thanks MB - Yeah I've frozen a number of synths w/o problems in S2 but I tried a couple of times with the faulty track and it keeps freezing this particuar track about 200ms too late.

As a keyboard player who reads, I REALLY like the improved staff view in S2.  It makes really usable renderings and printouts.  It makes 8.5's rudimentary staff view look childish.

I do intend to come back to S2, but I've come up against so many problems, that I'm going to wait for the revision to give it another thorough trial.

Peace,

Ian

Same here, what's your system spec, X2 (and X1) outperformed 8.5 for me hands down...

There's certainly a learning curve, as the whole UI was redesigned since 8.5.3, but maybe if we can get your frozen track problem fixed you could continue to work in X2?

This may be a silly thing, but does it change anything if you were to copy the track content and paste it into a new track?  Maybe something in the import from the prior release might work differently internally this way.

Bob Bone

MM - the audio engine is much better in S2, I agree. That's not the issue for me though. I just figure that w/ R1 a lot of the stuff I'm encountering will be ironed out. I've found a way to work around everything so far, but that's just it, I'm tired of working around stuff.
 
Bob - Thanks. I bet that might work. I've had 8.5 files become corrupted before and this technique has saved a couple of tracks. I've just decided to get off the learning and workaround curves for awhile. However, the track freezing 200ms late is a new one for me.
 
Peace,
 
Ian

Good luck with it - and try not to give up on X2 just yet.

It seems like many things have popped up, but most of what has done so has been addressed or worked around.

It's such a nice release in so many ways - just hang in there, refill that coffee (can't help you if you are a tea drinker - hee hee), and maybe between all of us - Bakers included, we can get most things working.

Bob Bone

Ian what synth was it? Are you using SONAR 64 or 32 bit? If in 64 bit mode was the synth a 32 bit pug-in wrapped with bit bridge or jbridge? I'm asking because you may have to tweak your "BounceBufSizeMsec" setting in X2. I had a similar issue with X1 when freezing and bouncing 32 bit soft synths in SONAR 64 bit due to the default size of the buffer, when I lowered the value the problem went away.

I just froze a synth in S2

What's S2? 

daveny5

I just froze a synth in S2

What's S2? 

my wildest guess would be.... sonar x2?