chuckebaby

Taurean Mixing
 

Keith Albright [Cakewalk]
Need clarification on this.  We would not have shipped with something fundamentally broken like that so it's not a general issue across all configurations.
 
Track selection is working here as is making strips active, all from the Track View.
 
You can make strips active by clicking the name control or the icon (if not a synth) or empty space on the track.

 
Keith does this video clear it up?
https://www.dropbox.com/s...9mfw/Untitled.avi?dl=0

cant seem to open this link
Im getting an error: Error (4xx)

Thanks Chuck, not sure why the link truncated like that. It should be good now, I edited the post.
And this should be the link https://www.dropbox.com/s...ntitled.avi?dl=0 

Taurean Mixing
 

Keith Albright [Cakewalk]
Need clarification on this.  We would not have shipped with something fundamentally broken like that so it's not a general issue across all configurations.
 
Track selection is working here as is making strips active, all from the Track View.
 
You can make strips active by clicking the name control or the icon (if not a synth) or empty space on the track.

 
Keith does this video clear it up?
https://www.dropbox.com/s...9mfw/Untitled.avi?dl=0
 
As you see, and as I mentioned before, with the tracks collapsed, they are not selectable by clicking the number area. When you open or expand the track then normal behavior resumes. Although you can see group selecting is possible dragging across several tracks even if they are collapsed. But yea, something is off here after the April update. 

Please report what running this util from the cmd prompt shows:
http://www.nirsoft.net/utils/dump_edid.html
 
Thanks.

Bob, I sent ya a PM with a 2nd util as the nirsoft one said your display is 7 inch diagonal (16 x 9 cm) which doesn't sound right.  I want to validate that the data is really what that's reporting.  If that data is wrong that would explain the behavior you are running into.  Is that your only display?  If not then you could try using the other one as the primary monitor.
 
Keith

Keith Albright [Cakewalk]
Bob, I sent ya a PM with a 2nd util as the nirsoft one said your display is 7 inch diagonal (16 x 9 cm) which doesn't sound right.  I want to validate that the data is really what that's reporting.  If that data is wrong that would explain the behavior you are running into.  Is that your only display?  If not then you could try using the other one as the primary monitor.
 
Keith

Ah that could explain it then. I have two displays. The main one is 42" and the secondary 21" so yea no 7" lol
But why all of the sudden is this an issue, I suppose that confused some users including myself. April and before releases didn't bring this on but anything after does. Ok thanks Keith, checking PMs now. 

Taurean Mixing

Keith Albright [Cakewalk]
Bob, I sent ya a PM with a 2nd util as the nirsoft one said your display is 7 inch diagonal (16 x 9 cm) which doesn't sound right.  I want to validate that the data is really what that's reporting.  If that data is wrong that would explain the behavior you are running into.  Is that your only display?  If not then you could try using the other one as the primary monitor.
 
Keith

Ah that could explain it then. I have two displays. The main one is 42" and the secondary 21" so yea no 7" lol
But why all of the sudden is this an issue, I suppose that confused some users including myself. April and before releases didn't bring this on but anything after does. Ok thanks Keith, checking PMs now. 

We were making improvements to general hit testing around various areas to make it easier to hit stuff based on DPI, in particular for various laptops/convertibles, etc. that have high pixel densities.  
 
However, unknown to us at the time, nothing like standards to be ignored, were these other devices misreporting their size.  Those wrong sizes are resulting in some strange calculations and these issues.  Most desktop or laptop users aren't running into these.  But for these other connected displays, it seems the standard isn't correctly implemented.  Once we get enough data about how the calcs are failing, we can try and work around the issue while still keeping the benefit.
 
Thanks.
 
 

Keith Albright [Cakewalk]

Taurean Mixing

Keith Albright [Cakewalk]
Bob, I sent ya a PM with a 2nd util as the nirsoft one said your display is 7 inch diagonal (16 x 9 cm) which doesn't sound right.  I want to validate that the data is really what that's reporting.  If that data is wrong that would explain the behavior you are running into.  Is that your only display?  If not then you could try using the other one as the primary monitor.
 
Keith

Ah that could explain it then. I have two displays. The main one is 42" and the secondary 21" so yea no 7" lol
But why all of the sudden is this an issue, I suppose that confused some users including myself. April and before releases didn't bring this on but anything after does. Ok thanks Keith, checking PMs now. 

We were making improvements to general hit testing around various areas to make it easier to hit stuff based on DPI, in particular for various laptops/convertibles, etc. that have high pixel densities.  
 
However, unknown to us at the time, nothing like standards to be ignored, were these other devices misreporting their size.  Those wrong sizes are resulting in some strange calculations and these issues.  Most desktop or laptop users aren't running into these.  But for these other connected displays, it seems the standard isn't correctly implemented.  Once we get enough data about how the calcs are failing, we can try and work around the issue while still keeping the benefit.
 
Thanks.
 
 

Could it by chance relate to TV's being used as computer monitors? In addition, not using VGA ports but DVI and HDMI?

Yea this pointer issue is odd.  I hadn't updated for awhile and everything was going smoothly until I upgraded my monitor to a 4K one.  As soon as I started Sonar I lost most of my control bar functions.  The hotkeys work but I cant actually PRESS the buttons.  They don't do anything.  Kind of annoying when you are used to pressing them.  Just tried the new update......still an issue. 

Taurean Mixing
 
Could it by chance relate to TV's being used as computer monitors? In addition, not using VGA ports but DVI and HDMI?

 If it helps support this idea Im using a 32" Samsung LCD TV for monitor with HDMI, but 2017.06 resolved most except the individual track/clip selection issue, (which was not the same behaviour/offset as it was in 2017.05 version). But Ill try it out using VGA next time I try re- update.
 
cheers    

Taurean Mixing
 
Could it by chance relate to TV's being used as computer monitors? In addition, not using VGA ports but DVI and HDMI?

"If it helps support this idea Im using a 32" Samsung LCD TV for monitor with HDMI"
 
OK so if it helps, this seems to support your idea. I tried out 2017.06 using only my LG 24" computer monitor, through DVI connections on both card and monitor  (GTX 960 doesn't have an actual VGA type connector, to try on Samsung 32"). and I dont have this issue, i.e. pointer functions normally selecting in track number box to highlight track clips. If Im using both, Samsung 32" (HDMI) and LG 24" (DVI) as an extended second monitor, the pointer issue exists in both monitors, i.e., if I move Sonar to display only in LG 24", the pointer issue persists.
 
Cheers 

Win 7 only understands system DPI so I believe the primary monitor sets the DPI for both which would explain why you have the issue on both.
 
The root cause of the problem is incorrect EDID data in the VESA standard of what the TV has stored in EEPROM.  However, while you could get the TV possibly flashed to update it's EEPROM (some hackers have managed that).  A much easier approach is to utilize an override inf that Microsoft has made provision for.  It will override the incorrect data with corrected data.  I'd advise anyone with this issue to pursue that approach or ensure the TV isn't the primary.
 
Here's some links about the issue:
https://www.google.com/search?q=edid+data+from+tv+incorrect&rlz=1C1CHBF_enUS723US729&oq=edid+data+from+tv+incorrect&aqs=chrome..69i57.8883j0j7&sourceid=chrome&ie=UTF-8
 
https://docs.microsoft.com/en-us/windows-hardware/drivers/display/overriding-monitor-edids