g-force

OSJ,

I have taken a look at those frames, and although they are showing some artifacts, they aren't as bad as the pics you are showing. There must be some differences between how the PAL reacts to the script compared to the NTSC version. So I have updated the script yet again, and now am not getting any artifacts on those frames. Could you check the new script (on page one) with your PAL version and report back your findings? As a side benefit, there is now even more noise reduction!

(fingers crossed)

-G

Oldschooljedi said:

g-force,

I've done some testencodings and I'm getting some errors. Here are some screenshots:

OSJ, that truely is ugly! Let me investigate and I'll get back to you. I doubt the changes you made are the culprit. I have an idea what may be causing the errors, and if that's it, I know the fix. I'll get back to you with a fix within the next couple days.

-G

iRantanplan said:

You don't need to burn a custom DVD, media player classic supports AVIsynth scripts for realtime playback.

Yes, but only if the script runs in realtime! ;)

-G

dark_jedi said:

So is this the final?

 I think so, but I can't promise that until this one is encoded and I move on to ESB.

-G

Okay, I've finally got an update worth reporting (see page one for most recent script). And here is the shot I was referring to.

Original GOUT resized:

G-Force v. 3.05:

-G

Thanks for the screen shots DJ! Something I have never been very good about.

I really do like the results of v. 2.03, but it seems that if you get rid of all the "crazy" amount of grain in some shots, there is a residual amount that is persistent from frame to frame that seems to move along with objects. It's mildly annoying, so I will be getting rid of even more grain in the upcoming version. If you want to see what I'm talking about, make some screen shots (before and after) of Ben sitting in his hut right after he sees the Leia message. If you think that's a lot of grain removal, just wait 'til v. 3.00! I still have a couple very minor bugs to work out, and I'm going to need to upgrade the RAM in my PC to get it to encode in a decent amount of time. Stay tuned!

-G

Oldschooljedi said:

g-force,

would you say that the script version 2.03 is the final script or are there some more improvements since this script?

No, unfortunately this is not the final script. I'm working on an even better denoiser using a mo-comp'd median function with a larger temporal radius. Expect an update in the next week or so.

-G

gltaylor74 said:

g-force said:

Okay, I've finally got some good degraining that I'm extremely happy with. Check out the new script!

 

-G

 

 Thanks for all of your work on this g-force.  Are there any new avs filters needed for the new script?

There shouldn't be any new filters needed over the last posted version.

-G

Okay, I've finally got some good degraining that I'm extremely happy with. Check out the new script!

-G

dark_jedi said:

 

So have you actually encoded all these for yourself yet?

 No, not yet. I did have a complete encoding of a previous version of the script, but the encoding settings were not really great, so I took the opportunity to make additional changes to the script. I'm still not completely happy with the left over grain, but I just haven't found a resonably fast and artifact free way to get rid of it yet. (BTW, my previous script used VagueDenoiser, and that has some issues, so I removed it)

-G

Major update to the script today! This is the best so far. ;)

-G

-1,

Honestly, there is not much of this script that I could imagine using on a 35mm transfer of the film. Here is why:

1. Color. You are going to have an RGB signal to work with, which is much easier than Luma and Chroma to adjust.

2. Global motion stabilization: You are going to have the frame edges to work from for this, something that is lost on the DVD, and there will be much more accurate ways of stabilizing WITH the frame edges as a reference.

3. Local motion stabilization: this is an effect of film warp, and how the MPEG encoder handles this. You may very well have some film warp, but you won't have the MPEG effects on the film warp to worry about, so a more gentle local motion stabilization should be used if any is needed at all.

4. Jaggies - you won't have any (hopefully)

5. Sharpening - You shouldn't need this if the capture is decent

6. Subtitles - No need

7. Degrain - Okay, there's the exception to all of this. You are going to want to degrain. Admittedly, there are a lot better algorithms than what I'm using, but my script trys to do too much stuff so I've really had to compromize here. I've tried to get the most bang for the buck on this, but if you want the best degrainer, use TemporalDegrain(). Study that, as my script borrows heavily from it. It's really the best, and since you won't need to do much else, it should run at an acceptable speed.

-G

negative1 said:

 

draw a fixed (slightly cropped) box around the original to see how much the variation is ..

 ooh!, that's a good idea. Should work!

-G

negative1 said:

i tried to write a script to compare the two videos, vertically,

but couldn't get it to work.......(i actually put a reduceBy2 in front, and that didn't work either)..

#StackVertical("M:\data\movie\dvd\star wars ep #\4-gout\VTS_03_1.VOB","M:\data\movie\dvd\star wars ep 4-gout\gout.mpg" )

 

then i tried to overlay the clips, and i kept getting an error back from loading the .VOB

#clip1 = DirectShowSource("M:\data\movie\dvd\star wars ep 4-gout\VTS_03_1.VOB")
#clip2 = DirectShowSource("M:\data\movie\dvd\star wars ep 4-gout\gout.mpg")
# Overlay(clip1, clip2, mode="blend", opacity=0.5)

 

 -1,

you need to run the .VOB and the .mpg through DGDecode first, and load the resulting .d2v file with Mpeg2Source instead of DirectShowSource.

And you have to make sure they are the same size.

clip1 = Mpeg2Source("X:\...\...\xxx.d2v")

clip2 = Mpeg2Source("X:\...\...\yyy.d2v")

StackVertical (clip1,clip2).ReduceBy2()

The Overlay option won't work very well, because if you get them lined up correctly, it will look like just an average of both.

BTW: the results are indeed supposed to be subtle, and reducing both by 2 just makes the differences less noticable. Watch the original, note how much it jiggles, and then watch the output of the script and see how it jiggles much less, is sharper, better color, better contrast, less jaggies, etc. Please note that the script doesn't "remove" any of these problems, just lessens them without (hopefully) adding artifacts.

-G

Big update to the script today. I was having a hard time accepting the residual grain left over after my script, as it seemed to be too coherent from frame to frame, making it look like you were watching through a cheesecloth. I was toying around with going back to the FFT3DFilter that I had used in the past, but my PC is so slow that it would have taken 2 weeks to encode and there was a reason I didn't want to use it in the first place (too much banding). I have found an equally great spatial filter that is way faster, and has less banding! So now the script does even more degraining.

Back to encoding...

-G

I have the NTSC version it that would help. PM me if interested.

-G

I have the NTSC version it that would help. PM me if interested.

-G

Davis said:

 

Yes!  This was the problem- "force film" wasn't checked in DGIndex.  So it was DGIndex.

It looks great!  I can't wait until you finish tweaking the script completely, so that I can burn a copy for myself:)

-Davis

P.S. Will you be doing different scripts for "Empire" and "Jedi"? 

 Oh good! I'm glad you figured it out. I'm really close to having a new version. Some preliminary tests got rid of the things that were annoying me. Expect an update soon.

I do plan on doing different scripts for Empire and Jedi. I expect them to be largely the same except for the cropping and the subtitles. We'll see though. My hard drive isn't large enough to tackle all of them at once, so I need to finish ANH first.

-G

I have a copy of the NTSC DVD9 that I got from a generous board member. PM me if you need a copy PIF'd to you.

-G

Oldschooljedi said:

I watched ESB last night filtered trough your script and I have to say: Man what a good work, g-force!!! Thanks for that.

thanks OSJ!

I finally got around to encoding all of ANH and watched it on my HD tv over the weekend. I'm still not 100% satisfied with the results. :(

So, I will keep tweaking the script!

-G

Arnie.d said:

 

Darth Mallwalker said:

Regarding haloing, do you suppose a cable impedance mismatch could be affecting it?

Didn't you say you're using a BNC/RCA adaptor? Would that be an RCA cable with BNC adaptor on the LD end?

I wonder if you'd get any different results using a true 75-Ohm BNC cable with the adaptor on the PC end?

Can you explain how that can possibly make any difference? 

 

Arnie.d,

Im not a big advocate of the whole "the cable makes all the difference" that is so prevalent in the Audiophile community. But in this case it really does. At higher frequencies, cables stop acting like "wires" and more like "waveguides". So if you have some high frequency component of the signal that is (due to impedance mismatch like DM said) bouncing back and fourth between the mismatched impedance ends, you will set up standing waves and have the same signal arriving multiple times.

Give it a shot. Can't hurt right? Might even want to clean off some of the corrosion on the jack with a metal polish of some sort.

-G

All good ideas Darth Mallwalker!

-G

Whew! This makes more sense than my theory. Thanks Darth Mallwalker.

-G

So, I’ve been looking at Arnie.d’s captures of the Japanese laserdiscs, and comparing them to the GOUT. Turns out that the opening shot right after the pan down from the opening crawl has a completely different starfield. Doing some further investigation, It appears that at least the starfield and the planet in the distance on the GOUT are the same as the SE!

This makes me wonder, were elements from the SE used to re-create that sequence for the GOUT? Is it possible that even the opening crawl of the GOUT might not be original, and possibly computer generated.

Thoughts?

Here are some random thoughts about your rip Arnie.d:

That's a lot of noise (but I guess we had been warned of this by Laserman) on those laserdiscs. This makes it difficult to turn up the saturation, contrast and sharpness without making this thing nearly unwatchable. I tried to do some noise removal in my script, but still not enough in my opinion.

There is some sort of ringing or haloing most noticable on straight vertical objects. My guess is that this is the LD player. These become even more noticable with any sort of sharpening that is added.

It's nice to see SW stable and DVNR smear free!

My Levels, saturation and Hue are just what I could do quickly. You may have more luck playing around with these in RGB space (of which I have little experience)

I'm still excited to see how different the 3 captures are in terms of noise. might be a little more that could be removed.

I'm going to start another thread on this, but the opening sequence (Tantive and Destroyer) stars and planet are totally different from the GOUT. It appears that the SE was used for the GOUT. Did we already know this?

Keep us up to date on any progress you make!

-G