[mythtv] [PATCH] Re: policy on using 'VERBOSE' in myth

Isaac Richards ijr at po.cwru.edu
Fri Aug 29 02:06:39 EDT 2003


On Wednesday 27 August 2003 05:55 pm, Geoffrey Hausheer wrote:
> On Wed, 27 Aug 2003 17:30:58 -0400, "Isaac Richards ijr-at-po.cwru.edu
>
> |mythtv/1.0-Allow|" <e6kbhbk35r0t at sneakemail.com> said:
> |
> > On Wednesday 27 August 2003 05:23 pm, Geoffrey Hausheer wrote:
> > > This isn't really an error (it may or may not generate loss of data). 
> > > So I'm not sure why we want to report this by default.  Checking in the
> > > encoder if this is causing real data loss would be the right place for
> > > an error message, it seems to me.  specifically, I get this all the
> > > time using the transcoder, since I can effectively feed it data at the
> > > same rate that I read it, and blocking the write has no impact on the
> > > output....This is why I had changed it to an info message with a
> > > 'verbose' in my patch.  I'm cool with another solution, but I'd rather
> > > not generate lots of these messages while transcoding.  Comments?
> >
> > That's something you'd want to know during normal playback/recording,
> > however..
>
> Wouldn't that be a perfect use for VERBOSE(VB_IMPORTANT,...)?
>
> If nothing else, will you accept a patch that lets me disable these
> messages either during the creatiion of the RingBuffer, or as a sperate
> command?

Can't just redirect stderr?  That's probably be the best way to handle actual 
error messages, as opposed to informational things..

Isaac


More information about the mythtv-dev mailing list