What I deleted
 

Hi Sanyln,

What I deleted was:

VirtualDub.video.SetSmartRendering(0);
VirtualDub.video.SetPreserveEmptyFrames(0);
VirtualDub.video.SetFrameRate2(0,0,1);

As for the version of Virtualdub I was using it was one that has MPEG-2 support:

https://www.videohelp.com/software/Virtualdub-MPEG2

My Nephew has around 100 DVDs that he recorded from VHS using one of those Combo devices.

I've created an MPEG-2 file from the first of them and as the regular Virtualdub doesn't support these files I used the one I linked to.

It seems to work fine though if you have another idea to be able to improve MPEG-2 files other than Virtualdub and Avisynth then I'd be happy to give it a try.

Do you get the idea that the whole freaking family would like me to help with their old family movies - I told them I would be happy to :smack:

So I guess the error message was to do with a non standard version of Virtualdub?

Regards,
Paul

Those are legitimate entries for Virtualdub 1.7.x and later.


VirtualDubMPEG2 is long obsolete, hasn't been updated for 10 or more years. "Regular" versions of VirtualDub have had MPEG2 support for many years using FCCHandler's VDub plugins. Years ago he posted Virtualdub plugins for FLIC, FLV, WMV, QuickTime, MPEG2, Matroska (mkv), and audio codecs for AC3 (plugin), ACMac3 (Windows), AAC, and Lame/mp3.

I have 3 versions of VirtualDub in my system: VirtualDub 1.9.11, the ancient VirtualDubmod, and VirtualDubMPEG2. But they're in three different folders with three different names: "VirtualDub", "VirtualDubmod", and "VirtualDubMPEG2". No problems with any of them when installed in that way. But you can't name all of the folders the same way, i.e, you can't have three folders all named "VirtualDub" or your registry will get confounded

You need Version 1.9.11 for considerably improved performance and convenience. Do you have it installed? If you do, go into the program's folder and create a subfolder named "plugins32". This folder will be used for the FourCC plugins. Then create another folder somewhere called VirtualDubPlugins -- us that folder to download VirtualDub plugin .zips and packages, then copy the plugins themselves to wherever they belong. The FCCHandler plugins belong in Plugins32, the audio plugins and codecs will install wherever they are required. Each FCChandler .zip file comes with a text file with very simple install instructions. If you have VirtualDub 1.9.11 installed (don't go for v.1.10.x, it's buggy), you can get the FCChandler plugins and codecs here:

VirtualDub FLV plugin https://sourceforge.net/projects/fcc...v.zip/download

VirtualDub WMV plugin https://sourceforge.net/projects/fcc...v.zip/download

VirtualDub Quicktime plugin
https://sourceforge.net/projects/fcc...e.zip/download

VirtualDub MPEG2 plugin https://sourceforge.net/projects/fcc...2.zip/download

VirtualDub Matroska plugin https://sourceforge.net/projects/fcc...a.zip/download

VirtualDub FLIC pluginhttps://sourceforge.net/projects/fcc...c.zip/download

VirtualDub AC3 plugin https://sourceforge.net/projects/fcc...3.zip/download

acmac3 codec https://sourceforge.net/projects/fcc...m.zip/download

AACacm codec https://sourceforge.net/projects/fcc...9.zip/download

Setup Lame/MP3acm codec https://sourceforge.net/projects/fcc...4.zip/download

I told my family the same thing, and I echo your opinion: :smack:
I've posted some of the work required and some results here: http://www.digitalfaq.com/forum/vide...html#post42318

Concerning "improving" MPEG2 recordings. Remember that MPEG is a lossy final delivery codec. Final delivery means that it's a codec (like h.264) not designed for further modification without damage. You can do cut and joins edits in smart-rendering editors, but if it doesn't smart render then even even a simple edit means total re-encoding and more quality loss. With a lossy codec, you can't restore what's loss. Each re-encode involves accumlatively more loss.

I hate to tell you this, but the best way to re-process MPEG2 is with lossless media in Avisynth, with some help from Virtualdub. You can do it with Virtualdub alone if you want, but there's a visible quality cost. MPEG is decoded for Avisynth using the DGDecode plugin. The MPEG colorspace is YV12. I've had to re-process quite a few MPEG recordings -- I would never have attempted it without the specialized filters in Avisynth. If you want to submit a sample MPEG edit to see how it's done, with Avisynth and possibly with Virtualdub alone (good luck), look here: http://www.digitalfaq.com/forum/news...ad-sample.html

Another long thread. :eek:

Yes, install ffdshow separately, it's not something that installs simply by using my zipped VirtualDub.

I keep copies of VirtualDubMPEG2 and VirtualDubMod in the same folder because it makes no difference, and I rarely use them anymore. v1.9.x for capture, and the new FilterMod version for processing. I've not finished my packaging of that one yet. I keep 1.3 in a separate folder, for the rare instance where I need to edit an ASF.

Telling the family you'll convert their video is nowhere near as bad as converting obscure audio, or scanning photos. But I'm into preserving family history, so no complaints here -- unless I'm rushed or hassled.

@sanlyn: MPEG is NOT a delivery format. It exists as everything from edit masters (MXF, Sony IP GOP, etc) to mid-range (Bluray) to compressed (long DVDs) to ultracompressed (streaming pre-Flash, VCD).

Just to add that there are no capacitors to fail in the video circuit of the HS1000 apart from in the PSU can - which runs hot. Unlike older VCR's they used IC's to process video and not boards with SMD capacitors. There are a few caps, but they are through hole and very high quality.

The PSU will likely need rebuilding though for best performance.

I have seen one HS1000 with 'off' performance and it may have been one of the video IC's failing but I never did get to the bottom of it.

Lastly, please turn AI off - it will vary the sharpness and sometimes add too much or change it during a scene. Use the sharp to soft slider instead.