I reported this. Ugh, down time.

tracks

Transcending Music


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. 

fader in track pane works as expected, running win 7 64 bit

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.

There must be something going on here related to touchscreen and mouse functionality. 

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.

Cool, thanks for reporting Haddox

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.

Indeed.  I am very much aware of the multiple, potential factors involved.  I could, perhaps, appease you by correctly stating that the combination of my system and x2 did not have this issue yet, the combination of my system and x2a does.  I am also aware that not only is the information going to cakewalk thin, at best, but, given the response from them so far will not be helpful in solving the issue.  With every one else's system working well, there will be two of using the work arounds.  

Thanks for the input.  I think it's helpful to keep this thread on the top list.

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?

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?