[mythtv-users] Anyone else having issues with Community and multiple recordings?

Tom Lichti redpepperracing at gmail.com
Fri Oct 15 13:20:27 UTC 2010


Last week my wife said that Community simultaneously recorded 4 times,
so she deleted all but one. Being aware of that last week, this week I
checked the upcoming recordings in the afternoon, and it only showed
one recording scheduled. Sure enough, last night it recorded 4 times
again, two HD recordings from an HDHR, and two analog cable recordings
from PVR-150's. Along with the two other scheduled recordings on my
other HDHR, it seemed to saturate my network (the 4 HD streams to the
backend, and all of my recordings go to a Dlink NAS) as playback was
choppy to a remote frontend until I killed the extra 3 Community
recordings. After deleting 3 recordings, I then had to delete another
one that restarted. The strange thing is that even though the frontend
showed only one recording in progress, the backend still kept
recording the two analog versions until the end of the show, and it
showed this in the backend status, both in mythweb and through the
frontend in Info Center. I have 4 channels in my lineup that it could
have recorded from, 2 in the analog cable channels, and 2 in the OTA
channels, so it makes a bit of sense that there were four recordings
going.

Some details:

mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version   : 26776M
MythTV Branch    : trunk
Network Protocol : 63
Library API      : 0.23.20100917-1
QT Version       : 4.6.3
Options compiled in:
 linux debug using_oss using_backend using_bindings_perl
using_bindings_python using_dvb using_frontend using_hdhomerun
using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc
using_mheg using_opengl_video using_opengl_vsync using_qtdbus
using_qtwebkit using_v4l using_x11 using_xrandr using_bindings_perl
using_bindings_python using_mythtranscode using_opengl
using_ffmpeg_threads using_live using_mheg

the only modification to source is this (for some reason it wouldn't
work for me without the path to the binary):

svn diff mythtv
Index: mythtv/bindings/python/scripts/mythpython
===================================================================
--- mythtv/bindings/python/scripts/mythpython   (revision 26776)
+++ mythtv/bindings/python/scripts/mythpython   (working copy)
@@ -1,4 +1,4 @@
-#!python
+#! /usr/bin/python

 from MythTV import *
 import sys

I am using SchedulesDirect for my listings, as mentioned I have 2
HDHR's and 2 PVR-150's. The recording schedule settings are as
follows:

- record at any time on any channel
- duplicate check method - Subtitle and Description
- check for duplicates in all recordings
- filter - exclude repeat and generic
- preferred input - any

Having said all that I have two concerns:

1) why did the schedule only show one scheduled recording, yet insist
on recording 4 times?
2) after deleting the 2 analog recordings, why did the backend keep
recording, yet the frontend did not show that status in the Recordings
list?

Next week, what log level (currently set to default important,general)
should mythbackend be running at to capture useful info around this? I
looked through the logs, but I don't see anything glaringly obvious.
Oh, the other odd thing is that the two recordings on the analog
channel seem to only be 1 minute in length (verified in playback, and
in the logs) but the backend shows the tuner in use for the whole 30
minutes of the recording.

Thanks in advance for any ideas.

Tom


More information about the mythtv-users mailing list