No Video after channel change on ATSC - ConnectPins failed in logs

[sub]

hmm just a thought.. this might be more of a feature request, but could it be possible to disable timeshifting mode for a particular capture source?

Sorry, that wouldnt be straight forward. Its all or nothing.

[sgilani]

Fair enough, just thought I'd ask.

I hope we can get to the bottom of this timeshift bug though; something very strange seems to be going on.

[sgilani]

sub,

I took the plunge and formatted and re-installed everything from scratch. Once again, the same problem with ConnectPins and the Video Analyzer error comes up.

2008-05-01 21:34:08.314 VERBOSE ServiceID: 3, PMT PID: 48, VPID: 49, APID: 52
2008-05-01 21:34:08.314 VERBOSE SubmitTuningRequest() complete
2008-05-01 21:34:08.315 VERBOSE PCR PID is set to VID PID
2008-05-01 21:34:08.315 VERBOSE Creating Audio pin...
2008-05-01 21:34:08.315 VERBOSE getSetting(PreferredAudioDecoder)
2008-05-01 21:34:08.315 VERBOSE ...used cached audio media type
2008-05-01 21:34:08.315 VERBOSE Creating Audio pin mapped to PID 52 (AC3)
2008-05-01 21:34:08.316 VERBOSE getSetting(BDAUseCachedSequenceHeaders)
2008-05-01 21:34:08.316 VERBOSE Setting media type for HD
2008-05-01 21:34:08.316 VERBOSE Creating MPEG-2 Video pin mapped to PID 49
2008-05-01 21:34:08.316 VERBOSE ...used cached video media type
2008-05-01 21:34:08.323 VERBOSE ConnectPins: 'Video' to 'Input'
2008-05-01 21:34:08.331 VERBOSE Using DVR-MS mux
2008-05-01 21:34:08.331 VERBOSE ConnectPins: 'Output' to 'in'
2008-05-01 21:34:08.331 VERBOSE ConnectPins failed: hr = 80040209
2008-05-01 21:34:08.331 ERROR Failed to connect flowStatusFilter to Video Analyzer In
2008-05-01 21:34:08.332 VERBOSE ConnectPins: 'out' to 'DVR In - 1'
2008-05-01 21:34:08.332 VERBOSE ConnectPins: 'Audio' to 'DVR In - 2'
2008-05-01 21:34:08.332 VERBOSE About to call pSink->LockProfile(NULL)
2008-05-01 21:34:08.389 VERBOSE Target DVR-MS filename: J:\Buffer\Without a Trace_2_20080501_21012200.dvr-ms

This was with the DVR-MS mux, and I had the same problem with the same ConnectPins failed message for Cyberlink, MainConcept, and ATI mpeg muxes.. so the problem isn't the mux.. It has to be something in GB-PVR.

Can you please look into this? There must be something messed up somewhere. I'd hate to think I took all the time to format and re-install only to end up nowhere.

[sub]

Can you zip and attach that complete log file?

[sgilani]

whoops, sorry forgot to attach the logs. I just ran it again to re-create it, here's fresh logs for you. (same errors)

[sub]

I'm not really sure what the cause would be. It looks like its failing to connect two Microsoft components that normally have no problems connecting.

I see you're running vista home premium, does MCE work on this machine?

[sgilani]

I've never tried MCE.. and honestly have no clue how to do anything with it.

If it helps, I can confirm that everything works fine in Live Preview mode though. (when in timeshifting mode, it has this problem, and only after a channel change.)

[sub]

I suspect it'd probably record with the Cyberlink/ATI/TSMux BDA mux options aswell. It seems to be having a problem connecting two of the Microsoft DVR-MS mux components.

[sgilani]

Is it really a DVR-MS mux issue though? Because I get the same ConnectPins error and the same black screen for video problem if I use one of the MPEG muxes as well. (first post of the thread deals with when I was trying CyberLink mux)

[sub]

Is it really a DVR-MS mux issue though?

To be honest I have no idea. The last set of logs was failing to connect two DVR-MS components though.

Try the TS Mux option. If that doesnt work, attach the logs and I'll take a look.