radio

Does anyone here have any ideas on how to put a 10-30 second promo in front of the audio played out using the 1pixel player in the audio module? The KBOO.FM pledge drive is coming up, and they'd like to add a small promo file just during the drive (not permanently part of the actual files).

I guess it could be done with a playlist, but before I try to write custom code, thought I'd look for a ready-made solution.

I posted this question here (http://drupal.org/node/231395) but got no response yet.

Thanks,

Roger

I'm cross posting this because until I came across the PEG space Birds of a Feather session at DrupalCon I had no idea that there were two Drupal groupsworking on the resource and scheduling problems faced by community broadcasts. The other group had camouflaged themselves by using the insider name of PEG instead of something I'd have recognized like Public Access TV. Hopefully this can serve as the catalyst to get the two groups cross pollenating.

Hey all,

Just launched Drupal install w/ Station for Penn State's student radio station The LION 90.7fm WKPS. Stop by the site (www.thelion.fm) if you get the chance, and please let me know if you have any advice/suggestions/comments (we have many more features and tweaks planned, but we wanted to change it from the old Wordpress site as soon as possible). No podcast server yet, but we're getting there...

A huge thanks to drewish and all devs for a great module,

Sam PL

PicoStreamer been working for me great for me, from the site:

"Here you can find PicoStreamer, a set of script to build your own Internet station.
Starting from the v.2.2 you can broadcast live video using Flash embedded source and player: internet broadcasting has never been so simple!
Main difference between PicoStreamer and other streaming software, is that you don't need to use a dedicated machine: a classic hosting space with Perl/PHP is enough to setup a true real LIVE web station."

I think I've spotted a flaw in my test installation for streaming & recording.
I'm using MuSE to stream and station archive's ripper.php and streamripper to store MP3 of each hour, both on the same machine. There's no connection to Drupal for now; I just need to record the radio's output as hour-long MP3 files.

But what happens if the connection to the network and so to the icecast server is lost?
MuSE isn't giving me any error messages, but the MP3 file that's being recorded on my hard drive has stopped increasing in size.

Is there a way round this problem?

I'm trying to set up a linux box to take care of our stream (and maybe our archiving too, but one thing at a time), and I've tried a few streaming applications but none of them quite seem to work.

ices0 isn't available for ubuntu
darkice isn't compiled with MP3 support
MuSE looks pretty cool, but when I tried it I only get options for OGG streaming, not MP3 (and lame is already installed)
... I'm starting to give up here :(

Quiero presentarle mi ultima creación en Drupal 5.2:

http://www.jurassicradio.com.ar/

Básicamente se trata de un website para compartir audios de Radio. Y el concepto es recuperar esos viejos cassettes que alguna vez grabamos, convertilos en formato digital, subirlos y compartirlos con los amantes de la radio.

El theme fue creado desde cero. Tiene un concepto muy claro, el cual es: escuchar, buscar y subir material.

Algunos módulos utilizados fueron:

. Views: para armar esas listas que pueden ver en El Ranking.

I know that this is not the primary focus here, but does anyone have any good data on icecast or shoutcast streaming server requirements (or a pointer to such data)?

If you've got any info on what you're burning relative to the number of simultaneous users, that would be helpful. Bandwidth is easy to estimate, but specifically, I'm trying to quantify the kind of CPU and memory requirements needed per feed for a reasonable quality stream, even if it's a ballpark (and some info on your server setup).

Thanks,

Roger

I've been cranking away on the station module's HEAD branch adding features. I've committed a patch that makes the station schedule into a node allowing multiple schedules to be created. I plan to do something similar for the archives before creating a 5.x-2.x branch.

The next big feature that I wanted to announce here is the Station Catalog module. I'd committed the initial code in November of last year but got distracted by other projects. In the last few weeks I've started working on it again with the goal of moving KPSU's Microsoft Access based album catalog online. I'm happy to say that it's finally reached a usable state and I'd like to start getting some testing and feedback.

At WSUM, we are currently using a double install of Drupal with the station module.  The first install is installed at our ISP [dreamhost] for public consumption.  The second install is on our in-studio server.  The difference between WSUM's dual install and KPSU's dual install is in the hosting of the archived audio files.  At KPSU, Drewish has set up the archive hosting on the studio machine in anticipation of bandwidth and storage issues with the ISP.  Since Dreamhost offers free hosting for non-profits as well as good storage and transfer limits, WSUM rips the audio with the studio install and then posts the complete file to the ISP for import.  This avoids the need for public access to the studio install and allows us to set a longer retention limit for the local audio archives than the 2 week legal limit.  This setup has led to consideration of additional purpose to the studio install.