VHS Capture via Canon HV40

[Traderbam]

ConvertToYUV420() without interlaced=true right after the source filter will mangle your chroma.

Instead of cropping, this thread has some alternative scripting ideas to make the edge color issue less-bad: https://forum.videohelp.com/threads/354425-Hi8-capture-using-Digital8-camcorder-Edge-c...e2#post2557188

Interesting approaches, will look at that as an option.

For the ConvertToYUV420() option, what scenarios is this sort of conversion needed anyway?

I am still struggling to understand how I can do a interlace but retain HuffyYUV avi as the output format. I can do ProRes via Staxrip but as far as I know this converts to 10-bit and the file sizes are way bigger than the originals. Any suggestions as to a better flow to deinterlace, especially to a format I can import into Resolve for editing?

[Bwaak]

Firewire devices need drivers, which may be news for you.

No, they do not. The PC has to have the Windows firewire driver installed to operate the IEEE1394 subsystem but each device does not have it's own drivers. I have an HV20, a TRV-110, a TRV130, TRV 330, a couple of Panasonic MiniDVs and a Canon normal mini DV, all working on Win 10 and not one device-specific driver has been installed for any of them.

Now, it is a possibility that the Windows Firewire driver isn't installed correctly; I assume that is not the case though because, allegedly, the HV40 connects OK.

Here, a screenshot. I connected a Digital 8 camcorder to a computer that I haven't connected before. Until the driver installed, WinDV did not see the camcorder.

As I noted earlier, Windows 7 could not find a driver for a 1999 JVC MiniDV camcorder.

[Alwyn]

@Bwaak, my point is that the user does not have find a driver and manually install it for these camcorders. Windows has hundreds of drivers that are built-in and require no user input to install. I put in a cheap Firewire card in my Win 11 a couple of weeks ago. Guess what? I didn't do anything and it became operational the instant I turned my machine on.

I'll say it again. You do not need to install separate drivers for each Firewire camcorder you attach to you computer. Windows can do what it likes; I don't care. All I know, from extensive experience (including a few weeks ago), is that I have never needed to manually install drivers for any of the 12-odd camcorders I've used over the years.

As for WinDV, it is becoming increasingly unreliable and I no longer recommend it. And I haven't used Windows 7 for over 5 years; my analogue and DV capture workflows work just fine under Win 10 and 11.

[Bwaak]

@Bwaak, my point is that the user does not have find a driver and manually install it for these camcorders.

I am having a deja vu when someone renounces their own words. To my statement "Firewire devices need drivers, which may be news for you" you responded with "No, they do not. The PC has to have the Windows firewire driver installed to operate the IEEE1394 subsystem but each device does not have it's own drivers." Why don't you agree that you were wrong?

Windows can do what it likes; I don't care.

You not caring is not the same as Firewire devices not needing drivers.

All I know, from extensive experience (including a few weeks ago), is that I have never needed to manually install drivers for any of the 12-odd camcorders I've used over the years.

Anyone who had just a couple of lessons in logic will tell you that you cannot prove anything using an example or even a hundred of examples. You can prove something wrong by having a counterexample though. So, I am disproving your statement "each device does not have it's own drivers" by providing a counterexample, which I have documented with a screenshot. Q.E.D.

[Alwyn]

Troll.

[Bwaak]

Troll.

This is a funny response to factual information. Did not expect this from you.