IO Data GV-USB2 proc amp sharpness settings.

[rgr]

Three errors in one sentence:

The only errors are in your flawed reasoning and your flawed test.

Flawed test because you say so. Of course

1. VirtualDub does not introduce a/v asynch, it is exactly the opposite -- VirtualDub can resample the audio sample to fit the frame length -- that's why captures from VDub have better sync than from AmarecTV.

False. In addition to my own experiments, there are many reports from different users in various forums about that. Just few examples because I do not keep all the links, there are many others if you search:

Links to tests that don't provide any information about the settings? Poor. They definitely won't look through everything, too much noise.

2. AmarecTV's logs are great, but what good is it if it reports 0 dropped frames, and a simple count shows that it dropped 22

frames out of 180,000? So where are they? I can see that these frames are there after capturing them with VirtualDub. And AmarecTV skips one frame every 8,000 frames with perfect regularity, "just because".

In addition, the fact that a card drop a frame every a certain number of frames is not credible, because there are no scientific reasons for that, except a flawed test.

So you didn't read anything. VirtualDub didn't drop a single frame, AmarecTV did. So you think it's the card's fault or maybe the system selects programs that it works well with? (BTW: and it wasn't even the card).

In addition, the fact that the nuber of dropped frames changes with the software has low credibility, showing in truth a weakness or a marginality of the capture (and record) system.

You won't be a diagnostician

In addition, VirtualDub2 is not recommended by many as capture software compared to previous versions, because introduced a regression in the capture engine. I myself experimented that with VDub2 and a old OS (Win7) and modern OS (Win11) using an IODATA GV-USB card capturing an average quality tape, where Vdub 1.9.11 was performing better in term of dropped frames and a/v synch (as I reported in one of my recent posts about GV-USB2).

The capture module in VDub has been unchanged for ages -- the last changes were probably in version 1.6.x. You're creating your own matrix....
Based on your diagnosis, your system seems to be malfunctioning. For me -- every version works perfectly (VirtualDub2 and above).

As Sharc properly pointed out in the general approach we all have about our findings (me included), you are just focused on your (flawed) test, and simply do not see the real world.

Yes, yes. Flawed because it is flawed. Final argument. Worth 0.

[lollo]

You’re so blind that you did not understand a word of what I wrote. Pearls before swine!

Yes, final argument: you’re wrong, I am rigth; it is so obvious from our posts and evidences (mines, yours are flawed). As always

[rgr]

You’re so blind that you did not understand a word of what I wrote. Pearls before swine!
Yes, final argument: you’re wrong, I am rigth; it is so obvious from our posts and evidences (mines, yours are flawed). As always

But you're writing nothing. It's just unsubstantiated speculation, pure conjecture, unsubstantiated theorizing. I'm not asking for evidence because I know there won't be any. It's pure demagogy, the "I'm right because I'm right" kind of thing.
I know, I know -- when one thing works and another doesn't, the test was definitely bad. Why? Because it was bad Or the system was bad

[lollo]

Sure!