g-force

gltaylor74 said:

Thanks G-force.  Does this script offer any improvements for a New Hope, or is it just Empire and Jedi that have improvement through the script. 

 aside from a slight increase in top cropping for ANH, it should be the same. There seems to be some bad lines at the top and bottom of the film that I have always debated on cutting off or not. These are even worse on Empire and ROTJ, so I decided that they should all go.

-G

New version of the script is on the first page. Now with support for ESB and ROTJ.

-G

INv8r_ZIM said:

 It looks like it's in whatever is being referenced in the local stabilization part of the script.  If I comment out all of that section (apart from the Source, Sigma, and Filt lines) the problem is gone. 

INv8r,

try re-running the script with just the filt line replaced with "filt=source". this will eliminate the fft filter as a possible culprit. The only other thing I can think of is a different version of RemoveGrain, or a different version of Avisynth.

-G

INv8r_ZIM said:

Weeellllll....I've just checked it out again, and it's not apparent in the GOUT.  I say apparent, as I keep almost thinking I'm seeing it, but can't quite decide if it's there or not.  I dropped the demuxed raw GOUT mpeg into Virtualdub, and checked out the shots I posted; no streaks evident.  Next, I dropped in the AVS script (v3.)17), and there they are again, same places.  Weird.  I'll post pics later.

INv8r,

I'm guessing that if you're not seeing it in the raw GOUT, and you ARE seeing it in the Avisynth script previous to encoding, it must be an issue with Avisynth. I haven't been keeping up to date on the latest Avisynth version and plugin versions, so maybe one of those is the culprit. I know there is a new version of MVTools out, so you may try going back to an older rev, or even an older Avisynth.

-G

Well, I finally had some time to look into this. I can't reproduce the lines that I see in your screen caps. At this point I would suggest looking at that frame processed throught the script, but previous to encoding and let me know the results so that we can determine if it's a Avisynth plugin issue or encoder related.

INv8r's problem got me to check this out with ESB finally, and I did notice that the final crop values need to be modified slightly. I will update the script once I get the correct values (and subtitles!) for ROTJ in there as well.

-G

I can see what you are talking about in the 4th and the last one. I'm gonna have to get back to you on this issue.

-G

INv8r_ZIM said:

Has anyone noticed an occasional diagonal (high left to lower right) streaking, particularly during visually busy scenes (like the lost in the snow stuff, or the duel in the carbon-freeze chamber)?

Could you post a screen capture of this?

thanks,

-G

dark_jedi said:

I am still following this thread G-Force,in about 2 weeks I am going to switch everything over to my new PC and then give this encoding a try,the only reason I have been silent is because I was waiting to do the change,I am going to now be using an Intel Quad Core processor at 3.0GHz(I will probably OC ofcourse),with 8 GB's ram,and dual 500 GB hard drives,and dual GeForce 9800 GTX+ Video cards,along with some serious cooling ofcourse,I figured with all the encoding and edits I do I need a serious machine now,plus gearin up for Diablo III LOL.

 

so after ANH is done,I will be all over you for help on ESB and ROTJ LOL

I will keep you posted

DJ

OMG! I can't wait. I would really love to help. Maybe in return for some encodes?!?!

-G

Someday. I was working on them for a while, but realized I still had too much to do with ANH first. If I remember correctly, I had worked out the subtitles, but the start and stop frames were not sorted yet.

-G

resonator said:

I'd do it myself, but I'm booked up for work for weeks, but anyway, just to throw in the idea - As for motion smear, there are a lot of unchanged shots that could be taken directly of the 2004 SE DVDs. How about writing a script to color-correct and replace most of those shots? Anybody who has the GOUT on Disc 2 has the SE on Disc 1 as well. That could easily be a team effort directly here on the board.

I think that's a great idea, and is actually something I've been thinking about for some time. For me, it's going to have to wait until I get a faster PC and larger hard drive, but someday...

-G

I've got some updates to the script that I have been holding off posting until they were tested. Testing turned out great. They include better anti-aliasing, and some improvements that greatly help the last issue that OSJ had. As usual, the updated script is on the first page of this thread.

-G

negative1 said:

yes, i had to use some deinterlacing here and there in the final version, but it still looks good to me

 hmm, that doesn't sound right... I don't understand what would need deinterlacing.

negative1 said:

now i'll work on upscaling to 720p and 1080p with the solo21 script, and some more modifications..

hmm, that would add a lot of "lossy" and redundant steps. That's a lot of resizes and potential motion-compensation errors for something that that already doesn't even have enough detail for DVD quality.

-G

Oldschooljedi said:

Here is another artifact, maybe g-force could help:

 

Here is the short (avi) sampleclip.

G-force, would it be reasonable, to change the script for every artifact, I mean when the script is changed for this scene, wouldn't we get some artifacts at other scenes???

 

OSJ, So far, I have been very careful to make sure that no new artifacts are introduced when I fix one. This particular shot looks very difficult, due to lack of information for the motion compensation to lock on to. If you post the original, I'll take a look at it.

-G

Thanks OSJ. Fix posted.

-G

OSJ,

would you be willing to post  the unprocessed Vader clip from your pic above?

thanks,

-G

It wouldn't be he encoder. Try adding "trim(4500,4500)" to the end of the script, resave the script, and drop the icon for the script file into an open Media Player window. That will give you an idea if the script is functioning.

-G

dark_jedi said:

So are these script fixes just for the PAL version or are they overall improvements for the PAL and NTSC?

everytime I get around to encoding LOL there is a new version.

I will be doing an NTSC verison.

Alright dark_jedi, I think it is safe to say this version (3.09) is stable. I can't promise there won't be improvements down the road at some point, but this is the version I'm going to burn.

-G

OSJ, that was very helpful! Turns out that the PAL version has no built in overscan (the NTSC version has black on both sides of the fame, PAL doesn't) and MVDegrain likes black borders. Check out the new script and let me know how it works.

-G

Oldschooljedi said:

Here I posted a short clip, because I don't know how to describe it exactly.

I see the problems that you are referring to, but they are not showing up when running the script on my NTSC version. OSJ, could you post the original of the clip you just posted?

thanks,

-G

dark_jedi said:

So are these script fixes just for the PAL version or are they overall improvements for the PAL and NTSC?

 

everytime I get around to encoding LOL there is a new version.

 

I will be doing an NTSC verison.

Yeah, I'm always trying to improve the NTSC version, but OSJ is helping me sort some bugs with the PAL version. I would hold off until all the bugs are worked out with both versions because there may be some bugs I'm not seeing in the NTSC that are more apparent in the PAL.

-G

Well, I'm glad we're getting closer. I'll take a look at the clip you posted when I get home tonight.

Thanks for reporting back!

-G

Okay, I think I've figured out a fix. OSJ, please try the new script on page one and let me know if that works for you.

-G

Moth3r said: 

They did not deinterlace (otherwise the framerate would be 29.97fps). Instead, they carried out IVTC, which is of course the correct way to do it.

Oops, your right. Got my terms mixed up.

-G
 

Oldschooljedi said:

g-force,

in your current script you write

"Function Contra(clip denoised, clip orig)
{# re-write of Didée's contra sharpening routine from TemporalDegrain.avs"

So do I need the hqdn3d.dll-plugin as required filter for this as described here?

 

 

No, no need for that plugin.

I have a new theory as to what is happening. I think you may have a newer version of MVTools than I have. And that isn't necesarily a bad thing. BUT, here's the problem:

I encoded my newest version of the code and everything looks awesome EXCEPT when Luke lights up his lightsaber in Obi's hut. There is an annoying blur around the lightsaber. So I did some experimenting, and found that if I did a more accurate (but slower) motion estimation, sure enough, that blurring was much less. But now, with that better motion estimation, the motion vectors are locking on to the DVNR smearing that is present. The most noticable problem area I have seen so far is the Greedo scene. On the original, one can faintly make out a ghost of Han when the scene switchs to Greedo. So now when I make the motion estimation better, the algorithm locks on to that ghost and re-inforces it, making it even worse. And this looks very similar to the screen shots of the scene changes that OSJ has posted.

Bottom line is, there may not be a way to have both good denoising and little artifacting due to the DVNR smearing. I mean, I'll keep working on it, but things are looking not so good at the moment.

This GOUT is getting worse all the time.

-G

skyjedi2005 said:

what do you mean?

Both the Ntsc and pal releases of the gout were taken from a 480i D2 master tape.

Laserdiiscs are interlaced.

Just becuase they flagged the dvd as fake progressive does not make it a progressive scan transfer.

Any more than a fake resizing to anamorphic would make it an anamorphic  release.

They de-interlaced before mastering the DVD. And they did a terrible job at that, as witnessed by the poor vertical resolution and jaggies compared to the laserdiscs.

-G