g-force

Thank you Moth3r for showing us what COULD be done with the GOUT.

-G

What happened? Everyone has real pics. What did I miss?

-G

Hey msycamore,

just curious how you ended up making your subs the right size, but still have them not get cropped off the edge of the screen.

Makes me a bit nervous, but I have to say, if you managed to pull that off, they look really good from what I've seen!

-G

I'm at work right now, so I can't view this on a known good machine, but is anyone else seeing aliasing on the blurred subs? In particular, on 'y's?

might need a reference (unblurred subs) clip to compare.

-G

dark_jedi said:

g-force said:

Hmm. Don't forget that when you mess with the brightness/contrast/gamma, all of the mattes get really annoying. Took me months to get those right.

-G

What scene would you say this would show the most, because I certainly do NOT want to mess up any of the hard work you put into this.

You would have to check all of the space scenes for sure. I shot for a compromise between not seeing any of them at all on a properly calibrated TV, and only barely seeing a few of them on an overly bright screen like most people have.

-G

Hmm. Don't forget that when you mess with the brightness/contrast/gamma, all of the mattes get really annoying. Took me months to get those right.

-G

dark_jedi said:

Damn, I save everything, especially all the older g-force scripts, but now I can't find them, could someone post the old ones so I can see these settings and try them out?

Thanks, in the meantime I will keep searching.

all of my published scripts used sat=1.08 previous to removing is completely (I'm still not sure why it was removed).

-G

Moth3r said:

g-force said:

 -1

Everyone realizes that the script already has an 8% bump in saturation, right? I had a script at one point that did a 14% bump in saturation, and that was great for a few scenes, but looked like the SE DVD for alot of the scenes. (Lobster skin, neon yoda, electric R2...) The major problem with the GOUT is not the color, but the brightness/contrast, which the script also adresses.

-G

I can see the levels and hue tweaks, but not the saturation boost.

A saturation tweak was definitely in an earlier version but it looks like you took it out?

You are right! I took it out completely. Don't remember why, but I'm changing my answer. The script to afford to have a little saturation boost!

-G

ahope said:

Murry Sparkles said:

Jetrell Fo said:

Sluggo said:

Doctor M said:

If the right balance can be found, I say yes please.

+1

+1 from me as well..............

 

 

 +1 Again.

+1 and again.

 -1

Everyone realizes that the script already has an 8% bump in saturation, right? I had a script at one point that did a 14% bump in saturation, and that was great for a few scenes, but looked like the SE DVD for alot of the scenes. (Lobster skin, neon yoda, electric R2...) The major problem with the GOUT is not the color, but the brightness/contrast, which the script also adresses.

-G

I hate to say it, but the artifacts will be in all of the films. Sorry I didn't catch it sooner.

Changing the line as I suggested will be just fine. It was supposed to restore stars from other frames, but the number it restored were few, and I'd rather not have even more fast motion artifacts on top of the DVNR smearing already on these things.

-G

One quick suggestion, could someone replace the last line of the restore stars stage with:

MT_Merge(prest,source,last,chroma="copy first")

and let me know what happens?

thanks!

-G

Sorry, guys. Didn't realize there was any recent activity. Well, the restore stars stage is SUPPOSED to just take the really dark areas and anything slightly nearby and return that area back to its original state. I'll take a look at the script, but it will take some time to get these going again on my new machine.

In the mean time, maybe I could just take a look at what DJ is doing to avoid this artifact. Wanna post it? I'll let you know if it's a good idea or not.

-G

Thanks, msycamore!

I actually like them quite a bit. It really comes down to a preference thing, and by the way, I have no idea how to add grain to just the subs either.

-G

I'm not planning on a NTSC input to NTSC output release of the script. I just don't have the time right now, and the PAL to NTSC is really the way to go.

-G

DJ,

Thanks for the offer. I really need you to test the script. Yes, It handles the PAL to NTSC conversion. Just make sure to encode a small clip first, and watch it. Then do the whole thing.

thanks,

-G

BTW everyone, ROTJ script is on page 1.

msycamore,

could you post your subs script? I want to compare the timing to mine.

-G

All good points guys! I will release it soon, but as I was looking through some old posts to determine who sent me the PAL clips that I have (It WAS OSJ BTW), I remembered some issues he had running an older script with a PAL source. Shouldn't be an issue with the new MVTools, but I want to add the (easy) fix just to be sure, and it will be ready to go.

I hope a better release comes along so you guys don't have a reason to be running this thing in 5 years!

-G

dark_jedi said:

Sure, did you get the sample and will it help? the one I sent in your PM.

here is the sub pic.

I realized I had on old sample of the PAL that I think I got from OldSchoolJedi. Anyway, the script is complete, but here's my problem:

My vision is to have the subs hard-coded, but in the black bars. This accomplishes two things.

1. if anyone wants to use the encodes for their own projects, they can just wipe the subs if they want to.

2. since the subs are not an original element, keeping them in the black bars doesn't present them as something they are not.

So here's my dilemma. If I release the script now, Dark Jedi will change the subs, and no one will ever see my version. If I have to wait until I obtain a copy of the PAL, the release will be delayed even longer. I guess if Dark Jedi agreed to use the script "as is" then there would be no more problems.

What does everyone think?

-G

DJ,

would you post a screenshot of your v3 ANH that shows what the subtitles look like?

thanks,

-G

dark_jedi said:

g-force I know I asked you this a while back but I was wondering are you making any headway on the Jedi script or are you running into issues? I am curious to know if we might be able to get this bad boy set out by the Holidays is all, I am still currently working on the '97 SE v2 set now and probably have at least a couple weeks left before these are done, then I will have all my time on the v3 SW and ESB, then onto Jedi when ready.

Thanks

 With what I just learned about the PAL version, I am having difficulty finding the motivation to move forward with the NTSC version. This will have to wait until I get a PAL copy.

-G

Chewtobacca said:

That is scary.  So in effect we improve the GOUT by dispensing with the GOUT!

 Good way to put it!

-G

Doctor M said:

Hey, just a quick OT thank you.

I was working on another project today and the source had some unpleasant aliasing.  I remembered a line in this script about it:

[code]########## anti-alias
NNEDI2(dh=true, field=0)
NNEDI2(dh=false,field=1)[/code]

I've never seen that done before, I'm not sure HOW it works, but it does a beautiful job.

Thanks.

 I'm glad it's useful even outside of the GOUT sources. You may not like the answer on how it works, but here goes anyway:

1. neural-network interpolate a line in between every line of resolution.

2. throw away all original lines and neural-network interpolate every line in between the first interpolated lines.

3. the next step that you didn't include is to resize back to original height.

That's right, there are absolutely no original lines of resolution remaining from the source. They are all interpolated. Kinda scarey I know, but it works amazingly well, doesn't it?

-G

Doctor M said:

One more suggestion: fft3dfilter includes a dering filter...

Too bad it doesn't work with our source either.

-G

Doctor M said:

Probably a stupid question, but did you try dgdecod with the cpu > 4?

I've had pretty good success and it's fairly fast.

cpu: 0 to 6 (default: 0)
Post-Processing Quickset Options.
(Y=luma, C=chroma, H=horizontal, V=vertical)
- 0: DISABLE POST-PROCESSING
- 1: DEBLOCK_Y_H
- 2: DEBLOCK_Y_H, DEBLOCK_Y_V
- 3: DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H
- 4: DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H, DEBLOCK_C_V
- 5: DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H, DEBLOCK_C_V, DERING_Y
- 6: DEBLOCK_Y_H, DEBLOCK_Y_V, DEBLOCK_C_H, DEBLOCK_C_V, DERING_Y, DERING_C

You can use cpu2 if you want to disable/enable specific options (such as the strong deblocking).

Yes. the Deblocking in dgdecode in not necessary on these sources, and the de-ringing is not very effective and blurs quite a bit.

-G

vbangle said:

G-Force, is there anything you can share with us about your progress on the V3 ROTJ script? What are some of the time consuming tasks in tweaking your script for ROTJ that's different from the other two movies scripts?

You know, the most time consuming thing is really the convolution (deringing) filter. Painful really, getting rid of ringing without loosing too much sharpness. I suppose if I was working with that PAL version, I wouldn't even bother, as the ringing seems really low judging by the pics from the other thread. Then it's just a matter of getting the resizing and cropping right. Everything else in the script should just work, except the subtitles may need to be shifted by a few frames depending on if the PAL and NTSC are in sync or not.

-G