Page 1 of 1

Virtualdub & Avisynth = different results

Posted: Mon May 09, 2011 1:24 pm
by themaster
I'd like to understand why i get different results when i use neat video inside virtualdub and inside an avisynth script, please read below:

1) I feed vdub with an avs script in RGB32; in vdub i output in rgb 24, compression with huffyuv (that's what it like..rgb24)

2) Now this time in the avs script i use neat video directly, use the same profiles, same parameters (interlaced, temp radius etc..), output in rgb24:
Script:
Avisource("H:\MyVideo", fourCC="HFYU", pixel_type="YUY2")
AssumeTFF
ConverttoRGB32(matrix="rec601",interlaced=true)
LoadVirtualDubPlugin("C:\Program Files\VirtualDub-1.9.8\plugins\NeatVideo.vdf", "NeatVideo", 2)
NeatVideo("C:\Program Files\Neat Video for VirtualDub\PROFILES\blabla.dnp", "C:\Program Files\Neat Video for VirtualDub\PRESETS\blabla", "1.0", "2", "1", "1")
ConverttoRGB24(matrix="rec601",interlaced=true)

Comparison, image (noise):
vdub vs avs, click here


Full size pictures:
Vdub vs Avs

The sharpness is different and the noise residue is different .. What !?

Posted: Mon May 09, 2011 9:38 pm
by NVTeam
How did you extract these frames, using which controls in VD? From which point of the rendering workflow do they come? Please describe that step by step.

Thank you,
Vlad

Posted: Tue May 10, 2011 12:29 am
by themaster
I have extracted both of these pics with AVSP which is an avisynth script editor from Raw processed avi

Posted: Tue May 10, 2011 12:45 am
by NVTeam
Which version of NV did you use?

Vlad

Posted: Tue May 10, 2011 12:51 am
by themaster
I have used the version 2.22

Posted: Tue May 10, 2011 12:52 am
by NVTeam
Please update it to the latest version.

Thank you,
Vlad

Posted: Tue May 10, 2011 12:30 pm
by themaster
So in essence you're saying that in the latest version there is no such a bug?

Posted: Tue May 10, 2011 12:55 pm
by NVTeam
The version you use is outdated. Please try to update to the latest version to check if you still observe the same problem. It may or may not be present. To know for sure you need to check that in your own workflow.

Thank you,
Vlad