VirtualDub2

[shekh]

What's wrong?
https://i.postimg.cc/wT8gmVfd/filter.png

[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]

@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. :devil:

[LigH]

Alright, soon™ then ... and :thanks: 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:

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

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 (https://forum.videohelp.com/threads/397499-Decoding-WMAP-audio-codecs-with-VirtualDub).

[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/ycn7ce9fyw2ft3e/VirtualDub2%20issue.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

[shekh]

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

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

Looks like this is preview, you should start capture before, some details will change. In this state I don't see anything evil.

[Morku]

sry
https://i.imgur.com/rGnQu34.png

[shekh]

sry
https://i.imgur.com/rGnQu34.png

It looks wrong that cpu profile still indicates 5-100% - this is wide power range (I cant see proof that is actually has any bad effect).
Might be interesting to see the same test picture from the system where the capture works right.

Some generic ideas
disable audio resample (capture->timing->do not sync..)
change DirectShow options in capture->timing.

The choppy audio sounds like every sound packed is padded with silence - hard to tell with AAC on top. Don't know what can cause this.

[Morku]

This is from the System with mobile Sandy Bridge CPU where all is fine (with previous Windows OS version). Like it was on my main PC with previous Windows OS before 2004.

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

I changed option to like that:

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

It doesn't make any difference. Even disabling recording audio, the Inserted Frames till rise up and the preview video (Overlay) is choppy which is normally not.

[StainlessS]

Hi Shekh,
Perhaps you can inject some wisdom into this thread:- https://forum.doom9.org/showthread.php?p=1915724#post1915724
thanks.

[age]

Hi, is it possible to update ffmpeg and x264 to the latest releases?

[LigH]

@age - that seems to require a decision...

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.

[shekh]

Hi, is it possible to update ffmpeg and x264 to the latest releases?

It's good thing to do but I really lack time.

[Wam7]

Are there any Delogo filters that works with VDub2 x64?

[vigan1]

Hello, is there any tutorial on how to use it. Like all the function explained step by step.

I need to add a denoiser BM3D in virtualdub2 but I can't understand how to use avisynth scripts ?
Is there a way to use BM3D in virtualdub2 at 16bit (deepcolor i think) ?

Thank you.

[LigH]

VirtualDub filters and AviSynth plugins are different things. If you load an AviSynth script in VirtualDub2, then the filtering is probably mostly done in the AviSynth engine, so you will need to learn AviSynth scripting (http://avisynth.nl/index.php/Main_Page) to handle its plugins.

Apart from that, BM3D (https://forum.doom9.org/showthread.php?t=172172) seems to be a VapourSynth filter. Again, something different.

[Tehnicni]

Does anyone have experience with importing and processing raw images from any camera.
I am thinking of buying a good let say 14 bit camera for sunset time lapse and would like to ensure compatibility with VirtualDub2.

[poisondeathray]

Does anyone have experience with importing and processing raw images from any camera.
I am thinking of buying a good let say 14 bit camera for sunset time lapse and would like to ensure compatibility with VirtualDub2.


Raw images will not be accepted natively. They need to be debayered and processed and exported into some compatible format first, maybe 16bit PNG or TIFF .

eg. dcraw, RawTherapee, or commerical options like adobe, DxO etc...

[shekh]

Does anyone have experience with importing and processing raw images from any camera.
I am thinking of buying a good let say 14 bit camera for sunset time lapse and would like to ensure compatibility with VirtualDub2.

Yes VD2 does not have much to offer about raw formats. One thing you may think of is debayering with another tool to 16-bit tiff and then manipulate 16-bit sequence in VD2. Still, there is not much useful filters for that task, not a single HDR tonemapping for instance.

[Tehnicni]

I was dealing with these programs (free and paid) about a year ago, but I couldn't get a 16 bit image before tone mapping. Is LRTimelapse really the only solution for time lapse, which I don't like it.

For wide angle I have great solution YI action camera & VD2. At narrow angle (around 20 to 30°) sunset there is so big dynamic rang, that you can't handle without HDR.

Here is a nice wide angle sunset.
https://youtu.be/oI57LcjHOJs
And demo for txt and transition.
https://youtu.be/r4a5Vj4mPNs

[JK1974]

Is there a solution to split a long AVI file (in my case encoded with UTVideoCodec) to several smaller files (without recompression) not by setting a range for each segment?

I have used the scene detection feature of VD2 and then, after validation, set a marker on each correct scene start, but there does not seem to be an option to export those segments automatically into several AVI files.

Or does anyone know a tool that can accomplish this by importing a list of scene start frames? Because when I open the vdproject file in a text editor, I get entries like this;
VirtualDub.video.AddMarker(0);
VirtualDub.video.AddMarker(1030);
VirtualDub.video.AddMarker(1299);
VirtualDub.video.AddMarker(1311);
VirtualDub.video.AddMarker(1445);
VirtualDub.video.AddMarker(1449);
VirtualDub.video.AddMarker(1814);
VirtualDub.video.AddMarker(1911);
VirtualDub.video.AddMarker(2045);
Using a text editor, I could get rid of the AddMarker command, the brackets and the semicolon within seconds, so that I could get a plain list of section start entries... ;)

[nji]

Why are there 2 codecs offered for lagarith (lagarith.dll and lagarith.vdplugin), and what's the difference?

[LigH]

The archive VirtualDub2_44282.zip does not contain any lagarith.dll :confused:

[nji]

The version I use (44054) doesn't contain a lagarith.dll either. But still that codec is offered too when saving a movie.
Do you have only 1 lagarith entry when saving?

[StainlessS]

You probably installed a system wide Lagarith codec [maybe via some codec pack], the vdplugin thing comes with vdub2, and only works with vdub2.

EDIT:
This seens to be the Lagarith home site:- https://lags.leetcode.net/codec.html

Lagarith was last updated on December 8, 2011.
Last official version v1.3.27.

[nji]

The man from over the rainbow is right again :)
Thanks.

Actually I installed a codec pack (K-Lite).
But as probably most of VD users will,
and most of the codec packs will contain lagarith,
nearly everyone should have that double entry in VD (?).
Should be no problem to "disable" the vdplugin thing then?
(I hate unnecessary redundancy)

[LigH]

You might delete the vdplugin files from the plugin directories below VDub2. Would just be a pity if you missed any advantage of the native plugin if you prefer the VfW codec, if there are any.

[Blackout]

Hi i seem to experience a frustrating bug in the latest Virtualdub2

exactly same bug is in Virtualdub1. Hmmm

heres how to replicate:
1:/ Load Virtualdub1 or 2
2:/ Load avi
3:/ load "Load processing settings" containing the De-interlace plugin with setting to Yadif and double frame rate, bottom field first
4:/ scroll bar across bottom...avi ends early when dragged to far right.

in comparison...it works correctly if you do it in reverse:
1:/ Load Virtualdub 1 or 2
2:/ Load "Load processing settings" containing the De-interlace plugin with setting to Yadif and double frame rate, bottom field first
3:/ Load avi
4:/ scroll bar across bottom to the far right, last frame number listed on the slider bar far-right is double the figure from above procedure (as it should be)...avi ends correctly

????

Whilst there is a workaround it is fairly frustrating...please take a look at this would be much appreciated.

Cheers,
Blackout.

[LigH]

^ A few more bits were discussed earlier in the VideoHelp forums (https://forum.videohelp.com/threads/398846-Virtualdub-1-10-4-(last)-render-length-bug-due-to-framerate).

[shekh]

Blackout

Hi, show your processing settings (entire file). There is such effect when video length is written in script.

[Blackout]

hi shekh...sure thing here you are:

VirtualDub.audio.SetSource(1);
VirtualDub.audio.SetMode(0);
VirtualDub.audio.SetInterleave(1,500,1,0,0);
VirtualDub.audio.SetClipMode(1,1);
VirtualDub.audio.SetEditMode(1);
VirtualDub.audio.SetConversion(0,0,0,0,0);
VirtualDub.audio.SetVolume();
VirtualDub.audio.SetCompression();
VirtualDub.audio.EnableFilterGraph(0);
VirtualDub.video.SetInputFormat(0);
VirtualDub.video.SetOutputFormat(7);
VirtualDub.video.SetMode(3);
VirtualDub.video.SetSmartRendering(0);
VirtualDub.video.SetPreserveEmptyFrames(0);
VirtualDub.video.SetFrameRate2(1,0,1);
VirtualDub.video.SetTargetFrameRate(500000,10000);
VirtualDub.video.SetIVTC(0, 0, 0, 0);
VirtualDub.video.SetCompression();
VirtualDub.SaveFormatAVI();
VirtualDub.SaveAudioFormat("");
VirtualDub.video.filters.BeginUpdate();
VirtualDub.video.filters.Clear();
VirtualDub.video.filters.Add("deinterlace");
VirtualDub.video.filters.instance[0].Config(0,0,1);
VirtualDub.video.filters.EndUpdate();
VirtualDub.audio.filters.Clear();

Cheers,
Blackout

[TB54]

Hello everyone (sorry kinda newbie here)!

I was very pleased to discover the existence of Virtualdub2, and to see it could encode ProResHQ - which is really practical for video editing.

But weirdly, it seems most of the files I encode with Virtualdub2 (Uncompressed video files, h265 encoded files...) are not understood by Adobe Premiere/Encoder, which doesn't recognize the codec and doesn't want to import it.

Any idea why?

The weirdest happens when i export ProRes (in mov) from virtualdub2.

If the clip I export is shorter than 7mn10 (below 1,63 Go in this case), it opens without a problem in Quick Time Player, Adobe Premiere, or Adobe Media Encoder (the only difference with a "normal" ProResHQ exported from adobe or quicktime, is that when i import this one in Adobe, the video's codec will be called "APCH" and not "Apple Pro Res HQ").

But if the clip is longer than 7mn10 (or at least above 1,63 Go), it won't open in QuickTime, or Adobe Premiere/Encoder - the software says it can't read APCH codec (and Quicktime will also not open it anymore, speaking of "a bad public movie atom").

Of course it's an Adobe/QT problem, but what changes in the file after 7mn10 or 1,63 Go for it to suddenly be not recognized by Adobe? Is there a problem in the way it's exported? In the metadata? I first thought it was a problem related to .mov container, but it's the same difference once i muxed the file in a mkv...

The fact that an Uncompressed video file exported threw the old Virtualdub 1.10.4 opens in Adobe Suite without problem makes me think it's related to the software (well, freeware).

I would be very happy if there is a solution, or an explanation, because for video files encoded for the net or for my video player, Virtualdub2 is the perfect-dream freeware.

[LigH]

Thank you for your verbose report. The error message "bad public movie atom" is clearly a hint towards an issue with the structure of the MOV header.

[TB54]

Just to add a precision: the h265 not working in Adobe Suite were exported in mp4 container.

Thanks for the quick answer!

[shekh]

Maybe "mov +faststart" output option could change something, it alters the file structure (moves all headers to the beginning).
Also I had a bunch of requests to improve metadata on prores which I failed to reach yet. Could be related.