VirtualDub2

[jay123210599]

I noticed that sometimes .M2TS files don't work properly with VirtualDub2. The videos often glitch out and it skips some keyframes. How do I fix that, other than remuxing them into other container formats?

[v0lt]

I noticed that sometimes .M2TS files don't work properly with VirtualDub2.
In the file open dialog with the "All media types" filter active (default) you will not see any .m2ts files. This is because MPEG transport stream is not fully supported for obvious reasons. Use tools that will build by analyzing the entire file (e.g. AVISynth > FFmpegSource (http://avisynth.nl/index.php/FFmpegSource)).

[jay123210599]

In the file open dialog with the "All media types" filter active (default) you will not see any .m2ts files. This is because MPEG transport stream is not fully supported for obvious reasons. Use tools that will build by analyzing the entire file (e.g. AVISynth > FFmpegSource (http://avisynth.nl/index.php/FFmpegSource)).

How would that work, exactly?

[LigH]

How do I fix that, other than remuxing them into other container formats?

In fact, exactly this is recommendable when working with VirtualDub2. I would probably prefer MKVtoolnix for MKV or MP4Box + some UI for MP4 as result. Or maybe Clever FFmpeg GUI.

If not, you can let e.g. StaxRip create an Avisynth script that loads the M2TS as video source with FFMS2 or L-SMASH Works plugin, if you don't dare to write that little script manually. (Note: Using L-SMASH Works, i.e. LSMASHSource.dll, you need to use LwLibavVideoSource for M2TS files to create an additional LWI index file; LSMASHVideoSource only works with ISO Base Media files like MP4, MOV, FLV, 3GPP - which already contain an index chunk.)

[rgr]

What you write is not a VirtualDub problem. It is an old Windows bug.
https://superuser.com/questions/91655/open-with-dialog-ignores-my-selection

Yes, I have read these and similar threads and unfortunately I have no solution.

[rgr]

I noticed that sometimes .M2TS files don't work properly with VirtualDub2. The videos often glitch out and it skips some keyframes. How do I fix that, other than remuxing them into other container formats?

I used to work with MTS files in VDub. The preview was glitchy when seeking, but the output file was fine.
This was easily fixed with ffmpeg (ffmpeg -c copy).

[v0lt]

Yes, I have read these and similar threads and unfortunately I have no solution.
Then use regedit.exe to manually find and delete all keys with old paths to VirtualDub2.

[LigH]

There are workflows not recommended to use in VirtualDub2 (tested with release 44282, 2.2.0.755 and 2.3.0.845)...

I opened a 4K UHD video from a VIOFO 229 Pro dashcam, which plays fine when I let it play linearly or skip through frame-by-frame.

Then I selected a range (800 frames), the internal x264 8-bit video encoder (CRF 18, Slower, --nr 100) and the FFMPEG AAC audio encoder, saved the result in an MP4 +faststart. The playback in MPC-BE shows video artifacts which seem to be caused by wrong motion prediction references. When I open the result in VDub2 again, it plays fine without issues, until frame 781:
---------------------------
VirtualDub Error
---------------------------
requested frame not found; next valid frame = 783
---------------------------
OK
---------------------------


Same procedure with an intermediate AviSynth script using L-SMASH Works (LSMASHVideo/AudioSource for the MP4 source): Same issue.

Same script processed through external x264, QAAC and FFMPEG: Perfect result.

May the internal x264 codec have some issues with large frames and random access at the same time?

[v0lt]

May the internal x264 codec have some issues with large frames and random access at the same time?
No. You have a problem with getting the right frame from the container and then decoding it. Encoders are not used for this.

[LigH]

So this is a difference between VirtualDub2 multiplexing the MP4 incorrectly and ffmpeg multiplexing the MP4 correctly?

I can provide files if you want to have a look.

[v0lt]

I can provide files if you want to have a look.
Please provide your file.
This is a mandatory step when writing such bug reports. The developers do not have your file. Also, the developers do not have user "any files".

[LigH]

:o I'm sorry, my fault. Missed a little difference between the x264 options in VDub2 and in the batch. It makes a difference whether you use preset "Slow" or "Slower". That on UHD material will result in different GOP attributes, and some may exceed the support of a HW decoder in my GPU.

So, instead, uhm: "Thanks, Nvidia"? :angry:

[v0lt]

Test build VirtualDub2_v2.3.1.867+avlib_vdplugin_1.0.0.357 (https://disk.yandex.ru/d/R3Ob8yREy4ChvA)

Updated avlib-1.vdplugin to version 1.0.0.357:
The FFmpeg 7.1.1 x64 build from BtbN is used.
Added saving and reading of encoder settings from the registry.
Added hardware video encoders NVENC, QSV, AMF for H.264 and HEVC.
Added hardware video encoders NVENC, AMF for AV1.
Cosmetic changes.

[SupermanTV]

Hello @vOlt..
Just as a heads-up, on the latest Beta release VirtualDub2_v2.3.1.867 + avlib_vdplugin_1.0.0.357..
Capturing with ProRes crashes and will not proceed.
I tested this Beta with the avlib-1.vdplugin 0.7.1.264 from the current Stable release v2.3.0.845 and then it works normal.
Maybe you can look into that if possible..
Thank you.

[v0lt]

Just as a heads-up, on the latest Beta release VirtualDub2_v2.3.1.867 + avlib_vdplugin_1.0.0.357..
I do not confirm.
I do not confirm. Show a screenshot of the VirtualDub window with the error.

[SupermanTV]

I'm on Windows 10 up-to-date.

Screenshot:

https://imgbox.com/jWvrPRgO

[v0lt]

What is your frame size and format?
https://i.ibb.co/TBLs6Kpr/camera-format.png (https://ibb.co/TBLs6Kpr)

[SupermanTV]

What is your frame size and format?
https://i.ibb.co/TBLs6Kpr/camera-format.png (https://ibb.co/TBLs6Kpr)

1920x1080 / 29.97 / YUY2

[v0lt]

I was unable to reproduce the issue by encoding a 1920x1080 test video to Prores 420YUV 10-bit hq.
New FFmpeg DDLs may not work correctly for your computer. Try FFmpeg DDLs from v2.3.0.845.

[SupermanTV]

I was unable to reproduce the issue by encoding a 1920x1080 test video to Prores 420YUV 10-bit hq.
New FFmpeg DDLs may not work correctly for your computer. Try FFmpeg DDLs from v2.3.0.845.

Yes, it's something in this latest avlib-1.vdplugin..

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!!
Tested on AMD Ryzen 7 and FX-8370.

So from now on, I'll just have to replace the avlib plugin in future releases.
Thank you.

[v0lt]

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]

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]

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]

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]

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]

Did you test on AMD chips?
Yes. AMD Ryzen 3 3200G.

[SupermanTV]

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]

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]

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?
https://s1.directupload.eu/images/250611/temp/fhp5fc8f.png (https://www.directupload.eu/file/d/8947/fhp5fc8f_png.htm)

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

[jay123210599]

How do I speed up videos in VirtualDub2?

[LigH]

Video - Frame Rate... - Change frame rate to (a higher value); but this will probably mess up the audio, if present. And the result may not match a secondary format specification.

[jay123210599]

Video - Frame Rate... - Change frame rate to (a higher value); but this will probably mess up the audio, if present. And the result may not match a secondary format specification.

I mean like in other video players (e.g. 1.2x speed, 1.5x speed, 2x speed, etc).

[LigH]

VirtualDub2 is an editor, not a media player. I don't see much sense in changing the playback speed only, independent of the nominal frame rate.

[jay123210599]

VirtualDub2 is an editor, not a media player. I don't see much sense in changing the playback speed only, independent of the nominal frame rate.

So it's not possible?

[SeeMoreDigital]

Not in the way you want to use it. No!

[LigH]

If you have a stack of complex video filters, you can be happy when it still plays in normal speed. Usually it can't keep up anymore.

Being able to check the filtering result frame by frame is much more important in an editor than fast-forward playback.

If you want to skip 50 frames button by button, hold the Alt key. Or pull the timeline slider with the mouse.

[wonkey_monkey]

If you turn the scene thresholds off in Preferences, you can use shift-ctrl-arrow to play as fast possible.

[jay123210599]

Video - Frame Rate... - Change frame rate to (a higher value); but this will probably mess up the audio, if present. And the result may not match a secondary format specification.

I doubled the frame rate for one of my videos but it didn't double its speed.

[SeeMoreDigital]

I doubled the frame rate for one of my videos but it didn't double its speed.Did you re-encode the video? What media player are you using?

[jay123210599]

Did you re-encode the video? What media player are you using?

Yes, I'm playing the video in VirtualDub2?

[SeeMoreDigital]

With respect... You're exhausting!

[LigH]

VirtualDub2 will not skip frames to ensure the frame rate during playback. It will prefer to show every frame, even if it will fall behind the timing.

Media players may do the opposite, e.g. skip decoding B frames and restrict themselves to displaying only I and P frames if that is necessary to keep up the desired playback speed.

[StainlessS]

VirtualDub2 will not skip frames to ensure the frame rate during playback. It will prefer to show every frame, even if it will fall behind the timing.
Set (tick) Drop Frames When Behind (its not ticked in below graphic, just shows you where it is)
[click me]
https://i.postimg.cc/n9kyytQm/Drop-Frames-When-Behind.jpg (https://postimg.cc/n9kyytQm)

EDIT: Not sure, maybe have to also UnTick "Sync To Audio" (above 'Drop Frames When Behind').