Personal Video Database

Thanks for your immediate answers. Not only a nice app, but fast support, too...

So, if it is MediaInfo, that is used to fetch the length of an AVI- or MKV-file (did I understand that right?), then MediaInfo gets the seconds, too. Perhaps it behaves different with different file types? Didn't try it with VOBs till now, cause I'm still quite new to PVD... Within PVD the duration must be stored to its full extend, cause it is displayed as 01:48:43, for example (in preferences "Use minutes for duration field" must be unchecked to see this, of course). Sometimes audio streams are longer than the video stream, and even that is recognised and the duration reported seems to always represent the duration of the longest stream. I love that!  And I'd love to be able to export it... 

Yes and no. With "seen date" that makes sense, I really didn't think about it...

Just tried and it worked fine, the field could be cleared manually after clearing the seen flag (it did not clear automatically after removing the seen flag, though). I tried it a second time on the same movie and it didn't work anymore...    Restarted PVD and it still did not change (seen flag was cleared, but the seen date was still there and undeletable). Then suddenly it worked, then again it didn't... Seems somewhat unpredictable to me.

So I'm looking foward to version 1.0... 
Thanks in advance and thanks a lot in general for Personal Video Database!

There is a minor(!) issue when displaying in minutes or exporting via template: {%value=length}
The seconds are just cut off instead of being rounded. The shortest short film in my database is 54 seconds, what becomes a runtime of 0 minutes.
Maybe it would even be a good idea to always round to the next full minute (01:22:12 = 73 minutes). That seems to be the common practice for DVD-covers and throughout the net.
By the way, is there a possibility to to get the duration in seconds or as hh:mm:ss when exporting via {%value=length}?
(I'm running v0.9.9.18, WinXP)

First of all: great work, great application. Still has some minor flaws and glitches of course, but it's the only app of this kind that can do (almost) everything I ever wanted. Should sound like a huge compliment! 

Still there is this very annoying issue with its sort order (I'm using v.0.9.9.18, WinXP), still sorting upper and lower case chars and chars with accents in a strange manner (simply by codepoint order).

There also is a second thread on this:
http://www.videodb.info/forum_en/index.php?topic=1531.0

Of course, Firebird was to blame for the unwanted behavior, but with Firebird 2.1 things might have changed. I searched this forum, didn't find anyone mention it, so perhaps no one knows?

As it seems to me (just after doing some forum research. Hope, I'm not wrong...), all text is stored as UNICODE_FSS within the database? As this is superseded by now, it should be (or already was?) changed to UTF8. Then you can advise Firebird to use four different collations: UCS_BASIC (sorting by code-point order), UNICODE (using the Unicode Collation Algorithm, which really should do the job the best way possible), UTF-8 (completely case insensitive collation), and with Firebird 2.5 there will be UNICODE_CI_AI (totally ignoring case and accents, treating "A" as "a", "Ü" as "u", "è" as "e", and so on).

I'm referring to this page:
http://www.destructor.de/firebird/charsets.htm

The Unicode Collation Algorithm:
To cite Wikipedia: "Multilingual ordering... When lists of names or words need to be ordered, but the context does not define a particular single language or alphabet, the Unicode Collation Algorithm provides a way to put them in sequence."
Sounds good to me. 
In detail:
http://en.wikipedia.org/wiki/Unicode_collation_algorithm