Even though this video is a blatant ad for Ford Focus, it nonetheless shows what I have been talking about. The built in stereo Bluetooth receiver allows you to establish a stream on your phone (assuming your phone has a data plan) and then play it back through the car speakers.
As a side note, it would be interesting to do some testing on the interaction between the low-quality of the Bluetooth codec (SBC) and low-quality streaming codecs like Windows Media audio. In any case, the buzz is that SBC doesn't quite cut it, so folks like APT, Kleer, and Qualcomm are creating alternative wireless solutions. Both APT and Qualcomm aim to work over Bluetooth transport, which, in my view, makes them more attractive.
Showing posts with label internet radio. Show all posts
Showing posts with label internet radio. Show all posts
Wednesday, July 30, 2008
Friday, July 25, 2008
Lessons from AM radio
Why isn't Internet radio more widespread? (both inside and outside the car.) I have heard a number of theories. Too many codecs, too many formats, lack of bandwidth in mobile, etc. However, all of these theories are actually details obscuring an underlying reality.
For Internet radio to become truly widespread, it needs to "just work." The consumer needs to be able to power on, turn the knob, and have good sound coming out. If they don't like what they are hearing, they need to be able to hit the seek button to find something more to their taste. That's it, it needs to be that simple.
Before all the technologists yell foul and complain that that Internet radio is too complex for this to happen, let's look at AM and FM radio. The consumer experience of AM and FM radio is exactly as I describe above, but a lot of moving pieces had to be fixed down before it could happen. AM and FM are complex, they just don't feel that way due to good standardization.
Although first broadcast in 1906, AM didn't become commercially viable in North America until standards were set for carrier amplitude, modulation frequency range, channel spacing, and overall carrier frequency ranges for receivers. This standard stood alone for 30+ years until FM arrived and presented another selection of standardized components which added up to a complete solution. As a result, over 80 years later, we can still turn on an AM radio, tune the dial, and enjoy the broadcasts. You don't need a different type of radio for every single station.
For Internet radio to reach the same robust level, we need a unified standard which covers connectivity, discovery, directory, transport, and playback. The good news is that the nature of the beast already gives us a standard for connectivity, TCP/IP and UDP. Now we need to get to the brass tacks of the remaining items.
Disovery: Internet radios need to have a kind of global UPnP, which makes it automatically aware of relevant directories. It may be as simple as a directory of directories maintained by ICANN, but that's just a quick guess. And the problem remains, who gets listed and in what order? This may be the most difficult part since it needs to be truly neutral for it to work across all vendors and broadcasters.
Directory: Internet radios need a standardized way to get a list of stations which are available. Also that list needs to have some kind of globally relevant set of sorting and grouping tags.
Transport: Once we know what streams are available and where they are, we need a limited set of ways to get access to them. HTTP "Shoutcast" is the most widespread transport method used today, but it doesn't do well in lossy environments like mobile/car. RTSP is used by 3GPP and in IPTV and works great for mobile, but it isn't widely used by today's Internet radio. Although the purists (and you know who you are) wouldn't like it, any standard will need to support both transports. We would also need to implement a standardized backchannel interface for services like Pandora, which takes user preferences into account.
Playback: Now that we have the stream unwrapped, we need to put it out over the speakers and on whatever display is available. That means we need an audio codec. Given its widespread use, MP3 is probably required here. However, the content fees put forward by Thomson coupled with the recent lack of clarity around MP3 patent ownership means that this could be an issue. MPEG-4 HE AAC v2 is the standard in mobile and is also used by Shoutcast. Given its open-standards nature, its bitrate efficiency, and clear patent pool, HE AAC v2 should also be fundamental. Beyond codec, the playback standard also has to have a fixed methodology for metadata presentation, including album art and even advertising.
The parts needed for a true Internet radio standard are nearly all off the shelf. Existing solutions can be quickly adopted or tweaked to match the needs. The only real barriers will be in compromise, cooperation, and will power. Once we come together and establish such a standard, then Internet radio can truly blossom, be free of the PC, and be as ubiquitous as AM & FM.
For Internet radio to become truly widespread, it needs to "just work." The consumer needs to be able to power on, turn the knob, and have good sound coming out. If they don't like what they are hearing, they need to be able to hit the seek button to find something more to their taste. That's it, it needs to be that simple.
Before all the technologists yell foul and complain that that Internet radio is too complex for this to happen, let's look at AM and FM radio. The consumer experience of AM and FM radio is exactly as I describe above, but a lot of moving pieces had to be fixed down before it could happen. AM and FM are complex, they just don't feel that way due to good standardization.
Although first broadcast in 1906, AM didn't become commercially viable in North America until standards were set for carrier amplitude, modulation frequency range, channel spacing, and overall carrier frequency ranges for receivers. This standard stood alone for 30+ years until FM arrived and presented another selection of standardized components which added up to a complete solution. As a result, over 80 years later, we can still turn on an AM radio, tune the dial, and enjoy the broadcasts. You don't need a different type of radio for every single station.
For Internet radio to reach the same robust level, we need a unified standard which covers connectivity, discovery, directory, transport, and playback. The good news is that the nature of the beast already gives us a standard for connectivity, TCP/IP and UDP. Now we need to get to the brass tacks of the remaining items.
Disovery: Internet radios need to have a kind of global UPnP, which makes it automatically aware of relevant directories. It may be as simple as a directory of directories maintained by ICANN, but that's just a quick guess. And the problem remains, who gets listed and in what order? This may be the most difficult part since it needs to be truly neutral for it to work across all vendors and broadcasters.
Directory: Internet radios need a standardized way to get a list of stations which are available. Also that list needs to have some kind of globally relevant set of sorting and grouping tags.
Transport: Once we know what streams are available and where they are, we need a limited set of ways to get access to them. HTTP "Shoutcast" is the most widespread transport method used today, but it doesn't do well in lossy environments like mobile/car. RTSP is used by 3GPP and in IPTV and works great for mobile, but it isn't widely used by today's Internet radio. Although the purists (and you know who you are) wouldn't like it, any standard will need to support both transports. We would also need to implement a standardized backchannel interface for services like Pandora, which takes user preferences into account.
Playback: Now that we have the stream unwrapped, we need to put it out over the speakers and on whatever display is available. That means we need an audio codec. Given its widespread use, MP3 is probably required here. However, the content fees put forward by Thomson coupled with the recent lack of clarity around MP3 patent ownership means that this could be an issue. MPEG-4 HE AAC v2 is the standard in mobile and is also used by Shoutcast. Given its open-standards nature, its bitrate efficiency, and clear patent pool, HE AAC v2 should also be fundamental. Beyond codec, the playback standard also has to have a fixed methodology for metadata presentation, including album art and even advertising.
The parts needed for a true Internet radio standard are nearly all off the shelf. Existing solutions can be quickly adopted or tweaked to match the needs. The only real barriers will be in compromise, cooperation, and will power. Once we come together and establish such a standard, then Internet radio can truly blossom, be free of the PC, and be as ubiquitous as AM & FM.
Thursday, April 10, 2008
IP radio = standard car option?
Sorry to disappoint, but I don't see Internet radio as being a standard feature in US cars anytime soon. However, that doesn't mean that the use of Internet radio in the car won't become widespread. It will just take a different path.
Legal requirements for handsfree operation of phones while driving is pushing adoption of Bluetooth in the car. Conversion kits will give way to standard option Bluetooth, likely with A2DP (e.g. stereo audio) support. This means that instead of native devices, the route for Internet radio into the car is a docked cellphone.
The choice of Bluetooth connecting docked phones is also driven by the economics of alternative solutions. To have widespread adoption, you need a standard. Yes, MPEG-4 HE AAC over RTP is the standard for streaming Internet radio to vast millions of mobile phones. However, the means of getting IP connectivity to the car are varied, causing the need to purchase some kind of custom device for each carrier. If you are going to spend money on a new connection device, why not just dock the phone in the car? I know there is growing interest in 3G to WiFi routers out there which will make your car a roaming hotspot using a 3G dongle or PCMCIA card, but that still doesn't solve the last 3 feet problem of connecting to the car speakers.
A final driver for the Bluetooth A2DP route is that the 3G carriers in the USA don't have a consumer friendly business model for non-voice device connections. In other regions (e.g. Japan), device makers can release a data-only device which uses the wireless data network. I have also heard of these kind of devices in the EU, using GSM for remote monitoring applications. However, the dynamics of the US market don't seem to go that way. WiMax won't cut it, even if it gets deployed. WiMax only works in metros and people want a radio that works at least nationwide - you would need 3G and 2.5G support in the radio. My Sprint or AT&T music phone will that criteria just fine and my flat rate data plan on those phones is $15/month.
Bottom line, unless the carriers make a joint push with device makers for a data-only IP radio and a standards body approves the profile (3GPP in cooperation with NAB would be a good choice), docked phones using A2DP are the most likely near to mid-term scenario. The only real downside with this solution is that the SBC codec used by default on A2DP phones has quality issues. For IP radio, though, the benefit of getting the stream you want will definitely outweigh this quality limitation.
Legal requirements for handsfree operation of phones while driving is pushing adoption of Bluetooth in the car. Conversion kits will give way to standard option Bluetooth, likely with A2DP (e.g. stereo audio) support. This means that instead of native devices, the route for Internet radio into the car is a docked cellphone.
The choice of Bluetooth connecting docked phones is also driven by the economics of alternative solutions. To have widespread adoption, you need a standard. Yes, MPEG-4 HE AAC over RTP is the standard for streaming Internet radio to vast millions of mobile phones. However, the means of getting IP connectivity to the car are varied, causing the need to purchase some kind of custom device for each carrier. If you are going to spend money on a new connection device, why not just dock the phone in the car? I know there is growing interest in 3G to WiFi routers out there which will make your car a roaming hotspot using a 3G dongle or PCMCIA card, but that still doesn't solve the last 3 feet problem of connecting to the car speakers.
A final driver for the Bluetooth A2DP route is that the 3G carriers in the USA don't have a consumer friendly business model for non-voice device connections. In other regions (e.g. Japan), device makers can release a data-only device which uses the wireless data network. I have also heard of these kind of devices in the EU, using GSM for remote monitoring applications. However, the dynamics of the US market don't seem to go that way. WiMax won't cut it, even if it gets deployed. WiMax only works in metros and people want a radio that works at least nationwide - you would need 3G and 2.5G support in the radio. My Sprint or AT&T music phone will that criteria just fine and my flat rate data plan on those phones is $15/month.
Bottom line, unless the carriers make a joint push with device makers for a data-only IP radio and a standards body approves the profile (3GPP in cooperation with NAB would be a good choice), docked phones using A2DP are the most likely near to mid-term scenario. The only real downside with this solution is that the SBC codec used by default on A2DP phones has quality issues. For IP radio, though, the benefit of getting the stream you want will definitely outweigh this quality limitation.
Sunday, July 1, 2007
Success with Sprint Power Vision
May 2006 - I dumped Verizon and got a new contract with Sprint. I had Verizon for over 3 years, but Verizon plays control freak on their network and won't even let you browse to HTML sites off the deck, let alone stream live audio content.
Sprint, on the other hand, gives you unlimited 3G Internet, including streaming, on the phone for just $15/month (Power Vision Access plan). Sure, that price doesn't include Sprint TV, or the other bundled content, but I didn't want that stuff. I just wanted the pure, sweet nectar of free flowing Internet. Sprint delivered. Also, since the EVDO network was just being rolled out in the major metros, the bandwidth would be the real thing.
Since I am a music lover, I purchased the Samsung SPH-A920. $149.99 with a two year contract. Similar phones available now are much cheaper (more on that in a later post.) The cool thing is that all Sprint Power Vision EVDO phones are 3GPP enabled, complete with aacPlus audio. This means that if a content provider knows their stuff, the streaming audio won't sound like it is underwater or coming from a tin-can.
Sprint, on the other hand, gives you unlimited 3G Internet, including streaming, on the phone for just $15/month (Power Vision Access plan). Sure, that price doesn't include Sprint TV, or the other bundled content, but I didn't want that stuff. I just wanted the pure, sweet nectar of free flowing Internet. Sprint delivered. Also, since the EVDO network was just being rolled out in the major metros, the bandwidth would be the real thing.
Since I am a music lover, I purchased the Samsung SPH-A920. $149.99 with a two year contract. Similar phones available now are much cheaper (more on that in a later post.) The cool thing is that all Sprint Power Vision EVDO phones are 3GPP enabled, complete with aacPlus audio. This means that if a content provider knows their stuff, the streaming audio won't sound like it is underwater or coming from a tin-can.
Phone in hand, the next step was connecting it to the car. Since my 2002 PT Cruiser still has a cassette deck (yeah, I know...), I could use a $10 cassette adapter. However, I still needed to connect it to the phone. This is where things get tricky. I needed an adapter to go from the 2.5mm stereo/mic jack to a common 3.5mm (1/8") stereo jack. Sprint didn't carry them at the time, but luckily I was able to pick one up from the local Cingular store.
Adapter in hand, I connected the phone to the car, typed the Groove Salad url into my media player, and blammo, I had high-quality, untethered, Internet radio right in my car! The quality was even better than most XM Radio channels and I didn't have to pay an extra subscription. Listening to streaming radio drained the phone's battery, but a $30 car charger solved that problem. Very nice!
Not bad for May 2006. However, looking at my feature list for the Ideal Internet Car Radio, a couple problems remained:
- EVDO wasn't yet deployed wide enough for reliable listening over long distances.
- The phone was over $99.
- Available free content was pretty limited.
- Tuning into a radio station was pretty painful. (send yourself an SMS from the PC, or manually type in the URL. How do I text in a 'slash' again...?)
Fast forward to Summer 2007. Thanks to Sprint, EVDO now covers all major population areas and major transportation corridors. Thanks to Samsung, Motorola, Nokia, and Sanyo, aacPlus 3GPP-enabled phones are available for much lower prices. Thanks to Tuner2, there is a single point of tuning for high-quality Internet radio on the mobile phone. The content list isn't huge, but it is growing. And in the next couple of months it will grow like crazy once stations catch on to the untapped audience. Using Tuner2 mobile on my A920, today I drive around Southern California enjoying Internet radio, free and clear.
Things are looking good, but all is not sun and roses. In the next posts I will share some specifics about my LA driving tests, a long-distance drive through farm country, share a longer list of compatible phones, and talk about some issues you may encounter connecting the phones to your car.
-fred jackson
Saturday, June 30, 2007
Off to the races
So what is this all about? Since XM burst on the scene in 1999, I have been dreaming of the day when Internet radio would arrive in the car to give the satellite radio duopoly a run for its money. My first experiment was to take a spin around the parking lot at 241 Polaris Avenue, Mountain View, listening to my WiFi laptop through the car speakers.
Worked OK, but the range sucked!
Sprint and Verizon 1xRTT data cards soon arrived on the scene. Those had better range, of course, but the data hand-off was miserable, so driving down the road didn't work so well. Also, who wants to futz with a laptop on the passenger seat?
Smart phones arrived, but they are not a true mass market device and are notoriously short on standards-based multimedia features. Windows Media may be fine for the PC (for some), but stream it over a wireless network and it not only sounds bad, but cannot maintain a reliable stream.
So, now that I have ranted on what doesn't work, let's talk about what will work. The features of the Ideal Internet Car Radio are:
This list quickly eliminates a lot of hyped stuff. Slacker fails, iPhone fails, Sansa Connect fails, and anything that only supports WMA or MP3 streaming fails.
The good news is that the list is now satisfied by a number of phones from open-minded carriers like Sprint and AT&T/Cingular. I have conducted experiments using these phones and the results are pretty amazing. More on that soon.
-fred jackson
Worked OK, but the range sucked!
Sprint and Verizon 1xRTT data cards soon arrived on the scene. Those had better range, of course, but the data hand-off was miserable, so driving down the road didn't work so well. Also, who wants to futz with a laptop on the passenger seat?
Smart phones arrived, but they are not a true mass market device and are notoriously short on standards-based multimedia features. Windows Media may be fine for the PC (for some), but stream it over a wireless network and it not only sounds bad, but cannot maintain a reliable stream.
So, now that I have ranted on what doesn't work, let's talk about what will work. The features of the Ideal Internet Car Radio are:
- Receiver device is an off the shelf, consumer device ($99 or less when purchased with a plan)
- Device supports standards-based mobile streaming (3GPP) out of the box
- Device comes with a low-cost, unlimited, 3G data plan
- Can access free radio (without additional subscription) from anywhere on the net.
- Can connect to the car audio.
- Can connect to car power *while* audio is connected (don't want to drain the battery!)
- Works reliably for long times & distances (can commute without significant hiccups)
- Does not need a special antenna.
This list quickly eliminates a lot of hyped stuff. Slacker fails, iPhone fails, Sansa Connect fails, and anything that only supports WMA or MP3 streaming fails.
The good news is that the list is now satisfied by a number of phones from open-minded carriers like Sprint and AT&T/Cingular. I have conducted experiments using these phones and the results are pretty amazing. More on that soon.
-fred jackson
Subscribe to:
Posts (Atom)
