In spite of the aspect ratio being different, why are these so different, color, noise, etc...? Arent these the result of the same script?
I love everybody. Lets all smoke some reefer and chill. Hug and kisses for everybody.
@vbangle
I guess it's because mine is a 50KB jpg (encoded twice) and dark_jedi's is a 500KB png
@lkjacc, did you look over anymore of the file by any chance to see if it is any where else? I am thinking the whole file is going to need to be re rendered, but I wish g-force would drop in and check it out first, love to have his thoughts.
@dark_jedi, these are from the first possibly problematic shot that came to my mind
AR should match yours this time and the screenshots are PNGs from lossless x264.
SHIT! that is what I was afraid of, I am just going to re render the whole thing, now I am worried about the other 2, have you looked them over by any chance? Thanks a ton for pointing this out.
@dark_jedi, I only have the PAL set for the time being, so no idea about SW and ESB
They both have the same "restore stars" code as ROTJ, so they should be carefully examined, though you said you were able to fix it without removing those lines so I don't really understand what's causing those artifacts.
I will do some more testing, and look over SW and ESB to see if this is on them to, if g-force does not comment then I will tell you what I did, but this is his script and he has everything working together so I don't want to just start changing things, I will PM you in a while so you can test also.
Now that you mention it, I agree it would be better to give g-force some time for him to find the best way to fix this before posting any changes. I too have a lot of respect for his work, the GOUT is unwatchable without it. When the damn thing came out I never thought such improvement was possible.
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
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
g-force said:
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
yes, omitting the MT_Logic.. part from the restore stars stage does eliminate the artifacts.
as you probably already suspects the problem seems to come from MDegrain1 in this line:
pcorr = source.MDegrain1(idx2,bw_vec1,fw_vec1,thSAD=800,thSCD1=150,thSCD2=75,plane=0)
pcorr has a lot of artifacts high motion frames and looks like this:
All I was doing since we narrowed it down to that line is start lowering the threshold down by 1 till it was gone, but was not sure if that was the way to go about it so I was waiting for you to comment.
I will try out what you posted, so in your opinion do you think the other films are not affected? I didn't see anything myself yet.
g-force said:
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
That worked for me too, huge thanks!
g-force said:
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
It worked for me to, so would you consider doing all of them with this edited line or do you think Jedi is the only one affected?
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
g-force said:
I hate to say it, but the artifacts will be in all of the films. Sorry I didn't catch it sooner.
-G
No need to be sorry, we are only human, I can whip up new renders soon enough, just wanted your opinion on whether or not these would be on the other films, I actually was just going to do them again anyways for peace of mind.
Thanks for the correction and input.
G-force, can you please tell me if there's a way of placing the anti-aliasing part in your script after the Greedo-subtitling without completely redo the subs from scratch? I'd just like to get my own Greedo-subtitles a little softer with the help of additional anti-aliasing when using your script.
If I place the anti-aliasing and resizing after my sub-scripting as it now stands, it alters everything in it, size, positioning etc. Is there a way around it, or do I have to simply redo them?
We want you to be aware that we have no plans—now or in the future—to restore the earlier versions.
Sincerely, Lynne Hale publicity@lucasfilm.com
To answer for g-force - no, that's not possible. The reason is that the anti-aliasing function also doubles the height of the video. The following stage in the script crops/resizes to an anamorphic image with borders; I assume it's the size of the video frame at this stage that you have used to determine the size and position of your subtitles (is it the script in this post?)
One easy option you could try would be to add interlaced=true to every subtitle line. This parameter adds an additional blur to the subtitle text (its purpose is to reduce flicker on interlaced displays).
Beyond that, you would have to look at a workflow that involves using your subtitles on a blank clip, adding a resize line after the subtitles so that they then match the non-anamorphic GOUT video, and finally adding this clip as an overlay to the GOUT video before the anti-aliasing.
Guidelines for post content and general behaviour: read announcement here
Max. allowable image sizes in signatures: reminder here
Moth3r said:
To answer for g-force - no, that's not possible. The reason is that the anti-aliasing function also doubles the height of the video. The following stage in the script crops/resizes to an anamorphic image with borders; I assume it's the size of the video frame at this stage that you have used to determine the size and position of your subtitles (is it the script in this post?)
Yes, that is the script I was referring to. I suspected that it would not be possible, but now I really know. Thanks.
Moth3r said:
One easy option you could try would be to add interlaced=true to every subtitle line. This parameter adds an additional blur to the subtitle text (it's purpose is to reduce flicker on interlaced displays).
Beyond that, you would have to look at a workflow that involves using your subtitles on a blank clip, adding a resize line after the subtitles so that they then match the non-anamorphic GOUT video, and finally adding this clip as an overlay to the GOUT video before the anti-aliasing.
That looks actually quite similar to the effect the additional anti-aliasing had on the text. I think I'll go with this method, that second option sounds like too much work. Thank you so much for the help, Moth3r! I couldn't have done these subs without you. :)
We want you to be aware that we have no plans—now or in the future—to restore the earlier versions.
Sincerely, Lynne Hale publicity@lucasfilm.com
Hello, i am trying to get the script for anh working and was wondering what are all the filters needed, so far i have found that these are needed
DGDecode.dll
DePan.dll
DePanEstimate.dll
mvtools.dll
mt_masktools-26.dll
nnedi.dll
RemoveDirt.dll
RemoveGrain.dll
Repair.dllfftw3.dll
Are there any other filters needed?
Thank you :-)
OT-DAWT-COM nieghbour and sometime poster (Remember, Tuesday is Soylent Green day!)
I think DJ put together a package of these several pages back.
“I love Darth Editous and I’m not ashamed to admit it.” ~ADigitalMan
boba feta said:
I think DJ put together a package of these several pages back.
Do you mean the 2nd and 3rd posts on this page? Or is the package you are referring to posted more recently than that?
EDIT: I scanned through all pages after page 7 and it seems those on page 7 are all of 'em.
OT-DAWT-COM nieghbour and sometime poster (Remember, Tuesday is Soylent Green day!)
Here comes a package of the required plugins.
Make sure you install the fftw3.dll in your system32 folder. This is a subfolder in your 'Windows' folder.
Thank you OldSchool :)
OT-DAWT-COM nieghbour and sometime poster (Remember, Tuesday is Soylent Green day!)
I have a few questions about the plugins you uploaded OldSchoolJedi
When the mask tools rar is extracted a few folders apear along with the dll "mask tools" "common" "avs25" in the mask tools folder there are these: "limited sharpen faster" "mfToon-v0.54" and "vmToon-v0.74" Should these be placed in the avisynth plugin folder aswell? And the dll that came from this rar is name mt_masktools.dll, Is this now the preffered version of the dll over the other dll on page 7 called mt_masktools-26.dll?
When i extract the removedirt rar 3 dlls appear: removedirt.dll, removedirts.dll, removedirtsse2.dll; do they all need to be placed into the plugin folder or just removedirt.dll?
Same question with the removegrain rar, several "removegrain dll"s, several "repair dll"s several "ssetools dll"s should they all be placed in the plugin folder?
OldSchoolJedi, these filters will work for the ntsc version right? I know you were making adjustments to figure out how to get the script to work for pal way back when however i am doing this to the ntsc and wanted to be sure.
Thank you :)
OT-DAWT-COM nieghbour and sometime poster (Remember, Tuesday is Soylent Green day!)