Beginning to experiment with Avisynth - No clue what to do

[BasharOfTheAges]

Hm... Alright. I'll make sure in the future I don't rely on Avisynth for everything and filter every source I have. Although on my monitor, the noise and random blocks in the backgrounds were very noticeable... Thanks for bringing that to my attention.

This may sound like a dumb question, but bear with me. Do you see the same problems on the PNG as you did in (i'm assuming) virtual dub? If not, are you sure vdub is set to display the correct color depth? (I think it isn't by default)

[bloppyblue]

How does it look if you bicubicresize(1280x720,0.333,0.333) and don't filter at all?

Unfortunately, it still looks the same, just with a smaller resolution.

Oh, I see what error you are getting... just type:

Code: Select all

TTempSmooth()

That's it. All the defaults will load automatically. Alternatively, you could substitute the ? with the word: last
That way, you are at least offering TTempSmooth a clip to use for comparison.

Hm... I did both of those and, although I didn't get an error, nothing happened to the footage besides the frames shifting over.

hmm... are you running a 64-bit OS? You might need to copy it into your windows SysWOW64 folder [whoever named that directory is awesome ]

Yeah, I'm running on Vista 64-bit. I moved the libblahblah.dll over to SysWOW64 and retried both methods of TTempSmooth, and still, nothing happened

Thanks for all that help Phantasmagoriat. Your username is also very fun to type.

No problem some people call me phan 'cuz it's easier... or some variation thereof... it's an old username I think I'm outgrowing... but really I don't care as long as I know you're talking to me

http://www.lagom.nl/lcd-test/

Before going on with the tests, make sure your monitor is properly calibrated... it might be showing more issues than the ones that are really there.

Thanks. I don't think my monitor is extremely off.

This may sound like a dumb question, but bear with me. Do you see the same problems on the PNG as you did in (i'm assuming) virtual dub? If not, are you sure vdub is set to display the correct color depth? (I think it isn't by default)

I'm using AvsP to do the scripting and I captured the screenshots from there as well... And yeah, the display video has the same blockiness. I don't think it's a problem with preview.

I really wish these forums had an edit option.

Should I just skip this filtering process? Is it going to be a big deal if I want to enter this kind of footage to a con?

[Cannonaire]

In my opinion your footage is already pretty filtered as it is. Filtering more probably won't help much if at all, but also when i first saw the screenshots I didn't see the blockiness you were talking about (although I see it now). It's my guess that it will only be really visible on LCDs, and more so on inaccurately calibrated LCD displays. At a convention, it would likely be very difficult to see that specific video issue on the projected image. But that's just my opinion...

[Scintilla]

I haven't noticed TTempSmooth to produce a very visible effect at default settings, so don't be quick to assume it's not doing anything -- try encoding a clip without it and then again with it, and compare the file sizes.

As for conventions: unless your source has obvious problems like bad macroblocking, rainbows, dot crawl, etc., they very likely will not care about filtering. And K-ON! shouldn't have any of these, being of such recent vintage.

(A big part of the reason you would want to do spatial/temporal smoothing is to be able to reduce the file size of your finished encode while still getting it to look decent. But, with conventions, reducing the file size is not usually a concern.)

[bloppyblue]

In my opinion your footage is already pretty filtered as it is. Filtering more probably won't help much if at all, but also when i first saw the screenshots I didn't see the blockiness you were talking about (although I see it now). It's my guess that it will only be really visible on LCDs, and more so on inaccurately calibrated LCD displays. At a convention, it would likely be very difficult to see that specific video issue on the projected image. But that's just my opinion...

I haven't noticed TTempSmooth to produce a very visible effect at default settings, so don't be quick to assume it's not doing anything -- try encoding a clip without it and then again with it, and compare the file sizes.

As for conventions: unless your source has obvious problems like bad macroblocking, rainbows, dot crawl, etc., they very likely will not care about filtering. And K-ON! shouldn't have any of these, being of such recent vintage.

(A big part of the reason you would want to do spatial/temporal smoothing is to be able to reduce the file size of your finished encode while still getting it to look decent. But, with conventions, reducing the file size is not usually a concern.)

Thanks for the responses. I'll just leave the footage as is then. I'll also go and play around with TTempSmooth some more once I get the hang of it!

Thanks, again!

[Mister Hatt]

Also use the BD itself so you don't need to filter ANYTHING besides for spline36resize(1280,720).gradfunkmirror(). The video is not 1080p but I guess you could leave it so if you felt like it. If you choose not to resize, can probably get away with opening the m2ts file directly in your NLE and avoid avisynth altogether. It would be faster too.