On Oct 12, 2017, at 12:36, Lorne Tyndale <[email protected]> wrote:
> One question I have - is there an option to have the playout content
> details of the resulting audio file available somewhere? I'm thinking
> of something like a playout log - something with the start and end time
> of each track in the resulting file (or cart/cut),
> title/artist/additional info, etc.
You can get much of this information now by supplying the --verbose switch when
invoking rdrender(1).
> Something like this would seem to be very useful for situations where
> one station is generating programming for use on other stations, such as
> syndication type situations. One could just generate a log of a
> programme, render the log to a single audio file, and then you'd have
> your single file along with a track list for distribution.
>
> An XML file would probably make the most sense for this - similar to the
> XML files that can be generated with RDExport.
I agree that generation of a separate manifest file containing the details you
mention would make a lot of sense. Embedding it into the audio file begs the
question of how to structure the containing data chunk. To just say ‘XML’ is
not a sufficient specification; what DTD should be used? Are there any tools
out there already that are capable of reading such data? We could just write
the whole thing as a text block (say, into the TagText structure of a
CartChunk), but are there other, more structured, formats that would make more
sense?
Cheers!
|----------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|----------------------------------------------------------------------|
| You can never tell which way the train went by looking at the |
| tracks. |
| -- Kramer's Law |
|----------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
