Number pad +- keys in track view instigates system volume CWBRN-32083

sThe plus and minus keys on the number pad (not the qwerty keyboard at the ends of the row of numbers) causes Windows 8 system volume box to appear, even when a function in the track view has be put in focus.

 
This does not happen in Console or Pro channel View. These key do not effect any other programs outside Sonar, such as other DAW, internet browsers or Desktop. So is just an issue within Sonar's Track View
 
Re-creatable by myself and FidelityMusic on
Windows 8.1
Desktop and laptop
Laptop, wired and wireless keyboard
Windows 8.1
 
http://forum.cakewalk.com...-m3188536.aspx#3191758

Could you post a CWBRN number please?
https://www.cakewalk.com/Support/Contact/Problem-Report
 
Thanks..

I'd be interested to see if you get a CWBRN from an email, we shall see, it's generally best to use problem reporter for this. We definately need one. Recommended course of action for next time (on validated issues) is use problem reporter and quote any CWBRN number in any support emails.

Anyway fingers crossed.

Thanks.

Just doing that now Joey. Thought we got the CWMBRN number from emailing you. Didn't realize it was a separate process.
 
See mine and FM signatures for Soundcard details. we are both on Windows 8. I'm running Asio

Do not see this in Windows 7 64

Joey Adams [Cakewalk]
Kamikaze,
I've closed your CWBRN because this was determined not to be a bug. I am running this by development to see if there is some setting that might need adjusting. 

Yeah I noticed in the call. I would have preferred a little more dialogue before development came to this conclusion. It's not that it only happens in Sonar, but it only happens in a particular page in sonar that to me has Bug written all over it.

Well some can repro and some can't.

As this has been determined not to be bug by cakewalk themselves you should contact their support in order to get it resolved I suggest.

Please move this to Sonar forums..Sorry I can't see how it can progress any further in these forums right now...

I agree with Kamikaze. Jumping to a conclusion like you are right now is the same reason why my other bug that I had for months isn't fixed, because someone told me it was fixed, closed the CWBRN, and said if I upgrade I'll get the bug fix, here I am still waiting.
 
This has been tested in multiple programs in general (regular and Windows 8 specific), multiple DAW's (Pro Tools, FL Studio), by multiple users, on top of that like Kamikaze pointed out it is only present in the Track View. This is a Sonar issue, this is most definitely a bug by definition and based off of my experience with Cakewalk staff just because they initially say something doesn't mean they're right, so leave this here until this issue is rectified.

But before gaining more info, they closed. And as I stated, they have just asked if it in one view, even though I made that really clear. This was Support asking.
 
It is reproducible, both FM and me are able reproduce it. 
 
Why the rush to clear it out? What's your vested interest. This effects FM and me, so we have a vested interest. With a thread already in the Sonar forum, I see no benefit to me in moving this.
 
Just wait a bit, it's doing no harm.
 
MODs please do not move this without contacting me first?

Why do you care?

Kamikaze
Why do you care?

It's got nothing to do with how I feel. It's the forum handbook and procedure. I suspect one way or another you will still get a resolution. Thankyou.

..and everything to do with cakewalk closing the issue..

I have been in communication with Kamikaze via support emails. This is not a bug because it is not reproducible. We are trying to work with Kamikaze and any others who are experiencing this to come to a conclusion as to what is the specific recipe that is causing this to happen. For example: "It happens only in track view" is not specific enough to determine the recipe. Track view embodies loads of controls and there are several variables created by the user that can change the way it behaves. Please bear with us while we figure this out. 

Joey Adams [Cakewalk]
I have been in communication with Kamikaze via support emails. This is not a bug because it is not reproducible. We are trying to work with Kamikaze and any others who are experiencing this to come to a conclusion as to what is the specific recipe that is causing this to happen. For example: "It happens only in track view" is not specific enough to determine the recipe. Track view embodies loads of controls and there are several variables created by the user that can change the way it behaves. Please bear with us while we figure this out. 

Your question was
"Also, you said in the forum that this only happens in a particular page in SONAR. By that, do you just mean the Track View?"
 
It's the title of the thread and expanded in original post with the statement
"This does not happen in Console or Pro channel View. These key do not effect any other programs outside Sonar, such as other DAW, internet browsers or Desktop. So is just an issue within Sonar's Track View"
 
It is reproducaable, 2 users, one with a laptop and one with a desktop are reproducing it. The one with the Desktop is has tried a wired and wireless keyboard
 
Again from the original post
"Re-creatable by myself and FidelityMusic on
Windows 8.1
Desktop and laptop
Laptop, wired and wireless keyboard
Windows 8.1"
 
This was an attempt at creating a workaround to the fact Sonar does not work in Windows recommended display setting, but is proving to be just as much of a headache

Further info sent to Joey
 
Some further checks to find a behaviour pattern.
 
Console View, Track Inspector (and Prochannel view in both of those), Piano View, Staff View, Matrix View and Media Browser, do not cause the System Volume Control to appear, when either clicking a function or dead space
 
Track View as we know does, when either clicking dead space or a function
 
Which just leaves the Control Bar
 
In the Control Bar, I get mixed results
To save repeating explanations, I am going to refer to an action that causes the instigation of the system volume as Volume Prompting. Clicking on a unaffected view, (listed before) removes Volume Prompting Clicking on Track view, in either dead space or a function, causes Volume Prompting .
 
Starting with Volume Prompting off, clicking on the empty space of the control bar and in the dead space of a module in the control bar, or on a function in a module does not cause Volume Prompting. However, If a click anywhere in the track view, then click in the Control panel in any of thse 3 options, then Volume Prompting remains activated from having clicked in the track view. Where as in other views Volume Prompting  is turned off. So the Control Panel will go with the flow, if Volume Prompting  in on, it stays on, but if it is off, it stays off.
 
Now here's another little oddity. Before it seems that only the track view causes Volume Prompting, but it appears that collapsed Control Panel modules cause Volume Prompting  too.
 
I tried docking at the top and bottom, still the same.
 
So I tried floating the control panel. And to make sure that floating it over the track view was having the track view causing the issues, I floated it over the console view. When Floating, anywhere in the Control Panel causes Volume Prompting , be it Open or Collapsed Modules
 
So to summarise;

Volume Prompting seems to either be turned on or off by various views
Console View, Track Inspector, Prochannel,, Piano View, Staff View, Matrix View and Media Browser turn off Volume Prompting, and then the plus and minus number pad keys behave as expected.
Clinking in the Track View causes Volume Prompting, then the plus and minus numberpad keys causes the system volume box to appear and move accordingly.
The Control Panel does not turn off or on Volume Prompting, except when it is floated where it turns Volume Prompting on.
Collapsed modules in  the control panel turn on Volume Prompting, whether the panel is floated or not.
 
Maybe this info triggers some ideas?