163 votesStarted · AdminAlban Rampon (Product Manager, USB Docking and Graphics Adapters, DisplayLink) responded
The OS fix has been rolled out to Windows 10 Insiders build 18932. Would anyone else be able to feed back on the status for their application?
Matt and Brendan, may you please submit logs as described in https://support.displaylink.com/knowledgebase/articles/533818 ?
No need for advanced, it's for us to see machine and software details to reproduce in-house.
@Brendan, could you please give full name and version number of the application? We might need to contact the company to get a version for analysis.
@Elrond, we need more confirmation the fix is suitable to get it scheduled for Windows 10 v1903 servicing. Otherwise we risk keeping it in 20H1 (from build 18932). Brendan's feedback suggests more work might be needed. All applications we have tested were now behaving correctly.
Thank you very much for taking the time, Vladimir.
Paul, there not. This is a beta program from Microsoft. If that doesn't mean anything to you, I can only advise you to wait for a fix to be rolled out to you via Windows Update to the standard Windows.
@Eambo, the previous fix validation was done on a specific application via an OEM's end customer. I didn't schedule re-testing what someone else tested so we didn't have evidence first hand. That application worked... but it turns out it doesn't use the graphics API like most do. The other applications don't work because of an API issue (display enumeration to be attached to different GPUs in multi-graphics machines).
As a corrective action, DisplayLink are validating the fix ourselves in a Windows 10 graphics private development build. Once the fix is confirmed, it will make its way through Windows Insiders. As soon as we are satisfied with the fix, DisplayLink will work with the different laptop manufacturers to make the business justification so the fix is backported to Windows 10 v1903 via the monthly servicing updates. That item is and stays on our weekly agenda with Microsoft.
Does that clarify the action plan?
Eamonn, I would need to know what your testing it with and how you change the GPU affinity. The change was made a while back so it would be in any current 19H1 ring, slow and fast as we're so close to release.
The change was validated with Dolphin CAD/CAM, because it is known to use Windows APIs correctly. Before, when an indirect display was primary, it would use the Intel iGPU even when the Windows UI is selecting the external GPU, leading to slower computation.
Now, the application renders using the secondary GPU regardless of which display is declared as "main display" when the high end GPU is selected in the Windows UI.
The laptop manufacturer and Microsoft both closed the issue as fixed.
There was no code change needed from us to address that issue.
(I am simplifying a bit as there are 2 activities here computing/composing and displaying, both can be done by different resources)
@Daniel, you need to create a ticket with the logs (https://support.displaylink.com/knowledgebase/articles/533818-how-can-i-report-windows-issues-to-displaylink). Without data you can only get generic information. GPU works in any case so that message is, at best, misleading. Do you have a support case with DaVinci, if so, when you create your ticket by email with us, give contact details so we can contact DaVinci to understand what they rely on.
I don't understand the unsupported defamatory accusations from Elrond when transparency has been used from the start.
Windows uses the POST graphics card. Windows cannot select the POST card. POST is before Windows boots, that's at BIOS level. The OS is getting changed not to always use the POST GPU, and, when the change is done, an indirect display driver will be able to select GPU affinity.
The GPU setting in the OS is for application rendering rather than display adapters and includes a bug.
Currently, the work around is to use a direct display (ie. native laptop display) as primary or main display. That means keeping the lid open, for instance. Daniel confirmed that earlier in the comments.
Unfortunately, very few people took the time to report this issue through the Windows 10 Feedback Hub so we had to wait until a computer manufacturer escalated this so it got prioritised.
@Phil, this Thunderbolt 3 dock is not using DisplayLink technology.
@Slava, the thing on the app being started sounds like the old Intel graphics bug on OpenGL pass-through. The GPU used cannot changed at run time. Just use an Intel direct display before starting the app if your machine is below 6th generation. If 6+, get driver from xx.60.xx.xx or xx.65.xx.xx driver where this is fixed.
@Elrond, @Eugene and others, yes it will. This is now on the roadmap and planned. The OS release it will be in depends on development progress and quality testing. Once I have progress updates and I am allowed to share it, I will.
@AdamH, because the other option doesn't used the Microsoft IndirectKMD as it's not an indirect display.
@Jan, you can subscribe to comment notifications, as far as I can see from my end.
What is a CZ entry? There was a bug report and the rest was during meetings.
@ckoroglu The issue here is about Windows and their kernel graphics driver. Linux doesn't use Microsoft kernel graphics driver. Linux doesn't have the notion of "indirect displays" either. That's a Windows feature.
Jan, this report says Windows 8.0 (that's the build 9200). This discussion is about Windows 10 Anniversary Update onwards. If you're really on Windows 10 and the graphics tool reports Windows 8.0, I wouldn't trust it understands how the Anniversary Update graphics subsystem fundamentally changed the deal and how it can measure things properly for something it doesn't understand. If you are really on Windows 8.0, I don't see us doing any new development for it as almost no-one uses that OS (~1% maybe). Could also be the OpenGL bug on the Intel graphics driver affecting your tests.
Feedback about the OS using the GPU from POST is not a DisplayLink opinion, this is a Microsoft graphics team affirmation. They wrote that part of the feature. I am inclined to believe both the author and general test feedback.
Hell Jan, how do you check what GPU is used? I am rather inclined to believe Microsoft graphics engineers who told me the kernel driver doesn't change on the fly and that they won't change until they receive feedback from Windows 10 users.
https://aka.ms/Cojpi9 is a Windows 10 Feedback Hub entry from someone about the graphics card selection for Windows 10 v1709.
This is an operating system feature. The graphics card used is the POST one. if your Dell 7559 gaming laptop uses the Intel GPU for POST, then Windows will also assign it to indirect displays like DisplayLink.
Unless you report this to Microsoft for them to change the selection, then I don't foresee any suitable resolution.
@Manatax, can you use our Customer Support Tool (http://support.displaylink.com/knowledgebase/articles/533818) and that will create a ticket. We would need to find a machine close to yours to see how the disabling works. We can then discuss this with Microsoft.
Also, please do complain through the Windows 10 Feedback Hub that you want to use your high end graphics card with indirect display because the iGPU is not powerful enough to do <whatyoudo>. We need to send enough feedback for this to get prioritised.
No Zachary, unfortunately there hasn't been enough feedback through the Windows Feedback Hub to make it a priority for them. At the moment this is scheduled for Redstone 4 but may well be postponed again if customers don't flag this is important.
2 votesGathering Feedback · AdminAlban Rampon (Product Manager, USB Docking and Graphics Adapters, DisplayLink) responded
Asked for more information in comments.
Hello, I'd need more details to make sure I answer what you are asking. Where do you change the "scale"?
11 votesGathering Feedback · 9 comments · DisplayLink Feature Suggestions · Flag idea as inappropriate… · Admin →
Unlike you first post statement, the link you gave me is not for Thunderbolt 3 docking station at all.
Thunderbolt 3 is using a USB alternate mode, which means non-USB traffic over a USB-C *plug*.
I don't know which chip SKU is in this particular product and this is a key element.
The product may be HDCP capable and compliant, but not offer that feature on that particular OS. This feature will require collaboration with the OS vendor. It is on the roadmap but not done on macOS, and that's why the suggestion is not set as "completed" or "declined". Most of the use case for universal docking has been office productivity.
The product may also have no HDCP key and therefore incapable of ever decrypting content, by contractual requirement of DCP licensing. The product manufacturer must be a member of the body to be allowed to have chips with keys. Licensing also applies to companies who want to claim offering HDMI support.
If you create a support case with the DisplayLink logs (https://support.displaylink.com/knowledgebase/articles/755301), then we can look into if that product is HDCP capable or not as we'll get the chip SKU built-in. Videoseven doesn't claim their product offers HDCP, so to me, that is a hint that they don't support it.
HDCP is not just about software.
@Andreas, a Thunderbolt 3 dock doesn't use DisplayLink technology.
There is no trace of any ticket from this email address.
However, you are correct that if you were inappropriate or insulting, we would have closed your ticket without any reply. Being frustrated, whatever the level, doesn't mean our staff has to be insulted.
I have renamed the feature for what you wish: enable HDCP playback support on macOS. That type of feature will require collaboration with the OS vendor so we can get access to the encrypted pixels, like we did with Microsoft and Intel for Windows 10. Software vendors also had to follow the OS implementation changes. Then, based on capability reported, the video player decides what it plays, if it plays. For instance today, Netflix lowers the quality for non-protected outputs.
Finally, it will also require that your hardware supports HDCP. Not all device manufacturers are DCP licensees. Being DCP licensee is a requirement for DisplayLink to be allowed to ship them chips with HDCP keys inside that they can use in their product.
1 voteGathering Feedback · AdminAlban Rampon (Product Manager, USB Docking and Graphics Adapters, DisplayLink) responded
Would you please be able to detail? The DisplayLink driver is inboxed in Chromebook since R51.
Firmware update of the DisplayLink chip is non-optional and is happening on all OSes, transparently. It is not possible for the user to change the DisplayLink firmware selectively, even on Windows. You might be referring to other firmware for other technology your product can integrate. We can pass this onto the device manufacturer.
I can also pass your feedback about Multi Monitor Software to them. This is a third party whose software works with or without DisplayLink technology.
Which item(s) from DisplayLinkManager are you missing?
I've renamed the idea to something more meaningful. I have also removed the shouting and the dramatic wrongful direct causality effect. Not having TLS does not mean you get a malware.
Let's stay factual please rather than building up unhelpful alarmist accusations.
17 votesStarted · AdminAlban Rampon (Product Manager, USB Docking and Graphics Adapters, DisplayLink) responded
Support for gamma LUT is being added to some devices. See the idea on supporting f.lux.
@Ralph, not for now and it won't be technically possible in all devices. Anyway, the OS doesn't give us HDR pixels today anyway so even if the driver and the chip could do it now, you would still not get HDR on the displays.
908 votesStarted · AdminAlban Rampon (Product Manager, USB Docking and Graphics Adapters, DisplayLink) responded
The new estimate of delivery for f.lux, night mode, and monitor calibration on Windows 10 Creators Update onwards is for release 9.0, planned before the end of 2018. When a 9.0 Alpha or Beta is issued, you will be able to try the feature on products based on the DL-3000, DL-5000 and DL-6000 series ASICs.
f.lux has enabled some support for DisplayLink indirect displays (Windows 10)
You can download f.lux from https://justgetflux.com/
That's correct Gregor. F.lux implemented this on Windows 10.
Thank you Anon, but we cannot take any credit. What you have today is all thanks to the F.lux team.
@JI, there is a separate thread for Mac and it has different challenges. I have renamed this idea to specifiy Windows.
@Anonymous, the Dell D1000 is using the same hardware family (DL-3000/DL-5000) as the Dell D3100 and I have been using f.lux on Windows 10 successfully for weeks. Therefore there is no issue on that side. I have also tried it on the Dell D6000 using the latest DL-6950 chip and it works.
I suggest you check f.lux options.
F.lux has announced supporting DisplayLink indirect displays with their latest release. I have personally been using it since.
@mmm Dell D3100 with Windows 7 is targeted for release 8.3 currently scheduled for July. It's the right hardware, but wrong OS for 8.2 preview.
I'm looking at trying to get an *alpha* version of the 8.3 driver in May/June for those who feel like trying unfinished software. Today, it's not been tested enough to be acceptable even as an alpha. When I have news I will post.
Because of the issue with gamma tables in the Anniversary Update, we will not be able to enable this feature by default on that OS. Your feedback validates our testing with issue seeing the login screen as Windows may send black gamma tables instead of default which is not acceptable for people who didn't ask for that feature! You can use the current trick from the forums though.
Windows 10 Creators Update has the fix so we will enable support by default. Engineering is currently testing on Windows 7 - Windows 10 TH2 (build 10586). If testing goes well, then gamma table will be supported from DisplayLink driver v8.3 on devices whose Hardware ID starts with USB\VID_17e9&PID_43 which is the majority of devices in the field.
Devices whose Hardware ID starts with USB\VID_17e9&PID_6 are next in line but we have already identified restrictions on HDMI during feasibility study.
Devices whose Hardware ID starts with USB\VID_17e9&PID_FF will come later.
Devices whose Hardware ID starts with USB\VID_17e9&PID_0 and USB\VID_17e9&PID_40 cannot have new features added once they are in the field so will not get new features.
@Henrik, best channel is here. When ready I will communicate how to try for those who want and have the adequate hardware and OS. I'll probably open a new forum board for the colour correction feedback on Windows. Testing will tell me when it's ready.
Hello Piotr, our Mac team is starting evaluating if it possible. We have met issues with another part on Mac (DDC/CI) so this is not a straight forward port from Windows.
Hello Sven, very nice monitor, I use it for trade shows as it's light. This device will not be supported in the initial version version. We are still unsure about possibility. They are built differently and already have gamma curve tables which manufacturers like Asus would use to calibrate them in factory depending on panel used. We need to see if we can override the feature. Investigating is definitely planned.
@johan and all. The products which will first be supported have their hardware ID starting with USB\VID_17e9&PID_43. You can get the hardware ID from Device Manager in the device details (see how to find the HWID in http://support.displaylink.com/knowledgebase/articles/544834#otherdevices).
Once I have a development build, I will probably create a forum board.
It's not been "planned" for two years Rowen...
TL;DR: It's a big job and we don't do hack jobs so it takes time.
f.lux support is under analysis. This requires extensive firmware and some host software work.
There are 10s of millions of devices in the field with a bit more than one version of Windows, some with one display, some with two, some with three... Some with HDMI, VGA, DisplayPort, DVI, and a combination of everything.
Today, we do not modify the image in any way, we take the output of the graphics card. This is brand new feature that is requested, not just a tweak. This new feature MUST NOT, in any way, create issues when not in use (so in most cases). We need to setup brand new test rigs and test suite to defend it.
I have deleted injurious comments from Marek Ziel (Apsik).
@All. f.lux support is under analysis. We met with the f.lux developers to discuss an implementation which will keep working with new versions of f.lux.
We are trying to think about to support individual colour correction rather than just an identical gamma curve change applied to all displays. However, we don't yet if it is possible.
@Andrew. DDC/CI pass-through on DL-3000 and DL-5000 was released as part of 8.0 M0 so has been available already.
@Viking, you do not need f.lux to change brightness. You can use Screenbright, a free utility which is already supported across all recent docking stations with DisplayLink technology.
@Sergio, the comment about Windows 10 is not about applicability of the solution, but the reason for not having implemented it yet.
The flickering on Anniversary Update is a f.lux bug they are aware of and are working on. Please look for new versions of f.lux.
Felix, colour correction and contrast are different. From our 8.0 Beta 4, you are able to use applications like ScreenBright to change the contrast settings via the computer.
Colour correction is totally different, as f.lux states in their online contributions. The feature is currently on the roadmap for the devices which have the horsepower to handle it. Device with a USB Product ID starting with 0x0 will never be able to support it because, unlike brightness or contrast which are just a command to send, colour correction requires the device to compute.