Advice on VHS to DVD workflow and Virtual Dub Settings?

[sanlyn]

By VirtualDub filter chain, are you talking about during capture or in post-processing?

[zoink187]

Post processing


Sent from my iPhone using Tapatalk

[sanlyn]

The usual procedure is basic levels correction and denoising, etc., in Avisynth, then Virtualdub -- if necessary. There are many things VDub can't do. And stuff Avisynth can't. Each has its uses.

[zoink187]

I watched a tutorial on avi synth and it's quite overwhelming. When I capture the file in virtual dub, am I setting capture file to avi and then going to video>compression>
Lagarith>configure yuy2? Or am I going to uncompressed capture then save as lagarith?


Sent from my iPhone using Tapatalk

[sanlyn]

You set compression to Lagarith YUY2.

[zoink187]

I have been doing that but I had read that someone was doing that another way.


Sent from my iPhone using Tapatalk

[sanlyn]

Perhaps you can get this "someone" to explain to other extremely curious members how "someone" runs a VirtualDub capture without setting up their compressor.

[zoink187]

Reading further, it was a misprint. It was corrected. Sorry. At the very basic level, what would you recommend as far as filer chains? I'm assuming deinterlace to unfold then filters like flaxen and denoiser and deinterlace to fold back up. Does that sound right? I'm having a heck of a time with avisynth. Unless you have suggestions about scripts in avisynth?


Sent from my iPhone using Tapatalk

[sanlyn]

At the very basic level, what would you recommend as far as filer chains? I'm assuming deinterlace to unfold then filters like flaxen and denoiser and deinterlace to fold back up. Does that sound right? I'm having a heck of a time with avisynth. Unless you have suggestions about scripts in avisynth?

VirtualDub filters work with interlaced video. A small number of VDub filters have an interlace "on/off" indicator so that you can inform the specific filter if video is interlaced. Most VDub filters don't care. Deinterlacing with VirtualDub will suffice in a pinch if you're desperate, but it's inferior to what's available in Avisynth. Even the best deinterlacers have a quality and/or detail cost, so it's something done only when cleaning or repair requires it. If the source video is telecined, deinterlacing is a no-no.

We'd need more detail about "a heck of a time" with Avisynth. If you get errors when running scripts, we have to know specifically what the error refers to, and usually a copy of your script.

But you've ignored a few things: how did you get a frame size of 720x475? Is the original tape recorded in-camera as 6-hour tape?

Your submitted captures are an invalid frame size for standard video formats. The damage done to interlaced field and data structure has been mentioned. It's no surprise if Avisynth gives errors with that frame size and YUV colorspace. I avoided those errors with a few lines of code so that Avisynth would simply run, period, but the damage had already been done.

There's little sense to using VirtualDub filters until the source is repaired in AVisynth in its original colorspace. If by a "filter chain" you mean using the same filters and the same settings for every video, the answer is that the same filters and settings won't work for every video, or even for every scene in a home-made video.

Below is the Avisynth script I used to try to repair the damage. It cleans up somewhat, but there would be no use in continuing with a defective capture.

AviSource("Drive:\path\to\video\SampleKP.avi")

AddBorders(0,0,0,5)
Crop(4,2,-8,-6).AddBorders(6,8,6,0)

ColorYUV(cont_y=15,off_y=12)
ColorYUV(cont_v=-50,off_v=-3,cont_u=50,off_u=2)
Cnr2("xxx",4,5,255)
Checkmate(16)
COnvertToYV12(interlaced=true)
HQDering()
AssumeTFF().QTGMC(preset="fast")
MergeChroma(awarpsharp2(depth=30))
Spline16Resize(352,480)
TemporalSoften(3,3,8,15,2).TurnRight().TemporalSoften(3,3,8,15,2).TurnLeft()
Spline36Resize(720,480)

ConvertToYUY2(interlaced=false)
FixVHSOversharp(20,16,12)
FixVHSOversharpL(20,12,8)

ConvertToRGB32(matrix="Rec601",interlaced=false)
AssumeTFF().SeparateFields().SelectEvery(4,0,3).Weave()

[zoink187]

We'd need more detail about "a heck of a time" with Avisynth. If you get errors when running scripts, we have to know specifically what the error refers to, and usually a copy of your script.

I have trouble starting it and understanding the scripts because I'm a chuckle head.


But you've ignored a few things: how did you get a frame size of 720x475? Is the original tape recorded in-camera as 6-hour tape?

I cropped the bottom on that sample but that has been fixed since. It's a VHS-C tape



Sent from my iPhone using Tapatalk

[zoink187]

Thanks for the script advice


Sent from my iPhone using Tapatalk

[sanlyn]

Try submitting a better sample, and a little longer. No cropping or processing. Make a clip from an original, unaltered capture. Then we can get more specific about cleanup.

[zoink187]

Ok. I will work on that soon


Sent from my iPhone using Tapatalk

[zoink187]

I have attached an unfiltered sample. The settings are per the recommendations. I hope this helps.

[sanlyn]

Thanks for the new sample. Sorry for the delay.

The tape isn't the best specimen ever posted here, but we've seen worse. It has some terrific color, detail, and playback problems. It's evident that the budget equipment you're using won't give better results. Before processing, the video looks oversharpened. It even looks oversharpened after all the processing, and I didn't even use any sharpeners. If this tape was originally recorded at slow 6-hour speed, using a JVC for playback isn't going to get good results. I don't know of anyone who would recommend a JVC for extended play tapes. In any case, either you should clean your tape heads or, even better, try to find a better player and capture device. If you can't, so be it.

The image has ragged edges, isn't tracking properly (watch the curtains), and has some aliasing. Shadow detail is murky, most people in the audience look gray and there's hardly any color in the shadows. I used Avisynth for most of the work. A tape with this many problems can hardly be spiffed up any other way. Most of the color and levels tweaks were in VirtualDub with Colormill, levels, and built-in temporal smoother set low. There's a lot of camera shake, which means you'll have to use fairly high bitrates when encoding.

# --- adjust the path statements  ---# 
# --- below to match your system. ---#
vidpath="E:\forum\zoink187\B\"
ppath="D:\Avisynth 2.5\plugins\"
Import(ppath+"ContrastMask.avs")
Import(ppath+"HQDering.avs")

AviSource(vidpath+"SampleKP.avi")
COlorYuv(off_v=-3.0)
ColorYUV(cont_y=20,off_y=5)
Cnr2("xxx",4,5,255)
ChromaShift(C=2)
# --- try a little edge smoothing ---#
Santiag()

# --- The plugins below require YV12 ----#
ConvertToYV12(interlaced=true)
# --- Try to bring out some shadow detail ---#
ContrastMask(enhance=5.0)
HQDering()

# --- deinterlace without too much detail loss----#
AssumeTFF().QTGMC(preset="fast")

# --- For halos, chroma bleed, aliasing, edge noise, dot crawl ---#
MergeChroma(awarpsharp2(depth=30))
DeHalo_Alpha()
Spline16Resize(352,480)
TemporalSoften(3,3,8,15,2).TurnRight().TemporalSoften(3,3,8,15,2).TurnLeft()
Spline36Resize(720,480)

# --- For left and right dark edge halos ---#
ConvertToYUY2(interlaced=false)
FixVHSoversharp(20,12,8)
FixVHSoversharpL(20,12,8)

# ---- Crop off switching noise, fix old borders, center image
Crop(4,0,-8,-8).AddBorders(6,4,6,4)

# ---- Prepare for RGB filters, and re-interlace ---#
ConvertToRGB32(matrix="Rec601", interlaced=false)
AssumeTFF().SeparateFields().SelectEvery(4,0,3).Weave()

return last

If you want help with the filters, let us know.

[zoink187]

Ok. Thank you very much! The video source is a VHS-C tape that has probably seen a lot of action. I don't know if it was recorded in 6 hour speed but I do know that it's a 60 minute tape. I used the ATI 600 USB S-video inputs. What other player can I use without having to get a TBC? Will it make any difference?


Sent from my iPhone using Tapatalk

[sanlyn]

A 60-minuite tape isn't likely to be EP tape. (I never used VHS-C, so correct me out there). Your JVC isn't a bad player, so either the tape just looks the way it does, or you might want to consider head cleaning to see if it helps. Many home-recorded tapes from consumer cameras just don't look that great, even if they did look "good" on the old CRT. I'm afraid the digital age isn't at all kind to tapes. Takes a little perspiration to make the old stuff look better.

I believe the JVC has a sharpener called Digital R2, or something like that. If it does, don't use it but keep the TBC. That sharpener is the old fashioned kind that can make tape noise look pretty bad. You can always sharpen later, and there are better plugins for that in software.

[zoink187]

Yeah I don't want to dub to a blank vhs because maybe that will make it worse. I'm going to try the head cleaner se if it helps. I only have the tbc function on and I have it set to "edit". I will be home soon to review the files you attached.


Sent from my iPhone using Tapatalk

[zoink187]

Outstanding editing!!!!! It looks better! I don't think I can get it to how it looks when it plays back on the vcr because the clarity is lost a bit but even still very good restore. I'm going to try these settings


Sent from my iPhone using Tapatalk

[zoink187]

I noticed that you made it into an mpg. What did you use?


Sent from my iPhone using Tapatalk

[sanlyn]

Encoded with TMPGenc Plus 2.5, then resampled the audio to AC3 with the video in TMPGenc MPEG Smart Renderer. Another excellent MPEG encoder (free) is HCenc . There are some free tools that use HCenc, I believe AVS2DVD uses it. HCenc and the old TMPGenc-2.5 are both very popular.

[zoink187]

I need a day off from work to put this software setup together.


Sent from my iPhone using Tapatalk

[zoink187]

Thanks again


Sent from my iPhone using Tapatalk

[zoink187]

# --- adjust the path statements ---#

# --- below to match your system. ---#

vidpath="E:\forum\zoink187\B\"

ppath="D:\Avisynth 2.5\plugins\"

Import(ppath+"ContrastMask.avs&quot

Import(ppath+"HQDering.avs&quot



AviSource(vidpath+"SampleKP.avi&quot

COlorYuv(off_v=-3.0)

ColorYUV(cont_y=20,off_y=5)

Cnr2("xxx",4,5,255)

ChromaShift(C=2)

# --- try a little edge smoothing ---#

Santiag()



# --- The plugins below require YV12 ----#

ConvertToYV12(interlaced=true)

# --- Try to bring out some shadow detail ---#

ContrastMask(enhance=5.0)

HQDering()



# --- deinterlace without too much detail loss----#

AssumeTFF().QTGMC(preset="fast&quot



# --- For halos, chroma bleed, aliasing, edge noise, dot crawl ---#

MergeChroma(awarpsharp2(depth=30))

DeHalo_Alpha()

Spline16Resize(352,480)

TemporalSoften(3,3,8,15,2).TurnRight().TemporalSof ten(3,3,8,15,2).TurnLeft()

Spline36Resize(720,480)



# --- For left and right dark edge halos ---#

ConvertToYUY2(interlaced=false)

FixVHSoversharp(20,12,8)

FixVHSoversharpL(20,12,8)



# ---- Crop off switching noise, fix old borders, center image

Crop(4,0,-8,-8).AddBorders(6,4,6,4)



# ---- Prepare for RGB filters, and re-interlace ---#

ConvertToRGB32(matrix="Rec601", interlaced=false)

AssumeTFF().SeparateFields().SelectEvery(4,0,3).We ave()



return last

Is this the exact wording when I put in the avisynth scripts?
Are the # signs directions for me?



Sent from my iPhone using Tapatalk

[sanlyn]

[QUOTE=zoink187;2307978]Any line or section of code that begins with "#" indicates a comment, not executable code. The Avisynth runtime ignores comments.

However, note the following:

vidpath="E:\forum\zoink187\B\"

Statements like this are created to store a text string value. Text values belong inside double-quotes. The original statement reads:
vidpath="E:\forum\zoink187\B\"
which is the full path to the location of the original input video I was working with. I don't know where " is coming from, but it's not in the script. You have to change the path data to match the drive and path name on your computer. The statement is formatted so that the definition of the path string that is saved in vidpath will end with "\".

Later in the code you will see this statement:

AviSource(vidpath+"SampleKP.avi")

That statement uses a "+" or concatenation symbol called a "splice" to join two objects together. The two objects joined by this statement are text strings. The first text string is inside vidpath (which contains the text string value "E:\forum\zoink187\B\"), and the second text string is stated as "SampleKP.avi". When the two text strings are joined with the "+" operator, at run time the statement is interpreted like this:

AviSource("E:\forum\zoink187\B\SampleKP.avi")

I think you can see that you don't have a drive or folder names in your system that look like the path in that statement. Also, I think I can safely assume that you don't have your Avisynth plugins folder on the "D" drive of your system, but its probably in C:\Program Files\Avisynth 2.5\plugins\", or a similar location on your C drive. You will have to modify the path statements and locations to reflect your system setup.

The filters and plugins used in this script are in wide common use; there's nothing exotic about them. Many of the functions in the script are built-in Avisynth commands such as ColorYUV or ConvertToYV12. Those that are not built-ins are external plugins that should be in your Avisynth plugins folder. The external filters used are:

- ContrastMask.avs
- VariableBlur.dll
- HQDering.avs
- QTGMC.avsi and its support files
- DeHalo_Alpha.avsi
- aWarpSharp.dll
- FixVHSoversharp.dll

Is this the exact wording when I put in the avisynth scripts?

Yes. Before posting the script I ran it on my system, and it included the comments. I saved the output of that script as Lagarith RGB, then opened the saved file in VirtualDub to apply the color tweaks. The exception to the same wording is that you have to modify the path statements and probably the name of the AVI you want for input. I guess you know that an .avs script is just a simple text file typed in a text editor (such as Windows Notepad), but with .avs on the end of the filename instead of .txt .

If you're missing plugins, I or my wife will be monitoring the thread today while I work.

Note: as posted in your question above, the copied script doesn't mind skipped blank lines, but it will not run as posted in your reply. Be careful when copying text or code from forum posts if the code doesn't appear inside the CODE start and stop blocks. The forum software often inserts spaces between characters, and those spaces don't exist in the original scripts. For instance, the word "TemporalSoften" might be posted as "TemporalSo ften" with a space between the o and the f. You would get an error from Avisynth that says "TemporalSo" could not be found.

[zoink187]

Ok. Thanks. We are entering a realm of the unknown and complicated but I'm assuming that as long as I can duplicate this, the machine will do the work. Details to follow....


Sent from my iPhone using Tapatalk

[sanlyn]

Yipee, I just check and doom9 is finally running again. I say this because many functions are found either in doom9 posts or in links to doom9 discussion threads. Doom9 is for developers, really, although many of us mere mortals check the site for new versions or for details about using new filters. If you were in Google looking for QTGMC you'd see links to either the Doom9 main discussion thread for it, or to a download area on their server.

Most of the current "official" external plugins for Avisynth are listed at http://avisynth.nl/index.php/External_filters. Listed by category.
Some older plugins and even some discontinued stuff is listed at http://www.avisynth.nl/users/warpenterprises/ . Listed alphabetically.

Offhand, the first thing you might have trouble with if you've never used it is the blockbuster filter, QTGMC. Face it, few things work so well but you do need its support plugins. Those support files are actually stand-alone filters in their own right that you'll likely use elsewhere. So once you have the QTGMC package, you have something that's more than the sum of its parts. The official package (which includes everything you need for QTGMC) is at this doom9 page: http://forum.doom9.org/showthread.php?t=156028 . There are several download links, but the one you wants is Plugins Package. There's an Instructions link, but the instructions come with the package anyway. When you unzip the package download, look for text files with titles like "What to do with these files" or similar. For the time being you won't need the instructions; fortunately QTGMC has many clever default settings that set up lots of stuff for you. If you really want to get into "detail", the doom9 discussion thread is more than 80 web pages long.

You should not download Avisynth or VirtualDub plugin .zips and packages directly into those apps' plugin folders. Make subfolders for Avisynth plugins and VirtualDub plugins, and load the zips into their own subfolder. The reason for that is that zips often contain extra files you don't need, and some are even different versions of the same thing that cause errors if you try to run both at the same time. Unzip these packages into their own little cubby hole, then copy only the filters into the plugin folders. Avisynth only uses .dll, avsi, and .avs files. VirtualDub uses only .vdf's.

In the future you're likely to use more VirtualDub filters than are used here. But for many repairs when working with old VHS tapes, Avisynth is often the only way to go.

[zoink187]

Ok. So I gave it a shot but I'm having problems with getting the hqdering on the script. (What are the steps to doing so?). Also the masking I can't get on there either. I'm unzipping to the plug ins folder for other things but not those for some reason. There are others out there who have their own settings, it appears, for the hqdering. Is there a default setting? Also, am I creating a .dll or .avs file from those scripts? I'm totally a fish out of water here.


Sent from my iPhone using Tapatalk

[sanlyn]

Not sure what you mean by "unzipping to the plugins folder". Not all filters are supplied as zipped or 7z packages.

Avisynth by default is installed in Windows 7 into (usually) C:\Program Files (x86)\Avisynth 2.5. Inside that program folder, there is a subfolder called "plugins". If you have been downloading .zip files and unzipping them directly into the plugins folder, then you would collect unwanted files in your plugins folder. Post #57, above, explains how to avoid this.

Among the plugins you'll find in the Avisynth plugins folder are those whose names end with ".dll". Those files are found automatically when you run an Avisynth script. Another type of plugin will have a name with ".avsi" on the end. Those will also be found automatically when you run an Avisynth script. The other types of filters you'll find are plain".avs" file extensions. An .avs is not loaded automatically.

The .avs extension exists as a way of allowing users to design their own "filters" and procedures without having to write assembler or C++ compiled code. So if you want to include an .avs script inside your own script, there are three ways to do it:

1. Copy the text of the entire .avs script into your own script. This is not always a cool way of doing it, because an .avs script has to have certain provisions that will enable it to be included inside another avs script. Besides, some .avs plugins are hundreds of lines of code. That's a big headache to copy every time you want to use a filter that has 350 lines of coded text.

2. Use the "Import" command. The script that I posted earlier has two "Import" lines just below the top of the script. If you have HQDering.avs in your Avisynth plugins folder, then you can import it with this statement:

Import("C:\Program Files (x86)\Avisynth 2.5\plugins\HQdering.avs")

The path statement depends on where your plugins folder is located. Mine is located at "D:\Avisynth 2.5\plugins\".

3. Change the name of the file from "HQDering.avs" to "HQdering.avsi" so that it loads automatically. If you have 250 .avsi's in your plugins, you will sometimes have some rather slow-loading scripts. But it will work.

Except for modifying the path statements to locate your plugins and your source AVI file, the script that I posted earlier should run in VirtualDub -- assuming you have copied the plugins into Avisynth's plugins folder. You can give that copy of the script a name such as "script1.avs". Then open VirtualDub, click "File" -> "Open video file...", navigate to the location of your .avs script, click to select it, then click "Open".

To get more information about Avisynth, on your Win7 desktop click "START", then go to the "Programs" listing, find the program listing for "Avisynth 2.5", expand that program group, and click on "Avisynth documentation". Some of the web links of other choices in that program listing have recently changed since Avisynth 2.5 was released, but the link to the included documentation works because that documentation is in the "Docs" subfolder of your Avisynth 2.5 Windows program folder. Or go to http://avisynth.nl/index.php/Main_Page for a slightly different version of those docs.

[zoink187]

Ok. So after a few hours, I was only able to get 2/3 of those plugins in the folder. Things like contrast mask I was not able to load. I followed the steps and changed avs files to avsi. That worked for a couple of files. Turns out the QGtmc is a set of settings that need to be "made" into a .avsi file. It took an hour for that (following the directions) and I don't think I loaded it correctly but I can't get passed the first error message concerning the contrastmask. It would be great get be able to download and copy someone's already established 32 bit plugin folder.


Sent from my iPhone using Tapatalk