VirtualDub2

[tormento]

Would be hard to add mkv chapter support to be shown in the timeline?

Eventually, jumping to them would be nice too.

[nji]

I tried (for the first time) the version with newer avlib etc.
(both orig and v.2.1) @
Win7-64, VC++ redistr. x64 2015-2022.

Entry point "kernel32.WaitOnAddress" wasn't found in DLL
"api-ms-win-core-synch-l1-2-0.dll"
(freely translated).

So at least Win8 necessary?
https://learn.microsoft.com/en-us/wi...s#requirements

[v0lt]

Originally Posted by nji

Entry point "kernel32.WaitOnAddress" wasn't found in DLL
"api-ms-win-core-synch-l1-2-0.dll"
(freely translated).

I think some FFmpeg 7.0 builds no longer support Windows 7.
The function you mentioned is contained in avcodec-61.dll.

[nji]

So if it's only some ffmpeg builds that need Win8+,
it may be an option to use the other ones?

[LigH]

Worth a try for sure, some publishers may use different compilers/options. But no guarantee, ffmpeg may link modules which don't support outdated OS anymore. Multithreading is a feature that depends a lot on efficient OS features.

[jay123210599]

Originally Posted by jay123210599

and the rest of the my question? to extract frames and make image sequences, and also burn in subtitles?

@v0lt Can you answer my question, please? How do I use ffmpeg as an external encoder for these things in Virtualdub2?

[LigH]

I know that VirtualDub2 can export image sequences on its own.

And I know that AviSynth can burn in subtitles.

I would certainly not insist in learning how to do it in ffmpeg.

[v0lt]

Originally Posted by jay123210599

@v0lt Can you answer my question, please?

No.

How do I use ffmpeg as an external encoder for these things in Virtualdub2?

Read the FFmpeg documentation. Maybe there is what you need. This is off-topic here.

[nji]

Originally Posted by v0lt

I think some FFmpeg 7.0 builds no longer support Windows 7.
The function you mentioned is contained in avcodec-61.dll.

I checked the Win prebuilds mentioned at official site
https://www.ffmpeg.org/download.html

gyan.dev builds https://www.gyan.dev/ffmpeg/builds/
"Essentials build compatible with Windows 7 or above.
Full build requires at least Windows 10."
(Probably these are the ones you're using?)
==> No libs for Windows 7.

BtbN builds https://github.com/BtbN/FFmpeg-Builds
"are targetting Windows 7 and newer".
So I tried by exchanging the ffmpeg libs (in both 44282 and v.2.1 version)
but strange: same message at start.

EDIT:
It seems that BtbN builds are not targetting Windows 7/8 anymore,
at least from June on:
https://github.com/BtbN/FFmpeg-Builds/issues/386

EDIT2:
With that last Win7 compatible ffmpeg version mentioned in the issue...
replacing the av-libs, now both VD2 version do (at a first test).
Still it is not recommendable (e.g. the mentioned webp exploit
mentioned in the issue).
(OT: ESU since 2023, ffmpeg's (libs only!) since June, browser from Sept., ... finally time 4 Linux).

[jay123210599]

Originally Posted by LigH

There is one for AviSynth: SupTitle

What if the subtitles are embedded in the video?

[nji]

Originally Posted by nji

...replacing the av-libs, now both VD2 version do (at a first test).

But doing some comparison between "orig" VD2 with outdated ffmpeg and new v.2.1 with up-to-date ffmpeg
there is no difference in results (only few bytes in meta data).
I took an mp4/avc1 movie, rescaled and saved as mp4/avc1 again.
I would have expected especially that newer swscale would produce a better result.

Maybe I have a misunderstanding in the results new VD2 should produce?
What kind of differences should occur?
At the moment is seems it produces same as before...

[v0lt]

https://www.animmouse.com/p/ffmpeg-binaries/
Builds with DLLs are called shared.
Current versions of avlib_vdplugin require FFmpeg 7.0.x.

[LigH]

Originally Posted by jay123210599

What if the subtitles are embedded in the video?

If they are "embedded" as multiplexed subtitle stream in a container, then they can be extracted to a *.sup file. In case of MKV files ripped from Blu-ray using MakeMKV, eac3to is pretty useful.

[nji]

Originally Posted by v0lt

https://www.animmouse.com/p/ffmpeg-binaries/
Builds with DLLs are called shared.
Current versions of avlib_vdplugin require FFmpeg 7.0.x.

Yes, I know that.

As posted above I used
https://github.com/BtbN/FFmpeg-Build...shared-7.0.zip

With that I get the effect described above (i.e. no effect).

So, why's that?

[v0lt]

I think it's obvious. You are missing the file "api-ms-win-core-synch-l1-2-0.dll".

[LigH]

AFAIR it is provided by MS VC Runtimes 2015+; please note that these installers exist in 32 bit and 64 bit flavours. You might use the VisualCppRedist AIO to get all versions up to date.

[nji]

Originally Posted by v0lt

I think it's obvious. You are missing the file "api-ms-win-core-synch-l1-2-0.dll".

Not at all.

I would miss that runtime, if I would use the ffmpeg version you provide.
(BTW that runtime wouldn't be available for Win7).

But - as I tried to express in not only one of my posts above -
I do not use the ffmpeg version you provide,
but replaced your av-libs by ones that do for Win7.

They do well - without errors.
But... they produce exactly the same result movies as last shekh's (???)

My English must be very bad, that all my tries to express the matter are in vain...

[LigH]

Of course, exactly the same codecs produce (more or less) exactly the same results. No surprise.

Even updated codecs may produce still (more or less) exactly the same results. Not many updates will change the efficiency noticeably. Maybe such updates which introduce features not yet present in previous codecs, so you can't compare them directly.

The main reason for updating av-libs was fitting them to new ffmpeg interfaces which are required to add new and more complex codecs. Like AV1 and VVC decoders.

[nji]

Ah... thanks for that.

As there are generations of updates between shekh's and vOlt's ffmpeg,
I would have expected differences in at least swscale module
(which is known to produce quite suboptimal results in the past).
But - as said - there is literally no difference (only some meta data bytes).

So, if anyone should ever notice main differences between the ffmpeg version's results,
maybe post the example.

[v0lt]

avlib_vdplugin provides the following functions:
1. Opens and decodes various video files. If you open File Information, you may see "Caching Input Driver" in the title. In this case, avlib_vdplugin is used.
2. Adds the "fflayer" video filter.
3. Adds video and audio codecs to the list of codecs with the "FFmpeg" prefix.
4. Allows you to save videos in MKV, MP4, etc.