Capturing via GV-USB2 in correct frame rate and workaround

[waxstone]

I'm trying to make sure that my raw captures are suitable for encoding.

My current setup is: Japanese VCR -> GV-USB2 -> Amarec

I reinstalled GV-USB2 drivers (after device issues) and now the correct frame rate option doesn't appear in Amarec, it shows 59.94 fps rather than 29.94. (All interlaced captures)
As a result I have captured 3TB of 50+ hours of footage in the wrong frame rate. Recapturing everything correctly will take a lot of time. Prior to this, all was captured fine in 29.94. Something happened inbetween.

Main questions:

• Is there a way I can convert this existing 59.94 interlaced to 29.97 interlaced? This would save me from recapturing.
• Are there any workarounds to get Amarec to capture in the desired frame rate? Virtualdub is out of the question, like many others there are sync issues using modern hardware.

Settings in Amarec and GVUSB2 are as follows:


[Attachment 86544 - Click to enlarge]


[Attachment 86545 - Click to enlarge]


[Attachment 86546 - Click to enlarge]


[Attachment 86547 - Click to enlarge]


[Attachment 86548 - Click to enlarge]


[Attachment 86549 - Click to enlarge]

I've looked into the driver issue and have followed instructions to resolve the issue (reinstalling/rolling back the device drivers) and like others it didn't work out: https://forum.videohelp.com/threads/411694-IO-Data-GV-USB2-112-Driver-Minimum-Capture-fps-is-50

In terms end goal, I want all my footage to be converted to 59.94 to achieve that buttery smooth look. Another issue I'm struggling with is encoding workflow: https://forum.videohelp.com/threads/417773-Best-Hybrid-settings-for-encoding-broadcast-vhs-captures

(I generally just want to convert these to 59.94, soft noise reduction, correct aspect ratio, compressed to reduce space).

[Alwyn]

Here you go @Waxstone (my site):

https://www.aaproductions.net/gvusb2.htm

TLDR: in the Format box, just overwrite the 59.94 with 29.97. We PALites have the same issue with 50fps/25fps.

Re your captured footage at 59.94, I'm sure the experts will have a solution.