After reading the forums here I invested in a Panasonic NV-HS1000 VCR and a Hauppauge VCB-e capture card to digitize family videos from VHS-C casettes in PAL format. Previously I already digitized them using a consumer VCR and an EasyCAP (I know, I know...). My only complaint from this previous capture (at the time!) were a handful of casettes that occasionally switched to grayscale video with coloured stripes across the image horizontally (green/purple). This appeared mostly throughout the entire duration with varying severity. I initially ascribed this to a degraded tape, but then I though, hey, let me see if it can get any better. (I just now saw that this is a common issue with cheap hardware, most recently perhaps here: Color banding issue
Fast-forward to the new setup:
NV-HS1000 ==> S-video + RCA audio to 3.5mm Jack ==> Hauppauge VCB-e ==> Virtualdub
Using this workflow I made some nice progress with the casettes that previously showed the "colour loss and green/purple stipes". These were recorded in my newest attempt in a much better quality with proper colour, no stripes or colour banding, although perhaps a bit noisy. Still, it was nice to see the "instant" improvement. However, in every such tape there are some parts, where the entire image jumps completely left and right, exposing large patches of black areas. Independent of any settings that I use (on the VCR itself or in the capture settings) I always get this error at the same parts of the video. The error is new to this workflow and looks something like in the following image.
This is where I am stuck and would appreciate some input before proceeding. Based on my searches, the closest I came to finding this exact problem was Excellent videos showing the exact effects of time base errors & TBC
, where tapping on the VHS deck makes the image jump around. This would then appear to me as a severe time base error at only some sections of a few tapes. I realize I do not have an external TBC and my main question would be, is this the cause? Would an external TBC help remedy this artifact/error or is this some other issue and I am on the wrong track?