OT: (maybe) Web Radio

[Sivakatirswami]

I'm interested in web radio. I know there is a lot of software out there 
that does this, but I'm thinking with iRev engine and a little savvy 
coding and it should be easy as making sweet lassi to build a web radio 
station.

But, I'm totally ignorant and I suspect it would be silly  to re-invent 
the wheel from ground zero. One should at least familiarize oneself with 
the various web radio frameworks that are successful today. At the very 
least it would clue you in to the varous CMS framework and existing 
functional specifications. These could them simply, be implemented using 
iRev... instead of PHP... Drupal and all his friends are scary!

 but some of the models are good ones... basic idea is: users tune into 
some URL and everyone is listening to the same tune. I'm already 
familiar with building podcasts, but only with a 1 per day rollover... 
if you have an announcer lead that is 20 seconds, followed by a 6 minute 
music bit, followed by a 40 second announcer lead; followed by a 20 
minutes first person interview.. how do you do that? Is it as simple as 
setting the time codes in the RSS items? Or is the another, better model 
for web radio than RSS?

Assume you have tons of audio content (we do) call them "tracks"   ready 
to roll and the ability to crank out high quality "canned" announcements 
and announcer leads (B) in advance for any given "track"... how do you 
put it all together? set up cron to kick in a lead+track by using an RSS 
type of model.. somehow you would need to know when the track was over, 
to start the next one... you want all users to be hearing the same thing 
at the same time... do a randomizer on a hit (easy to do) doesn't work...

I'm a flat file fan myself, but if a dBase will help, we can always do 
one.... (

Any one who is familiar with web radio and has a minute to chat with 
me... contact me off line. I need a little coaching on the terms, and 
best practices already hammered out by great ones before me. I would 
really appreciate it.

(I'm off to dig on the web, but I think there are some here that already 
are way ahead of me...)

Thanks
Sivakatirswami