Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > VirtualDub, VDubMod & AviDemux

Reply
 
Thread Tools Search this Thread Display Modes
Old 4th September 2024, 16:05   #1401  |  Link
coolgit
Registered User
 
Join Date: Apr 2019
Posts: 242
Quote:
Originally Posted by v0lt View Post
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.
coolgit is offline   Reply With Quote
Old 4th September 2024, 16:23   #1402  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
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 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?
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid

Last edited by LigH; 4th September 2024 at 16:26.
LigH is offline   Reply With Quote
Old 4th September 2024, 19:46   #1403  |  Link
v0lt
Registered User
 
Join Date: Dec 2008
Posts: 2,085
Quote:
Originally Posted by coolgit View Post
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 and VirtualDub2 v2.1 Readme.md.
Quote:
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-...Win7/releases/
On more modern Windows, you shouldn't do this.

Quote:
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.
v0lt is offline   Reply With Quote
Old 5th September 2024, 12:58   #1404  |  Link
coolgit
Registered User
 
Join Date: Apr 2019
Posts: 242
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.
coolgit is offline   Reply With Quote
Old 5th September 2024, 18:17   #1405  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
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.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 6th September 2024, 15:30   #1406  |  Link
coolgit
Registered User
 
Join Date: Apr 2019
Posts: 242
Quote:
Originally Posted by LigH View Post
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.
coolgit is offline   Reply With Quote
Old 6th September 2024, 15:46   #1407  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
GyanD's codexffmpeg issue 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.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid

Last edited by LigH; 6th September 2024 at 15:49.
LigH is offline   Reply With Quote
Old 6th September 2024, 15:56   #1408  |  Link
v0lt
Registered User
 
Join Date: Dec 2008
Posts: 2,085
Quote:
Originally Posted by coolgit View Post
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 is offline   Reply With Quote
Old 6th September 2024, 16:13   #1409  |  Link
v0lt
Registered User
 
Join Date: Dec 2008
Posts: 2,085
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-...Win7/releases/

3.Use VxKex.
Link: https://github.com/i486/VxKex
v0lt is offline   Reply With Quote
Old 6th September 2024, 16:21   #1410  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
Quote:
Originally Posted by v0lt View Post


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...
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 9th September 2024, 12:47   #1411  |  Link
coolgit
Registered User
 
Join Date: Apr 2019
Posts: 242
Quote:
Originally Posted by v0lt View Post
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-...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 is offline   Reply With Quote
Old 9th September 2024, 13:05   #1412  |  Link
coolgit
Registered User
 
Join Date: Apr 2019
Posts: 242
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.
coolgit is offline   Reply With Quote
Old 10th September 2024, 00:48   #1413  |  Link
isidroco
Registered User
 
Join Date: Nov 2008
Posts: 49
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).
isidroco is offline   Reply With Quote
Old 10th September 2024, 15:32   #1414  |  Link
v0lt
Registered User
 
Join Date: Dec 2008
Posts: 2,085
Quote:
Originally Posted by isidroco View Post
Hi, last vdub2 2.1.1.609 crashes instantly when adding deLogo Filter
As far as I know delogo.vdf does not exist for x64.
v0lt is offline   Reply With Quote
Old 10th September 2024, 19:33   #1415  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
Gyan identified the latest Rust as the cause of Windows 7 incompatibility ... so building rav1e with an older rust appears to be a solution.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 11th September 2024, 01:21   #1416  |  Link
isidroco
Registered User
 
Join Date: Nov 2008
Posts: 49
Quote:
Originally Posted by v0lt View Post
As far as I know delogo.vdf does not exist for x64.
https://forum.videohelp.com/threads/...ub#post2645514
isidroco is offline   Reply With Quote
Old 14th September 2024, 12:29   #1417  |  Link
jpsdr
Registered User
 
Join Date: Oct 2002
Location: France
Posts: 2,369
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.
__________________
My github.
jpsdr is offline   Reply With Quote
Old 14th September 2024, 13:26   #1418  |  Link
v0lt
Registered User
 
Join Date: Dec 2008
Posts: 2,085
Quote:
Originally Posted by jpsdr View Post
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?
v0lt is offline   Reply With Quote
Old 14th September 2024, 13:31   #1419  |  Link
jpsdr
Registered User
 
Join Date: Oct 2002
Location: France
Posts: 2,369
I don't understand your comment...
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 ?
__________________
My github.
jpsdr is offline   Reply With Quote
Old 14th September 2024, 21:14   #1420  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,079
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...
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 01:54.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.