[mythtv] [mythtv-commits] Ticket #7759: [PATCH] Add support forrepeat_pict plus related AV-sync improvements

[Taylor Ralph]

--- On Thu, 12/17/09, Mark Spieth <mark at digivation.com.au> wrote:

> From: Mark Spieth <mark at digivation.com.au>
> Subject: Re: [mythtv] [mythtv-commits] Ticket #7759: [PATCH] Add support forrepeat_pict plus related AV-sync improvements
> To: "Development of mythtv" <mythtv-dev at mythtv.org>
> Date: Thursday, December 17, 2009, 3:11 PM
> >>
> >> I just installed the patch, and I am seeing a LOT
> of these
> >> in the log,
> >> not sure if they were there before:
> >>
> >> 2009-12-16 22:34:27.301 Set video sync frame
> interval to
> >> 16683
> >> 2009-12-16 22:34:27.301 Disabled deinterlacing
> >> 2009-12-16 22:34:27.318 Set video sync frame
> interval to
> >> 16683
> >> 2009-12-16 22:34:27.318 Disabled deinterlacing
> >> 2009-12-16 22:34:27.334 Set video sync frame
> interval to
> >> 16683
> >> 2009-12-16 22:34:27.335 Disabled deinterlacing
> >>
> >> CPU usage is higher than what it was, I think. A/V
> sync is
> >> much
> >> better, however. My frontend is a Zotac ION, using
> VDPAU,
> >> if it
> >> matters.
> >>
> >> Tom
> >>
> >
> > Those messages were there before and are a result of
> the following 
> > changeset which is totally unrelated to these
> changes.
> >
> > http://svn.mythtv.org/trac/changeset/22947/
> >
> 
> any logging which is done per frame should probably be made
> conditional on 
> TIMESTAMP.
> 
> mark
>

Agreed. Again it's not related in any way form or fashion to this ticket. I don't believe the code generating those messages should be executed on every frame. I've noticed it's happening for some of my recordings. Next time I find one I'll dig into it. It is definitely causing excessive logging and CPU usage.

--
Taylor