On Thu, 8 Sep 2011, Jay Ashworth wrote:
> ----- Original Message ----- >> From: "Rob Landry" <[email protected]> > >> I worked for many years at WCRB, a classical music station in Boston. It >> was common to have multiple recordings of the same piece of music on our >> playlist, and I used an external database to keep track of them. I wrote a >> Perl script called "Dada" to schedule the music and keep track of the >> broadcast histories of the pieces. > > Ah yes. You guys used to put me to sleep. :-) We still can (for different values of "we") if you move to Cape Cod or southern Rhode Island. >> In my database, I had a file called "Composition" containing one record >> for each piece of music in the playlist, and another file called >> "Recording" with one record for each recording. The thirty-odd recordings >> of Beethoven's Symphony No. 9 each had their own separate Recording >> record, but all were tied to a single Composition record, and the >> broadcast history was kept in a third file, "Progdet" (for "Program >> Detail") indexed by Composition number. So, all the recordings of >> Beethoven's ninth symphony shared a common history. > > I'm curious: did you use the Phonolog keys for those fields? (Is Phonolog > still in business?) Or did you make them up yourself? The keys were integers assigned in MySQLvia via AUTO_INCREMENT. > I assume you scheduled compositions, and actually *aired* recordings. No, we schedule[d] recordings. Different recordings of the same composition can vary in length by as much as several minutes, so it's usually the case that only a specific recording of a piece will fit in the schedule. But once that recording is scheduled, all recordings of that piece are disqualified until its rest period expires. Rob _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
