Lagarith.dll or Lagarith.vdplugin for capture?

[London]

In VirtualDub2 I have two versions of Lagarith available. There is 'Lagarith.vdplugin' (which I think is 64bit) and 'Lagarith.dll (which I think is 32 bit). Does anyone know what the differences are between the output from these codecs?

On my current Windows 10 workflow I can only get my Diamond VC500 USB working with VirtualDub2. I did the first VHS test captures using Lagarith.vdplugin but had errors when encoding to H.264 with command line FFmpeg. Redoing the capture using Lagarith.dll solved the error when encoding. Curious to know what the differences are and how they affect encoding.

[lordsmurf]

That VC500 card likely has others issues, like AGC.

I really dislike how VirtualDub2 gives options where none should exist. Use the original Lagarith, not the vdplugin. If not mistaken, the plugin is a passthrough to Lagarith, not the actual codec itself.

[London]

Having looked again I notice that both instances of Lagarith in VirtualDub2 are 64 Bit.

After doing more test encoding with command line FFmpeg, I couldn't reproduce the error I previously had with the vdplugin version. The error had prompted me to install Lagarith.dll (which turns out to be 64 Bit) to use with VirtualDub2.

I also managed to get VirtualDub 1.9.11 working with my VC500 USB, so I will use it for capture. The 32 Bit version of Lagarith appears there.