[mythtv-users] a new type of error
Stephen Worthington
stephen_agent at jsw.gen.nz
Fri Mar 9 13:51:33 UTC 2018
On Fri, 9 Mar 2018 06:50:07 -0500, you wrote:
>On 03/08/2018 11:40 PM, Stephen Worthington wrote:
>> It looks like you do not have a problem with the size of recordedseek
>> then - you must not have very many recordings at all.
>
>Or he has a ton of recordings in a format, such as H.264, for which
>MythTV doesn't need to build a seek table.
>
>Mike
So, since over half my recordings are DVB-T H.264, why is my
recordedseek table so huge? I think MythTV does actually build a seek
table for H.264 recordings, even if it does not need it.
Take, for example, a recording made today:
MariaDB [mythconverg]> select
chanid,starttime,endtime,title,subtitle,left(description,60),basename,recordedid
from recorded where title like "1 news%" order by starttime desc limit
1\G
*************************** 1. row ***************************
chanid: 1001
starttime: 2018-03-09 04:59:00
endtime: 2018-03-09 06:04:01
title: 1 News At 6pm
subtitle:
left(description,60): The nation's leading team of journalists brings
viewers the
basename: 1001_20180309045900.ts
recordedid: 33691
1 row in set (0.00 sec)
MariaDB [mythconverg]> select * from recordedfile where
recordedid=33691\G
*************************** 1. row ***************************
basename: 1001_20180309045900.ts
filesize: 3359161816
width: 1920
height: 1088
fps: 25.000
aspect: 1.777778
audio_sample_rate: 0
audio_channels: 0
audio_codec: AC3
video_codec: H264
comment:
hostname: mypvr
storagegroup: Default
id: 33126
recordedid: 33691
container: MPEG2-TS
total_bitrate: 0
video_avg_bitrate: 0
video_max_bitrate: 0
audio_avg_bitrate: 0
audio_max_bitrate: 0
1 row in set (0.00 sec)
MariaDB [mythconverg]> select count(*) from recordedseek where
chanid=1001 and starttime='2018-03-09 04:59:00';
+----------+
| count(*) |
+----------+
| 7356 |
+----------+
1 row in set (0.02 sec)
More information about the mythtv-users
mailing list