#311 Using VirtualDub2 to Recompress Video on Windows XP

[Anonymous]

I like using VirtualDub for years. I use it to capture video on a computer with Windows XP. Now, I'm trying VirtualDub2 on that computer. It's successfully capturing the video. I open the captured AVI file with VirtualDub2. I'm starting the Recompress task. VirtualDub2 gives the that message; “Requested frame not found; next valid frame xxx”. This happens if frames was inserted to that file. Whichever one Codec I try, the result does not change.

I open the same captured AVI file with VirtualDub1. I'm starting the Recompress task. I use the same codecs! VirtualDub1 completes the task successfully.

Then I tried this. I copied the same captured AVI file to a computer with Windows 10 installed. I opened the file with VirtualDub2. I started the Recompress task. I use the same codecs! VirtualDub2 has successfully completed the task. This is surprising!

It seems; VirtualDub2 has some compatibility issues with Windows XP. I hope you can fix it.

Thanks...
By the way, thanks also for that you keeping Virtualdub2's command line commands compatible with VirtualDub1

Okan Ozcelik

[Anton Shekhovtsov]

I don't think this is related to XP.
The message 'Requested frame not found' belongs to caching input driver and happens in decoding source (not very connected to recompress).
Can you reveal some info:
1 what is the codec of your captured AVI (what compression was used when you did the capture)
2 are you sure "caching input driver" is also used on Win10 system and behaves differently (correctly)
You can see input driver in video->decode format dialog or in file->information.

[Anonymous]

Caching Input Driver appears YUV420-FR on Windows 10; YUV420-FR appears on Windows XP. I have never changed the Decompression Format settings.

I use Ffdshow Codec to capture video. But, whichever one Codec I try, the result does not change. I use Xvid MPEG-4 Codec to Recompress Video.

Now I have tried this. I chose “Uncompressed RGB / YCbCr” to capture video. Then I opened the file with VirtualDub2. I started the Recompress task. This time, VirtualDub2 successfully completed the task; although frames have been inserted.

Thanks...

Okan Ozcelik

[Anonymous]

Hello again,

I wrote that there was a problem recompressing the video captured with VirtualDub2. Now I have tried this. I opened the same video file with Avidemux. I chose x264 Codec to compress. Avidemux successfully completed the task! Of course I tried it on Windows XP.

I thought you'd want to know the result.

Okan Ozcelik

[isidroco]

Okan, HDs aren't fast enough to keep up with Uncompressed RGB, please try using Lagarith Lossles Codec, which is fast and will reduce data flow 3:1. You can try recompressing later.
You can also try opening captured video with both: Audio/Video interleave input driver (internal), that will mimic original VDub opening; Caching input driver will allow opening more formats although direct stream copy won't work on most of them.

[Anonymous]

I am using Huffyuv Lossless Codec in VirtualDub1. I'm not sure I tried Lagarith Lossless in VirtualDub2. But I'm starting a 1-2 hour long video capture task. Therefore, inserted 3-5 frames will always be.

Thanks for the suggestion ...

Okan Ozcelik

[Anonymous]

By the way, without forgetting I also mention:

I use 640x480 resolution to capture video.

I open the video file captured with VirtualDub2 with VirtualDub1. I am using the same Xvid Codec. VirtualDub1 successfully recompresses that file.

Okan Ozcelik

[isidroco]

VirtualDub2 with AudioVideoInterleave input Driver will mimic VirtualDub1 behaviour.

[Anonymous]

So where is this option change?

Okan Ozcelik

[isidroco]

File, Open video file, [select video file] and on the bottom right there is a Input driver Box which has Open using: Caching input driver; change it to Audio/video interleave input driver (internal)
Beware if you use Audio from another file that you may also want to select "Audio/video interleave input driver" when you open Audio File, to enable audio direct stream copy, or else you will get uncompressed PCM (sometimes 32 bits depending on input) on audio output.

[Anonymous]

OK, I'll try it.

Okan Ozcelik