The power of Avisynth: restoring old 8mm films.

[egekhter]

I almost always use the killaudio() command in my scripts, specifically to avoid crashes. Many old hands in this forum have advised me that this isn't necessary, but that has not been my experience. With my particular editing workflow, I find that it takes absolutely zero effort (in my editing program, Vegas) to put the audio from the original source on the timeline below the video that results from the AVISynth script.

I know that's not the answer you were looking for, but I also wanted to let you know that you may find that you can't get stability with certain functions if you include the audio.

I figured out my problem.

The film was being captured at 50fps. The script was doing a framerate conversion to 18 fps.
The audio would finish before the video, and the frame processors did not like this.
After adding something to the attune of audio rate = 36% everything works like a charm.

I agree doing what you do is not a problem, but if we are going straight to hard drive, killing the audio and re-inserting it in a separate step is simply another step most people would like to avoid if possible.

Video is annoying - and rarely rewarding, but I do it anyways.

[manono]

...killing the audio and re-inserting it in a separate step is simply another step most people would like to avoid if possible.
I agree with johnmeyer. Keeping the audio in the script often leads to unnecessary difficulties. Some encoders only handle the video anyway (the ones I use only encode video). I never include it and always add it back later on. Maybe the quotation should read:
...killing the audio and re-inserting it in a separate step is simply another step some people would like to avoid if possible.

[johnmeyer]

killing the audio and re-inserting it in a separate step is simply another step most people would like to avoid if possible.
Maybe the quotation should read: "...killing the audio and re-inserting it in a separate step is simply another step some people would like to avoid if possible."As Abraham Lincoln once said (more or less):You can kill all the audio some of the time, and some of the audio all the time, but you cannot kill all the audio all the time.

[StainlessS]

JohnM Try 'KillAudio()' works pretty much 100% of the time. :) (Guess A.L., did not have Avisynth)

[potmat]

Hi All,

Pretty new to AviSynth, but very impressed with what videoFred's script can accomplish.

I have my grandfather's 8MM films scanned and the results given to me as image sequences. I'm able to use this script with only minor modifications.


I replaced AviSource with ImageSource
I have no desire to change the frame rate, the output can stay at 18fps - never transferring to DVD - so I removed all instances of .BlendFPS(final_framerate, frame_blend).


Everything works great with one interesting exception. The script comes with width and height as 720x576. This works fine even though my source images are 720x480. If I change H to 480 I get memory access violations at the degraining/sharpening step. I've tried newer versions of MVTools and MVTools2 but that actually seemed to make the problem worse.

If anyone has any ideas that'd be great.

[videoFred]

Hi Potmat,

Can you give us the error message you get?

Fred.

[potmat]

Avisynth read error: CAVIStreamSynth: System exception - Access Violation at 0x28ad680 reading from 0xae43d00.

Obviously the addresses will change each time you run. I should also point out that the problem is intermittent. It does occasionally work. I can live with re-trying over and over until it does, was just hoping someone had seen this before and go "ahh, you should change the block size....."

[johnmeyer]

Everything works great with one interesting exception. The script comes with width and height as 720x576. This works fine even though my source images are 720x480. If I change H to 480 I get memory access violations at the degraining/sharpening step. I've tried newer versions of MVTools and MVTools2 but that actually seemed to make the problem worse.I tried to duplicate your problem. I copied a fresh version of "01_C_Film_Restoring_Blending_Cleaning_Only.avs" from the June 2012 zip file. I then went through and made the minimum number of changes in order to match my project. Here are the changes I made:

film=
I changed this to point to my video file.

play_speed=
I changed this to 14.985, the speed of the film I transferred

final_framerate =
I changed this to the same as my play speed because, like you, I didn't want to make any speed changes.

W=720 H=480
As you can see, I changed this to match typical NTSC frame size, just like you were doing

That is all I changed. I then ran the script and got an error because it could not find one of the plugins. There is a reason for this, and I suspect it may point to the reason you are having a problem. The reason is that Fred's script uses very specific versions of certain plugins. In order to always make certain that I always use those plugins rather than newer or different plugins that I use for other scripts, I copied all of the plugins contained in his download to a unique folder, and then change all the "load" lines to point explicitly to that folder.

So, while I cannot duplicate your problem, I suspect that your problem may be caused by loading a different DLL than the one designed to work with Fred's script.

[potmat]

Doubtful, I only use the plugins that came with the script (except for when I briefly tried newer versions of MVTools, but quickly reverted).

Like I said the problem is intermittent, so it's not a show stopper. If I'm not doing something obviously wrong it's not likely we'll figure it out. Could be environmental, sometimes restarting virtualDub fixes it, sometimes restarting Windows does. Expecting a certain memory space to be unalllocated? It's been a long time since I've written any C and I hated it then, so if it's not obvious I'll just live with it. Trying to debug from source seems like a terrifying prospect:)

[johnmeyer]

Modifications to my version of the script
To salvage extraordinarily dirty film

I have posted elsewhere in this thread and in the companion thread Capturing and restoring old 8mm films (http://forum.doom9.org/showthread.php?p=1592567#post1592567) my alternative to Fred's script which does less sharpening, less color and levels corrections, but runs faster and does more dirt removal.

Because of a post on my YouTube page where I showed how to transfer Polaroid's "Polavision" instant movie film (Polavision Super8 Film Transfer and Restoration (https://www.youtube.com/watch?v=AfFj3dEw_nI)), I have been asked to transfer a lot of Polavision film. Because this film was developed in the cassette and then never removed from the cassette, it has been sitting in chemicals for thirty years and has huge, unremovable chemical stains which cover each and every frame. The normal script settings hardly touched this dirt. However, after extensive work, I was able to figure out how to modify the SAD, threshold, and scene changes in the RemoveDirt and RemoveDirtMC functions in order to remove most of this dirt. I then used an absurdly high removedirt setting of 93. The results, while far from perfect, are rather remarkable. Here is a sample of the result. In the "before," I have already removed the horrible vertical emulsion lines, and also have done extensive gamma and color correction. This example only shows dirt removal:

Polavision Before/After (https://www.youtube.com/watch?v=ud1XNIoh1P8)

Here are the modified remove dirt functions:

#Modified for Polavision film
#Mrecalculate thSAD changed from 100 to 20; scene thresholds added to MFlow
function RemoveDirtMC(clip,int "limit", bool "_grey")
{
_grey=default(_grey, false)
limit = default(limit,6)

prefiltered = RemoveGrain(clip,2)
superfilt = MSuper(prefiltered, hpad=32, vpad=32,pel=2)

super=MSuper(clip, hpad=32, vpad=32,pel=2)

bvec = MAnalyse(superfilt,isb=true, blksize=16, overlap=2,delta=1, truemotion=true)
fvec = MAnalyse(superfilt,isb=false, blksize=16, overlap=2,delta=1, truemotion=true)

# Increase thSAD if moving objects are being removed!!
bvec_re = Mrecalculate(super,bvec,blksize=8, overlap=0,thSAD=20)
fvec_re = Mrecalculate(super,fvec,blksize=8, overlap=0,thSAD=20)

backw = MFlow(clip,super,bvec_re,thSCD1=900,thSCD2=200)
forw = MFlow(clip,super,fvec_re,thSCD1=900,thSCD2=200)

clp=interleave(forw,clip,backw)
clp=clp.RemoveDirt(limit,_grey)
clp=clp.SelectEvery(3,1)
return clp
}

#pthreshold changed from 6 to 30
function RemoveDirt(clip input, int limit, bool _grey)
{
clensed=input.Clense(grey=_grey, cache=4)
alt=input.RemoveGrain(2)
return RestoreMotionBlocks(clensed,input,alternative=alt,pthreshold=30,
\ cthreshold=8, gmthreshold=40,dist=3,dmode=2,debug=false,noise=limit,noisy=4, grey=_grey)
}

[johnmeyer]

Like I said the problem is intermittent, so it's not a show stopper. If I'm not doing something obviously wrong it's not likely we'll figure it out. Could be environmental, sometimes restarting virtualDub fixes it, sometimes restarting Windows does. Expecting a certain memory space to be unalllocated? Try adding this statement to the script:

SetMemoryMax(1000)

If it doesn't eliminate the crashes, try changing the number (I often use 768).

As shown, this sets the memory allocation for your script to 1 GB. I have found that this statement can sometimes reduce or eliminate pesky script hiccups and crashes. It doesn't really fix any underlying problem, but it often results in a script that will operate.

[Gargamel]

Modifications to my version of the script
To salvage extraordinarily dirty film


Congratulations John !
That special script is the missing tool in some extreme cases...
Thank you again for sharing.

[GillesH]

John, congratulations also for this new RemoveDirt.
Avid reader of this forum for many years, user of your scripts since 2012 and new member of the forum for a few days.

Two questions, please, about this new script :
- What is this new RemoveDirt replace old version or is it only for the Polavision film.
- Is that there are a range of MIN and MAX setting with any argument
thank you

[johnmeyer]

John, congratulations also for this new RemoveDirt ... What is this new RemoveDirt replace old version or is it only for the Polavision film.
There is nothing new in my post other than changing a few parameters. "RemoveDirt" itself has been used in both Fred's script and in my variations to his script since 2010. I have posted those variations both in this thread and in this somewhat parallel thread:

Capturing and restoring old 8mm films (http://forum.doom9.org/showthread.php?t=165975&highlight=8mm)

So, there is not any new version of RemoveDirt being used. As for the changes in the three settings in the RemoveDirt and RemoveDirtMC functions, you can certainly try them on your own film transfer and see if they are better or worse than the settings I provided before. If you do this, you obviously want to feed a more sensible value to the function (something less than 25 rather than something in the 90s).

One issue with RemoveDirt is that I haven't figured out a way to tell it to ignore dirt objects less than a certain size, or to only look at black or white objects. As a result, when I restore old football game films (I'm doing dozens of these for a major football film collector), I have to use the script twice, with the remove dirt function disabled on the second pass. Then, every time the ball is thrown or kicked, I have to switch to the version with the dirt removal turned off because RemoveDirt tends to remove the ball in flight.

I am afraid that I don't understand your question about MIN and MAX arguments.

[manono]

...or to only look at black or white objects.

Thanks to poisondeathray and jagabo, I just learned how to do that the other day:

http://forum.videohelp.com/threads/360678-Filter-white-specks-with-Avisynth

If yours are larger than 'specks', then substitute RemoveDirt at whatever settings for RemoveSpotsMC. Maybe it'll save you from having to use it on one pass and removing it for a different pass and then switching back and forth between the 2 different versions.

[johnmeyer]

Thanks to poisondeathray and jagabo, I just learned how to do that the other day:

http://forum.videohelp.com/threads/360678-Filter-white-specks-with-Avisynth

If yours are larger than 'specks', then substitute RemoveDirt at whatever settings for RemoveSpotsMC. Maybe it'll save you from having to use it on one pass and removing it for a different pass and then switching back and forth between the 2 different versions.Very, very useful. When I get back to my main computer tomorrow I'm going to try some of the ideas in that post. I'm restoring full-length NFL and NCAA football films from the 1940s through the 1960s and the two-step approach adds hours to the work on each film. Thanks!

[GillesH]

Thank you John (and Fred). I will do further testing with different versions.
Sorry, my English is not always TOP ...
MIN and MAX : I just wanted to know if there were some parameters on which you could play to increase or decrease the effectiveness of the filter limits and what are the min and max.
But I realized the Multi-Passes could solve certain situations.
Thank you.

[joka]

Johnmeyer,

in case it is possible to create a mask for the removed object, you can restore the object with the function below.

dw_rd is your cleaned clip
dw_rg is the original clip
dwrm is a black and white mask (white forces restoring)

No need for an exact mask, the white ares can be smaller than the object. The mask only starts the restoring. RestorMotionBlocks will paste the object seamless.



Function dw_Restore (clip dwrd, clip dwrg, clip dwrm, int "limit") {

# workarround - addborders/crop moves green artefacts on borders (???) out of visible area
limit = default(limit, 6)

dw_r1 = Interleave(dwrd, dwrd, dwrd).Addborders(16, 16, 16, 16, $000000)
dw_r2 = Interleave(dwrm.mt_lut(y=0, chroma="copy"), dwrg, dwrm).Addborders(16, 16, 16, 16, $000000)

Return RestoreMotionBlocks(dw_r1, dw_r2, noise=limit).SelectEvery(3, 1).crop(16, 16, -16, -16) }



Of course it is possible to use this function for dirt removal directly. This gives more possibilities to control the process by creating, filtering and combination of masks.

However, the main problem is still unsolved. The problem is to decide what is dirt (not to restore) and what is "uncompensated" motion (has to be restored). Motion compensation will fail on a fast moving ball, hand, ... .

[jriker1]

So if I have a old video from 1968 that I took off a remastered DVD and want to clean up the pixilation and lines and the like in it and just improve it overall, how would I use this script to clean it up. Not the source video is in MKV format.

Noticed the original zip in this thread has a number of scripts and was trying to figure what I would do in my own AVS file to run cleanup against my MKV file and in what software I would do it in. Generally I work in Adobe Premiere and Sony Vegas which don't support avisynth.

Thanks.

[johnmeyer]

You only use one of the scripts in the zip file. Choose the one that has the capabilities you require. For cleaning up film that has been put on DVD you may first have to do inverse telecine. The scripts will most definitely NOT work on telecined film. Once you have the pristine 24 fps film, just simply run it through the version of the script that has the features you want to use. Make sure to first change the settings to match the problems in your source footage. The "S" parameter in the "results" variable will give you a "before/after" view that is very helpful in tweaking the script parameters.

[manono]

Not the source video is in MKV format.

Not if it's off of your 'remastered DVD' it's not. Why not decrypt the DVD itself, rather than making things more difficult by sticking it into the MKV container?

[jriker1]

Not if it's off of your 'remastered DVD' it's not. Why not decrypt the DVD itself, rather than making things more difficult by sticking it into the MKV container?

It's not really encrypted. I happened to have MKVMake so just used it to convert to something else other than DVD format.

JR

[manono]

It's not really encrypted. I happened to have MKVMake so just used it to convert to something else other than DVD format.
Then you can just drag and drop it onto the computer. You didn't convert it; you repackaged it and many find MKVs more difficult to work with than DVD VOBs. For example, how are you opening the MKV? And don't answer DirectShowSource.

The script isn't really needed for a DVD and was designed for something else. You can use the needed filters on your own without having to rely on the script, including a possible IVTC as mentioned by johnmeyer, something not covered in the script at all. If you post a short sample you might get some more informed advice.

[johnmeyer]

The script isn't really needed for a DVD ...Actually, I have found that some commercial DVDs contain really bad film transfers. For instance I have a Kinescope of a "Herman's Hermits" performance in Australia back in the mid 1960s. It was transferred from an old print and was absolutely loaded with dirt. The script really helped remove gate weave, improve sharpness, and get rid of the dirt.

[manono]

Hehe, I doubt it's a kinescope. In fact, he even said it's been remastered. In additon, he is, apparently, not all that knowledgeable where AviSynth is concerned, doing most of his video work using other programs. And the scripts can't be used as-is but will need some serious modifactions, I think, something he may not be prepared to do himself. However, a sample will tell the tale.

[frencher]

Translated with google translation

Hello everyone,
I would only stabilize videos of my child but I do not know at all an expert in AviSynth script.
In fact I will wish the same Stablisation vReveal that 101% with a avisynth script as simple as possible.
Thank you in advance, these videos are important to me.

http://i44.tinypic.com/23wjthg.png

[frencher]

I'm ready for create GUI with your Avisynth script if i'm welcome ;)

[Wolf]

Dear VideoFred, dear friends,

my question is if it's possible to stabilize a clip without change the original footage, in other words correct only the frame jitter (which is caused by limit of camera film transport).

This may be possible, digitizing all the frame info (like perforation and top/bottom line) and after synchronize the perforation hole with the top or bottom line of the frame (Revival and other restoring software works in this way).

Thanks!

P.S. VideoFred your script is fantastic!

Please, sorry for my english.

[johnmeyer]

my question is if it's possible to stabilize a clip without change the original footage, in other words correct only the frame jitter (which is caused by limit of camera film transport).Just decrease the horizontal and vertical motion stabilization values to small numbers. When you do this, you can also reduce the amount of zoom applied after the stabilization.

[johnmeyer]

Let me be more specific. Try these much smaller values:

CLeft=12 CTop=12 CRight=12 CBottom=12
maxstabH=4
maxstabV=4

I understand your idea of just stabilizing by using the sprocket holes. That can certainly work. To do this, you would mask out the center of the frame, leaving just the holes. Use this frame to create the Depan stabilizing vectors. Finally, use those vectors to stabilize the un-masked version of the film.

However, I think you will find that simply changing the variables, as I have shown above, will get you 95% of the way towards the result you want, but with only about 2% of the effort.

[Wolf]

Thanks Johnmeyer!! :)

[frencher]

Hi all,

I search to fix my bad stabilisation (only)...
From original Script HERE (http://sj1000hd.blogspot.fr/2013/09/optimisation-de-la-video-avec-avisynth.html)
Remove the fish eye effect and vignetting.
Stabilization.
Improved color

How ?
Thanks for all ;)

Package here avs + plugins folder + video sample (http://ul.to/pnyoonyy)

http://i62.tinypic.com/2yv5fs9.png

LoadPlugin("Plugins\mvtools2.dll")
LoadPlugin("Plugins\asharp.dll")
LoadPlugin("Plugins\defish_mt.dll")
LoadPlugin("Plugins\DePan.dll")
LoadPlugin("Plugins\DePanEstimate.dll")
LoadPlugin("Plugins\Deflicker.dll")

video1 = DirectShowSource("Video.mkv", audio=false).ConvertToYV12()
video2 = Optimisation(video1).ConvertToYV12()

video=stackhorizontal(video1,video2)

return video

function Optimisation(clip c)
{
# defish (v1.1) MT for Avisynth 2.5
c = c.ConvertToRGB()
c = c.defish(fov=99, scaling="fitxy",threads=0).ConvertToYV12()

# DePan, DePanEstimate
dymax = 20
sup = c.MSuper()
vec = MAnalyse(sup, isb=false)
globalmotion = c.MDepan(vec, pixaspect=1, thSCD1=400)
c = c.DepanStabilize(data=globalmotion,cutoff=2.0,mirror=0,pixaspect=1,initzoom=1.1,dxmax=0,dymax=dymax,rotmax=360,method=0,info=true).deflicker()

# Autres
c = c.Asharp(1.5,2,0.20,true)
c = c.Tweak(sat=1.1)

return c.ConvertToRGB()
}

[basil3w]

Does anyone know if Avi Synth or CiniCap will run on a Windows 8.1 machine?
Thanks,
basil3w

[flafla91]

No problem with Avisynth and Virtualdub with Windows 8.1
Fabien

[basil3w]

Fabien-
Sorry it took so long for me to reply, but Thanks Very Much for the response about Win 8!
-George

[papcom]

I have used and experimented with videofred's scripts since more than a year. No Problem so far. I used the scripts "as is", I made no changes, except the Video source an some slight Level adjustmens. The path's of the plugins I left untouched.

Alls Scripts are installed in a separate Folder on my harddisk as described in videofred's installing help.

Today I installed the new Version of virtualdub 1.10.4 and I installed avisynth 2.5.8 (after having correctely deinstalled the older avisynth Version). I restarted the PC correctely.

Since then I cannot process any scripts of videofred. There is always a load plugin error (unabble to load "plugins/deflicker.dll)
It doesent matter whether I use virtualdub oder AVSEditor Preview...the plugin error comes up.

I do not Change anything in the Installation!!!

Waht has happend? Can anyone help me.

[videoh]

When you reinstalled Avisynth, you wiped your plugins directory, which previously contained that DLL. Find it online and put it in the plugins directory. There may be others missing as well. If you kept a backup of your Avisynth plugins directory, just use that. If not, well, consider doing so whenever you uninstall Avisynth.

[papcom]

I don't think it's the Problem You describe. All the plugins which are needed by videofreds scripts are there, as described in the Installation Guide of viodeofred. The folders ar as mus be:

helpfiles
scripts (contains avs scripts and plugins folder with all DLL's)
sourcecode (with all plugins in it)

My Videofred's file installation is in a different Directory than the AVSynth installation in the Programm Folder. It does not touch anyhow the plugin Folder of AVS2.5.8

All DLL's are there at the correct place and also all plugins sources are there at the correct place. But anyhow the script cannot load any plugins which are listed in the script !!

[videoh]

OK, then can you post the script that does not work? Everything should have explicit loadplugin() calls if the Avisynth plugins dir is not used. Verify that the paths in those calls are correct.

[papcom]

OK, then can you post the script that does not work? Everything should have explicit loadplugin() calls if the Avisynth plugins dir is not used. Verify that the paths in those calls are correct.

here the relative code excerpt, which Shows the plugin calls. The paths are correct because the plugin Folder lies inside within the scritps: (it allways worked like this, and it is just like videofred's install guide)

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


SetMemoryMax(1000) #set this to 1/3 of the available memory

LoadPlugin("plugins/Deflicker.dll")
Loadplugin("plugins/Depan.dll")
LoadPlugin("plugins/DepanEstimate.dll")
Loadplugin("plugins/removegrain.dll")
LoadPlugin("plugins/removedirt.dll")
LoadPlugin("plugins/MVTools.dll")
LoadPlugin("plugins/MVTools2.dll")
Loadplugin("plugins/warpsharp.dll")
LoadPlugin("plugins/autolevels_06.dll")
LoadPlugin("plugins/Motion_06Dec05B.dll")
Import("plugins/03_RemoveDirtMC.avs")

source= AviSource(film).assumefps(play_speed).trim(trim_begin,0).converttoYV12()
trimming= framecount(source)-trim_end
source1= trim(source,0,trimming)

#STABILIZING/CROPPING
#..........................

[videoh]

See my post in your other thread.

[papcom]

for more information about the plugin load problem please read here:
http://forum.doom9.org/showthread.php?p=1687888#post1687888

or here:
http://forum.doom9.org/showthread.php?t=166492

[papcom]

For opening a QT MOV ProRes File with Avisynth, I use QTSource Plugin with the command "qtinput"...no problem

When I do the same in VideoFred's script I receive the following Script error:
"Invalid arguments to function "AVI Source" on line 146"
where the following is: source= AviSource(film).assumefps(play_speed).trim(trim_begin,0).converttoYV12()

What is my mistake?

[johnmeyer]

I don't know QTSource, but if the command is "qtinput," then I think all you do is use that in place of the AVISource statement:

source=qtinput(film).assumefps(play_speed).trim(trim_begin,0).converttoYV12()

[manono]

What is my mistake?
Is 'Source' referred to later in the script? If not, will:

qtinput(film).assumefps(play_speed).trim(trim_begin,0).converttoYV12()

by itself work?

[papcom]

thank You for Your answers.
I tried already with:

source= QTInput(film).assumefps(play_speed).trim(trim_begin,0).converttoYV12()

but it does not work.

Other useres wrote before in this thread:

Originally Posted by poisondeathray View Post
You can import prores into avisynth using ffms2 or qtinput

[johnmeyer]

Is 'Source' referred to later in the script? If not, will:

qtinput(film).assumefps(play_speed).trim(trim_begin,0).converttoYV12()

by itself work?Shouldn't the question be: "is film referred to later in the script? The variable film points to the actual video file, and if it was referred to again, then that reference would also have to be changed. However, once "source" contains the video stream, I think it should be usable elsewhere in the script.

If you temporarily change the script so that the final statement is:

return(source)

does it play correctly? I would certainly begin my troubleshooting by making sure that the QuickTime reader can actually read your source.

[papcom]

The script I use is the original script 01_A by videofred. I just would like to Import a ProRes422 QT Mov instead of the AVI.

From the principle QTSource works fine for importing my QT MOV with other scripts, which refer to the original plugin Directory within avisynth.

I just wasen't successful with QT MOV and videofred's script. As I have read in this very thread other users have imported QT Mov in videofred's script successfully.. so I think it's just a manner of how to.

Perhaps the users "poisondeathray" or "egekhtr" can explain how they did it. This would be very helpful.

[johnmeyer]

From the principle QTSource works fine for importing my QT MOV with other scripts, which refer to the original plugin Directory within avisynth. If any of your plugins are NOT in the original plugin directory, then you must load them explicitly. Since your earlier posts described a problem with plugins not loading, then perhaps this is the issue.

For example: loadPlugin("c:\Program Files\AviSynth 2.5\plugins\QTSource.dll")I started programming in the 1960s, and back then, you always had to load everything explicitly. While modern programming languages don't require that, sometimes the assumptions made by the program about where to search for things that it loads implicitly end up making the wrong assumption and grab the wrong thing.

Also, I just tried using the QTSource plugin to load a QuickTime file on my computer, but I got an error because I don't have QuickTime installed on this computer. So it appears that this plugin relies on QuickTime for some of what it does. This then reminds me of problems I have seen reported in other forums many times over the past few years, namely that many plugins are very sensitive as to what version of QuickTime is installed.

[edit]Also, not all QuickTime files are created the same. Perhaps you should try loading this particular MOV file into one of the scripts that has worked with other MOV files.

[Reel.Deel]

For MOV files LSMASHVideoSource (http://avisynth.nl/index.php/LSMASHSource/LSMASHVideoSource) works great (at least with a few files I tried it on).