Yah, that's a funky part of it. A TiVo gets the OAD from the Tribune Guide Data (date only, no time) and stuffs the correct date in, but zeroes out the time since that's not important to the TiVo. It's in that format because that's what the TiVo uses internally. For all other Date/Time info the TiVo will adjust it internally to compensate for your time zone, but not for the OAD, it just looks at the date portion. If it actually adjusted it for your time zone, the date may end up being off if you're not in the GMT/UTC time zone. I guess the best thing to do would be to change the time portion of the OAD in the metadata to 12:00:00, since there are 25 time zones (GMT/UTC to GMT/UTC +/- 12 hrs). Since the TiVo ignores the time portion of the OAD, it won't cause a problem with the metadata for pyTiVo users.