Still getting frame drops/inserts when using TBC?
 

I bought a Key west TBC10 from lordsmurf a while ago. I’m capturing VHS with Virtualdub using a JVC S-VHS machine via S-Video into the TBC and then into capture card which is a GV-USB2 (I know there are mixed feelings about this capture device). I’ve done a few captures and there are variations but I’ve seen frame drops/inserts sometimes a few an hour. I know nothing about the technology behind TBCs so wouldn’t know if the unit is working or not other than the fact that it’s on. Should I have 0 drops and inserts at all times with this setup?

Not sure if it’s relevant but since I’m in the UK the unit had an adapter on the end of a plug and when plugging it in there was an instant pop and that power cable then didn’t work. I have since replaced the power cable to a UK one that doesn’t need an adapter and the unit powers fine so I’m hoping that this event didn’t damage the unit.

The TBC seems fine. What we need to now look at is the HDD/SSD config, and the capture computer.

Well I’m capturing on a NAS which is running a windows 11 virtual machine. The tape I’m doing now has 0 drops and inserts so it’s different for every tape, however the capture is going directly to SSD however I can change this to go to a HDD if that seems like the better option?

The easiest way to test if a TBC causing frame drop is to take it out of the workflow using the same tape in the same conditions with the same settings, If nothing changes it is not the TBC, look somewhere else, Pretty simple.

Unfortunately, that's not a controlled test.

Example:
- attempt 1 = TBC, record with dropped frames
- attempt 2 = no TBC, record without dropped frames
- attempt 3 = TBC, recording with dropped frames

But what's missing is the HDD/SSD write location. The above can be happenstance, when the actual cause is still the drives. So testing must be more meticulous than simple plug/unplug from a chain.

I've run into this myself. In general, swap for Samsung SSDs, or Seagate HDDs, and done.

He wants to know if the TBC is causing the frame drop, that's the only way to do it. "Looking somewhere else" statement summarizes what to do if the TBC is not the culprit, We can expand on that once he confirms the TBC is not to blame, Sure, it could be hard drives, OS, ...etc. but we don't know yet, so I didn't want to jump to conclusions, The process of elimination must be followed here starting from the source all the way to the computer.

I don't disagree with you. But OP needs to tread carefully, no haphazard conclusions. Essentially process of elimination, but with checks on all possible variables.