Tuesday night, House and 24 on Fox in HD, and two episodes of Star Trek TNG on WGN (analog) at the same time. (logs zipped from that night, whatever it was should be close to the end of the logs, within an hour or so).
House and the Treks all came through fine, but the 24 recording failed. I had a similar problem with an episode of Fringe some weeks ago under similar circumstances.
I've hatched a theory that might be dumb, but here it is anyway. What I think happened was GBPVR doesn't like to use the same tuner for back to back shows on the same channel if a 2nd tuner is available--logic that is presumably designed to make sure both files/shows have some buffer time on them.
So imagine I have Plextor, QAM1 (which is also Analog 1) and QAM2 (also Analog 2). Plextor gets tasked with the first analog recording, and QAM1 gets the first digital hour. As that hour is nearing the end, Analog 2 gets tasked with the next analog show just as GBPVR is trying to task QAM2 with the second digital show. QAM1 (aka analog1) is still tied up on the first digital recording, so it can't be used. Only one of the two second hour shows gets recorded, the other gets fubared even though QAM1 will be available to keep recording the same channel it's already on for the second hour.
Obviously, alternative B is I screwed something up or my setup did, or I don't understand all the limitations of my 2250. That might be more likely.
What do you think?
EDIT:
This same block appears repeatedly under GBPVRRecordingserviceexelog
It appears to fill up the better part of 2 log rollovers in the period where 24 should have started recording
House and the Treks all came through fine, but the 24 recording failed. I had a similar problem with an episode of Fringe some weeks ago under similar circumstances.
I've hatched a theory that might be dumb, but here it is anyway. What I think happened was GBPVR doesn't like to use the same tuner for back to back shows on the same channel if a 2nd tuner is available--logic that is presumably designed to make sure both files/shows have some buffer time on them.
So imagine I have Plextor, QAM1 (which is also Analog 1) and QAM2 (also Analog 2). Plextor gets tasked with the first analog recording, and QAM1 gets the first digital hour. As that hour is nearing the end, Analog 2 gets tasked with the next analog show just as GBPVR is trying to task QAM2 with the second digital show. QAM1 (aka analog1) is still tied up on the first digital recording, so it can't be used. Only one of the two second hour shows gets recorded, the other gets fubared even though QAM1 will be available to keep recording the same channel it's already on for the second hour.
Obviously, alternative B is I screwed something up or my setup did, or I don't understand all the limitations of my 2250. That might be more likely.
What do you think?
EDIT:
This same block appears repeatedly under GBPVRRecordingserviceexelog
Quote:2009-02-16 20:58:29.281 ERROR [5] Caught unexpected exception: System.ArgumentNullException: String reference not set to an instance of a String.
Parameter name: source
at System.Globalization.CompareInfo.IsPrefix(String source, String prefix, CompareOptions options)
at System.String.StartsWith(String value, Boolean ignoreCase, CultureInfo culture)
at NativeUtilities.BDARecorder.StartMultiRecord(String filename, Int32 serviceID)
at GBPVR.Backend.Common.BDARecordingSource.StartMultiRecord(String filename, ChannelTuning channelTuning)
at GBPVR.RecordingService.x93f60a55016d55c4.xcba1f05fb5a46d5f()
2009-02-16 20:58:29.484 ERROR [5] Unexpected error checking tuning on back-to-back multirecords
2009-02-16 20:58:29.484 VERBOSE [5] BDARecordingSource about to start multi-record oid:5 channel:T:69,0,0~P:25~V:66~A:67~PMT:87~PCR:66~N:>69.25 Unknown2* (000(AC3)) file:Q:\media\tv\24\24_20090216_20002100.ts
2009-02-16 20:58:29.484 ERROR [5] Caught unexpected exception: System.ArgumentNullException: String reference not set to an instance of a String.
It appears to fill up the better part of 2 log rollovers in the period where 24 should have started recording