Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink)

My feedback

  1. 734 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      104 comments  ·  DisplayLink Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

      The implementation progresses. The first products we are working on are the DL-3000 and DL-5000 series and you can have an early preview on Windows 10 Anniversary Update onwards for these devices: http://www.displaylink.org/forum/showthread.php?p=82958#post82958

      Still a lot of work to do… Please do read the limitations before you start using it and use the forum for the feedback so it can be individually tracked and answered to.

      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.

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

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

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

      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.

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

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

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

      It's not been "planned" for two years Rowen...

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

      Brian,

      TL;DR: It's a big job and we don't do hack jobs so it takes time.

      Details:
      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.

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

      I have deleted injurious comments from Marek Ziel (Apsik).

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

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

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

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

      Alban RamponAdminAlban Rampon (Windows Product Manager, DisplayLink) commented  · 

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

    • 83 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        9 comments  ·  DisplayLink Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

        Hello, that's correct. This won't work until we have access to the pixels. Our driver need to do a bit more than just be a USB device. Windows Phone also has additional restrictions compared to the full blown OS... but at a minimum, we need to get access to the pixels before we can think about packaging them through USB. That will require an OS change so please make sure to also flag your interest to Microsoft.

      Feedback and Knowledge Base