<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">As a sidenote, that's pretty much why I was never willing to get into<br>
Audible. MP3 had already been around for AGES, why the heck would I pay<br>
for something that uses a custom player? That's just ridiculous in this<br>
day and age - and even in the day-and-age it was 5 years ago.<br>
<br></blockquote></div><br>My understanding is the Audible format is MP3 in a DRM wrapper and some extra stuff for chapters markers, resume where left off, etc. that had to be implemented to make an experience equivalent to or superior to books on tape. <br>
<br>Audible's proprietary <em></em>format and DRM has yet to get in the way of enjoyment as long as I have a device that supports the Audible format. Audible makes its SDK available to device makers, it's up to the device maker to build in support. $20 a month for 20-40 hours of fiction or non-fiction isn't a bad deal. Much better than what's on the radio most days while driving to and from work. :) <br clear="all">
<br>That's the way technology works. Sometimes you get stuck with a legacy solution that was created before a standard was created or achieved wide adoption, or overcoming the inertia of of a solution (Flash Player anyone?) is extremely difficult. <br>
<br>-- <br>Andrew S. Zbikowski | <a href="http://andy.zibnet.us">http://andy.zibnet.us</a><br>IT Outhouse Blog Thing | <a href="http://www.itouthouse.com">http://www.itouthouse.com</a><br>