Unexpected error checking tuning on back-to-back multirecords

[BrettB]

Tonight I had a few programs set to record. One of them (Fringe) did not record successfully. There is a 13MB file for it (not a 0 byte), but if I attempt to play it via the NMT, it hangs.

Looking at the recording logs (attached), I see a couple of errors:

2010-01-28 18:59:00.046 ERROR [5] Unexpected error checking tuning on back-to-back multirecords
2010-01-28 21:00:00.234 ERROR [5] Unexpected error checking tuning on back-to-back multirecords
2010-01-28 21:00:04.125 ERROR [5] Unexpected error checking tuning on back-to-back multirecords

And since I don't see any tuning info for Fringe, I'm thinking that it was supposed to be just continuing using the tuner from 2 20:00 shows. But the logs show:

2010-01-28 19:59:00.171 VERBOSE [5] BDARecordingSource about to start multi-record oid:6 channel:T:553250,0,0~P:3~TSID:542~V:2045~A:2043~PMT:2046~PCR:2045~N:>9.1 KMSP-DT* (000(AC3)) file:\GBPVR Videos\Fringe\Fringe_20100128_20002100.ts
2010-01-28 19:59:00.171 VERBOSE [5] RecordingFactory.save()
2010-01-28 19:59:00.281 VERBOSE [5] Save(): Updated existing scheduled recording
2010-01-28 20:02:00.046 VERBOSE [5] Recording has passed endtime+padding. Stopping.
2010-01-28 20:02:00.046 VERBOSE [5] Stopping multi record: 1

Which looks to me like it started to record at 19:59, but then the tuner stopped at 20:02 (after the end of the original 2 shows).

[sub]

Unfortunately there isnt currently enough info in the logs to tell what exactly it didnt like about the multirecord tuning. I've added some log messages for the next release though.

You could probably disable multi-record for now if you have continuing problems.