VirtualDub2

[nji]

Thanks for your help.

Still you got me wrong:
By "ffmpeg filter" I didn't mean source filter (just to open a file with ffmpeg),
but moreover an ffmpeg manipulation filter. For example:

Open movie and deinterlace it - then pass to VD.

[LigH]

Avisynth is indeed a frameserver which does a lot more than just serve frames from a supported source media format to an application which would usually only ask Windows to handle an AVI file. The real power is in all the core functions and plugins which allow manipulation of the video between opening the input and serving the output.

Many of the filters available in ffmpeg are also available in Avisynth and its plugins (either exactly the same or almost identical). And even more. So you don't actually need to cling to ffmpeg, you may just have to find the analog (or even better) filters in Avisynth.

I guess we could explain it better when you can provide a more or less complex example of what you are used to do in ffmpeg, so we can translate it to an equivalent Avisynth script. And this may even go beyond the topic of this thread... VirtualDub(2) does not really need to care how it receives its material, only that it is in a compatible uncompressed format which can be forwarded to the encoders it supports.

[v0lt]

VirtualDub2 x64 with updated avlib-1.vdplugin (ffmpeg 6.1.1 test 12) (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Alternative link (https://www.sendspace.com/file/wvaeao)
Fixed a crash when calling RunNullVideoPass().
VirtualDub2 has been rebuilt in Visual Studio 2019.

Source code:
https://github.com/v0lt/VirtualDub2
https://github.com/v0lt/avlib_vdplugin

[tormento]

Fixed a crash when
Dunno if it happened with previous versions too but I can't jump to keyframes in a video, both with shortcut and with key buttons. It simply jumps to the end or the beginning of the video.

[v0lt]

Dunno if it happened with previous versions too but I can't jump to keyframes in a video, both with shortcut and with key buttons.
I don’t confirm this.

[tormento]

I don’t confirm this.
Try with a mkv.

I can send you a video clip of the issue.

[v0lt]

VirtualDub2 x64 with updated avlib-1.vdplugin (ffmpeg 6.1.1 test 13) (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Alternative link (https://www.sendspace.com/file/4m7pv4)
Fixed reading of key frames for MKV.

[FranceBB]

Vapoursynth users

He's not a VapourSynth supporter, he's an ffmpeg one.
Sadly most ffmpeg Devs are rude and not polite.
The fact that he's adding a derogatory comment against Avisynth like that in this VirtualDub topic just demonstrates it as it doesn't bring anything to the conversation and it's done only to instigate an argument.
The remarks he made are downright disrespectful to the people who spent time on this amazing frameserver.
That being said, VirtualDub and Avisynth have always worked together and I would imagine that they will keep doing so for years to come.
Besides, facts are that we can do 32bit float YUV calculations in Avisynth and we've been able to do that for almost 10 years while his beloved FFMpeg can't go past 16bit planar, so before attacking other frameserver he should be checking his own.


VirtualDub2 x64 with updated avlib-1.vdplugin (ffmpeg 6.1.1 test 13) (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Alternative link (https://www.sendspace.com/file/4m7pv4)

Thanks for the new version, I'll test it tomorrow. :)

[foxyshadis]

Avisynth is low quality plugin and code dumpster, do not use it.

Struck for rule 2. Ignore richardpl and his pot-stirring, it's a weak troll.

[SkilledAbbot]

Moderate as necessary, but just dropping in to say, thank you to the entire Vdub history. I still use as of right now since 2002. And If that is link to newer version, can't wait to try it out.

[v0lt]

VirtualDub2 version 2.1 (deleted)

Changes:
Windows XP is no longer supported.
Builds for x86 are no longer planned to be released.
Fixed crash when calling RunNullVideoPass().
Updated avlib-1.vdplugin to version 0.6.1.70.
├ FFmpeg 6.1.1 is now supported.
├ Removed CineForm HD (native) codec.
├ Removed manual lazy loading of DLL for FFmpeg DLLs.
├ Removed support for systems older than Windows 7.
└ The 32-bit plugin is not implemented because there is no official build of FFmpeg 6.1.1 for x86.

[nji]

Thankyou for your work! :)

I would like to mention drawbacks of dropping 32bit:

There are several filters which are only for 32 bit.

If I remember right it is the internal logo filter for 64 bit,
that produces slight false colors ("DeShaker default color").
(shekh once had a look at it, but didn't worked on as it is confusing code).

I don't know if ffmpeg source code would allow to be build as 32 bit?

[LigH]

What does DDL mean? Just a typo of DLL?

PS: I tried to select a video compression and it crashed:
An out-of-bounds memory access (access violation) occurred in module 'VirtualDub64'...
...reading address 00000000A9C072E0...
...while querying video codec "ffdshow Video Codec" (compchoose.cpp:420)...
...while opening video codec with FOURCC "ffds" (compchoose.cpp:528)...
...while enumerating video codecs (compchoose.cpp:515).

[v0lt]

I don't know if ffmpeg source code would allow to be build as 32 bit?
There are unofficial builds of FFmpeg (https://www.animmouse.com/p/ffmpeg-binaries/). You can look for x86 shared version 6.1.1 there.
But I'm not interested.

What does DDL mean? Just a typo of DLL?
Yes. It's a typo.
PS: I tried to select a video compression and it crashed:
This doesn't happen to me. I don't have "ffdshow Video Codec".

[LigH]

This doesn't happen to me. I don't have "ffdshow Video Codec".

Are you interested in a crash log? Your repo doesn't seem to have an "issues" page.

It contains an error:
Thread call stack:
Incorrect VirtualDub.vdi file (build 44282) for this version of VirtualDub -- call stack unavailable.

VirtualDub2 x64 build 44282 has no issues enumerating video compressors.

The ffdshow VfW codec is part of ffdshow-tryout rev4531 by e.g. clsid2

https://sourceforge.net/projects/ffdshow-tryout/files/Official%20releases/64-bit/
https://forum.doom9.org/showthread.php?t=120465
__

P.S.: I believe this problem was introduced between VirtualDub2 x64 ffmpeg6.1.1 test 11 (contains an old EXE from 2020) and 12 (contains a new EXE).

[v0lt]

I installed ffdshow_rev4533_20140929_clsid_x64.exe (https://sourceforge.net/projects/ffdshow-tryout/files/SVN%20builds%20by%20clsid/64-bit%20builds/) and during installation I saw a warning about possible crashes.
https://i.ibb.co/tzFh2KM/ffdshow-vfw.png (https://ibb.co/tzFh2KM)
I also get a crash when ffdshow VFW is installed.

PS: Perhaps the problem with ffdshow VFW appeared after replacing the Windows SDK and other things.

[v0lt]

Your repo doesn't seem to have an "issues" page.
I turned on the "Issues" page and created Issue #1 (https://github.com/v0lt/VirtualDub2/issues/1), where I collected various information on this issue.

[LigH]

:thanks:

I hope someone competent can find the real reason, skipping a codec is indeed not a perfect solution.

[v0lt]

VirtualDub2 44282 + avlib.vdplugin 0.6.1.70 (https://github.com/v0lt/avlib_vdplugin/releases/tag/0.6.1)
I decided to re-release the old VirtualDub2 build 44282 with updated avlib.vdplugin 0.6.1.70.

[LigH]

OK, nice, can handle an MP4 with AV1 video from YouTube and use ffvfw codecs.

[v0lt]

VirtualDub2_v2.1.0.603 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Alternative link (https://www.sendspace.com/file/8s9dwu)
Please check this version. Will it crash when choosing a video compressor or not?
ffdshow Video Codec (ff_vfw.dll) and Logitech Video (I420) (lvcod64.dll) are not supported.

[LigH]

It does not crash but ffvfw is not listed.

[jpsdr]

That's odd. I've tried the 1rst version of 2.1 on my PC, which have ffdshow 1.3.4533 installed, and it doesn't crash when i choose compressor, and the ffshow codec is listed.

[LigH]

For me it crashed from test12 on, because this included a new EXE built with a more modern MSVS. I guess it might be related to the set and maybe order of VfW codecs being enumerated, but we will need to trace the reason to understand what happens and find a way to avoid it. I hope a test build creating a verbose log of the enumeration loop may help...

[v0lt]

VirtualDub2 v2.1.0.605 (https://github.com/v0lt/VirtualDub2/releases/tag/2.1.0)

Windows XP is no longer supported.
Builds for x86 are no longer planned to be released.
Fixed crash when calling RunNullVideoPass().
64-bit "ffdshow Video Codec" (ff_vfw.dll) and "Logitech Video (I420)" (lvcod64.dll) are not supported because it crashes when opening the video compression selection window.
Updated avlib-1.vdplugin to version 0.6.1.70.
* FFmpeg 6.1.1 is now supported.
* Removed CineForm HD (native) codec.
* Removed manual lazy loading of DLL for FFmpeg DLLs.
* Removed support for systems older than Windows 7.
* The 32-bit plugin is not implemented because there is no official build of FFmpeg 6.1.1 for x86.


VirtualDub2 44282 + avlib.vdplugin 0.6.1.70 (https://github.com/v0lt/avlib_vdplugin/releases/tag/0.6.1)
Old VirtualDub2 with updated avlib.vdplugin.

[Emulgator]

Many thanks, v0lt !
As a sidenote: As long as there are classic 32-bit AVS plugins which won't get any update
because stable (or developer had to take on other tasks) it is viable to still have 32-bit applications
like VD2 available, so again thanks if somebody caring for that still.

[jpsdr]

What is CineForm ? Is it a lossless codec ?

[LigH]

CineForm Intermediate (https://en.wikipedia.org/wiki/CineForm) is the codec used in GoPro cameras, not lossless but wavelet oriented. I believe more modern camera generations moved on to HEVC and even AV1.

[shekh]

CineForm Intermediate (https://en.wikipedia.org/wiki/CineForm) is the codec used in GoPro cameras, not lossless but wavelet oriented. I believe more modern camera generations moved on to HEVC and even AV1.

AFAIK it wasn`t used in cameras. It is great as intermediate :)

[LigH]

Ah, okay... well, it's constant quality oriented, low loss, easy editing. Comparable to DNxHD/R

[jpsdr]

As i said, i don't know why, but in my PC (Windows 7 x64), the v2.1.0.600 didn't crash with ffdshow 1.3.4533 installed, and the codec is in list of the compression Codec.
Maybe this information can help to figure out how fix the issue...?
If more information is needed, ask and i'll provide them if i can.

[LigH]

I believe we need a test tool which runs the enumeration loop exactly like in VirtualDub2 64bit but creates a verbose log, up to a crash handler which can log down to a CPU / stack / heap level.

[v0lt]

I updated avlib.vdplugin to version 0.7.0.72. It now supports FFmpeg 7.0.
Download link (https://disk.yandex.ru/d/R3Ob8yREy4ChvA).

[tormento]

Download link
What is the difference between the two files?

[LigH]

Original EXE does not crash with unstable 64 bit VfW codecs but is not up to date otherwise.

[v0lt]

What is the difference between the two files?
The difference is written on the previous page. (https://forum.doom9.org/showthread.php?p=2000784#post2000784)

[v0lt]

I updated avlib.vdplugin to version 0.7.0.86 (FFmpeg 7.0).
Added support for JPEG XL images.
Improved navigation support for long FLVs and MKVs with audio.
More default formats for the "FFMpeg : video" and "FFMpeg : images" groups.
Download link (https://disk.yandex.ru/d/R3Ob8yREy4ChvA).

[TCmullet]

Many thanks, v0lt !
As a sidenote: As long as there are classic 32-bit AVS plugins which won't get any update
because stable (or developer had to take on other tasks) it is viable to still have 32-bit applications
like VD2 available, so again thanks if somebody caring for that still.
I HEARTILY 2nd your motion (and NJI's motion) to not let any 32-bit version of anything die this soon in computer history. I think there are millions of 32-bit PCs still alive and well. In fact, I have one myself, though I don't use it often. I'd be sad if I ran into "oh I can't run a decent Vdub here b/c this old reliable workhorse PC of mine isn't 64-bit".

[LigH]

Maybe the 32-bit version of VirtualDub2 has no issues handling VfW codecs...

[v0lt]

avlib.vdplugin 0.7.0.90 (FFmpeg 7.0)
Added support for VVC videos.
Changed the display of the "Metadata" field in "File Information".
Download link (https://disk.yandex.ru/d/R3Ob8yREy4ChvA).

[LigH]

Dear v0lt, could you please make a VfW enumeration test tool which tries to catch and report all exceptions as much as possible?

[v0lt]

Dear v0lt, could you please make a VfW enumeration test tool which tries to catch and report all exceptions as much as possible?
No.
I tried to put a "try catch" block on the problem spot, but it didn't help.

[v0lt]

avlib.vdplugin 0.7.0.93
was fixed and re-released as version 0.7.0.123

VirtualDub2 v2.1.1.607
was rebuilt and re-released under version v2.1.1.609

https://forum.doom9.org/showthread.php?p=2006278#post2006278

[Bernard]

I'm back after a 20 year break so I apologize in advance if I've missed something obvious.

Using either Vdub2 official or the latest v2.1.1.607 release, the built in huffyuv codec isn't recognized by VLC. Even if I change the FourCC code to what VLC expects, it still won't play. If I install the old huffyuv codec and save the file in Vdub2, VLC plays files encoded with it fine.

Is there a setting to make Vudb2's built in huffyuv codec compatible with VLC? I'd rather use the built in codec.

[v0lt]

Is there a setting to make Vudb2's built in huffyuv codec compatible with VLC?
VirtualDub2 does not contain the HuffYUV ('HFYU') encoder. It contains the FFMPEG Huffyuv (ffvhuff, 'FFVH') encoder. These are different encoders.

[LigH]

IIRC, the original Huffyuv codec only supported YUV 4:2:2 (YUY2/UYVY), while ffmpeg's Huffyuv adaption also supports planar YUV 4:2:0 (YV12).

[qyot27]

As a libavcodec-based player, there's absolutely no reason why VLC should be rejecting ffvhuff. Unless it's a positively ancient version of VLC.

[richardpl]

VLC is mess.

[Bernard]

Thanks for the idea about VLC being out of date. But no, updating VLC to the latest version still doesn't let it read HFYU files.

[LigH]

Again: VLC does support the original Huffyuv codec (by Ben R.G.) with FourCC "HFYU". But not the ffmpeg/libavcodec variant with FourCC "FFVH". And I see no reason for it not to, because its shipped plugins\codec\libavcodec_plugin.dll does contain the FourCC "FFVH", it is at least detected. Issue added (https://code.videolan.org/videolan/vlc/-/issues/28661) but there are still almost 4000 issues open.

Some players which should work instead: ffplay, mplayer, SMplayer, MPC-HC, MPC-BE ...