2009-02-17, 11:44 PM
I'm pretty certain it wasn't mux related, it was just that I first saw it happen when trying out different muxes and just assumed it was that. When it happened again after reverting to dvr-ms I realised that probably wasn't the case.
With the aid of my System event log and my archived gbpvr logs, I can confirm the last case was just after a recording had started on BBC4 and things were set for dvr-ms. The rec. service logs show the recording started at 19:23:05 (and there the logs end) and the System log shows the 7304 error at 19:23:17. That was on Saturday before I applied the patch.
In fact, looking at the timing of the System log entries, almost all are shortly after ~2 minutes before a normal programme schedule time (i.e., most programmes start on the hour or half hour or 5 minutes past, 25 minutes past etc.). I use 2 mins prepadding and have System log entries for HH:58, HH:28, HH:03, HH:23.
I see your System log entry is for 21:45:59 and you use 5 mins prepadding - was there anything set to record at 21:50 (EPG scheduled time)?
Cheers,
Brian
With the aid of my System event log and my archived gbpvr logs, I can confirm the last case was just after a recording had started on BBC4 and things were set for dvr-ms. The rec. service logs show the recording started at 19:23:05 (and there the logs end) and the System log shows the 7304 error at 19:23:17. That was on Saturday before I applied the patch.
In fact, looking at the timing of the System log entries, almost all are shortly after ~2 minutes before a normal programme schedule time (i.e., most programmes start on the hour or half hour or 5 minutes past, 25 minutes past etc.). I use 2 mins prepadding and have System log entries for HH:58, HH:28, HH:03, HH:23.
I see your System log entry is for 21:45:59 and you use 5 mins prepadding - was there anything set to record at 21:50 (EPG scheduled time)?
Cheers,
Brian
