VirtualDub2

[rgr]

"Special" colour spaces, I see ...

So, in your opinion, would adding the native AviSynth+ API to the A/A-id be "close to impossible"?

What is "A/A-id", "C-id"?

[LigH]

What do we talk about for days now?

"A/A-id" = "AVIFile/Avisynth input driver"
"C-id" = "Caching input driver"

[rgr]

Still, I wonder if there is any reason to use the C-id for AVS, at least a theoretical advantage of additional information useful in any workflow inside VD2

??? This is the MAIN advantage.

[LigH]

Well, rgr, right now the problem is that I need to decide between two problems:

a) I open the AVS file with the "AVIFile/Avisynth input driver": Then I can edit the script in the internal script editor, save the changes, reload it and see the changes in the main video window of VirtualDub2; but it doesn't work with "advanced" colour spaces only supported by FFmpeg, but not by AVIFile functions.

b) I open the AVS file with the "Caching input driver": Then I may be able to see the video in the "advanced" colour spaces; but I can't save changes I made in the internal script editor. I would have to close the video in VirtualDub2, edit the script in an external text editor, and then open the edited script in VirtualDub2 again. Is that convenient in your opinion?

I guess an optimal solution would be if the "AVIFile/Avisynth input driver" would not rely on AVIFile functions only but add AviSynth+ native functions in case an AVS file is opened; but that requires a developer with both remarkable competence and enough spare time.


It might even be useful to add VapourSynth to support VPY files, along with Python based syntax highlighting in the internal script editor. But I fear no hobby developer would take such a Sisyphus burden...

[rgr]

No, that's not convenient. Interestingly, ffmpeg.exe itself doesn't block editing of such an AVS file -- you can modify it and, for example, start a different conversion.

[rgr]

b) I open the AVS file with the "Caching input driver": Then I may be able to see the video in the "advanced" colour spaces; but I can't save changes I made in the internal script editor. I would have to close the video in VirtualDub2, edit the script in an external text editor, and then open the edited script in VirtualDub2 again. Is that convenient in your opinion?

You didn't check well. You can make changes in an external editor and then refresh VDub with F2 (Reload). But I noticed a downside to using "Caching..." - in the event of an error in the script, VDub only returns "FFMpeg - unable to load."

[v0lt]

Thanks for the tip. It was a scripted.vdplugin issue; it couldn't write to files that another application had open for reading. Fixed (https://github.com/v0lt/scripted_vdplugin/commit/ac1991e5c8685dbe0dc502fe3f02570a98ccabb9).

[LigH]

Just what I hoped that might help: Windows file sharing flags. Glad we shared our ideas.

[rgr]

Another inconvenience that's always been there comes to mind.
If the program (plugin) crashes, the output file is still held and can't be deleted. I found that it's held by the "dllhost.exe" library, which remains in memory. After killing it, the file can be deleted.
Is there a way to make this library also be killed in the event of a crash? I'm guessing it's something related to the plugin or encoder?

[LigH]

That can be tricky, there may be multiple instances used by different applications... and once a process crashed, it may not have much control anymore (except for the crash reporter).

[v0lt]

Test build VirtualDub2 v2.4.2.935 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Updated scripted_vdplugin 0.2.3.106
- Settings are now saved in HKEY_CURRENT_USER\SOFTWARE\VirtualDub2\Script Editor.
- Implemented the ability to save scripts opened in other programs with read access.

[LigH]

Works for me.

:thanks:

:thanks:

:thanks:

[rgr]

- Implemented the ability to save scripts opened in other programs with read access.

Great! Is the error message in the script still so laconic?

[coolgit]

2.4.2.934/5

caching input driver not working... greyed out.

[LigH]

Strange. Do you possibly have ancient hardware not supporting CPU instructions required by ffmpeg 8.0 or something similar?

[coolgit]

Windows 7 yes. However windows 7 worked if user use kusaanko ffmpeg.

Last known working version is VirtualDub2_v2.4.0.891, anything above that doesn't work.

So what changed?

[LigH]

One possible reason: The libav version changed between r917 and r918. (https://forum.doom9.org/showthread.php?p=2023263#post2023263)

[v0lt]

On Windows 7, you can use the win32 version.
You must install the Microsoft Visual C++ Redistributable packages for Visual Studio 2015-2022 (https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-supported-redistributable-version) or the Update for Universal C Runtime in Windows (https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c).

FFmpeg 8.0 x64 for Windows 7 doesn't seem to exist. However, you can try alternative methods (https://forum.doom9.org/showpost.php?p=2006672&postcount=1409).

[v0lt]

Test build VirtualDub2 v2.4.2.936 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Updated avlib_vdplugin 1.0.2.407.
- Added display of FFmpeg error text when attempting to open a file fails.
Updated scripted_vdplugin 0.3.0.112
- Fixed the display of error text when opening an AviSynth script file fails.

[coolgit]

Where is v2.4.0.894 file?

[coolgit]

FFmpeg 8.0 x64 for Windows 7 doesn't seem to exist. However, you can try alternative methods (https://forum.doom9.org/showpost.php?p=2006672&postcount=1409).


I know that. I did say i AM using kusaanko ffmpeg for windows 7. It worked up to v2.4.0.891 but does not work for 2.4.2.9**.

So why does it not work?

[v0lt]

So why does it not work?
I don't know. I don't have Windows 7.

VirtualDub2.exe does not use FFmpeg DLLs.

Older releases of avlib.vdplugin are available (https://github.com/v0lt/avlib_vdplugin/releases).
The first build of FFmpeg 8.0 from BtbN (2025-09-26) is also available (https://github.com/BtbN/FFmpeg-Builds/releases/tag/autobuild-2025-09-26-13-21).

[v0lt]

I know that. I did say i AM using kusaanko ffmpeg for windows 7. It worked up to v2.4.0.891 but does not work for 2.4.2.9**.
Other users have already answered your question on the previous page. I'll just quote the "documentation" one more time.

avlib_vdplugin history.txt (https://github.com/v0lt/avlib_vdplugin/blob/master/history.txt)
1.0.1.393 - 2025-10-01
----------------------
The FFmpeg 8.0 x64 build from BtbN is used.
The FFmpeg 8.0 win32 build from Defisym is used.
avlib_vdplugin Readme.md (https://github.com/v0lt/avlib_vdplugin/blob/master/Readme.md)
Copy FFMpeg 8.0 DLLs to 'VirtualDub2' folder.

avcodec-62.dll
avformat-62.dll
avutil-60.dll
swresample-6.dll
swscale-9.dll

[coolgit]

Older releases of avlib.vdplugin are available (https://github.com/v0lt/avlib_vdplugin/releases).
The first build of FFmpeg 8.0 from BtbN (2025-09-26) is also available (https://github.com/BtbN/FFmpeg-Builds/releases/tag/autobuild-2025-09-26-13-21).

I said "Where is v2.4.0.894 file?"

You know what i meant. It is the test build not release.

[v0lt]

I said "Where is v2.4.0.894 file?"
I don't have this. I didn't save the old test builds of VirtualDub2.

[v0lt]

2.4.2.934/5

caching input driver not working... greyed out.
I had grayed out panels when I disabled "Enable input pane" and "Enable output pane" in the "View" menu. :) I suggest resetting the settings.

[v0lt]

Test build VirtualDub2 v2.4.2.937 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Fixed error text display in UTF-8, system ANSI, or mixed encoding (different encodings in different strings). This fixes the display of AviSynth+ errors (https://forum.doom9.org/showthread.php?p=2023259#post2023259).
Updated scripted_vdplugin 0.3.0.112
- Changed the text highlighting styles for AviSynth and VapourSynth scripts.
- Cosmetic changes.

Test build VirtualDub2 v2.4.2.938 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Updated avlib_vdplugin 1.0.2.408
- Increased priority for AviSynth script files from kDC_VeryLow to kDC_Low.

[StainlessS]

Thanx v0lt.

[v0lt]

VirtualDub2 v2.4.3.944 (https://github.com/v0lt/VirtualDub2/releases/tag/2.4.3)

Changes:
Fixed error text display in UTF-8, system ANSI, or mixed encoding (different encodings in different strings). This fixes the display of AviSynth+ errors.
Cosmetic changes.

Updated avlib-1.vdplugin to version 1.0.3.410.
- Fixed a temporary freeze in the file open window when selecting certain .avs files. AviSynth script files are now identified by extension.
- Fixed frame navigation for Avisynth script files.
- Added display of FFmpeg error text when attempting to open a file fails.

Updated scripted.vdplugin to version 0.3.1.123.
- Settings are now saved in HKEY_CURRENT_USER\SOFTWARE\VirtualDub2\Script Editor.
- Implemented the ability to save scripts opened in other programs with read access.
- Fixed the display of error text when opening an AviSynth script file fails.
- Changed the text highlighting styles for AviSynth and VapourSynth scripts.
- Cosmetic changes.

[rgr]

H265 encoding (lossless)

"temporal-layers=0 / open-gop / min-keyint=25"

Does this notation mean that VDub writes H265 with or without open-GOP?

If with Open-GOP, can it be written without Open-GOP? Many programs cannot properly read MP4 files with Open-GOP—including VirtualDub itself.
I filed a ticket on the ffmpeg forum about this, but the response I got was "the Open-GOP idea is too shitty to fix it. Don't use it" :D

[v0lt]

Does this notation mean that VDub writes H265 with or without open-GOP?

If with Open-GOP, can it be written without Open-GOP? Many programs cannot properly read MP4 files with Open-GOP—including VirtualDub itself.
I haven't noticed any issues with "FFmpeg / x265 - HEVC lossless" in VirtualDub2 v2.4.3.
I can say the opposite: "Many programs can properly read MP4-HEVC files with Open-GOP."

[rgr]

I haven't noticed any issues with "FFmpeg / x265 - HEVC lossless" in VirtualDub2 v2.4.3.

Strange, because it's one of the easiest things to observe. A one-minute test of the latest version with a simple file:
https://i.imgur.com/1AdFbZ1.png

I can say the opposite: "Many programs can properly read MP4-HEVC files with Open-GOP."

Define many. Vegas has it (I checked), Premiere has it too (but the smallest). Even VirtualDub has it.

[rgr]

The error in reading the frame can sometimes be very large (499 vs 484)

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

ffmpeg -y -v debug -hide_banner -nostdin -nostats -f lavfi -i "testsrc2=320x240:25:d=20" -c:v libx265 -preset slow -crf 19 "Out-default.mp4"

[rgr]

And with the latest VirtualDub and H265 lossless open-gop.

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

ffmpeg -y -v debug -hide_banner -nostdin -nostats -f lavfi -i "testsrc2=320x240:25:d=20" -c:v libx265 -x265-params lossless=1 "Out-lossless-default.mp4"

[nji]

I can't tell if there is any connection, but exact frame seeking seems to be a problem of... ?? ffmpeg?... openCV (https://github.com/opencv/opencv/issues/9053)

(Since years!! BTW)

[rgr]

If you don't use open-gop ("-x265-params no-open-gop=1"), the problem disappears. It only affects H265; I haven't noticed it in H264 or AV1, probably because it is disabled there by default.

[rgr]

Problem with H256 Lossless Output File

I'm attaching a sample output file from Vdub H265 Lossless (a fragment, the first second, but that's enough).
The file should be 59.94fps (the source in VDub is an AVS script).

https://files.fm/u/abnbq95cxh

There's something wrong with the output files because ffmpeg sees them as Variable Frame Rate, and after converting them using a simple "ffmpeg -i vd_h265_lossless(trim).mp4 -c:v libx264 output.mp4" we get a Variable Frame Rate file.

Frame rate mode: Variable
Frame rate: 56.073 FPS
Minimum frame rate: 19.980 FPS
Maximum frame rate: 59.940 FPS


Edit: The only way I found was to recode H265 like this:
ffmpeg -hide_banner -r 60000/1001 -i "vd_h265_lossless(trim).mp4" -c:v libx264 -c:a copy "out (rp+recode).mp4"
Only copying the H265 stream using -r or -fps_mode drop does not help.


Edit 2:

I don't know what's causing it, but the video stream dump looks quite strange.

frame,video,0,1,0,0.000000,2002,0.033367,0,0.000000,1001,0.016683,44,4020777,1920,1080,0,0,0,0,yuv444p12le,N/A,I,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified,H.26[45] User Data Unregistered SEI message
frame,video,0,0,3003,0.050050,3003,0.050050,3003,0.050050,1001,0.016683,9835648,2420191,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,4004,0.066733,4004,0.066733,4004,0.066733,1001,0.016683,12259935,2477013,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,2002,0.033367,5005,0.083417,5005,0.083417,1001,0.016683,7263387,2568165,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,5005,0.083417,6006,0.100100,6006,0.100100,1001,0.016683,14736948,2335271,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,1001,0.016683,7007,0.116783,7007,0.116783,1001,0.016683,4024917,3234374,1920,1080,0,0,0,0,yuv444p12le,N/A,P,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,8008,0.133467,8008,0.133467,8008,0.133467,1001,0.016683,23738857,2571856,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,9009,0.150150,9009,0.150150,9009,0.150150,1001,0.016683,26314809,2648145,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,7007,0.116783,10010,0.166833,10010,0.166833,1001,0.016683,20930851,2803910,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,10010,0.166833,11011,0.183517,11011,0.183517,1001,0.016683,28962954,2441652,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,6006,0.100100,12012,0.200200,12012,0.200200,1001,0.016683,17076315,3850440,1920,1080,0,0,0,0,yuv444p12le,N/A,P,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,13013,0.216883,13013,0.216883,13013,0.216883,1001,0.016683,38227021,2662911,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,14014,0.233567,14014,0.233567,14014,0.233567,1001,0.016683,40889932,2603627,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,12012,0.200200,15015,0.250250,15015,0.250250,1001,0.016683,35340520,2882405,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,15015,0.250250,16016,0.266933,16016,0.266933,1001,0.016683,43497655,2531199,1920,1080,0,0,0,0,yuv444p12le,N/A,B,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified
frame,video,0,0,11011,0.183517,17017,0.283617,17017,0.283617,1001,0.016683,31408702,3927722,1920,1080,0,0,0,0,yuv444p12le,N/A,P,0,0,0,0,tv,bt709,unknown,unknown,unspecified,unspecified

[v0lt]

Use MKV container to save videos in VD2.

[rgr]

Use MKV container to save videos in VD2.

Premiere does not support MKV, but it does support MP4 H265 lossless.

[v0lt]

Premiere does not support MKV, but it does support MP4 H265 lossless.
Try the test build avlib_vdplugin_1.0.4.414 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA).

[shekh]

Hmm. For some reason unknown to me, the command "File > Export > Single image (skip dialog)" in the key settings is called "File.SaveNextImage".

PS: In the next build it will be fixed to "File.SaveImageSkipDialog".

"NextImage" is because user is supposed to save "first image" using the dialog first. That was the logic :)

[v0lt]

"NextImage" is because user is supposed to save "first image" using the dialog first. That was the logic :)
But I still redid it.


I'm thinking of expanding UTF-8 support in the next version:

Save VD2 scripts/projects in UTF-8 format. There will no longer be \xXX codes for string parameters. Text fields will be easier to read and edit.
Set activeCodePage=UTF-8 in the manifest. This will add support for AviSynth+ scripts with Unicode character paths.

[rgr]

Try the test build avlib_vdplugin_1.0.4.414 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA).

Thanks, I'll test it. For information, after converting to MKV/H265, ffmpeg sees the file as CFR and transcodes to H265 correctly. But in the stream dump, the frames still have the same problematic data.

[rgr]

Try the test build avlib_vdplugin_1.0.4.414 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA).

First attempt -- at the very end, an error (stream reading?) occurred. The output file (MP4/H265) was unreadable.

ffmpeg:
[mov,mp4,m4a,3gp,3g2,mj2 @ 000002785fd75080] invalid size 0 in stsd
[mov,mp4,m4a,3gp,3g2,mj2 @ 000002785fd75080] error reading header
[in#0 @ 000002785fd74e00] Error opening input: Invalid data found when processing input
Error opening input file 1. source (astoria)-złe.mp4.
Error opening input files: Invalid data found when processing input

I'm rendering the second clip simultaneously, so we'll see how it goes...

[rgr]

First attempt -- at the very end, an error (stream reading?) occurred. The output file (MP4/H265) was unreadable.

I'm rendering the second clip simultaneously, so we'll see how it goes...

Same thing. "Unknown error during filter processing"

[rgr]

ProRes encoding

Using the simple command "-c:v prores_ks -profile:v 5" (prores xq) in ffmpeg, I can achieve the 1MB/s bitrate declared by this profile.

Video: AP4X 1920x1080 59.94fps 927211kbps [V: prores xq, yuv444p12le, 1920x1080, 927211 kb/s]

However, in VDub, this bitrate is significantly lower.

Video: AP4X 1920x1080 59.94fps 658093kbps [V: prores xq, yuv444p12le, 1920x1080, 658093 kb/s]

BTW - is it better to report issues here or on github?

[Emulgator]

What about mediainfo of the both encodes ?

[v0lt]

ProRes encoding

Using the simple command "-c:v prores_ks -profile:v 5" (prores xq) in ffmpeg, I can achieve the 1Mb/s bitrate declared by this profile.

Video: AP4X 1920x1080 59.94fps 927211kbps [V: prores xq, yuv444p12le, 1920x1080, 927211 kb/s]

However, in VDub, this bitrate is significantly lower.

Video: AP4X 1920x1080 59.94fps 658093kbps [V: prores xq, yuv444p12le, 1920x1080, 658093 kb/s]
Change the quality setting from 4 to 2 and the bitrate will increase.

BTW - is it better to report issues here or on github?
It would be better on GitHub, but...
You and many other users provide so little information to reproduce their problem. And I'm often uninterested in spending days begging for additional information to reproduce the bug. Users don't provide a video file that reproduces the bug. And there are many other things that make developers waste a lot of time and effort.

[v0lt]

Test build VirtualDub2 v2.5.0.978 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)
Improved Unicode support.
Script, job, and project files are now saved in UTF-8 encoding.
Updated avlib_vdplugin 1.0.4.416
- Closed GOPs is used for the "x265 - HEVC lossless" encoder.
Updated scripted_vdplugin 0.3.2.127

Added:
Updated to version 2.5.0.978.

[StainlessS]

Cheers v0lt, you are such a sweetie :)