???

 I'm guessing you mean "now time". I don't experience any "now time" bug with X3E.
 
Without knowing exactly what version of Sonar you are on, or what exactly this issue is (steps to repro), or Cake's current plans in terms of whether there will be an X3F which may or may not fix this apparent bug, well my answer is ... ??? right now :)
 
Please enlighten us.
 
Cheers...

I rarely see this complaint anymore so yeah... are you on X3(e) yet VV? I think I MAY have gotten it a couple times in X1 or X2 but I was more concerned with other nonsense (that has disappeared now) to notice it.

Beepster
I rarely see this complaint anymore so yeah... are you on X3(e) yet VV? I think I MAY have gotten it a couple times in X1 or X2 but I was more concerned with other nonsense (that has disappeared now) to notice it.

I'm on X3e and I still have it.

As most don't seem to be getting this issue with X3E, please give us specific steps to repro from a brand new project leaving nothing out so we can repro (I could repro with X3D but not X3E). Without exact steps it would be extremely unlikely your issue will ever be resolved. Thanks :)

CakeAlexS
As most don't seem to be getting this issue with X3E, please give us specific steps to repro from a brand new project leaving nothing out so we can repro (I could repro with X3D but not X3E). Without exact steps it would be extremely unlikely your issue will ever be resolved. Thanks :)

I make my living in music and I don't really have the luxury of stopping work to troubleshoot.  The bug has been there for a while and others have had it.  If I have to pay to get it fixed it will be just another reason to use Cubase more and avoid Sonar.  I just need to get some work done.

vintagevibe

CakeAlexS
As most don't seem to be getting this issue with X3E, please give us specific steps to repro from a brand new project leaving nothing out so we can repro (I could repro with X3D but not X3E). Without exact steps it would be extremely unlikely your issue will ever be resolved. Thanks :)

I make my living in music and I don't really have the luxury of stopping work to troubleshoot.  The bug has been there for a while and others have had it.  If I have to pay to get it fixed it will be just another reason to use Cubase more and avoid Sonar.  I just need to get some work done.

Right. But if it can't be repro'd by other users or the Bakers so it can be handed off to the developers to fix then it likely won't end up on the list of things to be fixed... especially if they are under the impression it HAS been fixed.
 
It's pretty late in the release cycle though. I don't really see them putting out another patch at this point. I would personally like to see the Baker adopt a policy of releasing one final patch for versions before moving on so people can linger on what they have if they are happy but that's not really good business sense in the world's current business philosophy. It would have been better to report this five months ago when they were cranking out patches like crazy. It might be a hardware specific thing that they could have dealt with. I'm assuming they are in full X4 mode right now.

Hey Vintage vibe...
 
I am no person of merit in techish tactics...or of any influences in, or for liking Bug fixing or hashing out either..\(newbee)...But if you take the time to express the problem fully...and You have this bug with said software, or any other...It could help others find or solve for it? , when the bug is reproducible (on certain systems of likeness)....To solve for it, with your help...Is all they are asking for...in gaining that info....and in making the software even better than X, Y <Z Stienberg>...Would be the outcome for all, If CW takes notice of the postings here?....They are around you known, from time to time!...So I know they do read these forums!.
 
Now that may be a little hard work, or so on your part?...But would it not be rewarding in the end, if it gets solved for? , to offer up a freebee on your part...To address this issue?...Just asking, and saying...If you do not address the issue correctly or dispose the info asked for by others, who do help so many people here , You will never solve the Problem, by posting here....And it will continue until someone does it....and Gives the details to reproduce, which could take time...
 
And it is over for you, and them, when you, or they do that, and it becomes, the technical tech base here who play a big roll in solving for X, and the Builders issue to look into....If you or they, cannot make this Producible state reoccur on others systems of likeness, and the techs here who do try to solve problems for CW, and PC Builds here, and then send them (CW) the bug issues/steps to gain/setup/system specs/devices and OS build... If they can reproduce, with your instructions this bug,... then to move it towards CW, if they cannot solve but agree with you there is a issue...Then How are you going to gain Bliss?..or make it be for others if this is a Bug ?....and I am not saying there is not a bug or bugs...nor am I saying there isn't or aren't any.
 
There is a support line for CW, and it is free to call?......You could call them...But, you would still have to give the info they will ask you for, and steps to reproduce the Bug...or bugs.
 
Just saying....and I wish you that Bliss!...and in every camp or forum I have been to...they all have Bugs of some kind!...WINK!
 
 
 
 

I've had since X2 and several other on this board have reported it since X2.  My understanding is that it has been reported.  I've had it through 2 video cards, hard drivse and Win 7 and Win 8.1.  Can't see a scenero where it would be hardware related anyway.

It was reported a while back and it has been fixed in X3E. Members of the community gave feedback that it was working in X3E for them. I would assume then this is deemed as fixed and is no longer regarded as a bug.
 
So you are left with three options:
 
1) Give us exact steps to repro in your scenario (see post #5) and we will try and reproduce at our end to confirm the issue.
2) Give Cakewalk a call and ask them if it is still a known issue in X3E that we don't know about here in the forums. Or maybe they can nail it down to a PC configuration issue.
3) Live with it.
 
Be aware that not even the mighty Cakewalk will not be able to fix a bug like this without full steps to repro from somewhere.

Cheers...
 
Alex