I'm using 1.9.11, but I suppose I could try the beta.

ColourLikeFBF is a function that Antcufaalb wrote for ColourLike.

function ColourLikeFBF(clip c1, clip c2)
{ # Color-matches c1 to c2, frame by frame.
  # Assumes c1 and c2 are the same length and are
  # both compatible with ColourLike.
  global c1 = c1
  global c2 = c2
  return c1.ScriptClip("""
    ca = c1.Trim(current_frame, -1)
    cb = c2.Trim(current_frame, -1)
    ca.WriteHistogram("hist1.txt", 1)
    cb.WriteHistogram("hist2.txt", 1)
    ca.ColourLike("hist1.txt", "hist2.txt")
    """)
}

Thanks, Antcufaalb.  I'll have a go with avs2avi; however, as I can't encode with x264 either, I'm not sure it will help.

I would also like to thank Andrea, who sent me this via PM.

I had initial problems maybe be due to the fact I used wrong avisynth.dll and/or setmemorymax/setmtmode - to be sure, I downloaded avisynth 2.6, and don't use setmemorymax/setmtmode when using colourlikeFBF.

So, yes, I definitely have not problems with colourlikeFBF.

By the way, when I had them, the picture was clearly not "colorliked" and an error message appeared on the screen.

Hope you could solve your problems soon!

I think this confirms that it's a problem on my end and not the filter/function.

Okay, neither the beta of Virtualdub nor avs2avi worked. 

avs2avi input.avs output.avi -c LAGS

Here's the error message.

Runtime Error!

Program...

This application has requested the Runtime to terminate in an unusual way.  Please contact the application's support team for more information.

Well, I tried rendering the script on another computer, and the same error occurs.  I guess this filter doesn't like me.  Are you guys using ColourLike_25Aug05.dll and feeding it RGB32?

AntcuFaalb said: Does ColourLikeFBF work with AvsPmod's preview?

It does.

AntcuFaalb said: OK. Does it work with AvsPmod's "analysis pass"?

The analysis pass begins but stops at around the same point that Virtualdub stops rendering, judging by the progress bar.

I don't use Avisynth MT, so I don't think I can be using more than one thread.

I know it sounds like I'm being a pain, but I'd rather not.  I've tried uncommenting everything but the part that applies Colourlike, and it makes no difference.

a=Avisource()

b=Avisource()

ColourLikeFBF(b,a)

The relevant part is written like that.  If there were a syntax error, I would receive an error message upon opening my script.  Is the length of the movie a possible factor?

AntcuFaalb said: Do `a' and `b' have the same number of frames? Are they both in the same color-space (RGB32)? Does a.info() and b.info() look more-or-less the same?

Yes.  :)

Try experimenting with two different (shorter!) sources. Are you still experiencing the same problem?

No!  I successfully rendered a short clip, so it might be the length, but I'm starting to wonder if it's the external drive from which I'm reading.

Thanks for the help so far.

I have successfully ruled out the hard drive's being the issue.  It might be the length of the clips.   I have no clips of comparable length to hand and don't fancy ripping two versions of a similar length film to my hard drive to test it out.    I'm about ready to give up, to be honest.