logo Sign In

GOUT image stabilization - Released — Page 5

Author
Time
 (Edited)
Hi Old School Jedi!

Managed to fix it. I went through the AVIsynth plug-ins folder, and deleted any duplicates there which might exist for other CPUs.

I also downloaded a different mt_masktools.dll (dated 27th Jan '06) from http://manao4.free.fr/

Lastly I ran my test clip through DGIndex again and created a fresh D2V file.

One or all of these seemed to do the trick!

Fingers crossed it will work for you as well :)
Author
Time
 (Edited)
seventiesfilmnut said:


I also downloaded a different mt_masktools.dll (dated 27th Jan '06) from http://manao4.free.fr/


Oops, I forgot that that .dll is a bit tricky as well. I think I'm using Masktools v.2. Not sure of the date, but most likely at lease 2.0 alpha 27 which is the most recent listed on this page: http://manao4.free.fr/mt_masktools.html
but I noticed he also has some higher versions on the page that seventiesfilmnut listed.

I kinda had to go through this same process of aquiring the necessary plugins when Arnie.d and Moth3r started the anti-aliasing thread. I wouldn't want to deny you guys the same fun! ;)

-G
Author
Time
Turns out that NNEDI TurnLeft NNEDI TurnRight doesn't do any more than NNEDI alone. BUT - it seems that NNEDI TurnLeft, then EEDI2 DOES help on the same scenes that the TurnLeft TurnRight did before and without any of the other blur bubble issues. Im going to update the script again.

-G
Author
Time
g-force said:

seventiesfilmnut said:


I also downloaded a different mt_masktools.dll (dated 27th Jan '06) from http://manao4.free.fr/


Oops, I forgot that that .dll is a bit tricky as well. I think I'm using Masktools v.2. Not sure of the date, but most likely at lease 2.0 alpha 27 which is the most recent listed on this page: http://manao4.free.fr/mt_masktools.html
but I noticed he also has some higher versions on the page that seventiesfilmnut listed.

...

-G


That was it!

I am using the different masktool.dll and now everything works!

I'm doing another encoding at the moment and can't wait to see the result.

Thank you, guys!!!
Author
Time
Are you sure the vertical anti-aliasing is necessary? I think the vertical aliasing is barely noticable and if you remove it you blur the image more.
Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.
Author
Time
 (Edited)
Arnie.d said:

Are you sure the vertical anti-aliasing is necessary? I think the vertical aliasing is barely noticable and if you remove it you blur the image more.


The vertical aliasing is VERY visible in VERY rare places. So I'm torn. A little bit more sharpness for the whole movie, and faster running script, or fixing some very rare but extremely ugly problems? The issue I'm talking about can be seen here:

[IMG]http://img87.imageshack.us/img87/4302/owenorigxh0.th.jpg[/IMG]
[IMG]http://img72.imageshack.us/img72/2860/nnedily5.th.jpg[/IMG]
[IMG]http://img87.imageshack.us/img87/9493/nnedieedi2ce3.th.jpg[/IMG]

Make sure to click on the image after it opens to see it full size. The 2 anti-aliased ones were made without changing any sharpening settings. Notice the zaggies on the droid on the right that are fixed by the rotated EEDI2. What does everyone prefer?

-G
Author
Time
The last one fixes the jaggies in the lower right but at the expense of blurring the whole image. I like the middle best. The contrast and color is slightly improved on the first and the the vertical antenna pole on the right shows up the sharpest.

Take back the trilogy. Execute Order '77

http://www.youtube.com/user/Knightmessenger

Author
Time
Trouble is the ringing is alot more noticeable in the 2nd and 3rd examples. Personally I think I'd rather stick with the original for this scene. I guess it's all a huge balancing act, and there isn't one script that can do the entire film - I'm leaning towards splitting the film into scenes and using different filters depending on what each clip dictates.
Author
Time
seventiesfilmnut said:

Trouble is the ringing is alot more noticeable in the 2nd and 3rd examples. Personally I think I'd rather stick with the original for this scene. I guess it's all a huge balancing act, and there isn't one script that can do the entire film - I'm leaning towards splitting the film into scenes and using different filters depending on what each clip dictates.


I like the idea of splitting up each scene. Would take a lot of work though. Sticking with the original for this scene is not an option in my opinion, as there is was too much crazy local motion (things that shouldn't be moving are)

Anyway, it turns out that the script that I used to generate #2 had too much sharpness, and as a result the playback appears to "nervous". It's starting to re-introduce the local motion that I'm trying to remove.

Also, I've got a new star preservation routine that I'll post into the script on page one.

-G
Author
Time
g-force said:

New test encode.

stabilize.m2v

Please take a look and tell me what's wrong with my Tie lasers? This problem doesn't show up in the Avisynth output, it is something that is happening during the encode. Any ideas?

-G


I have the same error at my encodings.

G-force, can you remember what the error was?

I have this error when I use HC encoder, not with other encoders. But HC encoder runs faster with this script than other (commercial) encoders, so I prefer this encoder.

By the way: What version of avisynth do you have installed and what encoder are you using?

Author
Time
It seems, that there was something wrong with the EEDI2-plugin.
When I did encodings with "NNEDI(dh=true,field=1).TurnRight().EEDI2().TurnLeft()" the lasers of the imperial starship over Tattooine sometimes turned from green to white and looked a littlebit like bubbles.

Now I tried your script from the 20.03. with "NNEDI(dh=true,field=1).TurnRight().NNEDI(dh=true,field=1).TurnLeft()" and everything works fine.
Author
Time
Oldschooljedi said:

I have the same error at my encodings.

G-force, can you remember what the error was?

I have this error when I use HC encoder, not with other encoders. But HC encoder runs faster with this script than other (commercial) encoders, so I prefer this encoder.

By the way: What version of avisynth do you have installed and what encoder are you using?



I was having that problem with QUenc, but then I switched to HCenc and the problem went away. Strange, seems to be the exact opposite of your problem.

I am using avisynth2.5.

As for the double NNEDI, The second one doesn't do anything. I'll check the lasers you mentioned and update the script as needed.

-G
Author
Time
Oldschooljedi said:

It seems, that there was something wrong with the EEDI2-plugin.
When I did encodings with "NNEDI(dh=true,field=1).TurnRight().EEDI2().TurnLeft()" the lasers of the imperial starship over Tattooine sometimes turned from green to white and looked a littlebit like bubbles.

Now I tried your script from the 20.03. with "NNEDI(dh=true,field=1).TurnRight().NNEDI(dh=true,field=1).TurnLeft()" and everything works fine.


Oldschooljedi, thanks for spotting this! I found the problem you are referring to, and it turns out that the error isn't in the EEDI2, it's in the motion compensation stage. I added "thSAD" to the MVCompensate lines, which fixes this problem. (see updated script on first page)
I've also moved the resized to before the TurnLeft, which speeds up processing a bit.

-G

Author
Time
Oh man, I captured the Jabba scenes from the Definitive Collection laserdiscs for subtitle creation. So I had the laserdisc footage next to the GOUT footage. Damn, the LD capture looks so blurry and noisy compared to the GOUT, but it has soooo much more vertical detail. The GOUT really could have been so much better than they made it, it's rediculous.
Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.
Author
Time
Haha nice avatar g-force. Rather appropriate I would hasten to add.

“I love Darth Editous and I’m not ashamed to admit it.” ~ADigitalMan

Author
Time
I was just thinking the same thing.
Author
Time
boba feta said:

Haha nice avatar g-force. Rather appropriate I would hasten to add.


Thanks! I just wish with all the work that I've put into the GOUT that there was a better source to work with.

-G
Author
Time
Have you considered the Japanese SC? It's pre DVNR, and IMO has a more faithful colour representation.

“I love Darth Editous and I’m not ashamed to admit it.” ~ADigitalMan

Author
Time
I have been following this topic, even though I haven't posted for a while. I'm impressed with the amount of work g-force has put into this, his AviSynth scripting is more advanced than anything I could do.

However, I've given up on the GOUT discs for the time being. Yes the picture is more detailed than the laserdiscs, but I find the aliasing (or side effects from anti-aliasing filtering) and DVNR motion smearing is more noticeable. I think I could live with a softer image that didn't have these distracting defects.

I'll probably be taking a look at laserdisc sources in the future. I think a hybrid of the French THX discs (more vertical detail and less telecine wobble than the DC) and the US pre-THX special widescreen edition (can't afford the JSC discs) is on the cards. But that's a different topic...

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Moth3r said:

...his AviSynth scripting is more advanced than anything I could do.


[blush]Come on[/blush] there was a time just a couple months ago where everything I knew was from you. I would dissect your scripts and run parts of them just to see what they were doing.

Moth3r said:

However, I've given up on the GOUT discs for the time being.

I can't blame you there. I figure this is the best we have so far, so I want to make it as good as I can and then I'll have the skills to do the next version that needs fixing. And in the mean time, if I ever stop tinkering and actually encode the whole thing, I'll have something watchable.

Moth3r said:


I'll probably be taking a look at laserdisc sources in the future.

I can't wait!

BTW, Small updates to the script on page one. No change to the picture, but should speed things up a bit.

-G
Author
Time
QUick question G-Force: when encoding in VirtualDubMod which codec do you select? I gather pure RGB takes ALOT of space, so this leaves Huffy I think as being a good second best?

Also do you leave the re-muxing of the audio till the last stage?

Many thanks!

- John
Author
Time
seventiesfilmnut said:

QUick question G-Force: when encoding in VirtualDubMod which codec do you select?

Also do you leave the re-muxing of the audio till the last stage?

Many thanks!

- John


John, I honestly haven't gotten that far yet. Currently, I'm encoding the avs script to Mpeg with HCenc, and just limited portions of it so far. I plan on adding the audio back in when I re-encode the whole thing to DVD.

It would be cool to have a huffy file of this though so that non-linear editing could be done later. I don't know though, something about manually painting frames doesn't sit well with me. Maybe if someone wanted to use this for replacing scenes from the SE, but then I think I'd suggest applying the filters differently depending on the scene. The global motion stabilization for instance can be so much better if you know there are no large objects moving in scene (and even better yet if there is no intentional motion at all). And I'm also toying around with making the stars less shimmery, but am having trouble doing it safely on the whole movie.

So that's the long winded answer to your question about encoding, which is really just me thinking out loud about the need for a lossless file.

-G
Author
Time
 (Edited)
Thanks for that G-Force - have downloaded HCenc and will have a play with that.

Hehe I doubt this script will EVER be finished - always something else to tweak or to try out :)

- John

EDIT: Just been reading about DVD authoring, and industry standard black/white levels. Apparently black should be 16, and white 235, rather than 0 and 255, if the final DVD is to be used on a TV set as well as a PC. If solely on a PC or other digital device then 0 and 255 is apparently fine. Any thoughts on this?
Author
Time
 (Edited)
When encoding in CCE I always set the luminance level to 16-235 instead of 0-255 or else the ouput will be to dark (with an RGB input anyway).
Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.