[mythtv-commits] Ticket #2459: Mythcommflag catches up to 10 +- 2 seconds behind recording
MythTV
mythtv at cvs.mythtv.org
Mon Sep 25 14:35:47 UTC 2006
#2459: Mythcommflag catches up to 10 +- 2 seconds behind recording
-------------------------------------+--------------------------------------
Reporter: paulx at andreassen.com.au | Owner: cpinkham
Type: defect | Status: closed
Priority: minor | Milestone: unknown
Component: mythtv | Version: 0.20
Severity: medium | Resolution: wontfix
-------------------------------------+--------------------------------------
Changes (by cpinkham):
* status: new => closed
* resolution: => wontfix
Comment:
We've tried reducing the requiredBuffer down before and a bunch of users
have had problems. It would be nice to put this down below the 30 seconds
we use currently, but doesn't work as a general use case. See the
following changelogs where we bumped it down then had to bring it right
back up. [9237]. [9265], and [10167].
For the +- 2 seconds mod. With your mod, we would run 'slow' for 5
seconds, then run 'fast' for 5 seconds. So
you spread the 'waves' out. With existing code we run 'slow' or 'fast'
for a max of one second and then switch,
so our overall cpu usage over a 10 second period is more consistent rather
than having 5 seconds fast and 5 slow,
we're more evened out. I'm not sure I like this part because of this. If
you want to discuss, mention it on the -dev list and we can talk about it.
Going to close this ticket for now, but may reopen in the future if my
logic above is flawed.
--
Ticket URL: <http://cvs.mythtv.org/trac/ticket/2459#comment:1>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list