|
|
Thread Tools | Search this Thread | Display Modes |
|
10-23-2013, 01:34 AM | #1 |
Junior Member
Join Date: Mar 2013
Posts: 8
|
How you can ditch your Displaylink adapter using a Apple TV
|
10-23-2013, 03:49 AM | #2 |
Junior Member
Join Date: Jul 2013
Posts: 5
|
Nice video! I've been pretty unhappy with DisplayLink in general, and Mavericks isn't helping, so I'm seriously considering this.
Do you notice a large CPU spike when you play video on the Apple TV screen? Also, you mentioned you had the Apple TV and your computer hooked up together, did you do this directly with an ethernet cable or through some type of router or switch? |
10-23-2013, 04:13 AM | #3 | |
Junior Member
Join Date: Mar 2013
Posts: 8
|
Quote:
|
|
10-23-2013, 04:38 AM | #4 |
Junior Member
Join Date: Oct 2013
Posts: 23
|
kinda embarrassing that you can get that from an apple TV over ethernet with all the overhead involved (even with gigabit) but somehow they can't get this thing working over a 5gbps USB 3.0 connection. And they claim they don't know how to "get the pixels" obviously airplay works. Seems like us mac users (probably one of the primary demographics for this type of product) just aren't important enough. Especially considering how long mavericks GM was available to test with.
edit: it also should be noted that the Apple TV has only a 10/100 ethernet port so… yeah… not even usb 2.0 bandwidth. Last edited by gilesmartin; 10-23-2013 at 04:42 AM. Reason: see above |
10-23-2013, 04:42 AM | #5 | |
Junior Member
Join Date: Mar 2013
Posts: 8
|
Quote:
|
|
10-23-2013, 10:28 AM | #6 |
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
The Apple TV and AirPlay uses private APIs in OS X to get it's screen updates. These APIs are not public. We would LOVE to have access to this API as we could make an improved USB display solution without the issues that are seen today.
This has been discussed with Apple but they have been unwilling to give access to this private API. As you might understand this is very frustrating for us, as it makes our solution doesn't perform as well as it could because we're locked out of a private API. Wim |
|
|