Revisions/Modifications to Playlist Entry

it was great to get to talk to you on the phone about this and i think i've got a system in mind that'll do a good chunk of this. i like the idea of a unified log of events (show begin, played track, played track, show ends, show starts). from which you're able to determining a record of what program played when and build playlists of the track events.

hey just a quick link in responce to the icecast stuff. here´s what i´ve managed to come up with in terms of using the station.module to automate a radio station. it uses mpd as a streaming client and a simple python script actually calls the programs a the correct times with checking in case the program starts late. the live content actually comes from other streamings . participants in the project publish their own streaming url when they publish their url, and the script loads the apropriate url for the given time. station.module patch and script are in the link. i´m fairly new at this sort of thing, so certainly their are improvements to be made.

station module patch and script are here:
http://drupal.org/node/79968#comment-237098

Here's part of a proposal I worked up for WSUM. I don't know if they'll end up sponsoring it but I wanted to make the

Overview
This project will revamp the playlist functionality of the Drupal Station module to provide a system for DJs to record information about
the songs they play as they play them. This information is used for several purposes:

• Logging and licensing purposes (i.e. future use in SoundExchange reports)
• Displaying current and recent songs on WSUM's website
• Broadcast metadata (RDF for radio and ID3 for Icecast stream)

Data Entry
DJs will be presented with a form allowing them to enter the following details for each song:

• Artist name
• Track title
• Album title
• Label
• A URL
• The time it began playing
• Musical genres

Additionally the system will record:

• The DJ's id
• Time of posting
• The schedule their program is on

Automation software is used at times when no DJ is available and the songs it plays must also be able to be recorded. The module will not do the importing itself but provide a function to allow an external script to pass in data from the automation software.

DJs will indicate the first and last songs of their program. This time range will be used to create a playlist node which will be listed on their program's web page.

The admin needs to be able to who is allowed to post playlist entries. This should be done by specifying user roles and providing a white list of IP addresses or subnets.

Data Display
The station module's "Now playing" block will display the artist and title of the song with the greatest start time that is not in the future.

In addition to viewing the songs through the existing program playlist nodes, a page will be provided to enable listeners to view what was played at a given day and hour.

It would be great to be able to push the currently playing song title to the Icecast stream but I'm not certain it would be feasible. More investigation would be needed.

Migration
There needs to be a a migration path for WSUM's playlist history. Since this schema is based on the existing WSUM system this should be straight forward. This will be provided as a separate script that, because of it's custom design, will not become part of the official module.

Proposed database tables

• plays: play_id, schedule_id, user_id, artist, album, title, label, link, posted_timestamp, start_timestamp
• plays_term table: play_id, term_id
• playlist table: node_id, schedule_id, start_timestamp, end_timestamp

that intro sentence got cut off. it should have read: I don't know if they'll end up sponsoring it but I wanted to post it incase other groups were interested in sponsoring the work.