VirtualDub2

[shekh]

What's wrong?

[nji]

There are several things that are wrong here.

1. At my (quite typical) installation sections "Preferred filter" and "Display mode" are all greyed ( = can't be changed).
2. "Preferred filter" is set to "Any available" which means that it (at my config) uses bicubic.
This is completely nonsense as I (as already mentioned) need to assess the actual pixels, and no "en-nicing".
3. Enabling section "Preferred filter" works at me only if enabling "OpenGL" (which has time-consuming disadvantages I assume).
If I disable DirectX at all (and fall back to GDI?) has other drawbacks I assume. But obviously (although still greyed "Any available"
chosen then) it uses the wanted "Point" method.

==> Everything is wrong.

[shekh]

Check this: https://sourceforge.net/p/vdfiltermod/wiki/display/

Why best setup is not initial? Because of historical reasons.
With Direct3D all options should be enabled, if you have them grayed it is strange.

[videoh]

I confirm options are all enabled when configured that way. Thanks!

[nji]

I agree to that ... IF options are configured that way.
(If anything else fails >> read the wiki ;-)
(Will take my time now to read all it's pages finally).

Still I would like to point out once again that to my opinion it makes no sense to set "Preferred filter" to
- "Any available" (since you don't know which that may be)
- anything else but "Point" (since I want to assess the movie, and not enjoy a "en-niced" version of it).

Hope that it may be of any enlightment for not only me ;-).

Thanks for the contribs!

[nji]

For this issue I have one more suggestion:

Could you please remember the chosen values for "Preferred filter" in VD2?
As you do with "zoom".

[LigH]

We may need new ffmpeg input plugins supporting AV1; I could not open the YouTube beta UHD files.

[LigH]

@shekh - any opinions about updated input plugins?

[shekh]

Originally Posted by LigH

@shekh - any opinions about updated input plugins?

Hi, the plan to do this is to update ffmpeg build to the current version and check for any breaking changes. Also it will lose XP compatibility so I have to decide something about it.

[StainlessS]

Shekh, if you do decide to abandon XP users, then please make available "LastForXP" version on your github, and thanks very much whatever you decide.

EDIT: I meant Sourceforge.

[videoh]

C'mon shekh, drive that stake through the heart of XP.

[LigH]

Alright, soon™ then ... and in advance.

[Emulgator]

Hi shekh, many thanks for your continued work on that valuable tool !
Donation time for me.

Please no unnecessary XP killing if it can be avoided
There are still many use cases around the world.
Here running 5 machines XP32ProSP3, 3 machines Win7U64SP1.
Let's not forget: Some useful softwares, devices and their drivers are working perfectly well, but are abandoned and will never be updated above WinXP. People in some parts of the world are still blocked out by embargos (I was once too) and will see no financial progress.
They won't have access to newer, hungry, more expensive machines, but are capable of doing good stuff with the old ones...

Where do I put it ?

[wonkey_monkey]

A couple of feature requests:

A couple of things have bugged me about this dialogue box for a while.

Firstly, "Video data:" and "Audio data:" have the suffix "KB", but "Projected file size:" has the suffix "K". Making them match would make the numbers in the last two line up and make for easier comparison.

I think the bitrate in "Video data" should come before the data size to maintain that alignment for all three fields. Come to think of it, why not include a bitrate for "Audio data" as well?

Lastly, it has always bugged that there isn't an "Estimated time remaining" because this would be the most useful information to display. "Time elapsed" and "Total time" don't actually tell you anything useful unless you do the mental gymnastics to subtract one from the other.

[LigH]

Does the ffmpeg input plugin also have known limits regarding very low bitrate WMA9 and (possibly HE) AAC, or on-the-fly resampling while decoding? Seems to be the case in this VideoHelp forum thread.

[Morku]

Are there any known issue for Windows 10 Version 2004 (Version 19041.329) when Capturing AVI? I have.

Today I wanted capture some AVI with my Dazzle DV100 (DirectShow) with VirtualDub. But instead to get my fluid and clean result as usually, the video is choppy and audio distorted.

To show you, I recorded a short clip (little compressed) and uploaded here: https://www.dropbox.com/s/ycn7ce9fyw...issue.zip?dl=1

I have also put my VirtualDub Settings into it.


Luckily, I have some other hard drive with Windows 10 Version 1809 (Build 17763.1039) on it.

So: Same hardware, same grabber, same player, same settings, same VirtualDub2 version -> no problem at all. The result is clean.

Now, to verify, it's 'not NVIDIA again', I took my older Laptop with integrated Intel HD graphics on it, also Windows 10 Version 2004 (Version 19041.329).
The result is again choppy and audio distorted.
And of course to verify, it's not my player, I checked my Nintendo N64 on my grabber, but the result is the same.

The choppy video and distorted audio is already in the Preview, not just the output file.

So it comes down, the only difference I notice between fine and distorted result is the Windows version.
What can I do and try now?

VirtualDub2 is build 44282

[shekh]

Morku

I don't know, the only idea: make sure you capture at 100% cpu power. "balanced power profile" may have bad effect on capture and it may change with os version. I saw it happening only once though.

[Morku]

For test, i set my energy settings in control panel to "ultimate performance". Also I set the hook in VirtualDub2 for "Maximize CPU power when capturing", but the result is the same. Chopy and audio distorted.

During capturing, the Inserted frames statistics rise up. "Like my PC is to slow". But can't be, it's i7 6-core 8086K, 32GB and all SSD.

I have tested another Laptop with Windows version 1909 on it. Sandy Bridge i3-2328M CPU 2-core CPU, 4GB RAM and same old slow HDD and the recording is absolutly fine.

Unfortunately I have no other DirectShow recording device to check the result there. Still could be something incompatible driver of Dazzle DVC100 in 2004. But the device and driver is detected fine and video/audio passthrough 'somehow'. So I don't know...

It's definitely really annoying

EDIT: tested with OBS and the result is choppy, too. So probably some driver or W10 2004 in general issue...

[shekh]

To get more info:
during capture test
1) Capture->DShow graph
dshow may construct extremely weird decoding chains
2) Capture->Realtime profiler
just make screenshot of it

[Morku]

Thank you for having a look, also when I think there is nothing we can do.

https://i.imgur.com/daLWVDr.png