This document discusses the need for an independent radio station to track playlists for licensing purposes and proposes a solution called LaForge that uses Musicbrainz and Picard to automatically track songs played. Currently, DJs at WRPI track playlists manually which results in slips getting lost and shows not getting fully tracked. LaForge matches songs to their PUID identifiers to look up metadata and log playlists without manual input. The status update notes integration of listening and logging is upcoming while basic fingerprinting and metadata retrieval is currently functioning through Libofa and Musicbrainz.

1. LaForge: Playlist Tracking for
Independent Radio
Tom Buttner, RCOS Rookie

2. Playlist Tracking
● Required for license
● “Top 40” charts
● Tracking period: 2 – 4
weeks / semester
● A big pain in the
ASCAP

3. The User
● WRPI's Djs currently
track playlists by hand
● 1 Song at a time
● Small “tracking slips”
submitted for each 1
to 2-hour show
● Compiled by hand
● Slips get lost, shows
go untracked

4. Picard, PUIDs, and Musicbrainz
● Heavily influenced
by Musicbrainz
Picard
● Adds two pieces:
listening and
logging
● LaForge isn't
Riker, but he's
definitely bridge
crew (and “Data” is
a lousy name for a

5. Libofa and Time Resolution

6. Project Status
● Coming soon: ● So far:
● Integrate listening ● Libofa library used to
● Integrate logging create fingerprints and
obtain PUIDs
● Make it robust
● PUIDs used to query
● Deal with libofa time musicbrainz and
resolution issue retrieve metadata
– Smarter listening
● Discovered libofa
– Try to change libofa restrictions on time
resolution

7. Thanks To
● Sean O'Sullivan, Moorthy, and RCOS
● Tim Horton
● Musicbrainz, MusicDNS, Lukas Lalinsky, Philip
Wolfer, and the rest of the Picard development
team