logo Sign In

Info: GOUT Anti-aliasing — Page 2

Author
Time
Exactly.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Well AAA() does nothing for those lines - and it does introduce a slight blur/loss of detail into the image.

I've now found the readme for EEDI2(), so I'm going to try tweaking the parameters DE mentioned. The danger is that if you tweak it to detect weaker/shallower edges, it may give you unwanted artefacts elsewhere.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
I did give strange artifacts for me in Leia's cell at the ceiling when Vader comes in.
Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.
Author
Time
Those lines look completely separated - in such a case you'll be hard pushed to find a plugin that will join 'em all up - without causing horrible artefacts elsewhere as well.

DE
Author
Time
This is amazing work! Can't wait to see what you settle on, Arnie.d. My greedy little hands are itching to hold an anamorphic version of GOUT SW! It makes me carazzy!
Author
Time
Originally posted by: Darth Editous
Those lines look completely separated - in such a case you'll be hard pushed to find a plugin that will join 'em all up - without causing horrible artefacts elsewhere as well.

DE


I agree, that doesn't even look like a line anymore. You might want to try NNEDI (the recently released successor to EEDI2), but I doubt it will do much good.
Author
Time
I'd given up on those jaggies. I'm just going to stick to the improvement offered by a simple EEDI2().

I also tried DeGrainMedian in conjunction with MVDegrain2. It performed slightly better at removing grain but unfortunately removed detail out of motion/panning scenes (which are already in poor shape after being trashed by the '90s DVNR algorithms).

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Just a word of encouragement: the work here is AWESOME! Especially since the source is letterboxed. Jaggies or no, your work on this is great.
Author
Time
Originally posted by: Moth3r
I'd given up on those jaggies. I'm just going to stick to the improvement offered by a simple EEDI2().

I also tried DeGrainMedian in conjunction with MVDegrain2. It performed slightly better at removing grain but unfortunately removed detail out of motion/panning scenes (which are already in poor shape after being trashed by the '90s DVNR algorithms).

Yeah, those jaggies are probably well beyond any attempt at automatic fixing. In any case, if you're going to use EEDI2, I'd strongly recommend you in the way I mentioned earlier:

EEDI2().TurnRight().EEDI2().TurnLeft()


It stands to reason that the above line should help in most cases as it processes along both the horizontal and vertical axis, therefore jagged lines that are too steep for the first part should be easily handled by the second one.
Author
Time
Darth Editous/Arnie.d discussed that on page 1 and it was concluded that the turnright/turnleft arrangement was not required. I haven't seen anything in my tests to make me disagree.

I've also been testing a gamma adjustment to the luminance levels and an increase in the colour saturation; it looks better on my PC's monitor (greys are blacker and pinks are redder) but I've yet to view on my main TV.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
It stands to reason that the above line should help in most cases as it processes along both the horizontal and vertical axis, therefore jagged lines that are too steep for the first part should be easily handled by the second one.


There's nothing "missing" in a vertical sense, so that won't work. It's not that the jagged lines are too steep, and wouldn't be after rotation, but that they're the wrong kind of jagged lines

DE
Author
Time
Moth3r,

I tried to make my own transfer of the movie like you described it here, because this looks very, very good. But I get always some errors and I'm not sure, if I did use the right avisynth-plugins. Some of them were not easy to find for download and I'm not sure, if they are the right plugins, that I downloaded. So, would you be willing to zip your avisynth-plugins used for this and post them maybe to rapidshare (for example) so that I could try it again?

This would be nice.

Greetings,

oldschooljedi.
Author
Time
I could, but it's not that simple. Some dll files are optimized for the capabilities of your CPU - I have an Athlon 64 X2 dual-core, so I try to get the multi-threaded or SSE3 optimized versions where available (but use SSE2 version of RemoveGrain because SSE3 causes crashes).

What's your CPU?

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Oh, I didn't know that there are so several dll's avaiable. I have an older PC with an Intel Petium 4 with 2,66 MHz.
Author
Time
Arnie.d,

could you post the "dustv5.dll"?

I've been searching for this but I didn't find a downloadlink.

Author
Time
Thank you, now I have all the .dll's that are needed.

I've been trying to do my encodings, but now I always get this error:

import: couldn't open "C:\Program Files\AviSynth 2.5\plugins\avsfilter.vdf.avs"



In my plugin-directory is no avsfilter.vdf.avs, there is only a "avsfilter.vdf"

Do you have any ideas?
Author
Time
Vdf files normally live in the VirtualDub plugins folder. Try moving this file out of your AviSynth plugins folder.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
So I did eventually finish my version of an anti-aliased GOUT (I posted screenshots at fanedits.com).

In the end, after discussions in the GOUT Film Grain thread, I only used a very subtle degrainer - just enough to "take the edge off" the grain present in the GOUT video.

There are still issues with near-horizontal edges and loss of vertical detail, as well as the smearing and trails from the DVNR process. These defects can only be fixed by returning to pre-THX laserdisc sources, or a colour-corrected and "de-specialed" SE/DVD/HDTV source.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Moth3r,

Would you say your anti-alised version is an improvement (in terms of video quality) over your PAL laserdisc transfer?

You know of the rebellion against the Empire?

Author
Time
Good question.

This version is my disc of choice ATM. It doesn't have the missing screenwipe, line drops or halos that my previous LD capture had. The adjusted colour also seems to be much more "cinematic". And of course the audio is at the correct level with no glitches.

However, I cannot watch this without noticing the issues mentioned in my above post. (I guess I'm just very picky.) Maybe a new laserdisc transfer, using the knowledge I've gained since I did the original, would fare better.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Moth3r,

the improvement of the picture quality is incedible.

Could you post your avisynth-script, that you were using at last for your anti-aliased version?

Greetings,

Oldschooljedi
Author
Time
Here's the final script I used. I've reformatted and added comments to make it easier to read.
# Crop and upsize using anti-aliasing
# Use less aggressive settings for the probe droid
# interrogation scene to avoid artefacts

a=mpeg2source("e:\project.d2v").crop(0,102,0,-104).eedi2().trim(0,58642)
b=mpeg2source("e:\project.d2v").crop(0,102,0,-104).eedi2(maxd=15,nt=8).trim(58643,-351)
c=mpeg2source("e:\project.d2v").crop(0,102,0,-104).eedi2().trim(58994,0)
source=a+b+c

# Adjust the luma (Y) levels
# with a little function I found at Doom9. A modification of Didée's YLevels,
# this one gives a lower brightness and increased contrast
# without excessive "crunching" or "clipping"

source.FlimsYLevels(10)

# Subtle grain filtering for hot pixel removal

DeGrainMedian(limitY=5,limitUV=5,mode=3)

# Adjust colour, more saturation, less pink

tweak(sat=1.15, hue=-6.25)

# Sharpen and resize to NTSC DVD resolution

limitedsharpenfaster(dest_x=720, dest_y=366)
addborders(0,57,0,57)

# Add subtitles for Greedo scene
# Approximate match for theatrical font and position,
# compressed horizontally to keep text within overscan "safe area"
# Note you need AviSynth 2.58 Alpha for the font_width parameter

subtitle ("Going somewhere, Solo?", \
-1,370,70663,70698, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("It’s too late. You should have paid him when you had the chance.", \
-1,370,70825,70931, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("Jabba’s put a price on your head so large every\n" + \
"bounty hunter in the galaxy will be looking for you...", \
85,330,70940,71088, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5,lsp=1)
subtitle ("I’m lucky I found you first.", \
-1,370,71098,71137, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("If you give it to me, I might forget I found you.", \
-1,370,71203,71282, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("Jabba’s through with you.", \
-1,370,71365,71406, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("He has no time for smugglers...", \
-1,370,71435,71489, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("...who drop their shipments at the first sign of an Imperial cruiser.", \
-1,370,71498,71595, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("You can tell that to Jabba. He may only take your ship.", \
-1,370,71656,71748, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("That’s the idea.", \
-1,370,71806,71833, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)
subtitle ("I’ve been looking forward to this for a long time.", \
-1,370,71843,71931, \
"Franklin Gothic Demi Cond",36,$ffffff,font_width=10.5)

function FlimsYlevels(clip clp, float amp)
{ wicked="x x 16 - 34,85493 / sin "+string(amp)+" * -"
return( clp.mt_lut(Yexpr = wicked) )
}

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
It works really good on my test-encodings (I'm a real dummy in that).

Everything worked fine, as long as I encode without this line: "source.FlimsYLevels(10)"

When I do the encodings with this line in the avisynth-script, I get always this error: there is no function named "FilmsYLevels".
I searched in the doom9 forum and found this link here: Link
I installed the MaskTools-v1.5.5.dll but maybe I need another avisynth-plugin???

Any ideas?
Author
Time
Originally posted by: Oldschooljedi
It works really good on my test-encodings (I'm a real dummy in that).

Everything worked fine, as long as I encode without this line: "source.FlimsYLevels(10)"

Any ideas?

I'm guessing it's a typo... FilmsYLevels is probably what it should be.