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"?
10 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.
16 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.
896 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.