Modify

Ticket #5262 (closed defect: fixed)

You must read the TicketHowTo before creating a new ticket or commenting on an existing ticket.

Opened 4 years ago

Last modified 13 months ago

mythweb statistics report incorect percentage of time spent recording

Reported by: udovdh@… Owned by: kormoc
Priority: major Milestone: unknown
Component: mythweb Version: 0.21-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description (last modified by mdean) (diff)

Recording Statistics

Number of shows:

123

Number of episodes:

166

First recording:

Friday April 25th, 2008

Last recording:

Sunday April 27th, 2008

Total Running Time:

1 day 17 hrs 11 mins

Total Recorded:

4 days 21 hrs 12 mins

Percent of time spent recording:

284%

Yes, multiple channels, but how can one record more than 100% of the time? This is on my 0.21-fixes which I was persuaded into installing after wrestling with the issue of ticket 5260.

Attachments

Change History

comment:1 Changed 4 years ago by udovdh@…

Please include all output in bug reports. MythTV Version : exported MythTV Branch : branches/release-0-21-fixes Library API : 0.21.20080304-1 Network Protocol : 40 Options compiled in:

linux release using_oss using_alsa using_backend using_dbox2 using_dvb using_firewire using_frontend using_hdhomerun using_iptv using_ivtv using_joystick_menu using_lirc using_opengl_vsync using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmcw using_xvmc_vld using_bindings_perl using_bindings_python using_opengl using_ffmpeg_threads using_libavc_5_3 using_live

comment:2 Changed 4 years ago by paulh

  • Owner changed from ijr to xris
  • Component changed from mythtv to mythweb

comment:3 Changed 4 years ago by kormoc

  • Owner changed from xris to kormoc
  • Status changed from new to accepted

Do you have more then one capture card?

comment:4 Changed 4 years ago by udo

1 card with 7 virtual tuners defined.

comment:5 Changed 4 years ago by kormoc

  • Status changed from accepted to closed
  • Resolution set to fixed

(In [17425]) Fixes #5262, this should fix the over 100% stats numbers

comment:6 Changed 4 years ago by udo

Now you divide by the amount of tuners where I would expect the percentage to be for the whole box: the box records or doesn't. Be it 1 channel or more than one. It records. The amount of tuners doesn't really matter.

comment:7 Changed 4 years ago by kormoc

That's what I did

comment:8 Changed 4 years ago by udo

The amount of tuners doesn't really matter. (as I wrote) It records or it doesn't.

(making this configurable between on/off and per tuner is a step too far I guess)

comment:9 Changed 4 years ago by kormoc

The queries to do per box (and it gets way more complicated when you have slave backends as well) is too complicated for the point of this module. It's just meaningless info that's fun, not something that has to be perfectly correct.

% of tuner usage is easy, % of box usage is not.

It's not worth my time to solve box usage (including slave backends), but feel free to submit a patch.

comment:10 Changed 4 years ago by udo

In my case I have 7 virtual tuners for 3 channels: I can have some overlap for preroll/postroll and one tuner for whatever without conflicts. 3 channels are almost continuously recorded. So I get (300/7) % ?

comment:11 Changed 4 years ago by kormoc

Yes

comment:12 Changed 13 months ago by mdean

  • Description modified (diff)

Fix the wiki-format misuse that was breaking formatting of the page. Just an annoyance.

comment:13 Changed 13 months ago by udovdh@…

Number of shows:

6193

Number of episodes:

127454

First recording:

Sunday April 27th, 2008

Last recording:

Friday January 28th, 2011

Total Running Time:

2 years 9 months 1 day 19 hrs 1 min

Total Recorded:

7 years 5 months 26 days 11 hrs 10 mins

Percent of time spent recording:

38%

So it is worse now. It is saying 38% instead of 100%.

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.