Going back to 8.5 for now

'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.

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

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

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.

daveny5

I just froze a synth in S2

What's S2? 

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

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

So why doesn't he call it X2? I think everyone here knows X2 means Sonar X2. S2 sounds more like Sonar 2.

"S2" is more symmetrical than "X2"

Ian,

I've had a couple of issues with importing projects from older versions of SONAR where one of the soft synth tracks has weirdness with timing or latency.  I've found in all cases that either going into the soft synth instance and disabling then reenabling any effects or turning off (not freezing) then turning on the synth cleared everything up. I think it has something to do with the "read ahead" aspect of the effect (especially 32 bit - bitbridged effects) that messes things up and they just need to be reset.  

This is just my experience, but it might give you some clues to help clear up your issues when importing older projects.

Also, there was mention in another thread about a button in the control bar at top (in the same grouping with "turn on/off all FX... hey, you might try this as well) that I can't remember the label of (I'm not in front of my DAW), but it eliminated that "read ahead" of some bothersome effects.  That has worked for me as well. Just clicking it on then off cleared up a latency problem that was occuring.

Best,
Rob

"S2" is more symmetrical than "X2"

No its not. Actually its less. 

emwhy


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.

Thanks so much guys for all the responses.
 
emwhy - it was taking a long time to bounce or submix and I set "BounceBufSizeMsec" to 100 to remedy that.  I think the default value was 1 - which has it's own problems.  (IE get a cup of coffee while it bounces) It kind of looks like there's no real good solution?
 
You're correct that I was using a 32 bit plug in a 64 bit environment.  Seems like something CW should be able to fix.
 
Rob - The track this happened in was started in S8.5 but the synth was recorded in X2.  What you're describing about reenabling the effects is along the lines of cutting the midi track and pasting to a new instance of the synth.  Yeah, it might fix the problem.  But at best, it's a workaround.  At less best, it's inelegant and somthing that'll probably get addressed by CW in the revision.
 
I really like X2 guys.  I actually came back to it today to use the staff view.  But I'm still going to more-or-less wait till the revision to fully commit.  X2 has a lot of imperfections!
 
Peace,
 
Ian
 

Ian Ferrin


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

Interesting,
 
Can you compare and contrast the SV in 8.5.2 with X2? 
 
What improvments have been made in X2 which make SV in 8.5.2 look rudimentary and childish?
 
I only have X1, but my impression is that the SV in X1 has less functionality than 8.5.