FLV vs. RSS – maintaining balance

Jon Udell made an interesting post about a screencast conundrum he’s having on his site, and JD felt I’d have opinions/guidance (usually more of the former… heh!). What are the best practices to support both browser-based playback of media content alongside RSS-referenced downloadable video files for alternate devices (iPod, PSP, iRiver U10/etc.)? I can only give my suggestions here as the subject is very open to preference/audience and other variables – but here goes.

Generally speaking- MP4 video/MP3 audio seems to be the most universally-supported across devices (although H.264 is gaining ground, it’s still got a ways to go). I also strongly favor – as you probably would have guessed – Flash Video for browser playback simply due to it’s ubiquity, it’s hard to argue with the installed user base. ;-)

How I would implement a solution for both delivery means, were I posting videocasts (which I’m not- yet), is largely akin to what I’ve done with audio podcasts on this blog in the past – use a Flash/SWF/FLV solution for in-browser playback, and point the RSS enclosure tag to the media file (in the case of audio- MP3) on the back-end so podcatching software can grab and manage it. Audio is easy- MP3 is an accepted standard between devices, browsers and Flash. However, FLV presents an issue in that it can’t play back outside a SWF wrapper (and although playback engines such as WimpyFLV exist for direct desktop playback of FLV files, they’re not available on alternate devices). So that being said, I’d recommend encoding an alternate MP4 version of my vidcast (MP4 video, MP3 audio) at 320 x 240 resolution (reasonably standard) for the download file referenced from my RSS enclosure tag.

Cellphones/handsets generally use the codec/playback engine supported by the handset itself, which is largely either Real/.3gp or .MP4, and you should also know that some devices (such as the miniscule iRiver U10) have fixed frame rates you may need to consider, particularly if you’re a video star in Korea. :) The U10’s 15fps requirement isn’t a bad one in general, as it’s thrifty on file size and not so horrible for general video. Your mileage may vary, though. What devices are your readers/listeners/viewers using, generally speaking? That’s a question you’ll have to answer for yourself.

So… that’s my initial response to the problem.
How are you – or more accurately, ARE you solving this problem today?