Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Dev

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

 

 

MythTV dev RSS feed   Index | Next | Previous | View Threaded


jppoet at gmail

Oct 24, 2009, 9:40 PM

Post #1 of 6 (1290 views)
Permalink
Re: [mythtv-commits] Ticket #7419: mythcommflag broken on HD-PVR x264 files

On Sat, Oct 24, 2009 at 9:11 PM, MythTV <mythtv [at] cvs> 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 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.


John
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


harley at thepetersclan

Oct 25, 2009, 9:15 AM

Post #2 of 6 (1234 views)
Permalink
Re: [mythtv-commits] Ticket #7419: mythcommflag broken on HD-PVR x264 files [In reply to]

On Sat, 24 Oct 2009 22:40:49 -0600
John P Poet <jppoet [at] gmail> wrote:

> On Sat, Oct 24, 2009 at 9:11 PM, MythTV <mythtv [at] cvs> 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 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.
>
>
> John

It would be nice if those "error" messages could be moved to a different
error level.
I have had to set my master backend's logging to none,general to keep
the log file from becoming huge over time.
This of course turns off most logging making seeing any real errors
(errors I can do something about) unlikely.

Harley
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


mtdean at thirdcontact

Oct 25, 2009, 10:17 AM

Post #3 of 6 (1234 views)
Permalink
Re: [mythtv-commits] Ticket #7419: mythcommflag broken on HD-PVR x264 files [In reply to]

On 10/25/2009 12:15 PM, Harley Peters wrote:
> On Sat, 24 Oct 2009 22:40:49 -0600 John P Poet wrote:
>
>> On Sat, Oct 24, 2009 at 9:11 PM, MythTV wrote:
>>
>>> #7419: mythcommflag broken on HD-PVR x264 files
>>>
>>> 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.
> It would be nice if those "error" messages could be moved to a different
> error level.
> I have had to set my master backend's logging to none,general to keep
> the log file from becoming huge over time.
> This of course turns off most logging making seeing any real errors
> (errors I can do something about) unlikely.
>

http://svn.mythtv.org/trac/ticket/6729

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


harley at thepetersclan

Oct 25, 2009, 8:38 PM

Post #4 of 6 (1221 views)
Permalink
Re: [mythtv-commits] Ticket #7419: mythcommflag broken on HD-PVR x264 files [In reply to]

On Sun, 25 Oct 2009 13:17:54 -0400
"Michael T. Dean" <mtdean [at] thirdcontact> wrote:

> On 10/25/2009 12:15 PM, Harley Peters wrote:
> > On Sat, 24 Oct 2009 22:40:49 -0600 John P Poet wrote:
> >
> >> On Sat, Oct 24, 2009 at 9:11 PM, MythTV wrote:
> >>
> >>> #7419: mythcommflag broken on HD-PVR x264 files
> >>>
> >>> 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.
> > It would be nice if those "error" messages could be moved to a
> > different error level.
> > I have had to set my master backend's logging to none,general to
> > keep the log file from becoming huge over time.
> > This of course turns off most logging making seeing any real errors
> > (errors I can do something about) unlikely.
> >
>
> http://svn.mythtv.org/trac/ticket/6729
>
> Mike
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Ok using nogeneral still leaves a lot of garbage in the logs. And also
turns off some logging I want.
The attached patch works well enough for me.
I don't expect it's good enough for general use but it's a better fit
for me.


--- libs/libmythtv/avformatdecoder.cpp.orig 2009-10-25
19:15:23.271761195 -0500 +++ libs/libmythtv/avformatdecoder.cpp
2009-10-25 22:23:34.900631324 -0500 @@ -120,7 +120,7 @@
verbose_level = VB_IMPORTANT;
break;
case AV_LOG_ERROR:
- verbose_level = VB_GENERAL;
+ verbose_level = VB_LIBAV;
break;
case AV_LOG_VERBOSE:
case AV_LOG_INFO:
@@ -3984,7 +3984,7 @@

if (ret < 0)
{
- VERBOSE(VB_IMPORTANT, LOC_ERR +
+ VERBOSE(VB_LIBAV, LOC_ERR +
"Unknown decoding error");
have_err = true;
continue;
Attachments: reduce_avformat_verbose_logging.patch (0.73 KB)


kbass at kenbass

Oct 28, 2009, 9:10 PM

Post #5 of 6 (1161 views)
Permalink
Re: [mythtv-commits] Ticket #7419: mythcommflag broken on HD-PVR x264 files [In reply to]

John P Poet wrote:
> On Sat, Oct 24, 2009 at 9:11 PM, MythTV <mythtv [at] cvs> 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.
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


mythtv-dev at jstenback

Oct 28, 2009, 9:30 PM

Post #6 of 6 (1159 views)
Permalink
Re: [mythtv-commits] Ticket #7419: mythcommflag broken on HD-PVR x264 files [In reply to]

I agree, there's just an absurd amount of these messages generated with
HD-PVR content when commflagging, it's hardly useful to anyone just
using mythtv...

Ken Bass wrote:
> John P Poet wrote:
>> On Sat, Oct 24, 2009 at 9:11 PM, MythTV <mythtv [at] cvs> 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.
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

MythTV dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.