There's some more info from VRD at this point. It seems that ALL of the Hauppauge recordings that are edited with VRD are screwed up. Because (I guess) the SEI is unstable due to the way the Hauppauge makes recordings, it is only made even worse by VRD. They're recommending running it through TSmuxer FIRST before editing so that the SEI will be re-written and everything will be fine once it's edited.
A few frames are recoded around every edit point with VRD so there will likely be some sort of problem at every edit with Hauppauge files. It also depends from player to player how it will manifest itself.
From one of the authors:
Quote:
The problem is likely a mismatch between the few frames we have to recode for the edit and the original stream. Our encoder doesn't support every possible H.264 option, so if your source stream is using something it can't support then there will be a slight mismatch which could cause the error you're seeing.
|
They're (hopefully) working on a fix for it but there's no guarantee that they'll be able to fix the files that are already screwed up. Although TSmuxer can fix short files (probably around 1-2 minutes), anything longer it crashes. I'm hopeful that there's a way to fix it for larger files. *fingers crossed*
However, from this point forward, I'll run every recording through TSmuxer FIRST and then go from there with regards to editing and burning. It's just shocking that it's taken 4 years to find this problem.