VirtualDub2

[rgr]

Originally Posted by LigH

"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]

Originally Posted by LigH

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]

Originally Posted by LigH

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.

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

[rgr]

Originally Posted by v0lt

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

[v0lt]

On Windows 7, you can use the win32 version.
You must install the Microsoft Visual C++ Redistributable packages for Visual Studio 2015-2022 or the Update for Universal C Runtime in Windows.

FFmpeg 8.0 x64 for Windows 7 doesn't seem to exist. However, you can try alternative methods.

[v0lt]

Test build VirtualDub2 v2.4.2.936
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?