VirtualDub 2 vs original VirtualDub frame rate conversion

[rgr]

But it has an additional step - conversion with an external program and unnecessary recompression.
Using AviSynth, you would directly load this VFR file into VDub, already converted to CFR "on-the-fly".

[S-da]

Rgr,
can AviSynth really recognize a variable framerate (VFR in a MP4-video) completely correctly and output it for VirtualDub2 "understandable"?
(If you would have to specify a framerate for Avisynth to recognize it, then it would probably not be really accurate.)
If AviSynth can do so, then what would you have to do, step by step, to set it up for VirtualDub2 (also including the contents of a script-file)?

[rgr]

Yes.

name1="input.mp4"
a=LWLibavAudioSource(name1)
AudioDub(LWLibavVideoSource(name1, fpsnum=30000,fpsden=1001), a) # for 29,97fps

or better:

name1="input.mp4"
a=LWLibavAudioSource(name1)
AudioDub(LWLibavVideoSource(name1).TimeCodeFPS(name1+".txt", fpsnum=30000,fpsden=1001), a)

but in this variant you must first create a timecode file:

mp4fpsmod.exe "input.mp4" -p "input.mp4.txt"

[S-da]

Rgr,
I do not know how to use this code.

Actually I only have VirtualDub2 installed.

What I meant, what I asked for, was an appropriate guide to setting it up (step by step):
What needs to be (additionally to VirtualDub2) installed and where, what needs to be set up and where, what needs to be created and where, ...
What is all to do to make it possible that a VFR of a MP4-video is processed correctly in VirtualDub2?

First, i have to install AviSynth, right? But simply a regular Installation of a program or something special, even to make it work with VirtualDub2?
And then, what is all to do next?

[rgr]

1. Download and install AviSynth:
https://www.videohelp.com/software/AviSynth-Plus
2. Download, unpack and upload to "C:\Program Files (x86)\AviSynth\plugins64" these plugins (only .dll x64 files):
https://github.com/HomeOfAviSynthPlusEvolution/L-SMASH-Works/releases
https://github.com/Asd-g/TimecodeFPS/releases
3. Create a file input.avs with Notepad and place my code in it (change the file name in the content to the correct one).
4. Load the file into VDub. Done.

[lordsmurf]

VDub2
And it's still the only good, flawless tool for capturing.

That's never been true. VirtualDub2 tends to induce overuse of resources, incur dropped frames, etc. The likely reason is that the software was massively bloated vs. the original VirtualDub. It can sometimes work for capture, but you must have a lean system, essentially only using it for capturing. No other software, not online, nothing. (In some rarer cases, often due to Nvidia drivers, VirtualDub2 works when VirtualDub will not. But that's not even 1% of the time. Or in certain known scenarios, like Tevion/XP, due to audio preview.)

And when I switched to it, VirtualDub2 showed me that many things in it had been improved compared to the previous VirtualDub, even previous errors in the handling. -

But the issue is that it broke as much as it added or fixed. Certain VirtualDub filters, and VirtualDub 1.9.x capturing, was perfectly fine. Even 1.10.x official wasn't as wonky. And the issue is that the developer of VirtualDub2 did not care. Just more of the modern "it worked for me (so who cares abut you?)" attitude.

Yes, VirtualDub2 is obviously not perfect, but still definitely my choice.

But choice for what? I agree, it's fine for some. But terrible for others.

Yes.
or better:

My concern would be that no amount of importing variable framerate video will be a final fix. There's always going to be issues in editing or watching. Variable framerate was such a stupid idea, a 2000s half-baked attempt to save on file size. Not to be confused with TS broadcasting, where it does (or rather did) make sense.

[rgr]

VDub2
And it's still the only good, flawless tool for capturing.

That's never been true. VirtualDub2 tends to induce overuse or resources, incur dropped frames, etc.

This has always been true, you just need to use it correctly. What I proved:

https://forum.videohelp.com/threads/416658-Nero-Video-Grabber-vs-Hauppauge-WinTV-USBli...-August-VGB300

[lordsmurf]

But you just linked a thread that sort-of proved my point?

And it used Easycaps.

But it is nice to see, in that thread, what I've said all along:

AmaRecTV doesn't report accurately

I'm just going to back away slowly, carry on.

[rgr]

I don't need to continue, everything is written there.

[Alwyn]

everything is written there.

And it's codswallop.

[rgr]

everything is written there.

And it's codswallop.

This is your opinion, which is absolutely irrelevant in the face of evidence.

[Alwyn]

This is your opinion, which is absolutely irrelevant in the face of evidence.

I'm happy that the tests that I have done confirm the drops/inserts by AmarecTV are exactly what it reports. Your tests may show something else. Believe what you want.

[rgr]

This is your opinion, which is absolutely irrelevant in the face of evidence.

I'm happy that the tests that I have done confirm the drops/inserts by AmarecTV are exactly what it reports. Your tests may show something else. Believe what you want.

It's great that it reports what it loses. However, VDub doesn't lose anything, and that's somehow more important.
https://forum.videohelp.com/threads/416658-Nero-Video-Grabber-vs-Hauppauge-WinTV-USBli...e2#post2778478