matthewgrant5 at gmail
Sep 20, 2009, 7:27 PM
Post #1 of 1
(353 views)
Permalink
|
|
Re: Ticket #7105: Broadcast H264 tuning fails due to cascade of thousands of log messages
|
|
Hi st0ne,
I tested it by recording 4 - 5 programs and browsing channels madly,
repeating the test once to make sure. Took about 30 minutes while
doing this. Before the log messages were stopped, it failed miserably
at the same thing. Are you in Norway or NZ by any chance so that you
can test it for your self?
Don't forget that a LOT of CPU is spent in looping through
scanf/printf formatting the strings, and then logging the message to
disk. Believe me, the speed of tuning was at least 100% better, if
not 200%better, and it was RELIABLE.
I still think we want the log messages, but it should only be when a
channel/mux stream is NOT being tuned. i will have a dig into the
data structures on Wednessday to find something that I can use in an
if then statement.
Cheers,
Matthew
On Mon, Sep 21, 2009 at 8:18 AM, MythTV <mythtv [at] cvs> wrote:
> #7105: Broadcast H264 tuning fails due to cascade of thousands of log messages
> -----------------------------------------------------+----------------------
> Reporter: Matthew Grant <matthewgrant5 [at] gmail> | Owner: ijr
> Type: defect | Status: new
> Priority: critical | Milestone: unknown
> Component: MythTV - General | Version: head
> Severity: high | Resolution:
> Mlocked: 0 |
> -----------------------------------------------------+----------------------
>
> Comment(by einstein [at] st0ne):
>
> i think that solves the much log messages... but not the problem why it
> isn't tuning, or decoding the h264 stream...?
>
> --
> Ticket URL: <http://svn.mythtv.org/trac/ticket/7105#comment:5>
> MythTV <http://www.mythtv.org/>
> MythTV
>
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
|
