VirtualDub2

[jay123210599]

Originally Posted by tebasuna51

Right click over the image and select the aspect ratio desired.

If you have a correct source DVD (VOB file) VirtualDub2 select the correct aspect ratio for you, see the image.
Maybe for your source you need select the aspect ratio manually.

I opened my VOB file on VirtualDub2, but when I extracted a frame from it, the resolution was still at 720x480. Even when I adjusted the aspect ratio, the resolution of the image still wouldn't change.

[LigH]

The display aspect ratio only affects the display on screen. You need to actually resample the frame to a new dimension, that's what the resize filter does.

[SeeMoreDigital]

Originally Posted by jay123210599

I opened my VOB file on VirtualDub2, but when I extracted a frame from it, the resolution was still at 720x480. Even when I adjusted the aspect ratio, the resolution of the image still wouldn't change.

After importing your video. Select: Video -> Filters -> Add and navigate down the list to 'Resize' and press OK

While within the resize filter widow: -
Under 'Aspect ratio' select 'Disabled'.
Under 'Filter mode' select the resize filter that best suits your needs.
Under 'New size' select 'Absolute (pixels)' and enter the required pixel values in the two boxes.

[nji]

I'm using VD2 since a long time to improve (mostly older) videos
from all kind of devices.

Mostly I use internal and Anton's filters,
additional a few special ones (ACOBW and NDF, DeLogo, Deshaker and some MSU filters).

Some of the internal filters I never used.
Maybe I miss something with them, so I would like to ask for hints
when/ if these filters are useful:

2:1 reduction (high quality)
Which differences to filte "resize (50%)"?
Quality? Speed?

convert to floating point
Useful when ...?

gamma correct?
Useful when ...?

warp sharp, warp resize?
Both seem to produce bad results...

BTW
What does the "Save" button in filter dialog do?
(There is no "Load" etc.)

TIA

[v0lt]

VirtualDub2 v2.2.0.755

Changes:
The auxsetup utility now has two versions: for win32 and x64.
Removed "64" prefixes for exe and dll files.
Improved HiDPI support.
Fixed output of system messages in vdub2.exe.
Code refactoring for modern compilers.

Updated avlib-1.vdplugin to version 0.7.1.220.
- Video files with incorrect (or unrecognized) frame rates are not supported. This fixes the plugin crash.
- Code refactoring for modern compilers.

Updated scripted.vdplugin to version 0.2.1.92.
- Fixed script saving.
- Now uses Avisynth+ header files. Minimum supported version of Avisynth is 2.6.
- Code refactoring for modern compilers.

Also available is old VirtualDub2 44282 with updated avlib.vdplugin.

[v0lt]

It's very strange, but 32-bit scripted.vdplugin 0.2.1.92 for some unknown reason scores 9-12 points on VirusTotal. There is no such problem with the 64-bit version.

I used Visual Studio 2019 v16.11.42 and Windows SDK 10.0.19041.0.

Added
Rebuilt scripted.vdplugin 0.2.1.92 on a clean virtual machine with Visual Studio 2019 v16.11.42 and Windows SDK 10.0.19041.0 - nothing changed.

[StainlessS]

Is the offending file compressed with UPX ?,
if so try virustotal scan without UPX.

EDIT:
Damn, false +ve's growing, 19/71 (I did a rescan on VirusTotal original file, was original [for me] 17/70])
https://www.virustotal.com/gui/file/...989f005de3059d

EDIT: Maybe of interest (for Microsoft defender "Win32/Wacapew.C!ml" false +ve) :- https://www.purebasic.fr/english/viewtopic.php?t=84192

shows VirusTotal:BEHAVIOUR/Memory Pattern Domains/ and BEHAVIOUR/Memory Pattern Urls as "upx.sf.net"

EDIT:
VirusTotal:BEHAVIOUR/Full Reports/Zenbox/
Shows, "Uses 32bit PE files", in pink, so just being 32 bit seems to now be cause for concern.

[v0lt]

Originally Posted by StainlessS

Is the offending file compressed with UPX ?,

No packagers are used.
I tried to build in Visual Studio 2022 and got the same result. I can also try another Windows SDK, but I doubt it will help.

Damn, false +ve's growing, 19/71 (I did a rescan on VirusTotal original file, was original [for me] 17/70])

Wow. The first test was only 9 points.
The 64-bit version is still clean.

This is very strange. As if these antiviruses can't work with 64-bit code.

Maybe antiviruses don't like the large list of built-in AviSynth functions.

[StainlessS]

by me.

VirusTotal:BEHAVIOUR/Full Reports/Zenbox/
Shows, "Uses 32bit PE files", in pink, so just being 32 bit seems to now be cause for concern.

I've not long ago (1/2 hour) viewed this today posted YT clip [by NetworkChuck, a trustworthy good guy <but he drinks too much coffee and talks too fast >]:
Your Remote Desktop SUCKS!! Try this instead (FREE + Open Source):- https://www.youtube.com/watch?v=EXL8mMUXs88
Which suggests RustDesk as a cross platform Open Source Remote Desktop app.
https://github.com/rustdesk/rustdesk/
PC/MAC/Linux/Android/IOS/WEB

x64 no problem, but x86 exe download produces (maybe) false +ve with Comodo Internet Security antimalware.

O.T. @Wonkey-Monkey, I remember that you were searching for good Linux VNC, some years back, have you tried this one (RustDesk) ?

EDIT: I will not be installng Rustdesk any time soon, got too much to do already.

[wonkey_monkey]

Originally Posted by StainlessS

O.T. @Wonkey-Monkey, I remember that you were searching for good Linux VNC, some years back, have you tried this one (RustDesk) ?

What the... I had to go and search to check when I did that. But you just remember?

I switched back to Windows nn my work desktop in the end. I do successfully (mostly) use VNC on Ubuntu with virtual desktops.

[StainlessS]

Thanks.
I remember that I used to use TigerVNC (by same guys as TightVNC on Windows) on Linux Mint (Ubuntu based).

[isidroco]

1) x86 version works OK under Win7 x64. But x64 version gives error at start: "The procedure entry point kernel32.WaitOnAddress could not be located in the dynamic link library api-ms-win-core-synch-|1-2-0.dll", it starts but on video load gives: "Couldn't locate decompressor for format 'H264' (unknown)

Originally Posted by v0lt

The auxsetup utility now has two versions: for win32 and x64.
Removed "64" prefixes for exe and dll files.

This breaks my scripts which executes VirtualDub64.exe or VirtualDub.exe depending on filters and/or local win architecture. Please return to old naming style within same folder.

Also I used VirtualDub.exe /queryVersion to detect old version if less than 42475; but newer version gives 219 when I expect something bigger than 44282 which is the one I use now.

Win7 compatibility is important due to a lot of users (as me) use it with vintage capture cards to get VHS/Video8. Most of them needs WinXP, and some can be hacked to work with win7 which is my system for main Vdub usage.

[v0lt]

Originally Posted by isidroco

But x64 version gives error at start: "The procedure entry point kernel32.WaitOnAddress could not be located in the dynamic link library api-ms-win-core-synch-|1-2-0.dll"

Readme.md
Minimum system requirements
x64 compatible CPU
Windows 8.1 x64 or newer
VirtualDub2 v2.1 can work on Windows 7 if you replace the FFmpeg DLL files with Windows 7 compatible ones.

My VirtualDub2 x64 kit uses only official release shared builds of FFmpeg.
There are three possible solutions for Windows 7 users. I won't double check these solutions, Windows 7 users will have to do it themselves and use the one that suits them.

The VirtualDub2 Win32 kit uses the ffmpeg-n7.1-latest-win32-gpl-shared-7.1.zip build from the yt-dlp project. I haven't tested these builds on Windows 7 and don't plan to.

This breaks my scripts which executes VirtualDub64.exe or VirtualDub.exe depending on filters and/or local win architecture. Please return to old naming style within same folder.

This will not be changed.
I would recommend creating a shared folder that will contain several different folders with different versions of VirtualDub/VirtualMod/VirtualDub2. This folder can be added to PATH and you can use a relative path from this folder to different versions of VD. This will be a more correct solution.

[shekh]

Originally Posted by nji

I'm using VD2 since a long time to improve (mostly older) videos
from all kind of devices.

Mostly I use internal and Anton's filters,
additional a few special ones (ACOBW and NDF, DeLogo, Deshaker and some MSU filters).

Some of the internal filters I never used.
Maybe I miss something with them, so I would like to ask for hints
when/ if these filters are useful:

2:1 reduction (high quality)
Which differences to filte "resize (50%)"?
Quality? Speed?

convert to floating point
Useful when ...?

gamma correct?
Useful when ...?

warp sharp, warp resize?
Both seem to produce bad results...

BTW
What does the "Save" button in filter dialog do?
(There is no "Load" etc.)

TIA

Hi
2:1 reduction (high quality): it uses 3*3 sample matrix, which is (I guess) something in between bilinear and bicubic of the resize filter. Never used/touched.

convert to floating point: this is to force fp32 quality for next filter (e.g. gamma correct).

gamma correct: "Converts video color representation between gamma space and linear space." Some operations (resize) make more sense in linear. Somewhat HDR-related.

warp sharp, warp resize: no idea.

What does the "Save" button in filter dialog do: same as File->Save project. I mostly forgot why, maybe to have it at hand while making complex filter adjustment, which may lead to crash or adverse result requiring backup.

[nji]

Hi shekh.
Thank you very much.
It's good to know indeep the tool I'm using so often.

[nji]

Originally Posted by shekh

Hi
...
What does the "Save" button in filter dialog do: same as File->Save project. I mostly forgot why, maybe to have it at hand while making complex filter adjustment, which may lead to crash or adverse result requiring backup.

I re-checked.
Indeed, "Save" saves the project.
But only if you have a project defined/ loaded.
Otherwise "Save" button does (without message) not save anything!
==> If crash, the valuable filter chain is lost.
Something for the (non-existing ) bug list.

[isidroco]

Originally Posted by v0lt

This will not be changed.
I would recommend creating a shared folder that will contain several different folders with different versions of VirtualDub/VirtualMod/VirtualDub2. This folder can be added to PATH and you can use a relative path from this folder to different versions of VD. This will be a more correct solution.

Win7 agreed, workaround works ok.

But changing VirtualDub64.exe to VirtualDub.exe IMO is a mistake. My script tries to findout where VDUB is located, and which version is installed, and changes it's bahaviour according to that (even choosing x32 or x64 depending on desired filters).
Having the same name for both x32/x64 versions makes correct version usage very hard from batch.
Same with your chosen version to return: older VDUB v1.07.8 returns 28346; v1.10.2 returns 34807, v1.10.4 35491; newer VDUB2 returns 44282; I use 42475 as cut point to use or not use some functions (ie: VirtualDub.video.SetInputMatrix ). But your chosen return value: 219 completly breaks version ascending order.
I'm puzzled of why you decide to do those arbitrary breaking changes with no benefit at all.
I have to do a lot of useless changes to adapt to the new naming/version scheme and at the same time being able to run on older versions.

[v0lt]

I've been solving my problems with building, debugging and testing. I'm happy with everything now and I'm not going to complicate this process.

I don't know what kind of scripts you have, but I would do something like this at the beginning of the script.

rem C:\Progs\VirtualDub-1.10.4\VirtualDub.exe
rem C:\Progs\VirtualDub-1.10.4-AMD64\Veedub64.exe
rem C:\Progs\VirtualDubMod\VirtualDubMod.exe
rem C:\Progs\VirtualDub2_44282\VirtualDub.exe
rem C:\Progs\VirtualDub2_44282\VirtualDub64.exe
rem C:\Progs\VirtualDub2_v2.2\VirtualDub2.exe
rem C:\Progs\VirtualDub2_v2.2_win32\VirtualDub2.exe

SET VD_EXE="C:\Progs\VirtualDub2_v2.2\VirtualDub2.exe"

%VD_EXE%  "Test.avi"

[isidroco]

Originally Posted by v0lt

I've been solving my problems with building, debugging and testing. I'm happy with everything now and I'm not going to complicate this process.

My script is for anyone to run ANY virtualDub version on any Windows machine. And sometimes uses x32 or x64 depending on parameters. Your /QueryVersion behaviour is unacceptable (gives an older version). I can change it for new vdub, but it's not trivial to mantain older VDub support. This is an extract of my script as an example:

set PARAM=_%*& REM _ avoid PARAM being empty if no param passed, %* are rest of parameters passed
  rem delete all spaces
set PARAM=%PARAM: =%

set vdloc=C:\VirtualDub\&REM ***prefered virtualdub path goes here***

set vDub=VirtualDub.exe
set vDubCli=vdub.exe
if defined ProgramFiles(x86^) ( REM defaults on x64 windows
  set vDub=VirtualDub64.exe
  set vDubCli=vdub64.exe
)
IF not "%PARAM:x32=%" == "%PARAM%" ( REM x32 parameter forces 32b vdub
  set vDub=VirtualDub.exe
  set vDubCli=vdub.exe
)
IF not "%PARAM:fdeblk=%" == "%PARAM%" ( REM deBlock only in 32b vdub
  echo ***& echo *** Using x32 vdub due to FDEBLK deblock parameter ***& echo ***
  set vDub=VirtualDub.exe
  set vDubCli=vdub.exe
)
IF not "%PARAM:x64=%" == "%PARAM%" ( REM x64 parameter forces 64b vdub
  set vDub=VirtualDub64.exe
  set vDubCli=vdub64.exe
)

FOR %%S in ( "%vdloc%","%ProgramFiles%\VirtualDub\"^
  ,"C:\DVD\VirtualDub\" "C:\VirtualDub\","C:\DVD\VDUB\"^
  ,"%ProgramFiles(x86)%\VirtualDub\" "C:\Archivos de programa\VirtualDub\" ) do (
    set vdloc=%%~S& REM eliminate quotes" which are needed for spaces in dirs
    rem must use !vdloc! delayed expansion instead of %vdloc% here:
    IF exist "!vdloc!%vdub%" GOTO :vdfound
  )
  set errorStatus=VirtualDub not found: Modify vdloc path in batch or install vDub
  GOTO :error
:vdFound

set oldVDub= & REM space: Enable newer VDub2 commands: use color matrix, hide i/o video in status window
set xCompr=I& REM *I* default h264 vDub internal for new Vdub
IF not "%PARAM:ch264v=%" == "%PARAM%" set xCompr=H& REM *H* h264 vfw
IF exist "%vdloc%%vDubCli%" (  rem Check if old vdub version
  "%vdloc%%vDubCli%" /queryVersion >nul
  if not errorlevel 42475 ( REM if ver<42475 old version of virtualDub
    set noWavHeader= & REM don't use in new vdub versions
    set oldVDub=// & REM bars "// " comments out newer commands
    set xCompr=H& REM *H* default h264 vfw compressor for old Vdub
  )
)

IF "%vDub%" == "%vDub64%" IF not exist "%vdloc%plugins64\Deshaker_64.vdf" (
  set errorStatus=Please copy deshaker plugin in: %vdloc%plugins64\Deshaker_64.vdf
  GOTO :error
) ELSE (
  IF not exist "%vdloc%plugins32\Deshaker.vdf" (
    set errorStatus=Please copy deshaker plugin in: %vdloc%plugins32\Deshaker.vdf
    GOTO :error
  )
)

...

[nji]

@v0lt

Originally Posted by nji

I re-checked.
Indeed, "Save" saves the project.
But only if you have a project defined/ loaded.
Otherwise "Save" button does (without message) not save anything!
==> If crash, the valuable filter chain is lost.
Something for the (non-existing ) bug list.

Could you de-activate the "Save" button if there is no project defined/ loaded?
Or open a "Save project" dialog?

This would prevent possibly data loss at crash.