This is a minor thing, but I’ll mention it to consider for the upcoming release.

For TV series in mp4 files, I use the created tag field (mp4box ... -itags created=yyyy-mm-dd) to indicate the original air date. Mezzmo reads this value and stores it as the Created field value.

Sometimes an episode becomes available a few days before its official air date. When I add such a file to Mezzmo, it sets the Created field to January 1st of the current year.

I was able to fix this by changing the appropriate value in the relevant row of the mgofile table, but that’s the sort of hack I’d like not to have to do. (Still, the mere fact that I can do it, though it’s clumsy and unsupported, helps.) That this works shows that there’s no problem handling the in-advance date; it’s just that some well-intentioned sanity check on the input data is wiping it out.

I recall that Mezzmo also has, or at least had, trouble with file dates before January 1st, 1970. Again, it can understand them if they are forced into the database table; it just doesn’t read them in properly. (This, as I recall, was with file system dates; for example on mpg files, where there are no tags. Windows doesn’t always get such dates right either, though they are well-defined within the file system itself; it depends where you view them. It could be that a Windows system call which expects only “reasonable” file dates is the source of this glitch.)

Both of these are very minor, though, so long as you make it possible to correct the Created field through the Properties dialog in the user interface. These cases don’t come up often; it’s not being able to fix them without hacking at the database that’s the bigger problem.