X2a Track view fader issue

Can't use X2a. In track view the fader is like in a "jammed" state. While I am trying to move it, it doesn't move. Then when I release the mouse click, it shoots up to +18db.  I can move the fader just fine in the inspector pane. 

Sonar seems less snappy now too overall compared to without this recent update patch. 


i7 920, 16G Ram Win 7 64 Sonar 64

I also just noticed that once the little white brackets are around the parameter, the mouse wheel will adjust it.  So it's, gotta be a setting involving the mouse or a bug involving touch screens.

Sounds like offset mode, keyboard shortcut is the letter O. If the volume and pan in the track view have plus signs next to them, you are in offset mode.

So, what do we do in the meantime, twiddle our thumbs? 

TM, maybe you and Haddox can compare setups (including mouse type, any control surfaces, etc.) and what's on your tracks. If it's happening to both of you, I would think there's got to be something in common.

Here are all the details: I had X2 working "fine" - by that, I mean with the known bugs that were pending the X2a fix - with certainly no
fundamental issue like this mouse issue. I downloaded the update, ran it, and discovered this issue suddenly. No new hardware OR software other than the Sonar X2a has been added. Further, I checked it on a brand new project i.e. with no tracks, no plugins, in a word: clean. The issue persists. My system, as you can see is not old and considering all pretenses here, it must be a compatibility that CW did not thoroughly check over testing X2a. 

And just to be thorough, my system:

Gigabyte EX58-UD4P Intel X58. 
12Gb of Kingston HyperX DDR3/1600 Mhz Triple Ch. RAM. 
Intel i7 920 2.66GHz LGA1366 
Win 7 64 SP1 with the latest BIOS
Sonar 64 
Standard PS2 mouse/keyboard

It is a Microsoft Intellimouse Opitcal PS2

StepD


I thought I had an Intellimouse laying around somewhere, but I guess not. At least now someone else that has one can tell you it's working fine for them and you can eliminate that as the source. Did you try hooking it up to a PS2 port if you have one instead of USB?

You mean the other way around, it is PS2 right now. I just tested a USB mouse and same story. 

I ruled out the mouse as the problem as it works fine in all other apps and functions well in the prochannel pane.  I do have some trouble changing the ratio on the u-type compressor.

I don't believe that it's a setting because if it was, the setting would be pointless imho.

It isnt anything to do with envelopes as the mouse wheel moves these faders at .5 intervals without issue.

The mouse also works fine on the console view.  Adjusting the volume with the console is the obvious work around.  Using the mouse wheel will do as well.  

When I opened another project I had full functionality over these panes.  As I did before the x2a upgrade.  I haven't tested the "saving it in X2a brings on the issue" yet but, will.  It might help CW in the bug hunt.  I am pretty confident that it has to do with the code in these track panes that doesnt translate to Windows 7.  Or at least, the version I'm using.  We need a few more users to share the problem to figure it out.  I use the faders a lot and hope that the issue isnt ignored based on the few users with the issue.

Was all set to install X2 in place of X1 until I keep reading more stuff like this. How much more do we pay for the STABLE version? lol!

I reported this. Ugh, down time.

Works ok in my X2a as well.

However, X2 and X2a have screwed up my mouse, I mean really screwed it up, on two occasions now.  Once I could no longer use the mouse at all, after it started being erratic.  The second time when it started acting up I exited X2a and the mouse was back to normal when I reentered the program.

I've never had a program mess with the mouse.

Ok.  I reported it too.  And I asked for a patch that fixes the x2 bugs without the Windows 8 stuff.
I'm finding some mousing issues in other panes but, not consistent. Reboots seem to clear up some and create others.

I think it is worth pointing out that almost all issues with computers, in fact life, too, are due to a combination of factors, not a single factor.

I do not have a problem with the mouse dragging the track view fader, just like several others who have indicated the same. I am also running X2a on Win 7 64bit.

So it is not logical to blame the issue on X2a all by itself. There must be one or more as yet unidentified factors that are combining with X2a on your system to cause the issue. If you can work with the others having the same issue to discover more common denominators, you might be able to give Cakewalk information that would help them diagnose the issue more quickly.

As it stands now, they don't have much to go on, since for some users, perhaps the majority, there is no such issue with X2a on Win 7 64 bit.

As I sit in continuous contemplation over this matter, it seems like a straight forward trouble shooting flow chart would solve the issue rather quickly.

Is the pointer code in track panes the same as it is in console view?

If not,  what's different?

The idea that this isn't an issue for everyone doesn't positively relieve cakewalk of a code problem.  The track pane code for x2a is different than it was before and it is different than the other screens.  

I will buy a new mouse later today.  Keep the reciept.  I will also cycle through usb ports and perhaps reload the mouse drivers.

I will also try anything anyone here suggest.

Anyone?