Sign In

althor1138

User Group
Trusted Members
Join date
12-Feb-2011
Last activity
21-Oct-2018
Posts
933

Post History

Post
#1249593
Topic
Star Wars Laserdisc Preservations. See 1st Post for Updates.
Time

Regarding extra frames. I don’t have any of the scripts on the HDD anymore but I think I did reference it somewhere here in this thread. I believe it was 1 or 2 of the PAL releases and it was only ROTJ that had extra frames. There might have been 1 release that had the extra frame of the guy waving his hands while directing the droid into the back of the x-wing in the hangar in SW but I honestly can’t remember which release that was.

Regarding the black frames inserted to maintain gout-sync. Those were digitally created and should be entirely black. Also, I applied the limiter plugin to all encodes which sets the lowest pixel value allowed to 16, so with the script above you could probably set the global blankthreshold variable to 17 and extrapolate the missing frames from my various laserdisc releases. The black frames that should be in the film would contain dropouts/analog noise and should have a higher threshold.

Post
#1236524
Topic
Unofficially Official LD-Decode thread
Time

Seems like happycube has joined with domesday project and they are now actively updating the software. I think. I can’t find any links to the updated software but here’s the facebook group.

https://www.facebook.com/groups/2070493199906024/

Seems like they have updated the ld-decode repo recently as well so perhaps that is still where to find the latest version.

Post
#1226377
Topic
The GOUT Sync Thread
Time

Those scans are typically missing quite a few frames compared to the gout. If you take star wars, for example. The gout seems to be missing only 1 frame when compared against all of the other sources, whereas the other sources are typically missing quite a few frames at the beginning and end of each reel. I, for one, am onboard with adding this 1 frame and calling it the new standard but for understandable reasons not many seem to want to go this route as the new standard would be something that would have to be compiled together before comparison with another project.

What would it be called? Of course, the day that somebody finds a new frame it would have to become version 1.1, etc, etc.

I do believe there will not be many more new frames found. Over the years we’ve all poured over them time and again. Source after source. I think we’ve got it nailed down pretty well now.

Post
#1226276
Topic
The GOUT Sync Thread
Time

#Edit the special edition dvd to match the gout dvd frame for frame

swse1=swse.trim(0,15648) ++swse.trim(15669,0)
swse2=swse1.trim(0,21123) ++swse1.trim(21503,0)
swse3=swse2.trim(0,21600) ++ swse2.trim(21701,0)
swse4=swse3.trim(0,57790) ++ swse3.trim(57815,0)
swse5=swse4.trim(0,60434) ++ swse4.trim(61027,0)
swse6=swse5.trim(0,60499) ++ swse5.trim(60521,0)
swse7=swse6.trim(0,61452) ++ swse6.trim(61574,0)
swse8=swse7.trim(0,71278) ++ swse7.trim(71289,0)
swse9=swse8.trim(0,73845) ++ swse8.trim(76076,0)
swse10=swse9.trim(0,74228) ++ swse9.trim(74250,0)
swse11=swse10.trim(0,75798) ++ swse10.trim(75877,0)
swse12=swse11.deleteframe(143364)
swse13=swse12.trim(0,144345) ++ swse12.trim(144971,0)
swse14=swse13.duplicateframe(144395,144395,144395,144395,144395,144395,144395,144395)

Might be a start for dropping the SE frames.I can’t confirm these trims right now and I did this originally in 2007 I think. Adding black to the gout to match up to the SE would not be much harder.

Post
#1215818
Topic
1997 Star Wars Special Edition 35mm Project
Time

poita said:

I’m uploading you a new version now Althor. Sorry about that, it plays okay here in the quicktime player, but I encoded a new version anyway, it is uploading now.

No problems. Something must have happened during the download from the host or who knows what. I downloaded it twice and it had the same problems both times. Thanks for making another one for me!

Post
#1215763
Topic
1997 Star Wars Special Edition 35mm Project
Time

I synced my rips to capablemetal’s project involving the cinema dts which I believe is probably the “GOUT” standard for the 97se. So I guess his rips are what I would sync to.

Here’s the thread with the work that went into syncing up and creating a standard for the 97se.

https://originaltrilogy.com/topic/The-1997-Star-Wars-Special-Edition-Trilogy-Preservation-Standards-Thread-Work-In-Progress/id/14647/page/1

Post
#1140322
Topic
Enhancing LaserDisc Captures with AviSynth
Time

It was pretty painless for me. Mileage might vary I suppose. I had more troubles with going from win7 to win10 since avspmod stopped working for me. Somebody has patched it since then. Definitely backup your plugins folder to as many USB sticks as you can find. Worst case scenario, you can roll back to 2.5.8 if all else fails.

I have a lot of external filters loaded and there were maybe 2 that didn’t work right out of the cage with 2.6. It’s usually just a matter of finding the latest version on the wiki and overwriting it in the plugins folder.

Post
#1140276
Topic
Enhancing LaserDisc Captures with AviSynth
Time

Temporal Soften Motion Compensated

This is what I use on laserdiscs nowadays as it seems to be better at removing the analog noise of laserdiscs.

It’s quite simple actually and the dependencies are only:

Avisynth 2.6
Temporal Soften (this is an internal filter)
MVTOOLS2 (version 2.6.0.5 or similar)

The only things you really need to tinker with are tradius(temporal radius) and mthresh(motion threshold). Everything else I never change but I put them in as options in case you want to change the blocksize, for example. The only thing I ever adjust actually is mthresh.

mthresh=70 will denoise basically only stationary stuff.
mthresh=120 will denoise slightly moving stuff.
mthresh=180 will denoise moving stuff but not extremely high motion.

Anything over 180(depending on the source) can start to risk loss of detail that, imo, is unacceptable. However, 70-120 denoises A LOT but still looks good.

function TSMC(clip input, int “tradius”, int “mthresh”, int “lumathresh”, int “blocksize”, bool “MT”)
{
tradius=default(tradius,5)
#temporal radius-number of frames analyzed before/after current frame.

mthresh=default(mthresh,70)
#motion threshold-higher numbers denoise areas with higher motion.
#Anything above this number does not get denoised.

lumathresh=default(lumathresh,255)
#luma threshold- Denoise pixels that match in surrounding frames.
#255 is the maximum and default. 0-255 are valid numbers.
#Also adjusts chroma threshold.

blocksize=default(blocksize,4)
#larger numbers = faster processing times. Must be 4,8,16, or 32.

MT=default(MT,true)
#turn multi-threading on or off. If you are using single threaded avisynth this should be true.
#If you are using multi-threaded avisynth this should be false.

prefilt=input.blur(1.58)
super=MSuper(input, pel=2,mt=MT)
superfilt=MSuper(prefilt,pel=2,mt=MT)

multivectors=Manalyse(superfilt,multi=true,delta=tradius,mt=MT)
multivectors2=Mrecalculate(superfilt,multivectors,thsad=mthresh,tr=tradius,mt=MT,blksize=blocksize,overlap=2)
mc=Mcompensate(input,super,multivectors2,thsad=mthresh,mt=MT,tr=tradius,center=true)
dnmc=mc.temporalsoften(tradius,lumathresh,lumathresh,15,2)
decimate=selectevery(dnmc,tradius * 2 + 1,tradius)
return(decimate)

}

I want to add that if anybody has any ideas to make this better feel free to chime in. I’m by no means an avisynth guru and am open to improvement!

A quick how to use avisynth and this denoiser:

  1. Go download avisynth 2.6 and install it:
    https://sourceforge.net/projects/avisynth2/

  2. Download mvtools2. Navigate to the avisynth folder in Program Files and extract the mvtools2.dll file into the plugins folder inside the avisynth folder.
    http://ldesoras.free.fr/src/avs/mvtools-2.6.0.5.zip

  3. Open notepad and copy the code from the first post into it and save it as TSMC.avsi. Place this also into your avisynth plugins folder.

  4. open notepad and write a script to load the video file and denoise it. Here’s an example:

avisource(“c:\temp\starwars.avi”)
TSMC(5,120,255,4,true)

Save this wherever you want it as starwars.avs or whatever you want to name it. Just make sure you have .avs as the extension.

  1. Open Virtualdub. Navigate to your starwars.avs file and open it in virtualdub. It should pop up in virtualdub already denoised via avisynth.
Post
#1140275
Topic
Archiving Star Wars 1997 Special Edition laser discs...
Time

Unfortunately, spleen access has been locked down so I couldn’t hand out an invite even if I wanted to.

I have always used avisynth/virtualdub exclusively for my laserdisc rips. I can right away recommend that you have windows 7 running and buy a theater750hd pcie capture card if you are serious about results. This is hands down the best cheap capture card I’ve ever come across. It handles tbc correction as well so you don’t need an external tbc to straighten up the picture. The player probably won’t make a huge difference in quality.

As for color correction, etc., I only ever do levels adjustments to get a proper white/black level. Manual IVTC is a whole other bear to tackle. I’d recommend using an automated filter to do that unless you are masochist. If you read through my laserdisc preservations thread there is a lot of good information and scripts on how to accomplish it though.

Best of luck with your endeavor!

Post
#1140110
Topic
Archiving Star Wars 1997 Special Edition laser discs...
Time

If you are dead set on having the laserdisc versions. I have uploaded my preservation of the 97se laserdiscs onto the spleen. They are synced to the theatrical DTS, include the laserdisc 5.1, etc.

I don’t normally go around promoting my laserdisc preservations but I’ve seen a lot of people ask for these lately. The link below will give you an idea of what you can find.

http://originaltrilogy.com/topic/Star-Wars-Laserdisc-Preservations-See-1st-Post-for-Updates/id/15283

Post
#1135542
Topic
1997 Star Wars Special Edition 35mm Project
Time

poita said:

Althor, I’ll put some frames with the IR damage matte up on the share tonight.

Many thanks Poita. I should be able to play around with this and make a script in avisynth that makes dirt removal a whole lot smarter. As long as you have the IR to use as a mask anyway. Dirt on top of motion will probably still be problematic but getting it to hone in on only dirt and not a laser bolt, for example, eliminates half the battle I suppose.

I haven’t used any professional dirt removal tools other than pfclean. Perhaps dirt removal isn’t that big of a problem like it used to be for guys like you with all the right tools.

Post
#1135192
Topic
1997 Star Wars Special Edition 35mm Project
Time

For clarification, what should a person try to sync this to? The blu-ray? In the past I synced my 97se laserdisc projects to capablemetal’s files which were synced to the dts discs.

Also, was the 97se cropped and framed differently or was that only from 2004 forward? Just wondering.

EDIT: I’m not sure I have my terminology right here but if you have the Infrared channel would you share it for one of the accompanying files so that the community might play with automated dirt removal? I know I have a couple of ideas for using it as a mask in avisynth but just never have had access to the IR to attempt it.

Post
#1086547
Topic
Return of the GOUT - Preservation & Restoration
Time

Maybe drop eedi2 because this is dropping a field and interpolating it if I remember right. This kind of neuters the rest of the filter chain. Also, maybe try qtgmc using inputtype=1 as this might fix the aliasing without dropping and interpolating fields. I definitely would not eedi2 and qtgmc together. Also, move qtgmc up the filter chain to where you currently have eedi2. No need to run it at an upscaled resolution it just takes longer.