I was incredibly impressed, and think you will be too. It’s indistinguishable from a conventional external monitor, even when playing video. With my MacBook Air, performance is silky smooth. Duet says that the app works only with 2013 Macs and later (running OS X 10.9 or later), and this is pretty much correct–but not the whole story. I have two Macs: a heavily-upgraded late-2011 MacBook Pro 17, and a 2013 MacBook Air 11. You can also use it as a third monitor alongside a conventional one if desired. In subsequent launches, Duet remembered this setting, so it was a simple, one-off task. Reversing that works the same as any other external monitor: just click the Arrangement tab and drag the menu bar back to the Mac display. This looked rather funky, giving a sense of what an iPad running OS X would look like, but isn’t the most useful setup. ![]() I found the first time I connected it, it set the iPad screen to be the main one, with the dock and menu bar over on the iPad. Within 2-3 seconds, the Mac will automatically detect the iPad and start using it as a second monitor. To use your iPad as a monitor, simply connect it to your Mac using a standard Lightning or 30-pin cable (I use an Amazon Basics one, mostly because it’s black …) and launch the Duet app on your iPad. On an iPhone 6, it would be pointless, and I’m not convinced it would be that much more useful on an iPhone 6 Plus, but the option is there if you want it. You need to restart your Mac after installing the companion app, and then you’re done. Install the Duet iOS app on your iPad, then install the companion menu bar app on your Mac. Built by ex-Apple engineers, I figured it ought to be work well, so put it to the test … ![]() Instead of using WiFi, it feeds the video signal from your Mac to iPad using a standard Lightning or 30-pin cable. Second, even when they do work, there is an annoying amount of lag. First, they often don’t work on WiFi hotspots, which you’re likely to be using when away from home. There are existing apps out there, like Air Display, that let you use an iPad as a second monitor for a Mac, but they work via WiFi, which poses two problems. Sure, I could get a 15-inch Retina MacBook Pro, but I favor physical screen space over smaller screen elements. When travelling, though, I have fewer pixels to play with. It’s the reason my primary Mac is still a 17-inch MacBook Pro, and why I have that hooked up to a 27-inch Apple Thunderbolt Display when I’m in my home office. And forget about a new GPU for that 2010 Mac Pro: Anything that's current, especially the higher-end Radeons from the Vega and the RX 5000 series (not to be confused with the much older HD 5000 series), will be heavily bottlenecked in that old Mac Pro - if not by the CPU, then by the ancient PCI-E 2.0 bus that the chipset on the motherboard uses.I’m a big-screen fan. This is one case where a top-end CPU from 10 years ago can barely keep up with an entry-level enthusiast CPU that's five years newer (as far as overall processing power is concerned) although to be honest, most iMacs of that vintage (2015) used mobile CPUs rather than true desktop CPUs. However, the top Ivy Bridge CPU that was available for LGA 1155, the i7-3770K, would still have bottlenecked the RTX 2080 Ti, just not quite as severely as the i7-2600K did.Īnd I was mostly correct in my hunch that the 2010 Mac Pro is a retrograde from the 2015 iMac. Ivy Bridge, the architecture that succeeded Sandy Bridge, introduced PCI-E 3.0 support. While Sandy Bridge was a solid mainstream CPU for its time, it is now uncompetitive and obsolete in today's computing world.Īnd the Z77 chipset that i7-2600K system was using wasn't being utilized to its fullest because Sandy Bridge could only transfer its PCI-E controller at PCI-E 2.0 bandwidth. The owner of that system would do best to retire everything in that system except for the GPU, and then build an entirely new entry-level build around that GPU to replace that 9-year-old relic. This was a classic case of a severely imbalanced build - way too much GPU and way too little CPU. Not surprisingly, that i7-2600K/RTX 2080 Ti's overall PugetBench Premiere Pro score using the Standard preset was barely half that of my i7-7700/GTX 1650 SUPER system. In fact, its GPU score in PugetBench for Premiere Pro is actually lower than my GTX 1650 SUPER had achieved in my now-in-storage i7-7700 Kaby Lake system. ![]() The RTX 2080 Ti is severely bottlenecked in that system, not just by the CPU, but also by the PCI-E 2.0 bus that Sandy Bridge used. ![]() In fact, I saw a recent result in Puget System's public benchmark database of a system that's equipped with a 9-year-old Sandy Bridge i7-2600K and a GeForce RTX 2080 Ti - and I had to laugh out loud at its really puny result.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |