musicman61554
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. 

Nothing was changed in that area.  If you are using a 4K display, you'll likely need to change the scaling in Windows to be able to get a workable size.  100% will be too tiny to see/click.   There should be a setting that's recommended, so start with those in display settings.

Keith Albright [Cakewalk]
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
 
 

Hi Keith, just to be clear, you had mentioned in the PM to me that from that Dump data I sent you, you were able to reproduce this issue. So will there be a fix for this?

Keith Albright [Cakewalk]
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.

Ok thanks, its a little over my head (the inf and registry stuff) but Ill mess around with the primary monitor order and see if that works for me. Likely be going to Win10 soon also, also hope to be going to touch monitor soon as my primary monitor. Will post what I find.
 
Cheers

Taurean Mixing

Keith Albright [Cakewalk]
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
 
 

Hi Keith, just to be clear, you had mentioned in the PM to me that from that Dump data I sent you, you were able to reproduce this issue. So will there be a fix for this?

Yes, we're going to try and find a work-around.  FWIW, my home TV reports it's 1 inch diagonal :P
16 mm x 9 mm.  
Clearly incorrect, and I had wondered why HDMI output to it wasn't quite right.  I had a similar experience with a touch monitor I used to use.  I had to use VGA out to it to get the picture lined up.  
 
K

JohnEgan

Keith Albright [Cakewalk]
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.

Ok thanks, its a little over my head (the inf and registry stuff) but Ill mess around with the primary monitor order and see if that works for me. Likely be going to Win10 soon also, also hope to be going to touch monitor soon as my primary monitor. Will post what I find.
 
Cheers

Right, I brought it up in order for you to look for an updated inf from the Manufacturer.  I have seen driver updates like that before that were just an .inf file that was installed.  So if you can find one to download for your hardware, it's easy to right click and choose install.  If that fixes it great.
 
Otherwise yeah if you had to create an inf to override values, that would be quite a chore even for me.  

Keith Albright [Cakewalk]
 

Right, I brought it up in order for you to look for an updated inf from the Manufacturer.  I have seen driver updates like that before that were just an .inf file that was installed.  So if you can find one to download for your hardware, it's easy to right click and choose install.  If that fixes it great.



K so I set LG computer monitor to primary monitor, and it resolves issue in Samsung TV monitor, exactly as you indicated, its just a bit awkward to work with this arrangement. So next Ill try to find an inf solution (so I dont have rearrange my desk, LOL).
 
Cheers 

JohnEgan

Keith Albright [Cakewalk]
 

Right, I brought it up in order for you to look for an updated inf from the Manufacturer.  I have seen driver updates like that before that were just an .inf file that was installed.  So if you can find one to download for your hardware, it's easy to right click and choose install.  If that fixes it great.
 
K so I set LG computer monitor to primary monitor, and it resolves issue in Samsung TV monitor, exactly as you indicated, its just a bit awkward to work with this arrangement. So next Ill try to find an inf solution (so I dont have rearrange my desk, LOL).
 
Cheers 

You could try using something like DisplayFusion to override how Windows determines which screen is primary and leave the hardware as is. It might allow Windows to see the LG as primary so the calculations are correct, yet still swap the screens virtually. I've done this in my setup and it works fine, though both of my screens are the same resolution, I wanted a particular display one one side versus the other.
 
Regards,
Dan

dcumpian
 
 
You could try using something like DisplayFusion to override how Windows determines which screen is primary and leave the hardware as is. 

Cool, Ill check it out, yea I have secondary monitor right, so mouse moves to right for secondary (and my computer, AI and other stuff are rack mounted on right, (so Id have to get a new longer DVI cable also to reach), also it would seem awkward to me having secondary on left.
Thanks Dan for DisplayFusion reference, and your time
Cheers 

Just an update, turns out TVs typically put aspect ratio in the bytes that we were expecting to refer to physical size.
So that explains it.  Linux has struggled with determining this as well, so I'm not alone :)
What I'm seeing is that we seem to get size data from computer displays but from TVs not so much.  We'l implement a fix for this to keep the benefit for the devices that need it without these crazy breaks for those of you using TVs.
 
Don't worry about getting a new inf it won't do anything to help.
This has been an interesting one for sure!
 
Keith

BTW, you can simply drag reorder the boxes in the display settings to have one or the other left/right top/bottom.
That might be all you need to do.
 
Sure it might show as [2] [1] but that's ok.