Probably. But you should already have the ability to connect a display to the Thunderbolt ports of the M1 MBP so I wouldn't bother with DisplayLink.I have what may be a noob question. Actually, it probably is.
Will this software finally let me have an external display? My M1 MBP flat out doesn't see that I have a Samsung G7 hooked up to a Caldigit TS3+ over Display Port.
Is that your only monitor hooked up to your M1?I have what may be a noob question. Actually, it probably is.
Will this software finally let me have an external display? My M1 MBP flat out doesn't see that I have a Samsung G7 hooked up to a Caldigit TS3+ over Display Port.
That would depend on the DisplayLink adapter you buy. Use DisplayLink's product selector here.Perhaps its the late hour here - with an M1 Mac Mini, running an adapter cable that is usb3 from the Mini to a DisplayPort on the Benq2700u monitor should allow me to have 4k@60 with this software? No need for an intermediate such as a hub with breakout DisplayPort output port? (My HDMI port on the monitor is already in use by another device and have a choice of regular or Mini DisplayPort available.)
It's a 27" LG Ultrafine 5k, bought 1.5 years ago as new. It works just like it did with an MBP16, from full 5k (unusably small) to all scaled resolutions.What resolution are you running then 5k monitor? Which monitor do you have? I am experiencing issues with this and you appear to be satisfied.
Probably. But you should already have the ability to connect a display to the Thunderbolt ports of the M1 MBP so I wouldn't bother with DisplayLink.
The Samsung G7 is a DisplayPort 1.4 display, but the CalDigit only supports DisplayPort 1.2 but that shouldn't matter for 120Hz but you should try without the CalDigit especially if you want to see 240Hz (but you have no control of the included timings on M1 Macs).
Is that your only monitor hooked up to your M1?
If so, from what I know that should work fine. I have 2 monitors working out of my M1 mini, but realize you can only do 1 display out of the notebooks, so again you should be fine I would think.
The only suggestion I could provide is to maybe try swapping out the Displayport cable (You do mean DisplayPort, not DisplayLink (as is in this thread), right? Lots of different TB docks out there, I don't have one but from what I've heard, Calldigit seems to be a good manufacturer so I'd assume it should work. Maybe someone else here could give better advice that has a Caldigit dock.
Thanks.It's a 27" LG Ultrafine 5k, bought 1.5 years ago as new. It works just like it did with an MBP16, from full 5k (unusably small) to all scaled resolutions.
Thanks for the response. Let me get your take on this -That would depend on the DisplayLink adapter you buy. Use DisplayLink's product selector here.
Only if the monitor explicitly supports DisplayLink. They are usually very small monitors. There are some on the DisplayLink product page.Thanks for the response. Let me get your take on this -
"DisplayLink Manager is a new way to enable your DisplayLink dock, adapter or monitor on macOS platforms. It's an application that combines our latest driver with features that streamline the setup of mutliple displays up to 4K."
I made bold what is of interest. This is why I asked about an adapter cable. TB/USB-C to DisplayPort cable. If the above is read to mean it would work with software on the M1 controlling the monitor, wouldn't this suffice?
I think you'd be way better off just going straight from your TB port to DisplayPort (Not DisplayLink). I guess if you aren't seeing any performance issues or lags on the ext monitor, things work. But if using only 1 external monitor, is there a reason you didn't just use the native graphics on your Mac through TB directly to your monitor, without having to use DisplayLink inbetween?On a whim, I connected my MBP to this HP USB-C dock we have for imaging laptops. I plugged in a Display Port to VGA adapter, connected that to one of our KVMs (showing that there's a lot in the signal chain).
...the MBP output to the garbo monitor on the KVM, even identified the model number.
I think you'd be way better off just going straight from your TB port to DisplayPort (Not DisplayLink). I guess if you aren't seeing any performance issues or lags on the ext monitor, things work. But if using only 1 external monitor, is there a reason you didn't just use the native graphics on your Mac through TB directly to your monitor, without having to use DisplayLink inbetween?
I've tried this cable out on my M1 and it works great. Like you said though there are some problems for some people with ext monitors, so the only way to know is to just try. Have you tried using something like this cable?
USB C to DisplayPort Cable for Home Office (4K@60Hz, 2K@165Hz), uni Sturdy Aluminum DisplayPort to USB C Cable [Thunderbolt 3 Compatible] with MacBook Pro, MacBook Air/iPad Pro 2020/2018, XPS 15/13
(Amazon looong titles)
That would send the video signal out of your mac natively, without the need for software and a much slower interface (USB for DisplayLink). It should work, unless it doesn't?
I'm not sure what to make about what you said about plugging into the USB-C dock and the DP to VGA. Did you just use VGA because that's the only available port you had on it? Or was there some other reason.
Thanks much (though it is sadly not the news I wanted to hear). All I want to do is connect a Mac Mini M1 via USBC to DisplayPort on my BenQ PD2700u and enjoy 4k@60. Seems M1 and some monitors don't play well together (yet). Again thanks and appreciate your time and fast response.Only if the monitor explicitly supports DisplayLink. They are usually very small monitors. There are some on the DisplayLink product page.
Considering that there are a ton of 4k USB-C monitors out there, why do you think USB-C would be a bottleneck? 5 Gbit/s bandwidth is plenty fast for transferring the video signal many times over. The connection type seems like a non-issue.I don't have any experience with DisplayLink, other people have said on here that it works pretty well. But it's still going to be much much slower and at least some type of CPU draw on your Mac in the background to process and send that data. And I'm not sure how or why people would be using DisplayLink when connecting just a single external monitor (because you shouldn't have to, it's supported natively by your Mac, you just need an adapter from Thunderbolt to whatever your display has, like DisplayPort)
All of your post makes perfect sense. And it's great to hear it performs so well, as I am not currently a DisplayLink user. But after reading through this thread and hearing that it performs well, I think I'm going to try it for a 3rd monitor.So, if it doesn't make a difference for the internal GPU, barely makes a dent on the internal CPU, and USB-C isn't a bottleneck, where is the specific performance use case people should really be worried about? Because after almost 3 months I haven't seen any issues with performance or stability. My previous eGPU setup was both less stable and less convenient in comparison.
I have an LG 32UN500 sitting to my right that is purring right along at 4K60 out of my M1 13" MacBook ProApple has totally dropped the ball on display support for m1 macs. I still can’t get 60hz on my benq 4K monitor.
If I were Intel, this is what I would be laughing at... "we at intel have cpu's that can actually make your monitor work"
Reading through your posts in the thread, I couldn't tell whether you had actually tried a USB Type C to DP cable yet, or if you were saying it didn't play well together based on the information in the thread, which can be quite confusing given people freely mixing DisplayLink and DisplayPort.Thanks much (though it is sadly not the news I wanted to hear). All I want to do is connect a Mac Mini M1 via USBC to DisplayPort on my BenQ PD2700u and enjoy 4k@60. Seems M1 and some monitors don't play well together (yet). Again thanks and appreciate your time and fast response.
Good points.Reading through your posts in the thread, I couldn't tell whether you had actually tried a USB Type C to DP cable yet, or if you were saying it didn't play well together based on the information in the thread, which can be quite confusing given people freely mixing DisplayLink and DisplayPort.
I've seen some people try to clarify it, but just to recap in case you haven't tried yet:
- Yes, this should work. You'll just need a DisplayPort 1.4 to USB Type C cable like this one: Amazon.com: USB C to DisplayPort Cable for Home Office (4K@60Hz, 2K@165Hz), uni Sturdy Aluminum DisplayPort to USB C Cable [Thunderbolt 3 Compatible] with MacBook Pro, MacBook Air/iPad Pro 2020/2018, XPS 15/13: Computers & Accessories
- No, you don't need DisplayLink software, adapters, or special DisplayLink monitors to drive a single DisplayLink monitor using the USB-C port off of a Mac Mini M1 (or to drive two monitors, if you were to drive one from the HDMI port and one from the USB-C port). The M1 Mini uses a protocol called USB-C Alt Mode, which allows a DisplayPort signal to be generated by the GPU, carried through the USB-C port (almost as if it was a DisplayPort port with just a different physical form factor), through a USB-C-to-DisplayPort cable, to the monitor's DisplayPort port. All the cable is doing in that case is physically adapting the pins to the right pinouts, but it's not changing the _protocol_ being used for video at all - the language it's speaking is DisplayPort from the point it's generated by the Mac's GPU all the way through to the monitor.
- Since the signal is DisplayPort all the way through, you need to make sure your monitor is set in its settings to communicate using the 1.4 version of the DisplayPort protocol. Your particular monitor has a setting to "talk" DisplayPort 1.1 or 1.4. If it's set to 1.1, it will only talk 1.1, but 1.1 cannot handle 4K60, and you'll be limited to the resolution / refresh rates you can use (4k @ 30 or 2K @ 60). 1.4 can handle 4K60, however. Go into the On Screen Display on the monitor's menu, and go into System -> DisplayPort. Make sure the setting is set to 1.4.
Once you have the setting in the monitor's menu set to 1.4, connect up the USB-C port on the Mini to the DisplayPort on the monitor using a USB-C to DisplayPort 1.4 cable such as the one above. You should then be able to switch the monitor to the DisplayPort input and set it up in the Mac display settings to output 4K60.
Having said all that, if you _have_ tried that and it isn't working, you're positive that your cable is a DisplayPort 1.4 Alt Mode certified USB-C to DisplayPort cable, and you've verified the monitor's setting is set to DisplayPort 1.4 mode, you might be running into the issues Big Sur has been having with external monitors: Some Users Having External Display Connection Issues With macOS Big Sur 11.1 and 11.2 - MacRumors. There's discussion in the thread on that article that the Big Sur 11.3 beta 2 released last week has fixed the issues for at least one person experiencing them, so you may want to join the Apple Beta Software Program and upgrade to 11.3 b2.
For people who need DisplayLink (to drive 3+ monitors on an M1 Mini or 2+ monitors on an M1 MB / MBP), agreed - I've also seen people discussing issues on DisplayLink with 11.3 (though ironically 11.3 seems to fix native HDMI and DisplayPort, so people who really need DisplayLink for monitors beyond what's natively supported should stick to 11.2, while people using native HDMI or DisplayPort over USB-C Alt Mode connections may need to upgrade to 11.3).Good points.
Be aware - there are some issues with the DisplayLink software working well with the 11.3 Beta's. Perhaps try the most stable combination beforehand.
It's really disappointing that this is an issue at all. I have to imagine at least some of Apple's thousands of employees are using M1 Minis, and some would have run into this before it made it to the public. When you sell a product that literally doesn't have an internal monitor, and has to use external monitors, one of the core pieces of functionality needs to be broad compatibility and reliability with external monitors.Considering that driving multiple monitors on M1 devices is now front page on displaylink.com, hopefully for their sake, Apple fixes the 11.3 issues.
I have MBP 13 M1 so its connect to LG ultrafine 5k Direct TB3 and I want to connect a Samsung 32 4k with its got HDMI and DPI've been trumpeting the M1+DisplayLink combo a few times, might as well do it once more. In short, it's fantastic. Coming from an MBP16 + eGPU combo, it's so much more responsive overall. Completely silent. Nothing to eject, just pop the M1 off when done. Three ext monitors connected via one TB3 cable that includes power. One more TB3 port (and bus) free for other peripherals. Performs just as fast as a "real" GPU for my graphics/design-related workflows. Clamshell works fine. The native M1 app is just icing on the cake.
Trade-offs, which I consider minor compared to the upsides, are:
I sold my 1-year old setup second hand and got enough money to get the M1, the dock, AirPods Max, and still had money left over. It's been 13 years since I had a Mac setup that worked as well as the current one does. That was a well-equipped "cheesegrater" Mac Pro with a 32" Cinema Display.
- Log in with Apple Watch doesn't work when ext monitors are active (due to screen recording API being active); it works when undocked in laptop mode.
- NightShift/Flux doesn't work on DisplayLink monitors, only on the primary 5k TB3 monitor that is direct-connected, and also works as a USB-C hub for DisplayLink daisy-chaining, for 2 more WQHD monitors.
- Can't think of #3.
Agreed.For people who need DisplayLink (to drive 3+ monitors on an M1 Mini or 2+ monitors on an M1 MB / MBP), agreed - I've also seen people discussing issues on DisplayLink with 11.3 (though ironically 11.3 seems to fix native HDMI and DisplayPort, so people who really need DisplayLink for monitors beyond what's natively supported should stick to 11.2, while people using native HDMI or DisplayPort over USB-C Alt Mode connections may need to upgrade to 11.3).
The particular poster I was referring to is trying to drive one single 4K60 monitor on DisplayPort, so there's no need for DisplayLink, and that incompatibility wouldn't apply to them.
The most stable solution for them should be the one that is native with no conversion involved, which is going to be native graphics out of the GPU using USB-C Alt Mode to get native DisplayPort output, without DisplayLink technology being part of the stack at all.
That is supposed to natively work on 11.2 (and actually reportedly did on 11.1), but due to the bugs with external monitors on 11.2 (both HDMI and DisplayPort), they may need to go to 11.3 beta or wait for 11.3 final for Apple to fix native external monitors in general before it works as expected.