[ID3 Dev] Whole Album Tags

[Brian Mearns]

Thanks to all for the advice, I've been seeing all the traffic for CHAP 
and CTOC, but for some reason never looked at it (sorry). Now that I 
have, I'm very excited about the potential for these frames, I think 
they're going to be very powerful, and especially useful for live 
recordings. I think they'll also be exactly what I was looking for with 
my original post about album databasing.

After just a quick read through of the most updated published spec (rev 
3, 25.10.05), the only thing that really stuck out to me was a question 
about the heirarchical nature of the CTOC frames: should this structure 
be a tree, or is a graph feasible? The essential difference (as I'm 
describing it) is that if a graph is allowed, then a CTOC could 
reference another CTOC as it's child, which could re-reference the first 
CTOC as it's own child (actually, "neighbor" if we're talking about 
graphs). If you're familiar with Categories in Wikipedia, you should 
know what I mean. These can be mutually nested, but do not actually form 
a tree. I don't know of a real life situation in music where this would 
be required, but I do know that in a lot of different tree-based work, I 
often find the tree restrictions (as opposed to graphs) aggravating.

Just a thought, wondering what people think. I probably won't be working 
on my database (where I'll be using the CTOC and CHAP frames) for a 
while yet, but when I do, I'll make sure to post any question/comments, 
etc. on the evolving format.

-Brian Mearns

Chris Newell wrote:
> At 06:04 22/11/2005, py.thoulon at gmail.com wrote:
> 
>>Looks like a job fit for the newly define CHAP and CTOC frames. Check <http://www.id3.org/develop.html>http://www.id3.org/develop.html, under "Work in progress".
>>
>>Pyt.
>>
>>On 11/22/05, Brian Mearns <<mailto:bmearns at coe.neu.edu>bmearns at coe.neu.edu> wrote: 
>>I'm interested in constructing a data base of my record collection using
>>ID3 format. My plan is to just create a file for each album, the only 
>>contents of the file would be an ID3 tag with the album's meta data. I
>>want to set it up so that the entire tag contains all the data for the
>>album, plus a frame for each track which contains any necessary meta
>>data for that track, including possible "overrides" of the data in the
>>album (parent) tag (For instance, the album may have a certain composer,
>>but one particular track has a different composer.)
>>
>>I was just curious if there was any existing structure for something 
>>like this, or if anyone's came across anything like it before.
> 
> 
> Brian,
> 
> I agree with Pierre that this is an ideal application for the newly defined Chapter Frames.
> 
> I've created a tool for creating these Frames which is available from: http://id3v2-chap-tool.sourceforge.net
> 
> However, you have to bear in mind that the specification is "work in progress" and these frames are not yet supported by any Media Players.
> 
> Any feedback you have about the utility of the Chapter Frames would be very welcome
> 
> Chris
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dr J.C. Newell
> Digital Media Group, BBC Research & Development
> Kingswood Warren, Woodland Way, Tadworth, Surrey 
> KT20 6NP  UK
> mailto:chris.newell at rd.bbc.co.uk      http://www.bbc.co.uk/rd
> Tel:   +44 (0)1737 839659
> Switchboard:   +44 1737 839500
> Fax:  +44 (0)1737 839665
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~           
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org