176 results found

1. Add Display Controls, Brightness/Contrast for Windows 8.1 and above.

   Add these controls to the current displaylink taskbar application.

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Fix DisplayLink 5.1.1 drivers for Mac.

   5.1.1 causes Zoom.us video conferencing and CamTwist to crash when installed.

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Engage the Linux Foundation to develop your drivers.

   The Linux Foundation is the place to get things into the kernel. They will help you integrate your hardware into the mainline kernel without compromising any internal IP you may be worried about. Its really the only way to get a driver working for any OS. Work with upstream not against it.

   This translates to Windows and OS X as well. I was frustrated getting my device working with Windows. Complete pain and not plug and play by any means. OS X Mojave doesn't work at all and Linux shows the same behaviour. Flickering on and off rapidly an when looking at system logs it seems to be in a constant connect / disconnect rapid loop.

   Open Source the whole driver stack and work with the upstream OS developers to get support built into the kernel will make your hardware plug and play on all operating systems.

   The Linux Foundation is the place to get things into the kernel. They will help you integrate your hardware into the mainline kernel without compromising any internal IP you may be worried about. Its really the only way to get a driver working for any OS. Work with upstream not against it.

   This translates to Windows and OS X as well. I was frustrated getting my device working with Windows. Complete pain and not plug and play by any means. OS X Mojave doesn't work at all and Linux shows the same behaviour. Flickering on and off rapidly an when… more

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Avoid boot time stall due to udev rules

   The script deployed by the displaylink installer at /opt/displaylink/udev.sh is triggered by udev rules and will run:

   systemctl start displaylink-driver

   Under certain conditions this will trigger "udevadm settle" to block forever as it leaved processes left and can't return.

   I found https://github.com/NixOS/nixpkgs/pull/51760/commits/c72bb28b9cb5138d39647f8fa12394443fea682d which fixes the issue for them.
   Applying the same to /opt/displaylink/udev.sh in Ubuntu 20.04 works just fine, the boot is fast again and functionality had no negative impact.

   So please could you change this line in your code to be like:
   systemctl start --no-block displaylink-driver

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Xrandr panning on Linux

   I have a 12inch 2880x1920 monitor (eDP-1) and a 21inch (eDP-1) with a 1920x1080 native res. I tried to use

   xrandr --fb 6720x2160 --output DVI-I-2-2 --mode 1920x1080 --right-of eDP-1 --scale 2x2 --panning 3840x2160+2880+0

   and I got:

   X Error of failed request: BadMatch (invalid parameter attributes)
   Major opcode of failed request: 140 (RANDR)
   Minor opcode of failed request: 29 (RRSetPanning)
   Serial number of failed request: 46
   Current serial number in output stream: 46

   I have an Asus t303ua
   with:
   VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller])

   Is there a plan to support panning in the future on Linux?

   I have a 12inch 2880x1920 monitor (eDP-1) and a 21inch (eDP-1) with a 1920x1080 native res. I tried to use

   xrandr --fb 6720x2160 --output DVI-I-2-2 --mode 1920x1080 --right-of eDP-1 --scale 2x2 --panning 3840x2160+2880+0

   and I got:

   X Error of failed request: BadMatch (invalid parameter attributes)
   Major opcode of failed request: 140 (RANDR)
   Minor opcode of failed request: 29 (RRSetPanning)
   Serial number of failed request: 46
   Current serial number in output stream: 46

   I have an Asus t303ua
   with:
   VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller])

   Is there a plan to support panning in… more

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. When will displaylink support AMD cpu/gpu in Linux

   Currently displaylink-based docking stations and amgpus are not usable on Linux. The screen refresh lagging is horrible.

   Can you provide a plan when this will be fixed or at least make a proper disclaimer that Linux is not supprted. so people can spend their money on working products.

   Thanks.

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Manager / option for disable one of external monitor

   Hi,
   I am using HP G2 universal dock which support 2xDP and 1xHDMI.
   It would be great to control from app/manager enabling and disabling one of external monitor.
   I see it like available monitors list with checkbox (enabled/disabled) in DisplayLink Manager located in top bar - macOS.

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Auto-detection of new software release, donwload and install options from the Display Link manager
   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Please use versioning format x.x.xx instead of x.x (xx)

   We are trying to automate software updates and track inventory of DisplayLink drivers in our macOS environment. Trying to parse versions when the value reports as 4.1 (11) or DisplayLink Driver 4.1.11 - Copyright 2003... makes it difficult.

   In the driver Info.plist file, please set the CFBundleShortVersionString key in the x.x.xx format. Even better, clean up the CFBundleGetInfoString

   8 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Fix the memory leak in driver 5.3.1 for Ubuntu 20.04.1 LTS

    This DisplayLink driver will slowly and continuously cache RAM on the system. After about 12 hours, for me it'll consume nearly 8GB of RAM and force a restart. Rinse and repeat.

    Can confirm as no memory leak occurs when not using the dock.

    8 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Dual screen setup: Laggy vertical screen +DisplayLinkUser Agent eating 100% CPU with a MBP 2019 Intel

    Hello,

    I have 2 external monitor DELL AW2721D which are QHD (2x 2560x1440p). Both are plugged using HDMI. I can't close my MacBook Pro because you don't support clamshell on Intel Based MBP (sad). It's plugged on a StarTech Dual 4k universal docking station USB-C 100W.

    One is horizontal, the other is vertical (90° rotation).
    The horizontal screen position monitor runs smooth (moving windows around, moving cursor).

    PROBLEM: the rotated monitor (90°) is extremely laggy. Even moving the mouse feels laggy.

    I've noticed that DisplayLinkUser agent is eating up to 100% of the CPU when moving a windows in that monitor when it """only""" consumes 50% of the CPU on the horizontal setup monitor.

    I'm running DisplayLink manager v1.2.0 and MacOS BigSur 11.1.
    Intel MacBook Pro 2019 2,3 ghz Intel core i9, 32 Go RAM, and AMD Radeon Pro 5500M

    I tried to lower refresh rate from 144Hz to 100hz and then 60hz on both screen, but it didn't help.

    I've made a video of the problem. In the video, it seems like the "lag" on the vertical monitor is almost "ok" but I can confirm than in reality, it's WAY worse than captured. https://youtu.be/xR6ReH8hdsk

    PS: Istat monitor does not say that my AMD Radeon Pro 5500M is currently in use like it does when I plug my macbook pro to another docking system. It says it's still using Intel UHD Graphic 630. I don't know if it's excepted or not.

    PPS: The vertical monitor sometimes looses the connexion, goes black, and goes live again after 2seconds of black.

    Hello,

    I have 2 external monitor DELL AW2721D which are QHD (2x 2560x1440p). Both are plugged using HDMI. I can't close my MacBook Pro because you don't support clamshell on Intel Based MBP (sad). It's plugged on a StarTech Dual 4k universal docking station USB-C 100W.

    One is horizontal, the other is vertical (90° rotation).
    The horizontal screen position monitor runs smooth (moving windows around, moving cursor).

    PROBLEM: the rotated monitor (90°) is extremely laggy. Even moving the mouse feels laggy.

    I've noticed that DisplayLinkUser agent is eating up to 100% of the CPU when moving a windows in that… more

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. OBS can't see DL displays

    Please fix so OBS, Open Broadcaster Software can see DisplayLink displays.

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Fix the issue with playing protected content instead of advising people to disconnect their dock to watch streaming services.

    Recommending people disconnect their dock in order to watch protected content is untenable in 2023; this is effectively telling people that their dock is worthless if they use their Mac for personal use (and some professional use). Please fix this capability - or at the very least publish a warning that this incompatibility exists as you do with the M1/M2 chip issues.

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Fix DisplayLinkManager taking up to 95% CPU on audio software or causing it not to open at all

    On macOS 10.14.6 (2017 MBP with i7, DisplayLink running on i-tec USB-C hub), DisplayLinkManager takes up to 5-10% when supposedly idle. When running audio software - namely, Ableton Live and Reaper, but likely this can reproduced on any audio software and DAW - DisplayLinkManager can take up to one full core (~95% CPU reported). This doesn't seem to be related to the size of the project, so even small projects that take up 15-20% CPU are massively affected by this issue.

    Native Instruments Kontakt has an even weirder behaviour:
    - restart MBP
    - connect external monitor via DisplayLink
    - try to run Kontakt (actually, ANY NI app, including Komplete Kontrol, Maschine and Creator Tools). The icon bounces in the dock and the app doesn't start at all.

    Oddly, if you run Kontakt BEFORE connecting the external monitor, it will work fine. If you quit Kontakt after connecting the external monitor and relaunch it, it will open just fine. This issue only happens if you open Kontakt for the first time in a session while having the external monitor connected.

    DisplayLink is currently unusable in a real-world music production scenario. Please fix!

    Further details:
    Focusrite Scarlett 6i6 audio interface. CPU drain increases by around 10% when using external USB audio interfaces regardless of their manufacturer/drivers, which is unacceptable but seems to be only part of the issue.
    Tried to remove all the peripherals connected to the USB hub to no significant improvements
    Using HDMI port, only one display connected
    Tried on and off battery power

    On macOS 10.14.6 (2017 MBP with i7, DisplayLink running on i-tec USB-C hub), DisplayLinkManager takes up to 5-10% when supposedly idle. When running audio software - namely, Ableton Live and Reaper, but likely this can reproduced on any audio software and DAW - DisplayLinkManager can take up to one full core (~95% CPU reported). This doesn't seem to be related to the size of the project, so even small projects that take up 15-20% CPU are massively affected by this issue.

    Native Instruments Kontakt has an even weirder behaviour:
    - restart MBP
    - connect external monitor via DisplayLink
    - try… more

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Work on compatibility w/ Ableton Live 10 (current version crashes Live)

    I'm running MacOS 10.13.3 (downgraded from 10.13.4 for reasons that I'm sure you know) on a MacBook Air (13-Inch Mid 2011, 1.8Ghz Core i7, 4 GB RAM) and whenever I have any of your latest (e.g. most recent final releases, two most recent "Betas" to fix the issue with MacOS 10.13.4) it causes Ableton Live 10 (10.0.1) to not load/run.

    The main reason that my computer system and I have a DisplayLink in my environment is for making music. I use the two screen setup while working with Live to have my AU and VST plugins visible while tracking. Without this software in place my second display is essentially a paperweight.

    It'd be great if you could test later releases with Live 10 so this is actually usable for me.

    I've verified that it's the DisplayLink software by installing and uninstalling the software and being able to successful replicate the problem as expected.

    Please let me know if you would like any logs.

    I'm running MacOS 10.13.3 (downgraded from 10.13.4 for reasons that I'm sure you know) on a MacBook Air (13-Inch Mid 2011, 1.8Ghz Core i7, 4 GB RAM) and whenever I have any of your latest (e.g. most recent final releases, two most recent "Betas" to fix the issue with MacOS 10.13.4) it causes Ableton Live 10 (10.0.1) to not load/run.

    The main reason that my computer system and I have a DisplayLink in my environment is for making music. I use the two screen setup while working with Live to have my AU and VST plugins visible while tracking. Without… more

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Integrate memory of arrangement of separate spaces for different displays

    At the moment after unplugging external displays then reconnecting them the locations of different multiple spaces on the different displays are mix up and jumbled. In other words it seems display link does not remember which applications and which spaces were assigned to which display once the monitors are disconnected. Thereby needing to rearrange and reorganize all spaces everytime you disconnect from you external displays.

    Macbook M1 running latest Ventura

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Dual Displays on Android App

    Dual Displays on Android App

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Planned  ·  Wim responded

    DisplayLink can already support mulitple USB displays connected on Android with the DisplayLink desktop app: https://play.google.com/store/apps/details?id=com.displaylink.desktop.demo&hl=en_GB

    However Android does not have a concept of multiple displays like other OSes. As of Android Pie, a single app can use more than one screen, eg powerpoint uses the phone screen to show presenter notes, and the extended screen shows the presentation.

    For DisplayLink to properly support dual displays on Android, like other OSes, changes would be needed to Android to support multiple displays.

18. Add Debian support in general. As most Linux distros are based on Debian that would make your tech work on most Linux distros.

    You don't have to reinvent the wheel: https://github.com/AdnanHodzic/displaylink-debian

    That also would make it easy for Deepin Linux to adapt the drivers. Deepin is Linux distro #1 in China! Just think: Deepin + Lenovo (Thinkpad)

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. macOS and M1/Intel: Add 1920x1080 hidpi (looks like 1920*1080) for QHD/2K monitors

    1920x1080 hidpi (looks like 1920*1080) support for QHD/2K monitors is useful, for both intel and apple silicons.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Cross compile DisplayLinkManager for aarch64 to support Raspberry Pi 4
    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close