VirtualDub2

[nji]

Originally Posted by v0lt

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]

Originally Posted by Leo 69

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]

Originally Posted by LigH

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]

Originally Posted by v0lt

@isidroco
Try this file - delogo132_x64.zip.

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

[v0lt]

Originally Posted by isidroco

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

[isidroco]

Originally Posted by v0lt

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

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/e0utl...yM60f.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]

Originally Posted by isidroco

Image is broken using AV Internal input driver. Small sample here: https://www.mediafire.com/file/e0utl...yM60f.avi/file

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

[isidroco]

Originally Posted by v0lt

"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/...dc41dc6289e1ab

Added:
I wrote to Microsoft about the optimization problem.

[isidroco]

Originally Posted by v0lt

I wrote to Microsoft about the optimization problem.

Thanks for your concern. Maybe it could be compiled with the older working version used for original VDUB2.
More DV tests in old VDUB2: DV audio with caching driver has correct length, but 100ms silence at the beginning which causes slight synchro displacement. With AV interleave internal driver, length is 50ms shorter, but with no silence at the begin, so it's better. Video is the same on both.

[v0lt]

VirtualDub2_v2.1.2.647 (test build)
Fixed "Internal DV decoder".
(Disabled optimization for VDVideoDecoderDV:: DecompressFrame function. Visual Studio 2022 v17.11.4 was used)

Updated avlib-1.vdplugin to version 0.7.1.154.
FFmpeg 7.1 is now supported.

Updated scripted.vdplugin to version 0.2.0.44.
Fixed a crash when trying to save a read-only file.
Implemented Unicode support. Now script files are read and saved in UTF-8 format.

[jay123210599]

Originally Posted by v0lt

VirtualDub2_v2.1.2.647 (test build)
Fixed "Internal DV decoder".
(Disabled optimization for VDVideoDecoderDV:: DecompressFrame function. Visual Studio 2022 v17.11.4 was used)

Updated avlib-1.vdplugin to version 0.7.1.154.
FFmpeg 7.1 is now supported.

Updated scripted.vdplugin to version 0.2.0.44.
Fixed a crash when trying to save a read-only file.
Implemented Unicode support. Now script files are read and saved in UTF-8 format.

How do I add the SubText filter from StaxRip to your version of Virtualdub2? How do I cut losslessly at keyframes?

[v0lt]

Originally Posted by jay123210599

How do I add the SubText filter from StaxRip to your version of Virtualdub2?

VirtualDub supports filters and plugins written for VirtualDub.

VirtualDub can open Avisynth script files, and accordingly you can use Avisynth/Avisynth+ filters.

How do I cut losslessly at keyframes?

In general, no way. Because it works with many limitations (especially with modern formats) and the result will not satisfy you (judging by the number and content of your questions).

[LigH]

Originally Posted by v0lt

VirtualDub supports filters and plugins written for VirtualDub.

Another issue: Due to their heavy limitations, not many of these are being developed anymore. And if you find some ancient plugins from other authors, these probably exist in 32-bit code only. But the latest VirtualDub2 only exists in 64-bit code and can't use 32-bit plugins.

You should really learn to use AviSynth or VapourSynth if you seriously want to filter your videos efficiently. VirtualDub2 can serve as a solid host application to feed the results of these scripts to encoders then.

[jay123210599]

@v0lt @LigH But whenever I use an Avisynth/VapourSynth script, it doesn't use the same codec as the video I put inside it. How do I fix that?

[LigH]

Whenever you want to apply a filter to the video, it needs to be decoded first. And when the video has been filtered, it needs to get encoded again. Nothing can "fix" that. If you want to keep video as compressed as it is, you cannot modify it.

[jay123210599]

Originally Posted by LigH

Whenever you want to apply a filter to the video, it needs to be decoded first. And when the video has been filtered, it needs to get encoded again. Nothing can "fix" that. If you want to keep video as compressed as it is, you cannot modify it.

I want to encode the video, but I want to make sure it has the same aspects as the original. For example, I have a YUV444 video, and I want the output to also be a YUV444 video, even though the quality will not be the same due to encoding. My problem is that I insert a script and it doesn't start at the colorspace as my video (e.g. it starts at YUV420 instead).

[LigH]

AviSynth since v2.60 supports the colour format YV24 for chroma subsampling YUV 4:4:4. Most recent plugins for AviSynth+ should support that too. There is no reason to blame VirtualDub2, it can handle that. You will have to learn how you possibly have to force AviSynth source plugins to read your video in a way that it decodes to YV24 if you need YUV 4:4:4, or to convert it to that format in your script. But that's not a matter of this forum thread.