Archive for the 'podcast' Category

Page 2 of 5

At last: car stereos with frontal mini-jacks

JVC car stereo with line-in
You need portable MP3 player for when you’re on the move. On the move includes: in the car. Why would you want to listen through tiny white earphones, if you have dozens of Watt of pure musical power already at your disposal in that car of yours? Or: how to connect your iPod to your car stereo.

FM Transmitter

First of all, they’re illegal in Belgium, so you can’t buy them anywhere here. Thanks to my numerous maffia friends however, I’ve been able to try 2 Griffins and a white-label gizmo, but my experiences have always been disappointing: impossible to tune right or get an acceptable sound.

Fake tape

There are these cassette look-alikes that you can put in your tape player. Only, who still has a tape player in his car? And what does the conversion electric-to-magnetic-to-electric do for your sound quality?

Custom interfaces

Alpine has a special solution for iPod (didn’t BMW have something like that too?), but we don’t like vendor lock-in.

Line/Aux in

  • One year ago I had already talked about Kenwood making car radios with line-in possibility. But Kenwood used the RCA jack on the back of the device, which might have been a good idea in a hifi-stereo world, but not so for portable audio players.I wanted a mini-jack, damn it, but no vendor had that.
  • But now: behold the mini-jack!
    - Sony has the CDX-GT200 (about € 130) and its bigger brothers CDX-GT300 and CDX-GT400 (not in Europe).
    - JVC has the KD-G612 (bout € 150) with “Front AUX Input”, as well as the KD-G510 or KD-ADV6160 (last one even plays DVDs)

I hope the rest of the vendors get the message and provide a frontal AUX in on their products. Car stereos, boomboxes, mini-chains, DVD players, DivX players, …
Rip, Mix, Plug it in!

Technorati:

Christmas present: podcast feed validator!

I get a lot of “what is wrong with my podcast feed?” kind of questions because I have written a fairly popular tutorial on podcasting with Blogger and Feedburner, and a lot of people start doing podcasts that way. There’s a couple of things that can go wrong:

  • Not a valid RSS feed
  • RSS feed without enclosures
  • Feed not updated when posting new article

To check some of those things, I needed to read and interpret the RSS feed by hand. That’s why I decided to make a podcast feed validator to do the checks automatically. Let’s take Adam Curry’s DailySourcecode podcast as an example:

  • the URL of the feed is radio.weblogs.com/ 0001014/ categories/ dailySourceCode/ rss.xml, so I input it into the input field and the results are:
  • #1: feed URL exists and can be reached
  • #2: feed is a valid RSS feed (but does not conatin the iTunes extensions),
  • #3: feed items have audio enclosure (but not all, as you see in the image below. The reason is that two enclosures are wrongly specified as text/html instead of audio/mpeg.)
  • #4: the audio enclosure (MP3 file) exists and can be reached

podcast feed validator
So the enhancements for this feed would be: make sure all enclosures have the right type, and provide iTunes meta data. Better still: use Feedburner to get that and more: subscriber statistics and lots of feed tools.

Try it out for yourself:
Check your podcast RSS feed!

Some more features of the podcast feed check:

  • estimation of mean-time-between-posts (MTBP), a metric I talked about in RFM for RSS feeds
  • estimation of required bandwidth/storage per month (DailySourcecode: 600MB/month, 175-25.be podcast: 10MB/month)
  • works with MP3 audio enclosures and AAC (MPEG-4) audio/video enclosures (any audio/mp* enclosure)
  • detailed (technical) information is hidden by default and can be shown through some AJAX functionality.

Technorati:

New podcast icons based on Firefox/IE feed logo

Original Firefox feed iconYou might have heard that the Microsoft IE team (and Outlook 12 team) is adopting the orange square ‘feed’ logo for its web feeds:

I’m excited to announce that we’re adopting the icon used in Firefox. John and Chris were very enthusiastic about allowing us (and anyone in the community) to use their icon. This isn’t the first time that we’ve worked with the Mozilla team to exchange ideas and encourage consistency between browsers, and we’re sure it won’t be the last.
(from blogs.msdn.com)

So I decided to update my previous podcast logos with the new graphic:
(If you want to use them, and need the HTML code to copy/paste, check my podcast icon wizard)

Simple icons

Podcast RSS (generic): Podcast RSS (generic)

Audio podcasts

Audio RSS: Audio RSS
Audio RSS (Apple iTunes AAC): Audio RSS (Apple iTunes AAC)
Audio RSS (MP3): Audio RSS (MP3)
Audio RSS (QuickTime MP4): Audio RSS (QuickTime MP4)
Audio RSS (Ogg Vorbis): Audio RSS (Ogg Vorbis)
Audio RSS (RealAudio RAM): Audio RSS (RealAudio RAM)
Audio RSS (Windows Media WMA): Audio RSS (Windows Media WMA)

Video podcasts

Video RSS: Video RSS
Video RSS (Windows AVI): Video RSS (Windows AVI)
Video RSS (DivX): Video RSS (DivX)
Video RSS (Quicktime MOV): Video RSS (Quicktime MOV)
Video RSS (Quicktime MP4): Video RSS (Quicktime MP4)
Video RSS (Quicktime): Video RSS (Quicktime)
Video RSS (Windows WMV): Video RSS (Windows WMV)
Video RSS (XVid): Video RSS (XVid)

If you want to know whyI don’t use the acronyms “RSS” or “XML” in the icons, check Web feeds are like RSS, only different.

Technorati:

RFM for RSS feeds: Recency, Frequency, Momentary Value

I’ve been throwing round an idea in my head for a while: how the RFM method for analyzing and prediction customer behaviour could be applied to RSS feeds (blogs, podcasts, …).

Recency, Frequency, Monetary Value – customer segmentation

What does RFM do: it analyses 3 parameters for each customer:

  • date of last purchase (recency)
  • # purchases per month/quarter (frequency)
  • average amount of money spent per purchase (monetary value)

It then does a cluster analysis of the numbers (or in the simple version: a marketing guy decides based on gut feeling) and defines boundaries for each parameter, in order to split them up into categories.

Example:
Recency: R1 is everyone who purchased in the last 2 months, R2 is everyone who bought in the last year and R3 is the rest.
Frequency: F1 is every customer that purchased on average 3 or more times per quarter, F2 purchased at least 1 time per quarter and F3 is the rest.
Monetary Value: M1 are those who purchased more than �500 per visit and M2 are the rest.

In this scenario you have split up your heterogeneous customer group into 18 (3×3x2) more or less homogeneous subgroups that you can address in different ways. Your supercustomers R1-F1-M1 don’t need the same approach as the R3-F2-M1 (the big spenders that haven’t been around to your shop in the last year). And you hope you can predict the behaviour of each customer by analyzing his past behaviour.
(Side note: I learned this stuff while working in Sopres for Stefaan Vermeiren, who’s now teaching the Kiwis to do online banking)

RFM for RSS – feed segmentation

 

Now how would this work for RSS feeds?
RFM analysis for RSS feeds

  • Recency: date of last post
  • Frequency: average # posts per month, or mean-time-between-posts (important is that you only take into account the period from the first to the last post: if the feed contains 1 item per week but the last one was 1 year ago, the frequency is still 1/week i.e. around 4/month)
  • Momentary Value: (I know ‘momentary’ is not a great term, just couldn’t come up with a better 4-syllable alternative for ‘monetary’ yet) this is the most creative part: you can count the # of words, # of links, # images, filesize of the podcast audio or the video file, …

What can you do with this kind of statistic? Well, I see some applications:

  • is a blog ‘alive’? when do you decide if a blog is no longer active: it will be a combination of recency and frequency. If someone posted 1/week and there has not been any activity for 2 months: probably (momentary) dead. If someone posts 1/quarter and no activity for 2 months: perfectly normal. In statistic terms: calculate mean-time-between-posts MTBP and standard deviation STDEV. If the last post was MTBP days ago, there is a 50% chance that the feed is no longer updated. If it is (MTBP + STDEV) days ago, then the chance is 84%. (MTBP + 2 * STDEV): 97%, etc …
  • what kind of blog is it? if average # words/post is low, and # links per post is around 1 (and frequency is 1/day): it’s probably a linkblog (like e.g. bnox). If the #words/post is high, the MTBP is 1 month with a very low STDEV, it is probably a monthly newsletter.
  • do I have time for this blog? Now you subscribe to a blog without an idea of how often the author posts, and how long the articles are. With an RFM analysis, the blog could be marked as ‘low traffic’ (2 posts of 500 words per month) or ‘high maintenance’ (60 posts of 300 words per month).
  • how much data does this podcast deliver? There is a big difference between a show like DailySourcecode (about 20 podcasts of 40MB per month: 800MB/month) or IT Conversations (2 posts/day of 14 MB each: 840MB/month) and a humble effort like my Mash-up podcast (2 to 5 posts per year of 4,5MB: 1,5 MB/month). For a mobile device, where storage and bandwidth aren’t so readily available (nor cheap), this is an important distinction.

This RFM analysis could be done by a company like Technorati, Bloglines or Feedburner, and they could combine it with language, location, topic and popularity stats to create an excellent segmentation of blogs. Or if someone feels tempted to set it up?

Let’s get rid of podkeyword.com

Bad wake-up call: theregister.co.uk reports on Erik Marcus, a podcaster who has had his podcast feed hijacked by Podkeyword.com (no link, you know why). Why am I concerned? Guess under what name my Smoothpod Mashup podcast is registered in iTunes?

What is podcast hijacking

(…) it merely involves finding a target podcast, and creating a new unique URL for it on a website you control. You then point your URL to the RSS feed of the target podcast. Next, you do what it takes to make sure that as new podcast search engines come to market, the page each engine creates for your target podcast points to your URL instead of the podcast creator’s official URL. (Colette Vogele)
So years can go by and then the hijacker strikes: At some point, [the hijacker] can then spring out of the woodwork and demand payment from [the] target [podcaster].” The podcaster is “supremely vulnerable”, because the hijacker can at any moment change URL pointer to any other show of the hijacker’s desire and the target podcaster’s audience will “vanish.” (corante)

So someone provides a mirror service for your podcast feed, gets it registered with major podcast directories and search engines and can then choose whether to just mirror your feed, alter it (e.g. insert advertising), or replace it by whatever he feels like. That, in short, is the businessplan of podkeyword.

Who is behind podkeyword?

Some research shows that a George Lambert from Nashua (NH) is the owner of podkeyword.com (registered in Oct 2004). He also has Goldenware Travel Technologies (goldenware.com), providing airline timetable services (so he’s used to repackaging other people’s data). Another of his projects is cashcowmarketingplan.com, a spam-infested blog on “getting rich quick on the Internet”. This is worrying!

Let’s get rid of podkeyword

Here is what has to be done:

by every podcaster
check if you are affected: search for your podcast to see if it has been hijacked:
on iTunes: subscribe to your own feed because you won’t be able to see the actual feed URL unless you’re subcribed. If it’s a podkeyword URL, click the “Report a concern” button and tell Apple this is a wrong feed URL, give them the right one.
on Yahoo: search for it and if both your real feed and the podkeyword feed are present (I found 2 podkeyword feeds for my own podcast), give the hijacked ones a bad review (give it 1 star and write a review about the hijack)
by every podcast directory/search engine (iTunes, Yahoo, you listening?)
restore hijacked feeds (Remark: the following is NOT real code, just some pseudo code to clearly explain what should be done)

for $victimFeedURL in (*.podkeyword.com feeds){
# get the content of the feed
$victimFeedXML=getHTTP($victimFeedURL);
#every feed contains the URL of the homepage
$victimSiteURL=ParseRSS($victimFeedXML,"channel.link");
#get the HTML of the homepage
$victimSiteHTML=getHTTP($victimsiteURL);
# get the URL of the feed the author has specified
$victimRealFeed=parseHTML($victimSiteHTML,
"head.link('application/rss+xml')");
if($victimRealFeed  "" AND $victimRealFeed  $victimFeedURL){
#replace *.podkeyword.com by real feed URL
$victimFeedURL=$victimRealFeed;
}
}
by Feedburner (since they are an important podcast feed provider)
detect the feeds that are being queried by podkeyword (I don’t see them showing up as a separate UserAgent in my Feedburner stats, but Eric Lunt and his gang won’t have too much trouble finding them anyway) and (a) warn the feed owners that they might be hijacked, (b) offer the feed owners the option to include an extra post in their feed to alert their subscribers to switch to the real feed.

Doesn’t Feedburner do the same kind of thing?

Not at all. Feedburner also mirrors and alters RSS feeds but there are some really big differences:

  1. Feedburner is not evil. That is my opinion and I might be wrong, but I’ve had contact with Feedburner on several occasions and they seem to be a bunch of intelligent and down-to-earth geeks. Plus they have found a way to make money with Feedburner without taking advantage of people.
  2. Feedburner has added value: they convert a feed to a valid podcast feed, they can splice different feeds together, they provide essential stats.They deserve their place as a middleman.
  3. Most importantly: I have voluntarily chosen Feedburner as my service provider! I configured it myself and I added the Feedburner RSS feed link to my blog’s HTML template. On the other hand, I didn’t contact podkeyword, I have never asked them to do anything for me.

Technorati:

Filling a terabyte iPod

Muster said that within five years, Apple could release an iPod with one terabyte of storage — that’s almost 17 times the maximum amount of iPod storage Apple currently offers.
Munster envisions a one terabyte iPod as a portable, “coffee table” media center that would allow users to store hundreds of movies and thousands of photos and songs.
cnn.com

A 1000 GB iPod, that is

  • 200 movies or 370 hours of full quality DVD
  • up to 2000 hours (almost 3 months non-stop) at DivX/Xvid/MPEG-4 quality
  • using the H.264 video compression: 120 days or 4 months of video!
  • 1500 music albums of full quality CD (which means, no Sony XCP)
  • 15.000 albums if your rip/compress them to MP3 first, maybe 20.000 if you use WMA/AAC (that is over 2 years of audio to listen to!)
  • 2500 episodes or 100 seasons of TV series like Lost, L-Word, Desperate Housewives, Sopranos, … in compressed format (hey, it’s a 2,5″ screen, who cares about HD?)
  • If your terabyte iPod breaks down and you buy a new one, it will take you between 3 hours (FireWire 800 Mbps) to 2 days (Wifi 802.11g) to fill it up again (from the backup you of course had put on your snug little home 10GB RAID-5 storage cluster thingy).
    If by then all portable devices have 10-Gbit Ethernet built in: 15 minutes will be enough to fill ‘er up.
  • Our then-standard 48 megapixel camera would create 72MB RAW images, of which the iPod could store 14.000, or if you would compress them to 5MB JPEG: 200.000 pictures.

Other predictions: the iPhone (or Apple as mobile virtual network operator) and the iTIVO, a media-center/time-shifting/TV/video/DVD hub , all in the next 12-24 months. Let’s hope this inspires some people to seriously vamp up their design/user interface teams (Nokia, Microsoft, I’m looking at you!).

Technorati:

Adam Curry goes 100% podsafe


Adam Curry, godfather of podcasting, has had an epiphany:

I was told – maybe I should say … threatened is not the right word – but ‘promised’ that they (the music/broadcasting companies) are gonna come after podcasters, and they’re gonna shut them down. What was implied, is that they were going to shut podcasting down.
(at 9:58 in DSC-275-2005-11-07.mp3)

So he did not take this ‘promise’ lightly and got rid of all his licensed music.

11:10 Wondering why certain episodes of DSC are not in the archives? Adam has been contacted by several Dutch representatives of international music services tell him “hey, this file’s on your server, it’s licensed music, get it off there.” Adam has removed episodes with such songs on there. Adam has even “cleaned” his computers at home of every possible mp3, and now has only podsafe tunes on there. Adam will not play any non-podsafe song on the DSC. No more Mashups. If it’s not on PMN, it doesn’t get played.
from Daily Sourcecode Show Notes

Adam was actually in Brussels while doing that podcast, visiting some European Parliament contacts. He is concerned that the music industry could get a European directive passed, making sure that there will be no way for podcasters to play licensed music, no reasonable priced yearly/monthly license. Playing commercial music is only for the big boys.

So Adam’s reaction is: “Scr*w you, we’ll make you irrelevant”. Don’t know if it’ll work, but it’s a big step.

Once they get to know new artists in the free-and-legal bag they aren’t reliant on music which can only be shared in the underground, but getting them over the hump is not so easy: they have to hang around long enough to absorb new sounds and stop being disappointed that they can’t have the old ones. With Adam and the many podcasters he influences on board, we have a good shot at breaking through.
from Lucas Gonze’s blog via beatmixed

I am still before that hump, I’m not ready yet to throw out all my RIAA/IFPI licensed music. There’s just to many memories linked to music I have. Long Hot Summer, I Keep Forgettin’, Knocks me off my feet, That Night, these songs mean something for me, I cannot switch completely to podsafe music. Yet.

Technorati:

“Lost” in iTunes: good and bad news


There’s good news and bad news. First the good: Steve Jobs just issued a wake-up call to the movie industry. He already has shown everyone how to sell music (fixed price, basic DRM, no limits on burning) and hopes to do the same with video. The new iPod video looks great, and is clearly gonna end up on my desk in the near future.

Continue reading ‘“Lost” in iTunes: good and bad news’