![]() |
|
|
|
|
#1 |
|
Senior Member
Join Date: Sep 2015
Posts: 1,685
|
Hello Congo,
I created a new thread for this as that was an old thread and your text is not blurry but should be stretched or compressed. Would you please be able to provide the log files as described in my forum signature so I can look into what is going on? OSD doesn't measure the signal. OSD gives what is the closest to what it thinks the signal is. Our log files will tell me the timing being sent to the monitor. Kind regards, Alban
__________________
Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: May 2016
Posts: 3
|
You're right - Win10 thinks the monitor is displaying 1600x900, but the monitor thinks it's displaying 1440x900. That's why it looks blurred.
Anyway, log files attached! |
|
|
|
|
|
#3 |
|
Senior Member
Join Date: Sep 2015
Posts: 1,685
|
Hello Congo,
Thank you for the logs, this is helpful. Your monitor does not use the VESA standard timing whereas the VESA standard timings are being sent. The signal sent to the monitor is 1600*900 @ 118.25 MHz The signal the monitor expects is 1600*900 @ 108.00 MHz This is not really a resolution issue but a "detailed timing" one. The OSD doesn't measure but does a guess, and guesses wrong. I've flagged this to engineering to see what we can do to use the monitor detailed timings instead of the standard VESA timings. However this is not a quick fix I can just give you now, unfortunately. Kind regards, Alban
__________________
Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
|
|
|
|
|
#4 | |
|
Junior Member
Join Date: May 2016
Posts: 3
|
Quote:
|
|
|
|
|
|
|
#5 |
|
Senior Member
Join Date: Sep 2015
Posts: 1,685
|
Hi Congo,
I've scheduled a fix for this for version 8.0 and this is currently getting assigned to a developer. If you wish to get a development build for you to try when this is addressed, would you please create a support ticket by sending an email to technical_enquiries? You could title it 8.0 Development Build for 22482, for instance. I'll attach the internal bug number and will have your details to email a link to you. Thanks for your patience! Alban
__________________
Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|