> But because most of these data types are distinctly different, we
> should treat them differently. The only special case I can think of is
> music videos, but wmv/avi/ogm files have pretty different information
> in them so we'd have to use something else.
The idea of mmpython is to retrieve a common set of
information from these files. Hence using a common
table for wmv/avi/ogm would be feasible. If I would
layout the mmpython class structure into tables I
would do the following:
MUSIC
AV
IMAGES
DISCS / COLLECTIONS / PLAYLISTS (an aggregation of the
above)
AV would perhaps be divided into 2 tables for audio and
video tracks but that would require relations.
See the head of mmpython mediainfo.py for a common set
of attributes. (This set has already received some thinking
but we may have missed some attributes, which we should add)
For attributes that do not fit into the common set mmpython
uses 'tables' which are more or less just lists of key/value
pairs. There are tables for EXIF, IPTC and other additional
metadata. Since these are specific to a subset of media
files I don't know if we need to put them in a database.
l8r...
Thomas
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
