[mythtv-users] 0.24 recording troubles
peloy at chapus.net
Tue Nov 16 21:30:50 UTC 2010
On Tue, Nov 16, 2010 at 08:36:37AM -0800, Douglas Peale wrote:
> I'm using two HDHomeRun boxes (four tuners), and not seeing this issue
> when a second recording starts on the same tuner, or when a second
> recording starts on a different tuner. At most there is a slight
> glitch in the recording when another recording starts in the middle of
> a recording.
I think I got to the bottom of my issue -- in mythtv-setup, where one
adds the HDHomeRun tuners to the configuration, in the menu "Available
Devices" one can choose "manually enter IP address", and then enter IP
address of HDHomeRun and tuner to use, or one can select from a list of
auto-discovered devices. I have always used the manual method (enter
IP addr. and tuner) but it seems like if one configures the HDHomeRun
device manually in 0.24 things don't work and Myth never uses tuner 1
(I confirmed that Myth does not try to use tuner 1 by capturing traffic
during simultaneous recording and looking at the control traffic between
Myth and the HDHR -- I can see the commands being sent to the HDHR and
the responses since they show up in plain ASCII on the wire, and I never
see Myth try to use tuner1).
After deleting all capture cards and re-adding the HDHomeRun tuners by
using the auto-discovered devices I was able to get things to work.
The difference between manual config. and using discovered devices in
the database is that when using manual config, "videodevice" in the
capturecard table shows as 10.10.13.13-0, and when using auto-discovered
devices "videodevice" shows as 10194703-0. Guess something does not like
the a.b.c.d-n format.
This seems like a bug in some part of Myth (or in the HDHomeRun
library). I'll go file a bug unless someone thinks this is some other
Douglas, if you configured your HDHomeRuns by manually entering IP
addresses and tuner numbers then that ruins my theory.
More information about the mythtv-users