CakeAlexS
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

vintagevibe
My system is freshly built with all latest drivers.  I have a degree in programming and spent 8 years doing tech support for Hewlett Packard so I'm not speaking from an uninformed perspective when I say it is most likely that this is a Sonar issue.  M steps to reproduce are to just use Sonar.  I'm am just too busy to deal with it and I've not had good experiences with cakewalk support.   The good new is I'm busy.

Congratulations, like it or not you have chosen option 3.
End of thread then. We can all get on with our life ... (I'm busy as well).
(BTW were you expecting all of us to solve it for you because you thought that we were all less busy than you? Or were you just not interested in resolving this... in which case why bother posting).


Cheers....

To me it sounds like a video adapter or video driver problem. I had all kinds of similar weirdness with my ancient cheapo Nvidia card before I upgraded. VV did you name your video card somewhere in the thread?

CakeAlexS
End of thread then.

Not quite. We still don't know how often this happens. If it's not frequent, and one of the workarounds does the job (like typing "I" twice, which seems pretty painless), then it's the end of the thread unless other people can chime in and confirm that this is indeed an issue for more than just a handful of people.

Hi Craig,

Well we haven't seen any complaints since X3E about this. The OP hasn't gone into any detail about this issue, even if somebody says they have the exact same symptoms it would be pure speculation to say that this would be the same issue as the OP as we can't compare without any detail....  and the next poster would have to post steps to repro anyway.... So really the thread is pointless waste of time at least so far.
 
Right now I'm speculating the issue was system specific (graphics card, mouse drivers etc).... and anybody who says any different needs to help by provide evidence to the contrary (of course we are all happy to help in this scenario).
 
The OP says he's a software developer so he should know the score...
 
Cheers...

CakeAlexS
The OP [...] the OP [...The OP says] 

Don't wanna start a fight, but vintagevibe is a veteran poster here, so let's cut him some slack right?
 
Sven

Sorry this is the internet, "OP" is not a derogatory term. Nothing that I've quoted here is untrue or designed to be an attack, rather frustration at my end that we've wasted so much time on this thread and got nowhere. We are on post 46 now and still none the wiser of the exact issue. We are all repeating the same advice and have had no real feedback so I bow out of this now.
 
Cheers..

SvenArne

CakeAlexS
The OP [...] the OP [...The OP says] 

Don't wanna start a fight, but vintagevibe is a veteran poster here, so let's cut him some slack right?
 
Sven

I agree; that's why I researched workarounds, and tried to find other people who experienced the same problem. But I could find only one, and there was no follow-up from him, so at this point if VV can't post a bug report or as an option provide me with at least something about the nature of the problem along with specs that include the video card, whether he's using a high-res mouse, etc. (who knows? maybe there's a known issue), I've run out of ways to help. Hopefully one of the workarounds will do the job.
 
I do think the thread title was off the mark, though. I don't think Cakewalk even knows that some people are still experiencing problems unless either someone there wades through this thread, someone files a bug report, or I tell them (which I will if I can provide them any kind of clues).

CakeAlexS
 "OP" is not a derogatory term.

 
Of course not, "The OP" is something I've no problem of being called as a noob on some forum.
 
However, I wouldn't refer to you or Beepster or Bapu or whoever as "The OP" in your own threads. I'd call you by your screen name or your real name if you'd made it official. 
 
It's the sort of thing that makes this place a community. 

Anderton
I do think the thread title was way off the mark, though. 

I do agree since "we" implies the issue is widespread...

CakeAlexS
 "OP" is not a derogatory term.

 

SvenArne 
Of course not, "The OP" is something I've no problem of being called as a noob on some forum.
 
However, I wouldn't refer to you or Beepster or Bapu or whoever as "The OP" in your own threads. I'd call you by your screen name or your real name if you'd made it official. 
 
It's the sort of thing that makes this place a community. 

Sorry but there is nothing offensive implied by saying the word "OP" referring to "Original Poster" or "Opening Poster". It's a perfectly polite term on the internet and if I wish to use it from time to time I will, sometimes we take shortcuts down to lack of time. Also it can keep threads clear because sometimes threads get so long readers lose track of the original topic and who the original poster was. It's perfectly valid and if I created a thread and was referred to this way I would not be offended.... Thanks....