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.
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. "Dada" is still in use at World Classical Network, which is also a Rivendell user. The Rivendell database, like those of all other broadcast automation systems I've seen, is not set up to do this. You need to set up an external database. It's easy enough to do in MySQL, and you can use the Rivendell cart number as the Recording key. Don't put several recordings in a single cart. That feature is intended for rotating commercial messages, and will severely restrict your choice of music to play. Rob On Thu, 8 Sep 2011, Samuel Cifuentes-Favini wrote: > Hi. I am working on the duplicate cart names in my base. > Okay, a good solution that I have used several times is to put several > cuts in a single cart. > But I am faced with a problem: what do we do with data from the > "other"(s) cut(s)? > in the cart containing all the cuts, I lose the names of artists, and > all associated data (album name, composer, etc.). > how do you do with songs that have multiple versions or several interpreters? > > Sam > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
