>> And the scanner/API has to be written to cope with different schemas. >No, that's exactly what the scanner does not have to do. The scanner >just reads (all) tags and stores them. There's just one base schema >used for the database and tag storage. > Something will have to read the tag content at some point to convert into data that's used for browsing/display. If not the scanner (which currently has much logic for grouping songs onto an album, then it will be something else). i.e. the scanner may be simple - read the content of file tags, and store in some generic table. Then something else takes that data and build application-aware data structures from it.
I'm trying to keep an open mind, and hold judgement until some code has been produced and compare performance, but if there are issues by then it's probably too late to change direction. Phil _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
