VirtualDub2

[shekh]

There is error in file creation when using segments: odml header/index is disabled. Looks fixable

[osgZach]

I've been testing out a fixed build provided by shekh, and it appears to work well.

I am also currently investigating my work flow to try and determine where and how an extra frame was inserted into a video stream (at the end). I will report back here when I have some findings. I vaguely recall confusion about the way vdub reports an extra frame in the past - or perhaps I am misremembering?

[lansing]

Bug reporting, setting in preference doesn't save unless I explicitly clicked "save". Clicking "ok" after changes doesn't save.

[shekh]

Bug reporting, setting in preference doesn't save unless I explicitly clicked "save". Clicking "ok" after changes doesn't save.

This is the purpose of "save". Not a bug

[wonkey_monkey]

I would say it is outdated/unexpected behaiour, though. These days an "OK" is expected to save and for those changes to persist. That's if there is even an "OK" to begin with, since even that seems to be falling out of fashion these days.

[shekh]

I would say it is outdated/unexpected behaiour, though. These days an "OK" is expected to save and for those changes to persist. That's if there is even an "OK" to begin with, since even that seems to be falling out of fashion these days.

This project has deep roots in legacy and software archeology :)
Anyway, thanks for suggestion.

[lansing]

This is the purpose of "save". Not a bug

But then why does the setting change get "remembered" for that instance of the program and not after I close and reopen the app?

[shekh]

But then why does the setting change get "remembered" for that instance of the program and not after I close and reopen the app?

Exactly, to let you use the setting "now" while keeping the saved preferences unchanged (for someone paranoid about making global changes?).
I made it worse with this feature: https://sourceforge.net/p/vdfiltermod/wiki/vdscript/

[lansing]

Exactly, to let you use the setting "now" while keeping the saved preferences unchanged (for someone paranoid about making global changes?).

That does not make any sense. Why would anyone making a change in setting scared about making changes? If anyone is scared about messing up, there can be a "restore default" button.

[MeteorRain]

Feature request:

When rendering video from YUV to RGB on the UI, is there a place for me to select which colormatrix to use for the input pane?

Imported a BT.2020 YUV420P16 avs clip, and the color displayed seems to be either 601 or 709 matrix.

Hopefully there's an option to select the correct colormatrix.

I'm perfectly fine with a context menu to pick 2020 every time I load a clip. But if this has already been implemented somewhere, please kindly let me know.

Edit: It seems Decoding Format is what I was looking for. Still, 2020 could be added to the input color space.

[shekh]

2020 matrix is a known issue, I'll add it when I can.

[hintlou]

Can the VirtualDub2 filters be added to avs scripts which aren't be processed in VirtualDub2?

[StainlessS]

LoadVirtualDubPlugin:- http://avisynth.nl/index.php/Plugins

EDIT: For usage, Advanced Search for "LoadVirtualDubPlugin" , select 'posts', not 'threads', and in Avisynth 'Usage forum'.

[LigH]

But ... for many VirtualDub(2) plugins, there are equal (if not even superior) AviSynth plugins available, often for VapourSynth as well. Loading VirtualDub plugins in AviSynth is only recommendable for those without a match.

[hintlou]

Thanks for StainlessS and LigH. I will study it carefully!

[hintlou]

I want to load the VirtualDub2 Plugin "Deinterlace-Blend fields-Keep top fields,interpolate/discard bottom fields" to my avs script,
but I can't find its vdf file and don't know how to set the filtername for its plugin function.
17240
+++++++++++++++++++++++
Would anybody give me a hand,please?

[LigH]

I believe such basic functions are not a plugin, but in the application core.

Apart from that, discarding and interpolating one field can be achieved easily with AviSynth core functions (SeparateFields, SelectOdd/Even, *Resize).

And it would be one of the worst methods to deinterlace. Why waste quality intentionally (except for academic purposes, to show how bad this result is)?

Recommendable deinterlacers which don't discard a field but use adjacent fields to reconstruct content are, from fast to precious: Yadif(mod), TDeint, QTGMC (that one has a complex installation but will be worth the efforts).

[hintlou]

Thanks for your advice.

I know it's not a modern deinterlacing method.
But the Blend fields plugin of VirtualDub2 can offer me the effect I need in some dvdripping cases.
So can the plugin be loaded in avs scripts?
I really really need it be loaded in my avs scripts instead of being loaded in VirtualDub2 only.
I want to separate the different parts of pictures in video for differently deinterlaced.

[LigH]

For the "deinterlace" filter, the responsible "Module" is "(internal)", so it is not a plugin but code in the EXE.

If it is not a plugin, it cannot be loaded. But it can be executed equivalently with AviSynth core functions.

[hintlou]

OK，Thanks....
How can I get the same/similar effect from AviSynth core functions (SeparateFields, SelectOdd/Even, *Resize) ?
Is there a documentation explaining about it?

[videoh]

Older deinterlacers like FieldDeinterlace() and TDeint() have blend modes. There may be others, such as SmoothDeinterlace().

[hintlou]

Thanks.I tried them:

"FieldDeinterlace(blend=true,full=true)" :
the deinterlacing quality is bad...

"TDeint(mode=2)" this is a blend mode:
the deinterlacing quality is ok,but the blending effect is different from the Blend fields plugin of VirtualDub2.

I don't have 32bit softwares so "SmoothDeinterlace()" isn't suitable.

[Andouille]

Try this in Avisynth :
Blur(0,1)

[videoh]

"FieldDeinterlace(blend=true,full=true)" :
the deinterlacing quality is bad... What is bad about it? You specified full blending so the progressive parts will not be spared.

[videoh]

Try this in Avisynth :
Blur(0,1) Yup, sounds about right for him.

[Stereodude]

Is it not possible to use CineForm in a .mov using fast recompress? I have AVIsynth spitting out V210 and CineForm is set to 10-bit 4:2:2 and says it will use V210 with no conversion and I get a Video format negotiation failure when using fast recompress. It tells me to use normal recompress or full processing mode.

[poisondeathray]

Is it not possible to use CineForm in a .mov using fast recompress? I have AVIsynth spitting out V210 and CineForm is set to 10-bit 4:2:2 and says it will use V210 with no conversion and I get a Video format negotiation failure when using fast recompress. It tells me to use normal recompress or full processing mode.


The short version - nothing funky is going on with full recompression. Make sure you set it up as 10bit in the cineform configuration and YUV 422 10bit. You're actually sending p210 (planar 10bit 4:2:2) with avs script (check with vdub2's file=>file information) and it'a a conversion to v210. It's a lossless re-arrangement of pixel format required for cineform which does not support p210

If you use vapoursynth, there is an enable_v210 switch that sends v210 instead of p210, and you can use fast recompress

[StainlessS]

No idea if this helps:- http://avisynth.nl/index.php/Internal_functions#OPT_Enable_V210

OPT_Enable_V210

global OPT_Enable_V210 = true ## default false AVS+
For 10bit YUV422, Frameserve interleaved V210 instead of planar P210. (VfW)

§ VfW here means Video For Windows clients such as VirtualDub are affected, but not other clients such as ffmpeg.

[Stereodude]

The short version - nothing funky is going on with full recompression. Make sure you set it up as 10bit in the cineform configuration and YUV 422 10bit. You're actually sending p210 (planar 10bit 4:2:2) with avs script (check with vdub2's file=>file information) and it'a a conversion to v210. It's a lossless re-arrangement of pixel format required for cineform which does not support p210

If you use vapoursynth, there is an enable_v210 switch that sends v210 instead of p210, and you can use fast recompress
I used the v210 enable that StainlessS pointed out (after your post) prior to my post last night and it did not work. However, after updating to the lastest VD2 it works fine. I guess there was a bug that has since been fixed and I didn't realize how outdated my version of VD2 was. :o

[StainlessS]

I guess there was a bug that has since been fixed
Not sure, think not a bug, was just not supported back then, Shekh & Pinterf got together and arranged for joint support.

[poisondeathray]

Not sure, think not a bug, was just not supported back then, Shekh & Pinterf got together and arranged for joint support.

Nice!

I wonder if this can be extended to avs+ script in avfs since it's vfw based??

Maybe it's the wrong place to ask, but vapoursynth's enable_v210 = True emulates v210, so the virtual AVI looks like v210 (e.g. other programs and mediainfo identifies it as v210)

But avs+'s global OPT_Enable_V210 = true still identified as p210 when sent through avfs

[lansing]

I'm having problem displaying blu-ray m2ts file, where any random seek will result in blocky gray images for about 10 frames, then it became normal again. And the issue doesn't end there. When I apply Neatvideo, a temporal denoising filter, the problem goes 5-6 good frames -> 15 blocky gray frames -> 5-6 good frames and repeat.

[Sharc]

I'm having problem displaying blu-ray m2ts file, where any random seek will result in blocky gray images for about 10 frames, then it became normal again. And the issue doesn't end there. When I apply Neatvideo, a temporal denoising filter, the problem goes 5-6 good frames -> 15 blocky gray frames -> 5-6 good frames and repeat.
With a random seek we will get garbled frames until we hit the next I frame in the stream (GOP start for correct decoding).

[videoh]

I'm having problem displaying blu-ray m2ts file, where any random seek will result in blocky gray images for about 10 frames, then it became normal again. And the issue doesn't end there. When I apply Neatvideo, a temporal denoising filter, the problem goes 5-6 good frames -> 15 blocky gray frames -> 5-6 good frames and repeat. Instead of opening the M2TS directly, make an avs script with frame-accurate seeking and then open that in VirtualDub2.

I don't know what VirtualDub2 is using to open M2TS files.

[shekh]

Instead of opening the M2TS directly, make an avs script with frame-accurate seeking and then open that in VirtualDub2.

I don't know what VirtualDub2 is using to open M2TS files.

I agree. Reliability of seek in VD2 depends on FFMpeg API which is not sufficient for some formats (like m2ts)

[StainlessS]

I'm sure that VH knows this already but DGIndex has these available as file extension filters in DGIndex:

vob, mpg, mpeg, m1v, m2v, mpv, tp, ts, trp, m2t, m2ts, pva, vro

[videoh]

Quite right, SS. but remember DGIndex is MPG2 only. DGIndexNV can handle the other formats. I think ffms2 would be fine also. Don't like to push my stuff to avoid triggering some members. ;)

[StainlessS]

DGIndex is MPG2 only
Arh yes, did not see the Blu-Ray thing.

[lansing]

I agree. Reliability of seek in VD2 depends on FFMpeg API which is not sufficient for some formats (like m2ts)

Alright, I was trying to do some quick tweaking with VD on the fly and don't want to go through "opening the video in a script and then loading the script" for every single video. I guess the long route is still inevitable.

[videoh]

Arh yes, did not see the Blu-Ray thing. My new abbreviation for you is now SssS. Reminds me of Windows SxS stuff.

[SeeMoreDigital]

My new abbreviation for you is now SssS. Reminds me of Windows SxS stuff.How about SßS

[videoh]

That works! But how to type that funny B? I don't seem to have one on my keyboard.

[Groucho2004]

But how to type that funny B? I don't seem to have one on my keyboard.This German grapheme is largely extinct now. Just use a double s.

[SeeMoreDigital]

This German grapheme is largely extinct now. Just use a double s.Nein!!!!!!!!!!!!!!!!!!!!

[qyot27]

Alt+0223 is the combo for the Eszett.

[Groucho2004]

Nein!!!!!!!!!!!!!!!!!!!!OK. According to this (https://en.wikipedia.org/wiki/%C3%9F#Usage_in_the_reformed_orthography_of_1996), there are still some uses for that relic.

@vh
If you really have to mutilate Stainless' moniker, use SssS.

[StainlessS]

Common guys, keep on topic.

ssS

[videoh]

@vh
If you really have to mutilate Stainless' moniker, use SssS. Umm:

https://forum.doom9.org/showthread.php?p=1905458#post1905458

[Groucho2004]

Umm:

https://forum.doom9.org/showthread.php?p=1905458#post1905458
Yeah, I know it's your creation. I probably should have phrased it differently.

[nji]

As probably most VD2's users I take VD2 for enhancing movies.

For that I have to assess the exact look of the orig movie
and the effect of the filters ... in VD2's display panes.

Just recently I realized that when doing this
... by zooming with context menu ...
the shown zoom is NOT the actual content,
but what the interpolation alg does from it.
Choosing the alg (to "pixel" = orig.) is only possible
by disabling DirectX in "Options / Preferences / Display",
or by enabling OpenGL.

So my suggestion/ question:
To disable DirectX at that point by default.
(If it doesn't have any other disadvantages I don't know about).