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.

Conference Adventures - CANHEIT 2013

CANHEIT is a conference for Canadian Higher Ed IT folks and was held in Ottawa, Ontario earlier this month. It was my first CANHEIT, and it was quite different from most of the educational technology conferences I normally attend. I definitely see value in events where people with so much in common can gather to share ideas and look for solutions to problems that their peers also have or have had. Unfortunately, CANHEIT is heavy on the "IT" and light on the "HE".

Many sessions at CANHEIT 2013 focused on the centralization of IT services. The theory is that a single, centralized support team can satisfy the needs of the entire university. By centralizing services, duplication of work is eliminated, therefore costs are reduced. Faculties and departments negotiate terms of service, and perhaps have someone from Central ITS designated as project manager.

The first problem is the belief that there is a duplication of services. It would appear that Central IT leaders don't understand that departmental IT staff are working on solutions specific to their own faculty/department. The second problem is that while there may be a designated project manager, that does not mean they are a dedicated project manager. The project manager will often be assigned to multiple departments and faculties. Finally, when talking about "terms of service" it often refers to simple services like printing or software problems. Larger projects are put in a central queue, and the project manager may actually recommend that specialized or urgent projects be contracted out.

CANHEIT also served to highlight that there is a significant disconnect between IT staff, faculty, and students. In one classroom oriented session led by a faculty member, the presenter explained that he developed his own project because he knew if he didn't, "some jackass in IT would do it and screw it up". Few sessions were actually about services that support or improve teaching and learning. There was little discussion around what faculty are trying to do in their classrooms and what could be done to support them.

Little annoyances with Windows 8

I've already expressed my displeasure with Windows 8, but the little annoyances just never seem to stop.

One of the only things that I don't mind working full-screen in the new Window 8 way (and I do mean "Window") is the media player. That is until an update. After updating, a message "Sign in" would permanently appear in the top right corner. It could not simply be "canceled" to make it disappear. I had to go through the steps to create an Xbox music account to make the message go away.

I know that I could seek out other media players, but this is exactly the type of stuff Mac users make fun of Windows user about. I just want basic things to work. I don't want to spend time trying to find a media player that doesn't piss me off, or to create an account I'm never going to use just to be able to use the included media player without an annoying message on the screen.

Another annoyance perhaps isn't completely Microsoft's fault (but I'm sure they deserve some of the blame for it) is the broken Intel WiDi in Windows 8. Intel's Wireless Display won't work with the Windows 8 drivers. You actually have to use Windows 7 network drivers to get it to work. It's hard to believe that the driver model changed so drastically between versions 7 and 8 that a manufacturer as big as Intel can't get a feature to work, but clearly that is the case.

I'm not quite done yet. The bluetooth controls for Windows 8 are ridiculous in that they aren't "controls" at all. Double-clicking the bluetooth icon opens up the device panel listing all devices (not just the bluetooth ones). You can click on a bluetooth device in the list, but it doesn't actually do anything other than a press animation. You can't right-click on it to tell Windows to connect to or disconnect from the device, or control the bluetooth options for the device in any way.

Several times I've thought to myself, "Did anybody at Microsoft actually use Windows 8 before releasing it?"

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).

Conference Adventures - CONNECT 2013 Poster Session

I have never presented at a conference. I guess I still haven't really, but I did lead a poster session at CONNECT 2013. Although there weren't many visitors to my space, it was very interactive and quite rewarding. My session was about using AirPlay in the classroom, something that is rarely as easy as setting up an Apple TV at home. I will cover my own discoveries and solutions in another post, and hopefully it will help others as well.

After describing the problem and walking through the steps for my solution, I was told it addressed the very problem a school had been struggling with for a long time. In fact, it offered up even more than simply getting AirPlay to work from a single iPad.

There were a lot of things to like about CONNECT, but helping a teacher solve an annoying problem felt great.

Conference adventures

CONNECT 2013 was an amazing experience, although it was tiring. I can only imagine what it was like for the folks from the District School Board of Niagara who also had UGC on the weekend before.

Although I will share more about my experiences related to educational technology at the conference, the first thing I want to talk about is shoes. That's right. Shoes.

I knew I would be on my feet a LOT, and that some of the events during the conference would require me to be dressed more formally. I really did not want to wear dress shoes all day, nor did I want to have to carry around and worry about an extra pair of shoes.

I went shopping last week and bought some Clarks' Pickerton black leather slip-on shoes. They are incredibly light, very comfortable, and just formal enough for some daytime meetings and luncheons. That reads a lot like an ad, but considering just how many hours I was on my feet from Sunday to Tuesday, I am amazed that my feet are not killing me today.

Wireless display done right... and wrong

I have experimented with a variety of wireless display gadgets over the years. About 15 years ago I purchased a kit that included a transmitter and receiver for RCA video, allowing me to watch DVD movies from the brand new DVD drive in my computer without running a bunch of cables across the room. I have been looking for something that works as well as this did ever since.

In June 2011, Apple announced AirPlay mirroring. At first glance, this is wireless display technology done right. For most people, it just plain works. Plug in an Apple TV, get it on your wireless network, and then just search for it on an Apple device capable of mirroring. It really is that simple. Well, except for when it's not.

The first problem with AirPlay is that it is exclusively for Apple devices. For many educators, that's not really a big deal. I'm sure there are countless teachers who are completely within Apple's walled garden. The second problem (and yes, regardless of how Apple wants to spin it, it is a problem) is that the whole device discovery falls apart when used on a network that is designed to support more than just a couple hundred devices (like the networks typically used in schools). You can have your iOS device and Apple TV on the same network, but no matter how hard you try, sometimes they just can't see each other. There are workarounds out there, but they depend on supported IT infrastructure and configuration by IT staff. I'm sure many educators have already blamed their IT staff for not "working with Apple" to get AirPlay working. Let me be clear here. Apple is to blame. They wanted to beat the WiFi Alliance to the punch and rushed out a protocol that was not well thought out.

In January 2011, the WiFi Alliance announced WiFi Direct Display. WiFi Direct Display would show up in various news articles over the course of nearly two years (including being rebranded as Miracast) before any devices based on the standard would be available.

Miracast does not depend on your existing wireless connection. A Miracast transmitter and receiver setup a completely separate WiFi connection using an existing method known as WiFi Direct (thus the original name of WiFi Direct Display). This is truly where Apple went wrong with AirPlay.

So, Miracast is wireless display done right, right? Well, maybe.

Google announced Miracast as a feature of Android 4.2. This was wonderful news, although it was quickly discovered that even one of Google's newest tablets, the Nexus 7, doesn't support Miracast despite running Android 4.2. Even now, many months since the release of Android 4.2, only a handful of devices are actually available that have Miracast capability. None of the devices that I have access to fall into that category.

Intel obviously thinks Miracast is the way to go. With version 3.5 of WiDi, Intel has added Miracast compatibility. I do have a laptop that supports WiDi 3.5, so I picked up the Netgear P2TV-3000, a Miracast receiver. After installing all the right drivers in the prescribed order, I had absolutely no luck getting it to work. After several hours of trying various installation and connection options and methods, I stumbled on a page that had the answer. I had to uninstall the Windows 8 Intel WiFi drivers (from my Windows 8 laptop), and install the Windows 7 drivers. Sure enough, this worked (even though it shows an error every time it connects). While I was happy to have it working, I doubt that most people that walk into a Best Buy to purchase the P2TV-3000 would actually go through all of this hassle.

I suppose what I find most remarkable is that there really shouldn't be anything particularly challenging with implementing an open wireless display standard that works. Device discovery and pairing protocols have been used for decades. Encryption protocols have also been around for a very long time. Audio and video encoding and decoding have been hardware accelerated for a few years now, even on handheld devices. These are the pieces, and yet everything still seems to be a struggle, and it feels like it's just one software update away from getting broken.

How strange is it that the wireless transmitter and receiver from 15 years ago is by far easier to setup, and more reliable than anything we have now?