"-1" file size for some otherwise-complete and working recordings

[ylee@…]

About a half dozen recordings I currently have on my system have "-1" in the filesize field in the database. Here's what I've found:

• The recordings are totally intact, with no seektable issues.
• MythWeb says these files' sizes is "-1 B."
• No file size line appears in mythfrontend's Program Details screen.
• Beyond the above, the lack-of-proper-filesize issue limits what appears in Program Details. For example, I have two episodes of a TV show recorded back to back. One has the issue, one doesn't. The episode that does have the issue only displays the following lines of data in Program Details:

Title, Description, Category, Type, Original Airdate, Program ID, MythTV Status, Recording Rule, Recording Profile.

The episode without the issue displays the following lines:

Title, Description, Category, Type, Episode Number, Original Airdate, Program ID, Actors, Executive Producer, Guest Star, MythTV Status, Recording Rule, Recording Host, Recorded File Size, Recording Profile, Recording Group, Playback Group.

• ​Manually-rebuilding the seektable does not fix the file size.
• Transcoding the recording with autodetect (MPEG2-to-MPEG2) sometimes fixes the file size and sometimes it doesn't. Transcoding didn't fix the TV episode above, for example, and what appeared in Program Detail didn't change.
• This issue currently exists in seven of 985 recordings. All seven recordings were made with various iterations of 0.20-fixes.
• I've seen this issue similarly pop up perhaps a dozen more times I'm aware of over the past 14 months that, and thousands of recordings for, I've used MythTV. In addition to 0.20-fixes, I also saw it with 0.19.1.

[stuartm]

Are you seeing this issue with recordings created with recent trunk?

[ylee@…]

Replying to stuartm:

Are you seeing this issue with recordings created with recent trunk?

I am still on 0.20 (now 0.20.2), but haven't seen the issue in months and over hundreds and hundreds of recordings, so hopefully the issue's been fixed. I manually fixed the issue on the existing recordings by putting in the filesizes in the database, replacing "-1"; this permitted programinfo.cpp to show the complete recording information. (So, to the extent there's still an outstanding issue, it can be worded as "Bad filesize data in database causes mythfrontend to display incomplete program details."