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

But what's the brand, model and driver version of your mouse? Maybe not related but you never know.

It is a Microsoft Intellimouse Opitcal PS2

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?

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. 

Yeah, definitely weird. I should probably just shut up anyway since I'm running Win8 and it might be some kind of Win7 problem.

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.

Yes, the wheel does work on the track fader, that I noticed too. I am just surprised more users haven't chimed in on this. 

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!

Keysman, don't install X2 in place of X1, install it alongside X1 until you know everything's working fine. It's running great here. Unfortunately, weird things pop up in software for some users. And that goes for all software. Just read "The Version 2.5 bugs thread" on the Studio One forum if you don't believe me.