Airserver Universal - iOS, Android, and Windows Wireless Mirroring

I have been searching for a software-based Miracast solution for quite some time. iOS and AirPlay have had Reflector, AirServer, and more, but mirroring from Android or Windows has required a hardware Miracast receiver.

This past summer Microsoft released updates to Windows 8.1 with some promising comments about using Windows as a Miracast receiver. The updates enabled the capability, but didn't add the actual receiver; that was up to developers and needed updated hardware drivers.

Then at the end of October AirServer announced AirServer Universal, a new version adding Miracast to their existing AirPlay receiver software. There are some specific requirements to get it working. Unfortunately for Mac users, this only works with Windows 8.1. Your computer must also have a network device with a new NDIS 6.40 device driver. If you don't have a supported network chip, you can simply add the Asus USB-AC56 adapter. The combined price of the adapter and AirServer is under $100. I also installed AirServer on a sub-$400 Acer Switch 10 convertible laptop and was satisfied with the performance, even with two iPads (2nd generation) connected along with a Nexus 5. The Switch 10 did not require the Asus adapter.

AirServer has worked well as a Miracast receiver with every device I have tried, including a Nexus 5, Nexus 7 (2013), Nvidia Tegra Note 7, and Acer Switch 10 Windows 8 convertible laptop. Miracast connections from the Nexus devices did take longer to establish than other devices, and initially appeared to have significant input lag, but it improves fairly quickly. I created a video showing the Nexus 5 used alongside an iPad 3, connecting with a Nexus 7, and a game. The audio in the game is choppy, but that has been true with every Miracast receiver I have used. One interesting discovery is that I had to use the Asus USB-AC56 to get the Miracast capability of AirServer installed, but then was able to just use my laptop's existing wireless chip. I removed the Asus adapter completely and was still able to connect from the Nexus 5, Tegra Note, and Acer Switch. The Nexus 7 still saw AirServer as a receiver but it wouldn't connect unless I used the Asus adapter.

In addition to the system requirements, there are other limitations. AirServer only supports one Miracast device at a time. You can still have multiple iOS devices along with that single Miracast device. AirServer says support for multiple Miracast devices is coming. The other limitation is actually a Miracast issue more than a problem with AirServer. A device sending a Miracast signal will always send a landscape image. If your screen is in portrait mode, the device will rotate it and convert it to landscape before sending it to AirServer. If that is the only device being mirrored, it's not a problem. It is a problem when sharing the screen with an iOS device. In those situations the Miracast screen appears smaller than the iOS screen (as seen in the video linked above). AirServer may implement a workaround in a future update but isn't making any promises.

While not perfect, Airserver Universal is a step in the right direction for enabling a true BYOD environment.

Wireless Display Testing - Intel WiDi

WiDi is Intel's proprietary protocol for wireless audio and video. WiDi was released in 2010, a year before AirPlay included mirroring support, and two years before the first Miracast devices were available. At first it was limited to 720p, but is now able to stream 1080p with 5.1 audio. Additionally, as of WiDi 3.5 it is compatible with Miracast, and supports USB over wireless. In theory a WiDi receiver could be connected to an HDMI television or projector and a USB device.

The USB support was definitely intriguing. One scenario I considered was using a media center remote to control a video on the computer using a USB infra-red receiver located near the display. The other scenario I thought about was connecting an interactive whiteboard in a classroom. I imagine there would be many teachers happy to not have to worry about the computer needing to be located close to the interactive board. Unfortunately it does not seem that there are any receivers that support WiDi's USB over wireless feature. 

Although WiDi has been around for three years, and has had several major version upgrades, getting it working was far from easy. Compared to AirPlay, it is just downright frustrating and I'm not surprised that few people I know have ever used it. I tried using WiDi "out of the box" on two separate laptops (a Windows 7 based Dell and a Windows 8 based Lenovo), and neither would work. In both cases the WiDi software would detect the receivers, but never successfully connect. The installation instructions for WiDi direct you to install the newest Intel video driver, then the Intel wireless chipset driver, and finally the Intel WiDi software, of course with restarts after each step.

I started with the Windows 8 laptop (my personal laptop). Even after following the prescribed steps, WiDi still would not make the final connection to the receiver. Some searching finally lead me to a page directing me to use the Windows 7 wireless drivers for Windows 8. Sure enough this worked.

Oddly, I did not get WiDi working on the Windows 7 laptop. I tried a couple of different versions of the WiDi software and then gave up. I wasn't about to waste even more time trying to get another laptop working. The following video shows what happens on this laptop when trying to connect to a receiver.

When connecting to a receiver for the first time, the display will show an 8 digit number that you type into the WiDi software. This pairs the laptop to the receiver. Subsequent connections to the receiver are as simple as AirPlay. All you have to do is run the WiDi software, choose a receiver, and click Connect. You can even choose to have WiDi connect automatically to a paired receiver when the software is run.

Next I'll look at the two WiDi receivers I have available to test, the Actiontec ScreenBeam and the Netgear Push2TV-3000.

Actiontec ScreenBeam Kit

The Actiontec ScreenBeam Kit includes a receiver compatible with WiDi and Miracast, and a proprietary USB transmitter that can be used with Windows laptops that are not WiDi compatible. I managed to get the kit for $63 on sale, so it is a pretty good deal if you need the transmitter.

As you can see in the photo, there is a USB port on side of the receiver. I hoped that it might support USB over wireless, but it seems the port is just for firmware updates. The receiver is powered by a non-USB source, so you will always need access to a plug and be sure to have the adapter with you. An HDMI port and pinhole reset button are next to the power connection, and there is a single status LED on the top. At 77mm x 73mm x 17mm it is quite a bit smaller than an Apple TV, but quite a bit larger than the Netgear Push2TV-3000. The silver printing on the front and top, and the silver ringed vent on the top make this device much more noticeable than both the Apple TV and P2TV-3000.

In use, the ScreenBeam seemed to have slightly lower latency than the Netgear Push2TV-3000, but suffered more graphical and audio glitches. It also was quite warm to the touch, bordering on hot after using it for a few minutes. This was surprising considering it seems to be well vented.

To get started, just plug in the power and HDMI connections, and make sure the display is set to the correct HDMI input.

Netgear Push2TV 3000

The Push2TV 3000 (P2TV) is a very small and light WiDi and Miracast receiver that is available for $60 US. It weighs in at 48 grams and is roughly the size of a credit card (obviously thicker). Much like the Apple TV, it has a very basic, clean look with a glossy black finish. It can easily go unnoticed just sitting on my television's base. There is a single white LED on the front. The back has a mini-USB port for power, a full-size HDMI port, and a recessed reset button. There is a nearly-flush button on the side that is barely noticeable. The button was originally used to switch between WiDi and Miracast mode, but firmware updates removed the need to manually switch between modes. Now the button is used to put the P2TV into firmware update mode.

The P2TV had no problem being powered by the USB port on my television. Although I would recommend having a USB power adapter with you if travelling with the P2TV, it's nice to know that it can be powered so easily. As with the ScreenBeam, to get started just plug in the USB power, connect to the HDMI port of your display, and make sure your display is switched to the appropriate HDMI input.

Watch the videos below to see how to connect to the P2TV from Windows using WiDi, and to get an idea of the video performance. Note that I had previously connected to the P2TV and configured it to automatically connect.

Conclusion

It is hard to believe that WiDi is a technology that has been around for three years. WiDi installation was far from user friendly, and I'm guessing that many WiDi receivers are unjustly returned to stores as "defective".

WiDi is only available on laptops with newer Intel processors, Intel network chips, and Intel graphics. There are reports that Windows 8.1 will include Miracast support, and that it will be a free upgrade for Windows 8 users. Miracast support directly in Windows would open up compatibility with far more hardware configurations, and make WiDi redundant.

As for the two tested WiDi receivers, I would definitely choose the Netgear P2TV-3000. It is smaller, easier to power, slightly cheaper, stays cooler, and seems to have better image and audio quality at the expense of slightly higher latency. The ScreenBeam kit does include a USB transmitter if you want to use wireless video on a computer that does not support WiDi, but that seems to be its only advantage.

I will be testing these two receivers again in the near future with a Miracast-capable Android device.

Getting AirPlay to work in the classroom

I've talked about AirPlay in previous posts about wireless display technology. It works great in your home, and Apple really wants you to use it in the classroom. Unfortunately, the AirPlay protocol doesn't work that well on networks designed to support hundreds (or thousands) of wireless devices. Apple has workarounds that may or may not be implemented by your school's or board's IT staff. If not, there are still ways to get things working in your classroom, and maybe even for less money than you think.

Note that the following won't work for everybody, but hopefully it can help some people. This was my poster session topic at CONNECT 2013, and I know that it helped at least a couple of people.

Getting Connected

The first step in solving the AirPlay problem is getting all of your devices on a network that is a little more personal. There are a few options.

Bring your own router

If you can get away with plugging a wireless router into your network, this might be a good way to go.

Tether to a Smartphone

If you have a smartphone that can act as a wireless hotspot, you can use it to connect all of your devices together. If possible, you might want to disable your data connection to avoid an out of control wireless bill. Disabling your data does mean that none of your devices will be able to access the Internet, but AirPlay should work fine.

Internet Connection Sharing

If you already have a computer (Mac or PC) in your classroom that is connected to a wired network, you can take advantage of the Internet Connection Sharing feature built into the operating system.

On a Mac, click the Apple menu, then System Preferences, and look for Sharing. Check the box next to "Internet" and share the connection from your "Built-in Ethernet" to "Airport". Click the Airport button to choose settings for your hotspot.

The built-in feature of Windows involves more steps. Alternatively, just download Virtual Router, a free program that simplifies the entire process on Windows. Also, Windows laptops based on newer Intel Centrino platforms can actually share a wireless connection to other wireless devices.

Once you have your hotspot set up, just connect all of your devices to the hotspot and you shouldn't have any problem getting AirPlay working.

Using what you've already got

You're probably used to using an Apple TV to show videos from your iOS devices, but if you already have a computer connected to a projector it is a pain switching video cables or sources. Well, you don't have to.

Check out AirServer or Reflector. Both programs are available for Mac or PC, and make your computer look like an Apple TV to your iOS devices. There are some great reasons to use these instead of an Apple TV.

1. You don't have to switch video sources. Your computer is already connected to your projector.
2. You can display multiple iOS device screens simultaneously. Although the programs support more than 2 devices, things start to get sluggish with 3, and downright choppy with 4 or more (I've had up to 5). Displaying multiple devices is a great way to compare student work from iPads.
3. They are a LOT cheaper. AirServer is $15 and can be installed on up to 5 computers (although you can't mix and match Windows and Mac from the single $15 purchase). Reflector is $13 per computer, or $55 for 5 computers. Reflector does have an extra feature that lets you record the video from your iOS devices.

I personally chose AirServer. I don't need to record the videos, and it is cheaper. If I decide I want to record the videos I can always use the SMART Screen Recorder (free if you have a SMART Board and SMART Notebook installed).