[mythtv] [mythtv-commits] Ticket #7419: mythcommflag broken on HD-PVR x264 files

[Ken Bass]

John P Poet wrote:
> On Sat, Oct 24, 2009 at 9:11 PM, MythTV <mythtv at cvs.mythtv.org> wrote:
>   
>> #7419: mythcommflag broken on HD-PVR x264 files
>> -----------------------------------+----------------------------------------
>>  Reporter:  kbass@…                |       Owner:  cpinkham
>>     Type:  defect                 |      Status:  new
>>  Priority:  critical               |   Milestone:  unknown
>> Component:  MythTV - Mythcommflag  |     Version:  0.22rc1
>>  Severity:  high                   |     Mlocked:  0
>> -----------------------------------+----------------------------------------
>>  HD-PVR as my Tuner 1
>>
>>  Commercial flagging takes 100% CPU and prints
>>
>>  2009-10-23 17:03:05.969 AFD Error: Unknown decoding error
>>  2009-10-23 17:03:08.992 [h264 @ 0x7f481abbcd80]B picture before any
>>  references, skipping
>>  2009-10-23 17:03:08.992 [h264 @ 0x7f481abbcd80]decode_slice_header error
>>  2009-10-23 17:03:08.992 [h264 @ 0x7f481abbcd80]no frame!
>>  2009-10-23 17:03:08.992 AFD Error: Unknown decoding error
>>
>>  over and over.
>>     
>
>
> Those messages are normal.  The avformat library handles HD-PVR
> material well enough, but not perfectly.  You can basically treat
> those messages as warnings.
>
>   
I think we really need to get rid of these messages. There is about 5 
lines of text printed approx every 700 msecs.
For an hour show, that is about 26,000 messages.

>>  I killed it after 15 minutes.
>>     
>
> If you don't kill it, does it finish?  Single-sliced H.264 material
> can easily consume a core to process.  My mythbackend computer is just
> as powerful as my mythfrontend, just so I can flag HD-PVR material in
> real time.
>
> VDPAU cannot be used for commercial flagging, so it has to be done in software.
>   
I guess I was impatient. On my system a 1hr HD show seems to take about 
1 1/2 to 2 hours to flag.
The massive amount of messages seems to occur during the 'Searching for 
logo' phase. I have strict detection enabled. After the very very long 
searching for logo phase, it starts to report about 44fps.

So I think you can close this bug report but I hope we can fix the error 
logging. It was confusing to see a msg starting a decode error when it 
is an ignore.