strange time skip behavior

[cat6man]

this just happened out of the blue a couple of days ago, after years of smooth sailing.

i record with a hdhr prime w/cable card and while recordings are being made, and the files seem the right size, they play back funny and end way early.

1. i start to play a recording back (on either hd300 or hd200) and the video and audio are fine but the time stamp jumps about 30s for each 1s of real time........again, video and audio are fine but time bar is going wacky.

2. since the time status bar is going about 30x real time, the playback thinks it has reached the end of file way way early.

3. skipping ahead and back are also wacky.

i've rebooted the PC a couple of times with no improvement.

next step will be to play back the same files on the recording PC (running XP) and see if playing in sageTV on PC is also bad.

any ideas? could pc time be screwed up somehow? i re-sync'd to nist time, but that hasn't helped either.

[cat6man]

update: the files play back better with VLC on the PC but there are still apparently no timestamps.

a good recording (from earlier this week) plays in vlc, the time bar increases as it plays and the current time in the video updates as it plays. the 'go to a specific time' function works fine. it is clear that the entire recording is there and i can jump to any spot in the file.

a bad recording (from the last couple of days) plays in vlc, the time bar increases as it plays the but the current time stays as 00:00:00. the 'go to a specific time' function does not work at all

so it appears something in the recordings has gone bad relative to time stamping.

[KarylFStein]

I had some files with this problem and files with other problems when running SageDCT in dump mode. I think I ran them through Handbrake and all was well. Changing to ffmpeg capture helped. I haven't seen any weirdness since switching to OpenDCT.

[KryptoNyte]

If you're on Comcast, there was another Sage user that noticed they were now receiving h.264 instead of mpeg2. Maybe that's an issue for SageDCT? If you haven't already, it would be a good idea to move to OpenDCT as Karyl mentioned.