2005-03-19, 01:02 AM
I mentioned this in the 0.91 release thread, but basically a scheduling problem I had in 0.9 still remains. Obviously the 0.91 bug-fix that sub mentioned didn't quite do the trick
My default recording setup allows for 1 minute of pre-padding and 9 minutes of post-padding. Â When I have scheduled recordings that directly follow each other (ie one program ends at 8.30, one starts at 8.30), GBPVR of course ignores this end-program padding. Â The problem arises when the first program is taken from one capture source, while the second is on the other.
What happens is that the first program records correctly, and if you look at the recording status it looks like the new program is also recording correctly, but in fact the second one isn't recorded at all. Â On reviewing the video from the first program, I see that the channel is changed at the appropriate time to the correct new channel, which is then recorded for the nine padding-minutes.
The only applicable error message I can find in the logs is one in the gbpvrrecordingservice log, where it registers an error at the point where the second show's pre-show padding should be starting:
cheers,
tieke
[b Wrote:Quote[/b] ]- Now correctly identifying conflicts with multiple capture sources on the one device.The problem basically is that because I can't get a reliable xml source containing both terrestrial and cable channels, I have set up a separate capture source to deal with each, although as I have only one PVR250, they are both related to the same device.
My default recording setup allows for 1 minute of pre-padding and 9 minutes of post-padding. Â When I have scheduled recordings that directly follow each other (ie one program ends at 8.30, one starts at 8.30), GBPVR of course ignores this end-program padding. Â The problem arises when the first program is taken from one capture source, while the second is on the other.
What happens is that the first program records correctly, and if you look at the recording status it looks like the new program is also recording correctly, but in fact the second one isn't recorded at all. Â On reviewing the video from the first program, I see that the channel is changed at the appropriate time to the correct new channel, which is then recorded for the nine padding-minutes.
The only applicable error message I can find in the logs is one in the gbpvrrecordingservice log, where it registers an error at the point where the second show's pre-show padding should be starting:
[b Wrote:Quote[/b] ]20:29:02.264 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Analog Audio In'I suspect that this will take a release-fix, but if anyone has any suggestions, they would definitely be welcome, as I didn't spot a few of these channel-conflicts and ended up not recording a few shows that my significant other had been following - oops.
20:29:04.671 VERBOSE ConnectPins failed!
20:29:04.671 ERROR Failed to connect pinNameCrossbarAudioDecoderOut to pinNameCaptureAnalogAudioIn
cheers,
tieke
[SIZE="1"]Gigabyte GA-MA69GM-S2H motherboard, HD6450, Athlon X2 4800+, Ninja Mini cooler, 1Gig RAM, Antec Fusion Case, 2xHauppauge HVR-3000 DVB-S, win7, 1 MVP[/SIZE]