[mythtv] Mytharchivehelper and streaminfo problems

Paul Harrison mythtv at dsl.pipex.com
Sun Jan 27 22:56:12 UTC 2008


Otto Kolsi wrote:
>
> Some recorded files cause problems in MythArchive because video
> resolution is detected as 0x0. Timings/lengths might also be wrong.
>
> I did a simple script to create streaminfo files for all the
> recordings that I currently have. These are all DVB-T recordings, some
> have several audio, some several dvb subtitle tracks and some have
> data tracks.
>
> Out of 388 recordings there are 59 (15%) that produce 0x0 video
> resolution when analyzed with mytharchivehelper (with method 2). I've
> attached 2 example outputs.
>
> Rebuilding seektable doesn't help and these recordings can be watched
> just fine. Quickly looking at mytharchivehelper it seems that stream
> info comes from "av_find_stream_info(inputFC)".
>
> Is this just ffmpeg problem or can something be done in
> mytharchivehelper? It would probably be good to have some more checks
> in mythburn.py for these kind of problematic resolutions and timing
> values.
Like you say mytharchivehelper just relies on the stream info returned
from the avformat library.
 
If you play the file using 'ffplay -stats FILENAME' does the dump stream
info thats displayed show the correct resolution and does that differ
from the dump stream info displayed when mytharchivehelper is run?

If the file duration is wrong when using method 2 then that suggests
either the position map in the DB is wrong or the method used to
calculate the duration from the position map is wrong . The script
always uses method 1 when it need an accurate duration because it is
guaranteed to get the proper file duration because it counts the video
frames.

It should be possible to change mytharchivehelper to decode a few video
frames and get the resolution that way if necessary.

Paul H.


More information about the mythtv-dev mailing list