VirtualDub2

[coolgit]

Windows 7 users can try using FFmpeg files from builds here - https://github.com/kusaanko/FFmpeg-Auto-Build/releases

Your vdub doesn't work with win 7 as no catching input driver. Couldn't load ffv1 avi file.

Using above Kussaanko build and it worked. I haven't done a full test yet but so far so good.

Perhaps it would be wiser to use the above and not exclude win 7 users.

Sorry but win 10/11 are garbage.

[LigH]

German proverb, almost literally translated: "Wash me but don't wet me!" (Have your cake and eat it, too.)

If you insist in using the cancelled and therefore obsolete Windows 7, which is dangerous now that you can't rely on security updates anymore, you can still use VirtualDub2 up to build 44282, even in a 32-bit version, which does support the ffvfw codec. But then you may miss a few features of the new VDub2 EXE. And the new avlib plugin (https://github.com/v0lt/avlib_vdplugin/releases) was only made for the 64-bit version (it is available in a bundle with VDub2 r44282). But some of the latest codecs in FFmpeg 7 seem to need features Windows 7 lacks, I guess, so they need to be excluded to make FFmpeg work with the rest of less demanding codecs. Or what is the exact reason?

[v0lt]

Your vdub doesn't work with win 7 as no catching input driver. Couldn't load ffv1 avi file.
I know about this and added information to avlib_vdplugin Readme.md (https://github.com/v0lt/avlib_vdplugin/blob/master/Readme.md) and VirtualDub2 v2.1 Readme.md (https://github.com/v0lt/VirtualDub2/blob/master/Readme.md).
Using above Kussaanko build and it worked. I haven't done a full test yet but so far so good.
This is good. Use it.

There is also information that to use official FFmpeg builds on Windows 7, it is enough to put a special file "api-ms-win-core-synch-l1-2-0.dll" nearby, which can be taken from the link.
https://github.com/cristianadam/api-ms-win-core-synch-Win7/releases/
On more modern Windows, you shouldn't do this.

Sorry but win 10/11 are garbage.
Windows 10 22H2 works with the integrated graphics of my processor. When I used Visual Studio 2019, the installer immediately started the installation on a blank system. Visual Studio 2022 and other modern software that I need just work.

[coolgit]

I do use Vdub and have both 32 and 64 bit, but what reason could you have to exclude windows 7. It works and miles better than win 10/11 Security isn't an issue, just over-the-top scare tactics forcing lemmings to update because Microsoft said so.

As far as i know you may have fix some bugs but there no new wondrous features that requires excluding win 7.

[LigH]

Do not blame v0lt. He is not responsible for the decision of the ffmpeg developers to support new content even if that means to drop obsolete operating systems. If you need a VirtualDub2 which runs on Windows 7, you may need to avoid all the new content in ffmpeg which requires features of at least Windows 10. Sieving those out one by one is not a trivial job. And even more demanding when done for free.

[coolgit]

Do not blame v0lt. He is not responsible for the decision of the ffmpeg developers to support new content even if that means to drop obsolete operating systems. If you need a VirtualDub2 which runs on Windows 7, you may need to avoid all the new content in ffmpeg which requires features of at least Windows 10. Sieving those out one by one is not a trivial job. And even more demanding when done for free.

I am not blaming Volt for anything, just wondering what the new features are that vdub uses that requires excluding win 7.

[LigH]

GyanD's codexffmpeg issue 136 (https://github.com/GyanD/codexffmpeg/issues/136) reports a dependency on api-ms-win-core-synch-l1-2-0.dll; I assume that it is related to multi-threading features, organizing simultaneous access to Windows resources by several processes. Codecs or routines in ffmpeg which use these new features to avoid trouble and improve performance inside the Windows core are no longer compatible to a Windows system without these core features. There was mentioned that an essential ffmpeg build may still work on Windows 7, but more complete versions, especially those using OpenCL and Vulkan, will not ... but as mentioned before, working through a checklist which library may be downward compatible and which will not would cost a lot of efforts, especially for people who do not know ffmpeg sources line by line.

[v0lt]

I am not blaming Volt for anything, just wondering what the new features are that vdub uses that requires excluding win 7.
It seems you haven't read my messages. Everything is written in the topic.

[v0lt]

Let me sum it up.

I did not add anything incompatible with Windows 7 to the avlib_vdplugin and VirtualDub2.1 code.
You have a problem with the official FFmpeg DLL (avcodec-61.dll), which contains components incompatible with Windows 7.
You can find more details at the link: https://github.com/GyanD/codexffmpeg/issues/136

I didn't promise Windows 7 support to anyone. I'm not interested in this.

Windows 7 users can use one of the solutions:

1. Replace all FFmpeg DLLs with compatible ones.
For example, these FFmpeg 7.0 builds: https://github.com/kusaanko/FFmpeg-Auto-Build/releases

2. Put the api-ms-win-core-synch-l1-2-0.dll file in the VirtualDub2.1 folder (where avcodec-61.dll is).
Link: https://github.com/cristianadam/api-ms-win-core-synch-Win7/releases/

3.Use VxKex.
Link: https://github.com/i486/VxKex

[LigH]

3.Use VxKex.
Link: https://github.com/i486/VxKex

:thanks:

Even unrelated to VDub2, I know people who are stuck with Windows 7 on old hardware and might keep it running for a little longer...

[coolgit]

Let me sum it up.

I did not add anything incompatible with Windows 7 to the avlib_vdplugin and VirtualDub2.1 code.
You have a problem with the official FFmpeg DLL (avcodec-61.dll), which contains components incompatible with Windows 7.
You can find more details at the link: https://github.com/GyanD/codexffmpeg/issues/136

I didn't promise Windows 7 support to anyone. I'm not interested in this.

Windows 7 users can use one of the solutions:

1. Replace all FFmpeg DLLs with compatible ones.
For example, these FFmpeg 7.0 builds: https://github.com/kusaanko/FFmpeg-Auto-Build/releases

2. Put the api-ms-win-core-synch-l1-2-0.dll file in the VirtualDub2.1 folder (where avcodec-61.dll is).
Link: https://github.com/cristianadam/api-ms-win-core-synch-Win7/releases/

3.Use VxKex.
Link: https://github.com/i486/VxKex

Got it thanks. Just FFmpeg issue. Tested your vdub with kussanko ffmpeg and so far no probs.

[coolgit]

There is a bug that existed for a long time and frankly tediously annoying.

When using trims, at the bottom it says "selecting frames 50-100 (50 frames blah blah)"
When using curve editor and the mouse cursor goes over the curve area, it says "parameter curve editor blah blah" and over writes "selecting frames 50-100 (50 frames blah blah)" and this is the problem. To get back to "selecting frames 50-100 (50 frames blah blah)" i have to click on the rectangular box on the frame bar. This is the tediously annoying part.

Can't the "selecting frames 50-100 (50 frames blah blah)" be moved up to the "frame 100 blah" box as there is plenty of room or make "parameter curve editor blah blah" show up after "selecting frames 50-100 (50 frames blah blah)" instead of overwriting or make "selecting frames 50-100 (50 frames blah blah)" then the cursor no longer over the curve area.

[isidroco]

Hi, last vdub2 2.1.1.609 crashes instantly when adding deLogo Filter, (actually filter works if loaded from a script and one doesn't try to open it's settings):
Out of bounds addr 00000000 1ec68658... while configuring filter "DeLogo 1.3.2" (FilterInstance.cpp:1025).

[v0lt]

Hi, last vdub2 2.1.1.609 crashes instantly when adding deLogo Filter
As far as I know delogo.vdf (https://www.rationalqm.us/delogo132/delogo.html) does not exist for x64.

[LigH]

Gyan identified the latest Rust as the cause of Windows 7 incompatibility ... (https://forum.videohelp.com/threads/414767-ffmpeg-7-0-1-and-Windows-7#post2749956) so building rav1e with an older rust appears to be a solution.

[isidroco]

As far as I know delogo.vdf (https://www.rationalqm.us/delogo132/delogo.html) does not exist for x64.

https://forum.videohelp.com/threads/397927-64bit-Logo-Spot-remover-filter-for-VirtualDub#post2645514

[jpsdr]

About Windows 7 and V0lt avlib_vdplugin release, i've tested the both method :
a - Put the api-ms-win-core-synch-l1-2-0.dll file in the VirtualDub2.1 folder.
b - Replace all FFmpeg DLLs with compatible ones.

a didn't work for me, i even also put the dll in plugins directory, the filter was still failing loading.
b worked for me. Once all the ffmpeg dll were replaced, the filter wasn't failing to load anymore.

I just wanted to report.

[v0lt]

a - Put the api-ms-win-core-synch-l1-2-0.dll file in the VirtualDub2.1 folder.
...
a didn't work for me, i even also put the dll in plugins directory, the filter was still failing loading.
Did you do it wrong on purpose? :confused:

[jpsdr]

I don't understand your comment...:confused:
I said that putting in VD2 directory didn't work, then i also put in plugins directory and it still didn't work.
Where i was doing wrong ?

[LigH]

If you did it correctly, api-ms-win-core-synch-l1-2-0.dll should be in the same directory as VirtualDub64.exe and avcodec-61.dll and avformat-61.dll and others...

[v0lt]

Where i was doing wrong ?
I don't know what you're doing wrong. Here's what I did.

1. I am running Windows 7 SP1 with some updates in VirtualBox.

2. Downloaded VirtualDub2_v2.1.1.609.7z, unlocked the file. Unpacked the entire archive and launched VirtualDub64.exe. I get an error and cannot use the avlib-1.vdplugin features.

3. Downloaded mingw-11.2.0.7z, unlocked the file. Unpacked the api-ms-win-core-synch-l1-2-0.dll file into the VirtualDub2_v2.1 folder (where VirtualDub64.exe is located).

4. Runned VirtualDub64.exe without errors and I see FFmpeg video codecs in the list of video codecs.

[v0lt]

https://forum.videohelp.com/threads/397927-64bit-Logo-Spot-remover-filter-for-VirtualDub#post2645514
Yes, I confirm the problem.
Exception thrown at 0x00007FFA8DB433C6 (delogo.vdf) in VirtualDub64.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFBC6C6C08.
It is possible that delogo.vdf was not ported correctly for x64.

[jpsdr]

If you did it correctly, api-ms-win-core-synch-l1-2-0.dll should be in the same directory as VirtualDub64.exe and avcodec-61.dll and avformat-61.dll and others...
Yes it was, that what i said.

I'm running Windows 7 "naturaly", not in Virtual box or anything.
And i did exactly what v0lt described in this post, get VDub, put the dll, etc... And when i run VDub, it said that one filter failed to load, and checking the log it was avlib-1.vdplugin. That's why i tried to put the dll also in plugins directory, didn't change anything.

Don't waste too much time on this, as i said, i just wanted to report my testing.

As method b of using Windows 7 compatible dll worked for me, it's fine.

[v0lt]

@isidroco
Try this file - delogo132_x64.zip (https://www.mediafire.com/file/4n25r22s9f40fyu/delogo132_x64.zip/file).

[isidroco]

Test 1) Regular w7sp1: "Procedure entry kernel32.WaitOnAddress in lib api-ms-win-core-synch-l1-2-0.dll", after that VDUB opens and only works with internal AVI driver.
Test 2) If DeShaker_64.dll is in plugins64 dir, VDUB opens with no errors (still no caching driver, no FFMPEG compresion formats).
Test 3) Using api-ms-win-core-synch-l1-2-0.dll from mingw-11.2.0 ONLY works if it doesn't previously exist within C:\WINDOWS\SYSTEM32, old version there will take precedence (must take ownership and replace or remove it from there). After that everything works.

new DELOGOx64 version works with new virtualDub, but it crashes in previous version: Unhandled Microsoft C++ Exception

Partial report:
VirtualDub2 crash report -- build 44282 (release-AMD64)
7fefd0db855: 33c9 xor ecx, ecx
7fefd0db857: 4889442430 mov [rsp+30h], rax
7fefd0db85c: 89542424 mov [rsp+24h], edx
7fefd0db860: 48894c2428 mov [rsp+28h], rcx
7fefd0db865: 4d85c9 test ecx, r9
7fefd0db868: 0f856a030000 jnz fd0dbbd8
7fefd0db86e: 894c2438 mov [rsp+38h], ecx
7fefd0db872: 488d4c2420 lea rcx, [rsp+20h]
7fefd0db877: ff1523ca0300 call dword ptr [fd1182a0]
7fefd0db87d: 4881c4c8000000 add esp, 000000c8 <-- FAULT

[isidroco]

Yes it was, that what i said.

Please try replacing it within windows\system32 folder.

[rgr]

VirtualDub crashes when the edited avs file is write-protected.

It would be nice if it would inform about it and save only after giving consent, preserving the read-only attribute :)

[jpsdr]

Thanks isidroco for your informations.
I have indeed in system32 an api-ms-win-core-synch-l1-2-0.dll, wich seems to be a "legitimate" MS version, with a version displayed when i click on it. The mingw-11.2.0 file has no version or anything. Files are different (12k vs 91k...!).
Honestly, i'm not a big fan of deleting what seems to be a legitimate version version of a dll in system32 directory. If one day realy i'm stuck, i'll know now what should be done. But for now, as using the Windows 7 compatible dll works for me, i'll stay with that.

[v0lt]

VirtualDub crashes when the edited avs file is write-protected.

It would be nice if it would inform about it and save only after giving consent, preserving the read-only attribute :)
The problem is in scripted.vdplugin (https://sourceforge.net/p/vdfiltermod/scripted/ci/master/tree/)

[isidroco]

Honestly, i'm not a big fan of deleting what seems to be a legitimate version version of a dll in system32 directory...
Same here, but test it in VM without issues, now I have both original (api-ms-win-core-synch-l1-2-0.dll 12k 2019/4/12; dxgi.dll 363k 2013/1/13) renamed to .DL0 and the minGW-11.2.0 versions in place of them. That allows vDub2 and possibly other w8+ software to run (as latest FFMPEG). If any problem it's easy to rollback.
In that way you can install latest VDub2, FFMPEG, etc without having to replace files or VxKex treat them each time you update.

Edit: VMware Workstation v15.5.7 gives: CreateDXGIFactory not found in dxgi.dll (after that it works). Restored original dxgi.dll (which it's not needed anywat for VDub/FFMEPG).

[v0lt]

VirtualDub crashes when the edited avs file is write-protected.
scripted.vdplugin_x64_fix.7z (https://www.mediafire.com/file/7kthpit06y2rdb1/scripted.vdplugin_x64_fix.7z/file)

[tormento]

Would be possible to add support for mkv chapters?

Markers on the time/frames bar would be more than enough, jumping to them would be even better.

[LigH]

The MP4 container supports chapters too. Adding them via ffmpeg metadata (chapterEditor supports this format) is possible but the CLI parameters are a bit elaborate.

[v0lt]

Would be possible to add support for mkv chapters?
Maybe someone can do it. But I doubt it will happen.

[nji]

For still pictures the LUT-filter is well known.
If you need to change the "characterstic" of a picture
(say from one analog film type to another, or false colored exposure,
or if you want to have a sunset character from a beach photo to some other shooting).
The LUT matches every RGB entry from source to dest;
- mostly it is coarsened, so it will be extrapolated.

This kind of manipulation would be helpful for some of movies too,
as the manual color corrections are sub-optimal.

Does anyone know about such filter for VD?

Needless to mention there is an AVS filter for that
http://avisynth.nl/index.php/AVSCube

[LigH]

The whole concept of VirtualDub Filters became quite obsolete...

[nji]

... to be replaced by... what?

BTW: that's quite OT, isn't it?

[LigH]

By AviSynth or VapourSynth, both frame servers with Non-Linear Editing features and filters working in multiple color spaces, not just RGB.

[v0lt]

Avidemux and Shotcut support 3DLut.
Both editors are free and open source.

[Leo 69]

The whole concept of VirtualDub Filters became quite obsolete...

Some people can't write scripts as quickly and easily as they can use VDub filters. For you personally they may be obsolete, for others they are as relevant as ever.

[nji]

Avidemux and Shotcut support 3DLut.
Both editors are free and open source.

Thanks!
Wouldn't have expected that.
However they don't fit into my workflow with VD2.
Still I could export (huge) lossless results from them, to import into VD2.
Or use the AviSynth with the above script as frame server for VD2.

[LigH]

For you personally they may be obsolete, for others they are as relevant as ever.

I don't mean me personally, but rather developers of plugins. The fewer people desperately need something, the lower may be the incentive for a developer to put any efforts in its implementation.

And I absolutely did not mean to point at you. I have similar problems from time to time. Like, I may be the only one who would like to have an audio plugin ported to AviSynth+ 64b, so I may have to learn coding it myself or wait eternally.

[rgr]

I may be the only one who would like to have an audio plugin ported to AviSynth+ 64b

You're not the only one.

[isidroco]

@isidroco
Try this file - delogo132_x64.zip (https://www.mediafire.com/file/4n25r22s9f40fyu/delogo132_x64.zip/file).

Thanks for the build, is there a possibility to build one which also works with previous VDUB version?

[v0lt]

Thanks for the build, is there a possibility to build one which also works with previous VDUB version?
I don't have this problem with filter selection on my computer. I haven't tried using the filter. But I tried compiling the filter a little differently.
delogo132_x64_2024-10-01.zip (https://www.mediafire.com/file/6lxcigddhrep4jd/delogo132_x64_2024-10-01.zip/file)

[isidroco]

I don't have this problem with filter selection on my computer. I haven't tried using the filter. But I tried compiling the filter a little differently.
delogo132_x64_2024-10-01.zip (https://www.mediafire.com/file/6lxcigddhrep4jd/delogo132_x64_2024-10-01.zip/file)

Thanks, better, but still doesn't work when tried to use it in my script it gives: Cannot start filters: Filter "DeLogo 1.3.2" is not handling image formats correctly.

I would like to have only oneversion for all, but it's not critical.

Today I captured a NTSC DV. Original VirtualDub2_44282 using any input driver: all OK.
But with VirtualDub2_44282+avlib_vdplugin_0.7.0.123 or VirtualDub2_v2.1.1.609_x64only:
Image is broken using AV Internal input driver. Small sample here: https://www.mediafire.com/file/e0utl6hxbr2jzbp/tonyM60f.avi/file
Using Caching input driver can't see frames after aprox 1 second; seeking gives: error requested frame not found, next valid frame [lastFr]

Using old VDub, directStreamCopied to sample, partial, and full 7gb copy. None of those had problems with caching input. Will try to make a smaller direct sample with original winXP capture machine to upload it .

Unfortunately, new VirtualDub is for now less useful than 44282 which works with all the formats I'm using.

[isidroco]

Maybe "Audio/Video interleave input driver", and "Caching input driver" code should be left exactly as it was before, and add a new "FFMPG input driver" to handle newer formats without breaking old ones which could be opened as before...

[v0lt]

Image is broken using AV Internal input driver. Small sample here: https://www.mediafire.com/file/e0utl6hxbr2jzbp/tonyM60f.avi/file
"Internal DV decoder" does not work correctly due to optimizations in the modern compiler.

[isidroco]

"Internal DV decoder" does not work correctly due to optimizations in the modern compiler.

Yes, but many of us use vdub to deal with old video formats (recover old footage). So breaking DV support is a deal breaker here... With new caching driver, Sekh enabled ease of use with newer cameras as MOV/MP4, etc, but we could always return to old internal driver for compatible old behaviour . Here that's not working anymore. Maybe using older compiler, or disabling certain optimizations we could restore those lost functions...

[v0lt]

Looks like there is a problem with the VisualStudio 2022 compiler.
https://github.com/v0lt/VirtualDub2/commit/ded9caa528a6820204a6d1f9bfdc41dc6289e1ab

Added:
I wrote to Microsoft about the optimization problem. (https://developercommunity.visualstudio.com/t/Optimization-for-x64-produces-incorrect/10761549)