DonInTn
07-25-07, 06:27 AM
Well, I broke the cardinal rule of mythtv, if it isn't broken, don't fix it. I was having some problems with MythArchive so I upgraded my Myth .20 backend to .20.1 using yum upgrade mythtv-suite.
The problem I'm now having is for some recordings, myth frontend reports no file size information and if I look at the same recording through MythWeb, the file size is reported as -1 B.
The effected recordings are complete and play fine. If I look at the file through a filemanager the size is correct. There doesn't seem to be any pattern as to which recordings are effected. Last night I recorded 5 shows, only one had this issue. Yesterday none had this problem, Sunday 3 out of 8 had this problem.
If I look at the MythTV system info screen before deleting one of these programs, and then delete it, the available space changes so it appears to be limited to how MythTV generates the "file size" field in the recordings database, which apparently isn't used for anything other than reporting the filesize in frontend or Mythweb?
Anyone else have this issue, or know how to fix it?
Thanks
The problem I'm now having is for some recordings, myth frontend reports no file size information and if I look at the same recording through MythWeb, the file size is reported as -1 B.
The effected recordings are complete and play fine. If I look at the file through a filemanager the size is correct. There doesn't seem to be any pattern as to which recordings are effected. Last night I recorded 5 shows, only one had this issue. Yesterday none had this problem, Sunday 3 out of 8 had this problem.
If I look at the MythTV system info screen before deleting one of these programs, and then delete it, the available space changes so it appears to be limited to how MythTV generates the "file size" field in the recordings database, which apparently isn't used for anything other than reporting the filesize in frontend or Mythweb?
Anyone else have this issue, or know how to fix it?
Thanks