VirtualDub2

[v0lt]

Originally Posted by SupermanTV

As I mentioned before, I tested this Beta with the avlib-1.vdplugin 0.7.1.264 from current Stable release v2.3.0.845 and that works!!

Please copy FFmpeg DDLs from v2.3.0.845 to v2.3.1.867 to see if the problem is in FFmpeg or VirtualDub2.

avcodec-61.dll
avformat-61.dll
avutil-59.dll
swresample-5.dll
swscale-8.dll

[SupermanTV]

Originally Posted by v0lt

Please copy FFmpeg DDLs from v2.3.0.845 to v2.3.1.867 to see if the problem is in FFmpeg or VirtualDub2.

avcodec-61.dll
avformat-61.dll
avutil-59.dll
swresample-5.dll
swscale-8.dll

I just did that to comply with your request, and it doesn't work either..

It's related to the latest avlib_vdplugin_1.0.0.357, because as soon as I replace that with the older avlib-1.vdplugin 0.7.1.264 it works.

[v0lt]

Can you reproduce the crash in normal mode (not capture mode)?
x64 or win32?

[SupermanTV]

Originally Posted by v0lt

Can you reproduce the crash in normal mode (not capture mode)?
x64 or win32?

I can confirm the same crash in Normal mode trying to convert/encode a video to ProRes.. (x64).

I also tested this with Beta win32 version and same issue!!
Crash in both Capture and Normal mode.

[LigH]

Originally Posted by SupermanTV

Capturing with ProRes crashes and will not proceed.

Do you have any details about the kind and possible reason of the crash? You know, reasons can be very different, like e.g. a missing runtime DLL or an unsupported CPU instruction ...

[SupermanTV]

I'm attaching the crash report..

Things I'm wondering about as possible causes:

1 - AMD chips? I only tested on my PC (AMD FX8370 *Win10 latest), and my laptop (AMD Ryzen 7 *Win11 latest).
2 - Anything different with the Compiler used?
3 - Maybe backtracking changes made from the Current Stable version.
(*like this one: "Added saving and reading of encoder settings from the registry.")
Would that affect the way the avlib_vdplugin communicates with FFMPEG BtbN maybe, not plugging ProRes codec properly?

[v0lt]

Attachments are best posted on file sharing services.
Plain text can be posted on Pastebin.com.

PS: I checked encoding in Prores on two computers and one laptop. At my request, a colleague checked on his computer. There were no crashes.

[SupermanTV]

Originally Posted by v0lt

Attachments are best posted on file sharing services.
Plain text can be posted on Pastebin.com.

PS: I checked encoding in Prores on two computers and one laptop. At my request, a colleague checked on his computer. There were no crashes.

Thanks for pointing out.. Here's the log:
https://pastebin.com/ASeASUiQ

Did you test on AMD chips?

[v0lt]

Originally Posted by SupermanTV

Did you test on AMD chips?

Yes. AMD Ryzen 3 3200G.

[SupermanTV]

Originally Posted by v0lt

Yes. AMD Ryzen 3 3200G.

I see.. Oh well then, I'll just keep replacing the avlib with avlib-1.vdplugin 0.7.1.264.. I'm ok with that.

Thanks a lot for looking into it.

[LigH]

Windows 10 Pro (migrated from a Windows 7), AMD Ryzen 5, converting from a FullHD AVC recorded by a DSLR: No crash.

[SupermanTV]

Originally Posted by LigH

Windows 10 Pro (migrated from a Windows 7), AMD Ryzen 5, converting from a FullHD AVC recorded by a DSLR: No crash.

Thanks for testing too, LigH..
It's gotta be something within my settings.

[coolgit]

Originally Posted by nji

I recently noticed that (some?) HD movies (1920x1080p, YUV4:2:0)
which are not explicitely labeled as bt.709
are shown in VD2 orig pane as if VD2 takes them as bt.609
(esp. this typical small shift red/yellow to green/blue).

If I use alias format filter as first filter and choose bt.609
both panes (orig and result) are the same.
If choosing bt.709 in the filter the result pane is more red/yellow than the orig pane.
==> Conclusion: orig movie is colorspace bt.609.

BUT:
The orig movie actually is the red/yellow one!
At least MPC-HC shows it that way...

So VD2's orig pane view is misleading...

Or is it about the default handling of the case that movie dimensions are HD,
but no color entry (which usually means bt.609)?

It isn't a bug. I did some testing long time ago and this how it works. If you have a short clip of some red or green you can test it yourself.

If you know the video is 709 colour space but decode format doesn't show -709 in actual format box then click on 709 colour space. The correct colour will show on the panes then you can use the filters correctly. If you leave it at 'no change' then it won't affect the colour output so long there is 'no conversion' in the compression box.

Tests. 4 clips.

input 709 - output 709 - 709 on media info. colour same as original video - good
input 709 - decode 601 - output 601 - 601 on media info. colour same as original video but mislabelled as 601 - bad
input 709 - decode 601 - output forced 601 - 601 on media info. colour same as original video but mislabelled as 601 - bad
input 709 - decode 601 - output forced 709 - 709 on media info. colour change from original video with correct label as 709 - bad

Hope this helps.

[v0lt]

Does anyone have the "Display > Use effect file: display.fx" setting working? What is it for? Are there any example .fx files that will work in VirtualDub?

[Emulgator]

A junction for later exploration left by Avery Lee, I guess. I had no use for it so far, but others might.

Effects file created for Direct3D, a part of Microsoft DirectX that is used to define the appearance of 3D objects.
Contains plain text effects properties structured into three sections: variables, functions, and techniques
Written using Microsoft's High Level Shader Language (see also .HLSL files).
FX files are used to specify textures, lighting parameters, shading, rendering properties, and other effects.

[v0lt]

I found an example of display.fx in the help.

VirtualDub help - Video display shader support
This effect file produces an emboss effect on the displayed video. It should work on any video card with pixel shader support.

texture vd_srctexture;
float4 vd_texsize;

sampler src = sampler_state {
	Texture = <vd_srctexture>;
	AddressU = clamp;
	AddressV = clamp;
	MinFilter = linear;
	MagFilter = linear;
	MipFilter = linear;
};

void VS(
	float4 pos : POSITION,
	float2 uv : TEXCOORD0,
	out float4 hPos : POSITION,
	out float2 uv0 : TEXCOORD0,
	out float2 uv1 : TEXCOORD1)
{
	hPos = pos;
	uv0 = uv - vd_texsize.wz;
	uv1 = uv + vd_texsize.wz;
}

float4 PS(float2 uv0 : TEXCOORD0, float2 uv1 : TEXCOORD1) : COLOR0 {
	return tex2D(src, uv1) - (tex2D(src, uv0) - 0.5);
}

technique point {
	pass {
		VertexShader = compile vs_1_1 VS();
		PixelShader = compile ps_1_1 PS();
	}
}

And it only works for displaying on the display. I think this feature was very rarely used.