First video: I really don't know what to even call this. I've had no issues with capturing and editing home recorded VHS tapes, but it seems that when I try to capture some commercial VHS tapes, I run into this issue, where 95% of the frame repeats itself and flashes as if it is stuck within a buffer, while the very top scan lines appear to play as normal. This happens with stabilization, DNR, and TBC on or off. All of these are on in the first video. Playback was on a JVC HM-DH30000U.
Initially, I thought this was some sort of copy protection, but the fact that the frame just repeats itself makes me think it's an issue within
VirtualDub or the drivers. I'm using the 32-bit version provided
here on a XP/7/10 and tried both the OEM drivers and the drivers posted
here as well as the MV hacks for the ATI x1900.
My other thought is that the issue could be mechanical. The VCR has an issue with the cassette loading mechanism that I've narrowed down to either the carriage being out of phase or some issue with the levers that engage with the cassette. The person I bought it off of had no concept of proper packaging (they used old slices of cardboard boxes, trays, and I think beer boxes for padding...), and it was either damaged during shipping and/or they failed to mention or image the damage in their listing, as it does have some cosmetic damage to the top and front cover, but the playback mechanism and the electronics have no other damage as far as I have been able to tell. Nothing is loose, nothing broken. The power supply has been totally recapped with either voltage equivalent or derated 105C capacitors, the MOV and the cord was replaced. I don't have any tapes that I can use to calibrate or adjust anything though if it's being caused by that, though I do have all of the other tools to do it.
No post processing was done on the video.
Second video: I read somewhere that the vertical jitter is caused by running both the TBC and the stabilization feature, is that what I am seeing in this video? Deinterlacing helps but it seems to go away when one or the other is turned off. Is there a way around that limitation?