Skip to main content

Sonos Play:5

Over the holiday season I was looking for a speaker with a decent sound quality, and good support for playing music wirelessly. With a bit of research I settled on the Sonos Play:5 speaker. Most of the online reviews were favorable, and it supported streaming online music from Spotify, Pandora, and a dozen other services. The speakers were also on display at Target stores for a live test, and despite the background noise in the store, they sounded great. Sonos was running a promotion at the time, where you got a free bridge with the purchase of any of their speakers, which is a decent discount.

Setup was extremely easy. I plugged the bridge into my wifi router, plugged the speaker into a power outlet, and installed the Sonos application on my computer. The application guided me through the intuitive setup, which involved pressing a button on the bridge, and another on the speaker to connect the whole system together.  After that it was time to play music.

The Sonos application imports pre-existing music stored on the computer, including these managed by iTunes, in addition to providing streaming service through online providers. The application manages the streaming, so you have to provide your username and password to the application, and it streams music on your behalf.

I tried Pandora--the free account, and despite the low bit-rate the music was great. For Spotify premium--high bit-rate--the sound was amazing.

The application includes nice features such as a timer, and an alarm, as well as the easy control of multiple speaker groups, and defining speaker stereo groups. The app also has versions for the iPhone and the iPad that provide the same functionality as the desktop app.

I am very pleased with the sound quality even with one speaker, and I would highly recommend it. And perhaps by the next holiday season I would have added another one.



Comments

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...