Sign In

Info: cleaning up dirty frames for scenes

Author
Time
 (Edited)

i posted some cleaned up frames from

the star wars deleted scene here:

=========================

http://originaltrilogy.com/forum/topic.cfm/Star-Wars-Deleted-Scenes-Reincorporated/post/571037/#TopicPost571037

and more here:

===========

http://originaltrilogy.com/forum/topic.cfm/Star-Wars-Deleted-Scenes-Reincorporated/post/571040/#TopicPost571040

so now i’m working on more techniques

for other scenes… here’s a short 9 second

sequence from han shoots first in the cantina.

the top are the dirty frames, and the lower

is a test of the cleaned frames.

i didn’t color correct them… and it was harder

due to the dark color… also some of the frames

were out of sequence near the end…

the frame 135 was pretty tough to clean:

=================================================

<span style=“font-size: 12px; line-height: 14px;”></span>

here’s the toughest frame to clean:


if anyone has ideas, or techniques…

discuss them here…

most of it, is blending, and using surrounding pixel colors

to ‘guess’ what the best color to be is…

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time
 (Edited)

3PO Speeder

Blue Milk

Tosche

Luke Biggs

Luke Leia Hoth

PW=OT

Here's the changes to the script that I made.  I'm only posting the parameter variables as the rest of the script shouldn't be messed with except to trim the clip to whatever frames you want to process. Obviously if you want a different resolution for the end product you'll have to change it from 720x576 to whatever you want.

 

 

# film restoration script by videoFred.
# version with frame interpolation
# modified 30 august 2010
# added removedirtMC() as suggested by John Meyer
# cleaning, degraining, resizing, stabilizing, sharpening, auto-levels and auto-white balance.
#=============================================================================================

film="PATH TO FILM" # source clip, please specify the full path here

#PARAMETERS
#----------------------------------------------------------------------------------------------------------------------------
result="results4" # specify the wanted output here

trim_begin=0  play_speed=24  #trim frames and play speed (PAL: 16.6666 or 18.75)

numerator= 24  #numerator for the interpolator (final frame rate)
denumerator= 1 #denumerator  example: 60000/1001= 59.94fps


#COLOR AND LEVELS PARAMATERS
#----------------------------------------------------------------------------------------------------------------------------
saturation=1.2   #for all outputs

gamma= 1.1 # for all outputs

blue= -0  red= -0  #manual color adjustment, when returning result3 or result4. Values can be positive or negative


black_level=0  white_level=255 output_black=0  output_white=255 # manual levels, when returning result4
 

#SIZE, CROP AND BORDERS PARAMETERS
#----------------------------------------------------------------------------------------------------------------------------
CLeft=0  CTop=0  CRight=0  CBottom=0  #crop values after Depan and before final resizing

W=720  H=576  #final size after cropping

bord_left=0  bord_top=0  bord_right=0  bord_bot=0  #720p= borders 150


#STABILISING PARAMETERS
#----------------------------------------------------------------------------------------------------------------------------
maxstabH=0
maxstabV=0 #maximum values for the stabiliser (in pixels) 20 is a good start value

est_left=40   est_top=40  est_right=40  est_bottom=40  est_cont=1.4  #crop and contast values for special Estimate clip


#CLEANING PARAMETERS
#--------------------------------------------------------------------------------------------------------------

dirt_blur= 0.1 # some blur before cleaning to avoid pixel artifacts
dirt_strength=80 # set this lower for clean films.


#DENOISING PARAMETERS
#----------------------------------------------------------------------------------------------------------------------------


denoising_strength= 2000  #denoising level of second denoiser: MVDegrainMulti()
denoising_frames= 3  #number of frames for averaging (forwards and backwards) 3 is a good start value
block_size= 16  #block size of MVDegrainMulti()
block_size_v= 16
block_over= 8  #block overlapping of MVDegrainMulti()




# FOUR STEP SHARPENING PARAMETERS
#--------------------------------------------------------------------------------------------------------------------------------

USM_sharp_ness1= 60   USM_radi_us1= 3  #first sharpening (UnsharpMask) after cleaning with removedirtMC()

USM_sharp_ness2= 30    USM_radi_us2=2   #second harpening (UnsharpMask) after cleaning with removedirtMC()

USM_sharp_ness3= 20    USM_radi_us3=1   #third sharpening (UnsharpMask) after degraining with MVDegrainMulti()


last_sharp= 0.4 #final sharpening step after interpolation

last_blur= 0.2 #this smooths out the heavy sharpening effects



#AUTO LEVELS PARAMETER
#--------------------------------------------------------------------------------------------------------------------------------
X=2   # X is a special parameter for reducing the autolevels effect on the whites
X2=2  # X2 is a special parameter for reducing the autolevels effect on the blacks




# END VARIABLES, BEGIN SCRIPT
#=================================================================================================================================

Luke threw twice…maybe.

Author
Time

great, thanks althor..

 

i'll check it,

it might fix up some frames

better than what i did.

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time
 (Edited)

i can't get past this error:

===================

LoadPlugin("Deflicker.dll")

 

i keep getting a can not load error..

(from virtualdubmod)

 

i am using avisynth 2.5, and i do have all

the .dll files in the right directory..

 

i've tried renaming it deflicker.dll,

and i've redownloaded it a couple of times..

==

72.0 KB (73,728 bytes)

Monday, August 16, 2004, 7:31:08 PM

deflicker_25_dll_20040816.zip

 

still doesn't work..

 *UPDATE

=================================

ok, got past that error.. paths were wrong..

now i'm getting the same problem with : fftw3.dll

being called from depanestimate and failing..

 

again, i have that in the right directory..

 

*2nd update:

=======================================

never mind got it working..

It may be downloaded from ftp://ftp.fftw.org/pub/fftw/fftw3win32mingw.zip
For using, you must put FFTW3.DLL file from that package to some directory in path (for example, C:\WINDOWS\SYSTEM32). DePanEstimate will NOT work without it!

that was the problem!

 

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time
 (Edited)

yeah I had the same prob with fftw3. I should have mentioned it but I forgot Depan is dependent upon it.  After you get it working and try it out let me know what you think about it compared to your other software.

Luke threw twice…maybe.

Author
Time

althor1138 said:

yeah I had the same prob with fftw3. I should have mentioned it but I forgot Depan is dependent upon it.  After you get it working and try it out let me know what you think about it compared to your other software.

 it's a good simple start.

 

but it has a lot of problems with certain frames..

you have to tweak the parameters, and it's not

intuitive..

 

of course it won't match up against professional software.

 

the main thing is this gives you a good start on cleaning,

and i think for standard resolution video it will do..

for anything in HD it takes too long and its underpowered.

 

the software i'm using is near realtime, but you need

lots of ram, dual/quad processors, and a graphics card

that has hardware acceleration..

 

i know there are multicore dll's for avisynth, but it's not

a time issue for the rendering,.. it's the per frame

cleaning that is the problem..

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time

negative1 said:

 

it won't match up against professional software.

 

the main thing is this gives you a good start on cleaning,

and i think for standard resolution video it will do..

for anything in HD it takes too long and its underpowered.

 

the software i'm using is near realtime, but you need

lots of ram, dual/quad processors, and a graphics card

that has hardware acceleration..

 

later

-1

 

What software are you using? Also, how do you tell if your graphics card has 'hardware acceleration?'

And this looks awesome guys. I have been waiting to see someone taking the deleted scenes restoration initiative, and it looks fantastic so far! Very nice 

May the Force be with you.

Author
Time

ok, will be returning to this shortly.

 

with more examples soon.

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time
 (Edited)

ok,

 

here's the first stab at the han shoots greedo

scene.

 

again there's some large artifacts that come

up..

 

but it looks nice in parts!

====================

time : 64 seconds

Video: Xvid 640x560 24fps 7122kbps [Video 0]

------------------------------------

https://vimeo.com/46342319

 

*UPDATE:

password : OT

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time

here's shots from the newly cleaned

up video.. again, lots of artifacts in

some scenes:

=============================

 

 

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time

This is all just digital cleanup, not the FilmGuard, right?

This signature uses Markdown syntax, which makes it easy to add formatting like italics, bold, and lists:

Author
Time

Asaki said:

This is all just digital cleanup, not the FilmGuard, right?

correct.

 

we'll definitely be redoing some of the

scratchier scenes. although in some cases,

since we've cleaned some scenes already,

it might not be worthwhile.

 

we're evaluating the time it takes to redo them,

mainly.

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time

I'm not sure which parameters you are using but the artifacting is probably a combination of not enough "pre-blur" followed by too much sharpening.

Luke threw twice…maybe.

Author
Time

negative1 said:

 

 

later

-1

I don't remember this shot.  Is this a really quick one before he get's shot??

Author
Time

Yeah, that's the dummy that they used for the pyrotechnics of his death. Its visible for ~1 frame intact and looks, as you can see, a bit funny.

And yeah, these do seem over sharpened.

Author
Time

althor1138 said:

I'm not sure which parameters you are using but the artifacting is probably a combination of not enough "pre-blur" followed by too much sharpening.

yup,

there's a lot of parameters to play with!

so that's why i'm just messing around

with some of them. i might have tweaked

a few settings, but the final ones will be

more conservative.

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time

What a difference. Imagine how good a scene like this will look when it is scanned in with filmguard and then precise restoration is done to that very clean film scan. That's going to look amazing! :)

I hope they are re-scanned. Having seen some of the results of filmguard, it makes a huge difference, giving you the best possible source images to work with for the restoration. :)

The Star Wars trilogy. There can be only one.

Author
Time

ok,

here's an interesting test..

 

the very FIRST footage of any of the frames,

and scene from our RED english test partial reel.

the trash compactor scene in all its glorious

untouched red, downsampled to 720p:

=================================

https://vimeo.com/46590062

 

PASSWORD : OT

 

(don't mind the early sound synchronizing either!)

 

this is very first proof of concept that we did

to see if we could any video at all generated..

we won't be using this footage though.

 

this is just to give you an idea of what

the poorest quality of red faded sources

we have. we'll go through some of the

cleanup and correction after this.

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time

none said:

Are those the actual leader?  Parts of them match PuggoGrande:

http://originaltrilogy.com/forum/topic.cfm/Credits-Leaders-Thread-was-Star-Wars-Pre-Re-release-Credit-Change-June-77/post/510521/#TopicPost510521

The green '3' and the b/w 10 and even the hand drawn arrow.  Good to know that even that part is a direct duplicate, gives us another way to track variations.

i'm not sure.. it's what was on the partial reel.

it's possible it might have been, but how come it

hasn't aged?

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time

here's the very first image

that we got from the test reel

========================

 

and more:

========================

 

 

 

later

-1

 

[no GOUT in CED?-> GOUT CED]

Author
Time

this is one of those screenshots after a minute in photoshop, it's neat how much color information remains despite all that red!  

Author
Time

There are 24 frames of the tantive/destroyer scene I would like to show here if that's ok with you N1.

Luke threw twice…maybe.

Author
Time

althor1138 said:

There are 24 frames of the tantive/destroyer scene I would like to show here if that's ok with you N1.

go for it!

 

later

-1

[no GOUT in CED?-> GOUT CED]

Author
Time
 (Edited)

Just wanted you to understand beforehand that I'm talking about the 24 frames you posted on your site.  I don't remember if you said not to post it anywhere that's why I'm asking.

Luke threw twice…maybe.