The Sony SMP-N200 (or SMP-N100) is the only streaming player you need; eschew the Roku!

After much searching, buying, and evaluating, I'm convinced that the Sony SMP-N200 (or maybe the older SMP-N100 if you can find it) is probably the best streaming device you can buy. Well, it's at least the best value streaming device you can buy (under US$80). It does everything that a Roku device does plus a little more and is substantially cheaper when you compare apples to apples. The only thing you really lose is the ability to watch trailers in the Amazon Instant/Video-on-Demand application. However, trailers are available in basically every other movie app plus a Flixster application with plenty of trailers.

For US$66.99 on Amazon (and US$69.99 on Best Buy) at the time of this post, you get:

• HDMI output for full 1080p video and 5.1 channel audio
• Optical audio output (if your receiver doesn't do HDMI audio)
• Analog audio output (via RCA connectors)
• Composite video output
• Component video output
• Wired ethernet support
• Wireless 802.11b/g/n support built-in
• USB port (videos, pictures, music)
• DLNA client (and maybe server for that USB?)
• HDMI wake-up (i.e., device turns on and off automatically based on HDMI signal; moreover, this behavior is configurable if you don't like it)
• Very thin and simple remote control powered by a watch battery

  People say this remote is an improvement over the one that came with the old SMP-N100 model, but I disagree. For one, the "Home" button is too close to the down arrow. More importantly, the old remote control was quasi-universal in that you could program it to your TV and it would control your TV's volume, power, and video input. So I basically only need one remote with the SMP-N100 to do everything.

• Android phone and tablet remote control apps
• iOS remote control app
• ...probably more that I overlooked because I personally didn't care

With all of that hardware support, the device is great for a wide variety of home theater systems (e.g., with old TV's or old receivers). You can contrast this with the more expensive Roku that has an HDMI output and a composite output. Those people with older receivers and/or older TV's are not going to enjoy all of the advanced features of modern streaming content on a Roku. This is not as much the case with the Sony players.

And the applications that come on board the Sony SMP-N200 include:

• Hulu Plus (and free Hulu via PlayOn over DLNA, but see CAVEAT below)
• Amazon Instant/Video-on-Demand (although the app doesn't play trailers)
• Vudu (albeit without "Vudu Apps" but with full "Vudu Movies" support, including trailers and promotional credit)

  FYI, the current US$5.99 promotion for signing up a device works even if you've already signed up other devices; so you can keep adding promotion credit to your account... even if you end up returning the device

• Netflix
• YouTube
• CinemaNow (which looks to be a similar selection as Blockbuster On-Demand) – Note that the application is included but currently it tells you that it's "coming soon" when you start it up
• Pandora
• Slacker
• Sony Entertainment Network's Video Unlimited (yet another on-demand streaming service)
• Sony Entertainment Network's Music Unlimited
• Flixster
• DLNA sources (e.g., PlayOn and everything it supports, including free Hulu; CAVEAT: I own a Sony SMP-N100, and I haven't had trouble using PlayOn the few times I've tried. When I tested an Sony SMP-N200, PlayOn worked at least for the few minutes I tested (if I recall correctly), but I've heard that people are having issues with PlayOn now.)
• ...plus a lot more that I just don't care much about (e.g., streaming from Berliner Philharmoniker)

For some reason, Amazon Instant/Video-on-Demand was not advertised anywhere on the box or on the Sony website like it used to be. However, the application still exists on the device. Despite it being the same application that is used to access Sony's own "Video Unlimited" service that supports movie trailers, the Amazon app has no trailer support. That's frustrating and makes me think that Sony has been given financial incentive to de-emphasize Amazon over its other providers. One of those providers includes Vudu, which is provided by the full-featured Vudu application you get on every other streaming device (minus the "Vudu apps" support you might see on a Blu-ray player). Regardless, if you're OK with getting your trailers elsewhere, this is a fine selection of applications. UPDATE: As of a recent software update on my Sony SMP-N100 (and so also likely on the Sony SMP-N200), trailers are available now in the Amazon VoD app. So it is much nicer now to browse for movies within the single app.

And if that's piqued your interest, you should also take a look at the previous model, the Sony SMP-N100. It is nearly identical to the SMP-N100 except that it lacks support for a few providers, of which the only one you should care about is Vudu. It still has Netflix, Hulu Plus, Amazon Instant/Video-on-Demand (no trailers though), DLNA (which means PlayOn too), Crackle, YouTube (but no movie rental support), Pandora, and much more. However, it sells for at least US$20 less (so US$49.99 on Amazon (same price at Best Buy) at the time of this post) because the new version exists.

So if you're looking for a nice streaming player for a good value, I think most people will point you at the Roku. However, the Sony players (both the SMP-N200 and SMP-N100) are cheaper and do more. The interface is not as clean and cozy as Roku though. Moreover, it might be annoying to you that you cannot play Amazon video trailers. However, trailers are available through lots of other services, and there's a lot of value to having them all on one device (as opposed to having, say, Vudu on your Blu-ray player and Amazon VOD on your Roku).

Spotify, Google Music Beta, and Amazon Cloud Player? My choice is probably Google Music Beta

Between Spotify, Google Music Beta, and Amazon Cloud Drive/Player, I have had the most fun with Google Music Beta.

So Spotify is weird and uncomfortable. It’s cool that I can get easy access to lots of music that I don’t actually own, and it’s easy to make playlists. However, it is ugly to be able to both shuffle your whole library and put songs in multiple playlists without risking over-representing them in your shuffle. Over-representation is generally a major problem if you create artist playlists because one artist might have a whole bunch more songs in the Spotify database than others. It would be nice to “shuffle artists” where you’re guaranteed a balanced selection of artists (e.g., in every set of 30 songs)… What’s worse on Spotify is that playlists are static. You might be able to create an artist playlist, but you have to watch out for new songs to add to that playlist. Be careful though – songs get duplicated in a playlist if you drag them over. Having said all of that, I certainly have had fun discovering new music with Spotify. The interface is ugly though, and it sucks to have to pay $10/month just to have Linux access (yes, I know I can use Spotify through wine for free now (and $5/month later when the free accounts become limited), but I hate dealing with the headache of local MP3’s and the wine codec). Moreover, if I want Android access, I’m stuck with $10/month too. Boo.

Google Music Beta had an easy upload process. It took a while, but not that long. It was strange that it bogged down my entire Internet connection (while Amazon’s uploader didn’t affect my downstream at all), which makes me wonder what else Google is doing. However, I could select all of my songs on my Linux machine (no fancy Windows uploader needed) and they all got uploaded. Unfortunately, I cannot download them (unless I make them available offline on my phone and then figure out where and how Google stores them, which may not be tractable). Also, I cannot figure out how to buy new music (certainly a feature for the future, right?). However, Google randomly adds free music to my library, and that’s cool. What’s coolest is the Instant Playlist feature (which is similar to features in iTunes and other players/services) that builds a good-sized playlist from a single song. I’ve enjoyed its picks – even when the song I seeded lists with came from a local artist that it couldn’t have known much of anything about. Best of all, Google Music Beta gives me all of this for free (up to 20,000 songs) on all of my systems (including Android). I never need to worry about keeping a Windows machine.

Amazon’s Cloud Drive/Player is cool that it gives you 5GB for free and then $1/year/GB up to 1TB after that (starting at $20/year for 20GB). For the moment, if you pay for any storage, you get music storage for free. Any Amazon MP3 purchases can be placed directly in your library. Any song in your library can be downloaded. So Amazon’s Cloud Drive is a nice archival and music management solution. Almost all of the cool features of the player work on all systems. The only downside is that the MP3 Uploader (which re-organizes your music into Artist/Album/Song and will allow you to select a batch of thousands of songs to upload at once) is only available in Windows (and Mac?). On a Linux machine, you can use the web uploader from Amazon’s Cloud Drive, but you can only upload contents of one folder at a time (with no subfolders) and you have to organize everything manually. No one has figured out how to automate this through a script as far as I can tell. The Windows uploader does a pretty good job sitting in the background, and it’s safe to interrupt it in the middle of an upload (however, it may take a while building your upload list when you re-start it). The Amazon Cloud Player is fine. You can build playlists of your music, which is fine. You can shuffle. You can’t discover new music, but you can easily grow your library at 50 to 99 cents a song.

[ Oh, and all three will scrobble to Last.FM. It’s supported natively in Spotify (with no support for “Love”), and it’s supported with 3rd-party Greasemonkey scripts (for Firefox and Chrome (and Safari?)) for Google Music and Amazon MP3 Player. ]

Tools for combining BibTeX, PDFs, and e-Readers

Quick links:

• fix_pdf_tags BibTeX+PDF+e-Reader management script
• bibtex_to_pdf Mercurial repository

UPDATE: If you are looking for a simpler solution that updates PDF's in your BibTeX database with the corresponding BibTeX data, check out updatepdf.pl. Be careful though; the old PDF::API2 module only supports Adobe PDF 1.4 (i.e., compatibility-mode PDF's).

UPDATE: Apparently, you can also manage your Kindle collections efficiently using emacs, using Calibre, or manually so long as you're okay with possibly having to reboot your Kindle after every change. So it would be possible for me to add Kindle collections.json support to my fix-pdf-tags script; I just don't anticipate having the time to do that in the near future (plus, I don't own a Kindle anymore, and so I wouldn't be able to test it).

In trying to migrate to e-Readers, I've been experimenting with both the Amazon Kindle 3 and the Sony Daily Reader PRS-950. They both have nice features... I don't have time to go into a review, but I'll give a teaser...

• Kindle PRO's: It has a nice web browser (that works on 3G too!), and makes it super easy to get new content onto the device. In fact, you can even download PDF's from Dropbox via the nifty browser (although e-mailing to your Amazon Kindle e-mail address is convenient too). Plus, Amazon makes for a nice e-Book store -- lots of the books I would want.
• Kindle CON's: However, PDF's really have to be in compatibility mode (Acrobat 1.4). Otherwise, the Kindle will miss all of the metadata. More importantly, it is basically impossibledifficult to manage collections through the USB. So if you have hundreds of PDF's, you'll spend days tagging them via the clunky Kindle keyboard.
  • UPDATE: Apparently, the Kindle uses a simple SHA-1 hash of the file's full path as a key in the collections.json file that is accessible via USB. Consequently, you can manage your collections data more efficiently. You can do so with an emacs script or with a calibre plugin or manually. However, you may have to reboot your Kindle every time you make a change. At least with the older Kindles, the collections.json file was only read on boot. It's possible that the newer Kindles are smart enough to refresh collections data every time the USB is unplugged (like the Sony does), but I honestly don't know. I have a feeling that Hannes, the author of bibtex-kindle, knows though.
• Sony Daily PRO's: It has the optical touch screen. It doesn't require compatibility-mode PDF's. It has a large screen. It has terrific page viewing options. In theory, the PDF note options are very nice, but e-Reader notes just seem tedious to me in general regardless of interface. More importantly, it is essentially an "open" platform so long as you are OK with a little bit of reverse engineering. It is easy to write a few scripts to manage your XML files, and so keeping your PDF's organized is easy for your average script kiddy.
• Sony Daily CON's: The optical touch screen means the screen is sunk down so far that it the chassis casts a small shadow around the edge of the screen. The Sony case-with-light isn't as nice as the Kindle's case-with-light. The Sony Bookstore doesn't have as many books (or at least the books I care about). The zoom modes leave much to be desired. In PDF's that work fine on the Kindle, trying to click a word for dictionary lookup often leads to selecting a phrase (and there's nothing you can do about it).

And there's plenty more to talk about, but those are the quick things off the top of my head. So it looks like I'm probably going to keep both... so I can have a diversity of e-Books available to me. Plus, the e-Book experience is a little nicer on the Kindle, but the PDF experience might be a little nicer on the Sony. It's hard to tell.

But what this post is really about is a utility I've put together that automatically manages my research PDF collection on either the Kindle or the Sony Reader. In particular,

• It updates PDF's with metatags to match author/editor/title information from a central BibTeX database.
• If you invoke it with a "kindle" argument, it converts PDF's to 1.4 so the Kindle can read the metatags.
• If you invoke it with a "reader" argument, it also automatically generates categories based on file hierarchy (i.e., the folders in which your PDF files live). In fact, symbolic links indicate that multiple tags should be applied to the same file (i.e., the target of the symbolic link).

So maybe that will be helpful to someone (at least as an example to generate some ideas). The project started out as something customized for me, but I've tried to make the documentation clear (see the chunk at the top to start). Plus, most of the important custom information (paths, preferences, etc.) are at the top of the script.

Check out the most recent version of my fix_pdf_tags script; it resides in my bibtex_to_pdf Mercurial repository where you can view its change history.

P.S. I know that Calibre is an existing software package that has very similar aims and a nice graphical environment. However, it really is a poor choice for managing PDF research. Plus, the Calibre folks have basically written off Kindle users as poor schmucks with hobbled readers. More importantly for me, I'm much happier with scripted solutions that can be fired off quickly.