The Hauppauge Capture application produces corrupt .TS files when capturing long files.
I have now read every post in this long thread and it seems that almost half the posts talk about using TSMuxer, TSDoctor, VideoRedo's Quickstream Fix, etc. to fix the files captured by this application.
This is not right, especially after the product has been on the market for 2+ years.
Here is my current problem:
I'm using the Hauppauge Capture application with my 1512 PVR. I am using default settings, with the encoding set to Variable at full bitrate (14 Mbps). I am recording using the .TS setting. I am recording to my main editing computer via a hardwired network connection over a 1 Gbps network with no other users. I have the latest Capture drivers and updates (December 2015). I am capturing via Component from my Cisco ISB7500 DVR. The audio is captured via optical.
When I record short 10-30 second test clips, these load and play fine in Windows Media Player, VLC, Sony Vegas (versions 10 and above), VideoRedo, and more. I can capture AC-3 5.1. This is good.
However, when I do a "real" recording of a TV show that is 1-3 hours long, that file will not load and play in anything except for the VLC video player. It hard crashes everything else.
I have tried cutting the first 10 seconds of the file, using the Edit tab in the Capture application, but the resulting file still doesn't work. I have tried to convert to MP4, but I immediately get a Runtime error, and the Capture application crashes.
Finally, I tried recording directly to MP4 rather .TS, but found out that there is a major, undocumented problem with MP4, namely that Hauppauge Capture, when set to record to MP4 records in variable framerate
. Thus, instead of getting a 29.97 fps, the frame rate speeds up and slows down, resulting in a weird average rate (e.g., 29.82). The resulting file cannot be reliably edited, and results in horrible-looking video. I understand the need for variable framerate for streaming, but I don't see how it should ever be used for hard drive capture. This issue was first revealed, in this thread almost two years ago, here:
It has not yet been fixed or changed.
Also, this is not the first time in this thread that someone speculated that the length of the capture might be causing corruption. See this post:
Long Capture Corruption
I am now doing step-by-step troubleshooting, something that is really difficult, because I have to capture for a long time (at least an hour) to make the problem appear. I am first capturing to the local hard drive on my laptop rather than directly to my editing station via the LAN. If that doesn't result in a good file, I'll try Constant Bitrate rather than Variable, because some people have suggested it might create a more compatible file.
No reply yet from Hauppauge, although they usually do respond within a day or two.
Does anyone have any ideas as to how to make this work?
BTW, in my earlier posts about interference patterns on my capture, I have now ruled out cables as being the cause, and now believe that I have some sort of a ground loop (my home theater is a complicated setup). That's a bummer because ground loops are a bear to troubleshoot.