VirtualDubMod constantly rendering and won't stop

[Mister Hatt]

Best advice anyone can give you for cleaning your footage: Don't clean your footage, it doesn't need it and you are blind.

[Phantasmagoriat]

I am referencing the new guides.

The old guides did not have AvsP. Basically, it does what vdub does but with a different interface.
For useful avisynth scripts, there are simply too many to do a comprehensive guide.
You will see this just by doing a google search. But here are some relevant lists:

• http://avisynth.org/mediawiki/Internal_filters
  http://avisynth.org/mediawiki/External_filters
  http://avisynth.org/warpenterprises/
  http://www.aquilinestudios.org/avsfilters/

maybe even check youtube for an avisynth video tutorial
to install any of these functions simply download, unzip (if needed), and put into your avisynth plugins folder:

• C:\Program Files\AviSynth 2.5\plugins

This is also the place where you can see which plugins (.dll's and .avsi's) you already have.
Some plugins won't be there because they are internal to avisynth (see internal filters above)
And I would echo what Mister Hatt said about filtering:
You don't need to filter much these days... on newer footage anyways (maybe some limitedsharpen at desired settings)
But older footage might need some.

A simple script for deinterlacing would look like this:

Code: Select all

mpeg2source("path\your_index_file.d2v", cpu=6)
tfm()
tdecimate()

but you would have to read the author's documentation for these filters to specify extra parameters, like:

Code: Select all

tfm(order=-1, mode=0, pp=2)  # just as an example

If I'm not mistaken, the AMVapp tests don't work in Vista.
I'm not even sure if they are part of the App anymore since you have to download everything separately anyway.


@Zarxrax: Wasn't there a Video Tutorial for avisynth at some point? or was that just dgindex?

@Mister Hatt: That's useful information to know, but I haven't had any problems
with the programs I'm using, or need any extra features, so I'm pretty content.
But I may have to check out Mpeg2Dec3.

[Mister Hatt]

Your script for "deinterlacing" is incorrect. Firstly, multiple plugins provide mpeg2source, so you need a specifier in all example scripts. in the case of DGDecode, it would be DGDecode_Mpeg2Source(), and the cpu argument is unnecessary. Secondly, that script is actually for inverse telecine, not deinterlacing. TFM is Tritical's Field Matcher and TDecimate is Tritical's Decimate. Field matching calculates which frames match with which and then binds them via hints to an external deinterlacer with correct fieldswhile decimating removes the resulting duplicate. Actual deinterlacing is done purely with the same frame alternate field. A better string and probably the best IVTC you can do without using YATTA would be TFM(mode=1,pp=5,slow=2,micmatching=2,clip2=TDeint(mode=2,type=3)).TDecimate()

I love semantics. I do intend at some stage to finish making the video tutorials for ripping and filtering and cleaning that I promised mirko.

[Gaelstrom]

I do appreciate all your assistance in attempting to clarify this stuff. At this point, I get the feeling I won't be able to figure out anymore without trying it once again, even if I dread it, or a video tutorial -_- I have until May 1st to finish the project(s) I'm working on, so hopefully I have enough time. For the time being I'll use my other methods, annoying thought they may be. Sadly the most time consuming aspect is FINDING the footage. This is the last time I attempt to do anything with One Piece unless I have a friggan team.

[Phantasmagoriat]

lol @ Mister Hatt for calling me out on that one.
I wasn't even going to attempt explaining the difference between deinterlacing and IVTC
since most amv'ers treat them synonymously. Just trying to keep it simple.
Although, why is the cpu argument unnecessary?
I've found it to be a very quick and easy way to avoid macroblocks, and crappy quality from some sources...

oh, and a Video Tutorial would be awesome! *pokes*

@ Gaelstrom: There is a way of speeding up the process by editing with proxies in your editor;
aka the Bait and Switch technique... or whatever you want to call it. It is outlined here:
http://www.animemusicvideos.org/guides/ ... meth3.html
Keep in mind it involves a very good grasp of avisynth, so just do one hurdle at a time,
and maybe you'll give it a try at some point.

[mirkosp]

Well, cpu=6 is way too much. Generally speaking cpu=4 can be over necessary too, actually. It's probably best to keep the cpu parameter at 2 tops if really need be, or better yet just use cpu=0 and leave the deblocking to better filters, like for example Deblock_QED. That is, if the source needs deblocking to begin with.

[Qyot27]

Firstly, multiple plugins provide mpeg2source, so you need a specifier in all example scripts.

You don't if you only use DGDecode. It's pretty fruitless to assume that everyone still keeps the 7 years outdated Mpeg2Dec3 around anyway. It's not even included in AMVapp anymore either. So they'd have to be getting it from somewhere else, putting consideration of such in their hands only.

[Phantasmagoriat]

yeah, I guess cpu=6 might be a bit high.
Yet, I always valued the cpu parameter because it uses extra information from the .d2v index, which would make it better for post-production than downstream filters. I can't remember where I heard that though. Does it even matter with newer filters? I've never used Deblock_QED.

[mirkosp]

I find Deblock_QED to be really good when I need to deblock, but I guess you should compare by yourself the results of cpu=X vs deblock_qed or other filters, since some things are just about personal preference in the end. Some people prefer a sharper image with a few blocks here and there, others prefer a slightly blurrier one in favor of a lack of blocks.

[Mister Hatt]

Firstly, multiple plugins provide mpeg2source, so you need a specifier in all example scripts.

You don't if you only use DGDecode. It's pretty fruitless to assume that everyone still keeps the 7 years outdated Mpeg2Dec3 around anyway. It's not even included in AMVapp anymore either. So they'd have to be getting it from somewhere else, putting consideration of such in their hands only.

How about the updated-in-January-2010 version of mpeg2dec3? There are 4 or 5 forks of the original mpeg2dec3 that I can think of that are still actively used and developed, moreso than DGIndex which has been dropped by it's developer. There are even active forks of mpeg2dec2.

@Phantasmagoriat: leave the CPU argument on default, if your source needs filtering there are better ways to do it, and most of the time it really doesn't.