[mythtv] svn 7441: No errors, but file not created?

[Daniel Kristjansson]

On Mon, 2005-10-10 at 19:26 -0600, John P Poet wrote:
> Everything compiled fine, and mythbackend started up just fine. 
> However, when it went to record a show, no file was created.  The
> backend log shows no errors, and indicates that it started the record
> process just fine:
<snip>
> 2005-10-10 19:12:48.908 TVRec(1): SetFlags(NeedToStartRecorder,) ->
> RunMainLoop,AskAllowRecording,WaitingForSignal,NeedToStartRecorder,SignalMonitorRunning,
> 2005-10-10 19:12:48.914 Started recording: NFL Football "Pittsburgh
> Steelers at San Diego Chargers": channel 1001 on cardid 1, sourceid 1
> 2005-10-10 19:12:49.249 DVBSM(0)::UpdateValues: Signal Locked
> 2005-10-10 19:12:49.252 DVBSM(0)::UpdateValues: Waiting for table
> monitor to start
> 2005-10-10 19:12:49.256 DVBSM(0)::UpdateValues: Table monitor started
> 2005-10-10 19:12:49.257 DVBSM(0)::RunTableMonitor(): begin (# of pids 2)
> 2005-10-10 19:12:49.264 DVBSM(0)::AddPIDFilter(0x0):
> 2005-10-10 19:12:49.274 DVBSM(0)::AddPIDFilter(0x1ffb):
> 2005-10-10 19:13:02.733 Found 3 record profiles using max episode
expiration
<snip>
> I immediately realized something was wrong, when I did not hear any
> disk activity.  I checked the directory where shows are supposed to be
> saved, and a new file had not been created.
It doesn't create a file until the recorder has started.
And it doesn't start an ATSC recorder until it has seen the
MGT, VCT, PAT, and PMT. It looks like it got a signal lock,
but then never saw any of these tables it needs for a channel
lock. The only change from 7267 is that it no longer times
out on scheduled recordings, this is by request from the UK
where channels go off-air and on-air frequently.

But that shouldn't have caused any problem, perhaps it was
a fluke that it happened with the latest version? Can you
try repeating it? If it is repeatable, finding the check-in
that caused it might narrow in on the problem.

> It has been long enough since I updated, that I am wondering if there
> is a "step" I need to do before the latest version will work properly?
Nope, no DB change in over a month concerning this. There
was a per-tuner timeout addition a few weeks ago, but that
only effects LiveTV now.

-- Daniel