A few years ago, someone under the name Gelano created a program called My DVD Settings.  Among other things, it took the DVD Profiler Collections.xml file and created individual DVDXML files, named according to the name of the DVD.  These are NOT the same as the File/Export Database/Individual Files option in DVD Profiler: the Profiler naming convention is to use the System ID as a name, and the contents of a DVDXML file is basically ONLY the System ID (DVD Profiler creates XML files containing all the metadata).  DVDXML files are very useful for users of Vista Media Center (and perhaps other systems) in that they let VMC pull metadata automatically.

The old homebrew app has not been maintained, and it would seem to be a very easy option to add to the Export Database option within DVD Profiler.  If you want, I could send you a copy of the original My DVD Settings app.

Thanks, Todd

Sure, here's an example for Akira:

<?xml version="1.0" encoding="utf-8" ?>
- <Disc>
  <Name>Akira</Name>
  <ID>3E56E2F7|F552D236</ID>
  </Disc>

Like I said, the file only contains the name of the DVD and its System ID.  You can go to www.dvdxml.com for more information.  I just randomly checked several of my files, and the format is exactly the same for all of them.  Only the name and system ID vary.  The file name of this file would be Akira.dvdid.xml.

Todd

Wow, that was fast and unexpected!  And it's ALMOST perfect ;-) .  I don't feel like I have any right to ask for more, but he goes.

It's not exporting all the entries in my database, and I think I know why.  It looks like you are using the disk text in brackets [] after the disk ID in DVD\Edit\Discs as part of the identifier (LabelSideA tag in the XML).  For example, you are inserting this text into the title.  But if the text is the SAME across disks, it will only output one of thoses discs.

For example, there are two discs for movie "Foo".  Disc IDs say something like 1234567890ABCDEF [FOO] and 9876543210FEDCBA [FOO].  It looks like you would only output one of these, and its filename would be Foo_FOO.dvdid.xml .  I think you need to search on all valid disc IDs and ignore the subsequent text in brackets [].  I would prefer if you simply appended a sequential disk number to the filename.  So in this example, call them Foo_1.dvdid.xml and Foo_2.dvdid.xml.

Related problem: you appear to be missing Side B completely.  Again, I would just search for a valid disc ID in all possible entries under DVD\Edit\Discs.  So perhaps we name the above files Foo_1A.dvdid.xml and Foo_2A.dvdid.xml instead to keep the coding simple.  Had "Foo" been a double-sided disc instead, then the names would be Foo_1A.dvdid.xml and Foo_1B.dvdid.xml.

Finally, I notice that it outputs files without a valid disc ID.  I would just skip it in that case.

Like I said, this is more than I expected, so anything you decide to do is gravy for me.  Thanks again for this!  I wish I had kept up on my coding skills.

Todd

Absolutely awesome--thanks very much!  This does exactly what I need.

The only remaining issue is not one that your program should address, but should be handled at the database entry level.  If two discs have exactly the same name, one will get overwritten.  Out of 815 discs in my collection, this only mattered for 8, and so I'll edit those to make them unique in the database.  I'm posting this only for those who want to use the tool besides me, to point out that this is how the tool ought to work.  Anything the tool would do to handle identical names would be somewhat arbitrary, or make it unnecessarily complex.

Again, thanks very much!

Todd