New Media Initiatives Blog

For the installation of Worlds Away, we needed to find a way to show the YouTube videos in the gallery. If you’ve visited the show, you’d see the videos installed in a Rec Room in the center of the gallery, complete with green shag carpeting, faux wood-gain paneling, low ceiling and bean bag chairs. It looks very much like my grandparent’s basement, minus the musty smell. The videos are viewable on a CRT television set on the floor in the corner of the room. I built a custom interface to allow people to control the TV, play the YouTube videos over the internet, at a decent quality, without violating the YouTube terms of service, and being mostly mischief-proof.

If you want to be spared the details, here’s a video:

Or, view it in a browser. This opens a pop-up window, Safari suggested, since that what it was built for. Use the left and right arrow keys, enter and escape to navigate.

When we started the project, we looked into ripping the flash video files from YouTube and creating a DVD. Testing showed the quality wasn’t great, but passable on a standard-def CRT television. The big hang-up about a DVD based approach was that it’s expressly forbidden in the YouTube terms of service:

You agree not to access User Submissions (defined below) or YouTube Content through any technology or means other than the video playback pages of the Website itself, the YouTube Embedable Player, or other explicitly authorized means YouTube may designate.

While it’s one thing to just avoid agreements like this with a wink and a nod for one-off or personal use, it didn’t seem like a good idea to blatantly violate the terms of service for an installation that would be in the gallery for months.

We also discussed setting up a computer in the gallery and simply putting a web page on it thin a custom player and view the videos. We weren’t too happy with that idea either, since it didn’t really fit within the Rec Room concept in the gallery — my grandparents don’t have a computer in the basement. We also discussed putting a big plasma TV on the wall, more like a modern TV, and using a remote or some sort of a pointing device to select videos using a custom YouTube player. Again, this option seemed costly (no spare plasma screens sitting around) and not within the theme of the room.

What we wanted was something kind of like the Apple TV, except limited to the 12 videos we selected for the exhibition. Quick research revealed no way to lock down an Apple TV or limit it to a particular YouTube playlist, so that was out. But what about making a web page that worked in a similar fashion?

It is possible to make Safari work in fullscreen mode using Saft. And there are applications that work with the Apple Remote to set up custom events and keystrokes. A computer with the right video card can also go out to a TV. And a little javascript magic in the browser could pull it all together with fancy fade and scroll effects.

jQuery and Safari fun
I started with the web page. I already knew I wanted to use jQuery for this project, if possible. I’ve been using MooTools for a while now and I wanted to expand my horizons to include a second Javascript library (half kidding). Using a TV screen for a display limits the usable resolution to 640×480, so there is not enough room to display all the entries on screen at once. Instead, I found the jCarousel plugin that I was able to use to scroll the video information across the screen. JCarousel has a lot of hooks for various events, so it made it quite easy to plug in to. The second thing I’d need was something to show the videos on screen once selected. The thickbox plugin is a lightbox clone, and seemed to do the trick. I tied it all together with some custom event hooks for keystrokes and a some logic to keep errant keystrokes from triggering multiple videos, excess scrolling, etc. In the end, I found that using the arrow keys and esc and enter are the best. In Safari, if you use any actual letter keys, it will default to type ahead find functionality and interfere with the scrolling offset.

The interface is designed explicitly for Safari. Since this is a single computer installation under our control, I don’t have to worry about whether or not it works in IE or Firefox. I have no idea if it works in IE (ignorance truly is bliss), but it only half-works in Firefox. Firefox doesn’t want to load the flash player in Thickbox. I’ve experienced problems with Firefox ignoring the z-index on Flash elements in the past, so this is not surprising.

Remote buddy
Now that I had figured out how to deal with the browser, I had to figure out a way to have the remote interface with the browser by sending specific keystrokes for each button. After looking at several programs that do this with the Apple remote, I settled on Remote Buddy. It was the easiest to configure so that it would only work with specific applications. I configured it to send the left arrow key on left arrow press, right on right, enter on play and escape key on menu button press.

One problem with the remote was that our computer was an older mirror-door G4 tower, which does not have an infrared receiver. Thankfully, Remote Buddy supports third-party usb receivers, so I ordered one, and it worked like a charm. Microsoft does build good hardware.

Video out
Unfortunately, we weren’t able to track down a G4 that had S-video or composite out, so I also ordered a newer video card for that. We got an ATI Radeon 9200 which has an excellent control panel for TV-out settings, letting you manipulate all aspects of the size, stretch, overscan, etc.

Net connection
In this configuration, the videos stream in real time from YouTube’s servers. Our galleries have pretty good wireless saturation, and an airport card in this tower allows the machine to connect to the network. I spent some time looking into using Squid for caching the youtube videos, but it appears YouTube recently changed the way videos are embedded, using some sort of a time-based token in the URL, making caching difficult if not impossible. Another option would be to keep the videos loaded in the browser, but in a hidden element. However, since there’s no interface for controlling the YouTube embedded player with javascript, starting and stopping the player is not possible.

Putting it together
After connecting all these things, I cleaned up the interface a bit, changing the typeface to Avenir, choosing colors that worked better on the Television (don’t use white). I configured Safari to start in full-screen kiosk mode, which Saft enables. Safari and Remote Buddy were set to launch on login, and the machine is set to automatically log in. Additionally, I set up a simple shell script that checks each of them to make sure they’re running and if not, relaunches them. With relaunching the applications, it’s important to use the command-line version of Applescript, since that will cleanly deal with backgrounding the process and giving correct screen focus.

Doc Czypinski, who was the lead tech for installing the show, was able to figure out a way to glue a white plastic strip to the back of the remote. He was then able to cable the remotes to the gallery furniture so that they don’t walk away during the show.

Post-mortem
Now that the computer has been in the gallery for about a week, there are two things we’ve learned. First, visitors tend to expect things to be playing automatically on the TV, since that’s the way most media things are in galleries. When they do figure out they need to use the remote, they tend to click the big play button and not cycle through the videos to choose. I’ve attempted to help this by putting arrows on the screen to indicate left and right so that visitors know to use the arrows on the remote to scroll.

The second issue is that the wireless hasn’t been 100% reliable. As anyone who uses Wifi on a regular basis knows, it’s not always up 100% of the time, and the wifi in our gallery goes out once in a while. I’m looking at writing a script that will cycle the Airport card off and on if it looses connectivity, or displays a message on screen if there is extended connectivity loss. A wired connection would certainly be better, but the convenience of Wifi cannot be beaten.

Gallery photo by Cameron Wittig. Arm of Justin Heideman.

It is not often I find exciting Microsoft products on Slashdot, but there are exceptions to the rule. /. linked up a Popular Mechanics article on Microsoft Surface. Surface is a fancy multitouch table that Microsoft has been working on in semi-secrecy for a while. In addition to being multitouch, it also features proximity detection so it can talk to your phone (bluetooth) and camera (wifi) and other devices when you put them on the table.

Gattis took out a digital camera and placed it on the Surface. Instantly, digital pictures spilled out onto the tabletop. As Gattis touched and dragged each picture, it followed his fingers around the screen. Using two fingers, he pulled the corners of a photo and stretched it to a new size. Then, Gattis put a cellphone on the surface and dragged several photos to it -- just like that, the pictures uploaded to the phone. It was like a magic trick. He was dragging and dropping virtual content to physical objects. I’m not often surprised by new technology, but I can honestly say I’d never seen anything like it.

It looks and feels a lot like CityWall and some of Jeff Han’s work, but it does not appear that Han has worked with Microsoft. One of the notable differences between Han’s tables (which are pricey) and Surface is price. Surface is supposedly going to be on sale this year for $5,000 to $10,000. The article mentions commercial applications, but I would think that education and museums would also have a huge interest. While I wouldn’t be able to afford one for my home, $10,000 is a very accessible price point for a museum.

Whiz-bang aside, the table also reminds me a bit of Pac Man. I also wonder if it can run linux. I’m actually sure that when this comes out, there will be a linux distro that includes a Pac Man knock-off.

EDIT: Create Digital Music has some commentary, as does Chris O’Shea.

It’s hard to count the number of times I’ve been asked to explain the buzzword of the year “web 2.0“. I finally found an explanaition of the phenomena that makes more sense (to me). Ajit Jaokar took Tim O’Reilly’s principles of Web 2.0 and changed the order a little. I’ve found O’Reilly’s explanation complete but unweildy when trying to boil down this “web 2.0″ thing down to a simple couple sentences. Jaokar’s readjustment focusses our attention on outcome, not implementation and that makes all the difference in the world. So the next time Robin asks “What is this web 2.0 buzz about?” the answer could be as easy as “It’s about harnessing collective intelligence”.

source: O’Reilly Radar

Due to some scheduling conflicts at Museums and the Web this year we missed the workshop about STEVE, a tagging project for art museums, or to expand the acronymn, Social Terminology Enhancement through Vernacular Engagement. I’ve been scrounging around on the internet for notes on the presentation. All I found was this mention on the Powerhouse museum’s blog fresh + new. Luckily Günter posted a more complete set of notes earlier this year and there are two papers one on the project, one from D-Lib Magazine and one on the conference site

I does sound like a road we’ve been down before with the Word Association feature on our collection. Although that project was ahead of it’s time it remains sadly underused, for a variety of reasons. The STEVE project sounds like it has some real momentum and worth the extra reading, I’m sure you’ll see more on it here.

Edit:
Although the acronym mentioned above is fascinating, it is not official. The project itself remains officially acronym free.