[RDD] Synchronizing carts and logs

Fred Gleason fredg at paravelsystems.com
Tue Jun 14 13:23:08 EDT 2016

On Jun 14, 2016, at 07:57, drew Roberts <zotzbro at gmail.com> wrote:

> http://www.wavpack.com/ <http://www.wavpack.com/>
> "Uses ID3v1 and APEv2 tags for metadata (including ReplayGain)"
> Would that get us there?

ID3v1 is very consumer- and pop music-oriented, and thus is missing many of the fields that are relevant for broadcasters —e.g. Agency and Client.  APEv2 is more intriguing inasmuch as it includes a mechanism for extending the field definitions, however, it does not seem to enjoy very wide support.

Here’s an idea: what say we embed a copy of the relevant ‘cartList’ XML object (such as is currently generated by Rivendell's ListCart Web API call) in every file export?  I see a number of advantages to this approach:

1) XML is a widely-supported format, with high-quality FOSS parsers available for virtually every major programming language.

2) The format is human-readable and would be largely self-documenting.

3) The same parser code that reads cartList objects via the web interface would also work here with little modification.

Likewise, we then extend Rivendell’s import tools (RDImport and RDLibrary) to parse this same data structure, thus giving us a high-fidelity path for transferring both audio and Rivendell cart/cut metadata between systems.

For reference, here is a sample of the cartList object:

*** snip snip ***
    <title>American Pie</title>
    <artist>Don Mc Lean</artist>
    <album>100 Hits Party Classics</album>
          <description>Cut 001</description>
*** snip snip ***


| Frederick F. Gleason, Jr. |              Chief Developer             |
|                           |              Paravel Systems             |
|          A room without books is like a body without a soul.         |
|                                         -- Cicero                    |

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://caspian.paravelsystems.com/pipermail/rivendell-dev/attachments/20160614/a1a402b7/attachment.html>

More information about the Rivendell-dev mailing list