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]

Originally Posted by jay123210599

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

[jay123210599]

Originally Posted by v0lt

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

How would that work, exactly?

[LigH]

Originally Posted by jay123210599

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]

Originally Posted by v0lt

What you write is not a VirtualDub problem. It is an old Windows bug.
https://superuser.com/questions/9165...s-my-selection

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

[rgr]

Originally Posted by 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?

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]

Originally Posted by rgr

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]

Originally Posted by LigH

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]

Originally Posted by LigH

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]

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

[v0lt]

Test build VirtualDub2_v2.3.1.867+avlib_vdplugin_1.0.0.357

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]

Originally Posted by SupermanTV

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?

[SupermanTV]

Originally Posted by v0lt

What is your frame size and format?

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]

Originally Posted by 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.

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.