Chewtobacca

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?

romeo must die another day in paradise lost in space jam

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.

It might refer to this.

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

It does.

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?

Haha!  But I think dies --> die breaks xhonzi's rules, xhonzi.

I considered

robot chicken little big man on fire in the sky captain and the world of tomorrow never dies irae

but Robot Chicken without the subtitle probably doesn't count.

chicken little big man on fire in the sky captain and the world of tomorrow never dies

_,,,^..^,,,_ said:I thought to do it some months ago, but as it seems the interest is near zero, I don't know if I'll do it... a lot of work, captures, alignment...

If it's too much work, don't bother, but there would certainly be interest from me.  Because of the techniques that you've been developing recently, I want to see what you produce this time round.

captainsolo said: If you want to see what the film should look like, the initial MGM DVD releases of FAFDM and GBU are correct.

Thanks for the info on the night filter.  I'll have a look at my R1 disc of FAFDM.

I don't believe that the old MGM DVD of TGTBATU is correct though.  It looks very faded compared to the Italian BD.  My money's on the Italian BDs of all three films being closest to the intended looks.

Fistful looks like all the US prints which were sourced differently due to rights issues.

I'm not sure I understand what you're saying here.  Is it that because AFFOD's color timing looks consistent despite all the prints being sourced from different places it is likely to be correct?

The Alien material shown above seems to follow the template for coloring set by the Blade Runner Final Cut. That's one I'd love to correct back to the original, because though nice looking at first it doesn't really fit.

I agree that BR:FC is almost certainly removed to some extent from the original look, but I've no idea what the original look is.  The first DVD looks horribly red.  (And Alien doesn't look appreciably similar to the FC to me.)

That's interesting.  To be honest, neither of them looked like DE, but I guess that's down to the choice of shot. :-)

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.

The clips flash past really quickly when played in VLC (or whatever) because they are so short.  It's not easy to decode them, but I managed with ffmpegsource2.  They look good though.  I guess DE is on the bottom.

Andrea, this looks interesting, but why do you put h.264 in an AVI?

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.

That's an interesting concept.  Another potential pitfall is, of course, that a number of PAL LDs and DVDs use NTSC masters e.g. the SW and ESB GOUT DVDs.

I do too.  Good work, Andrea!

I suppose you could upload only the video track and let people mux it with whatever they like.

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")
    """)
}

I'm using the ColourLikeFBF() function. Whenever I render my project, I receive a livelock in VirtualDub.

Dub: I/O thread has not cycled for ten seconds -- possible livelock...

I have googled the problem extensively and tried the following things, to no avail.

• setting priority to idle
• adding SetMemoryMax() to the script
• rendering to a different codec
• updating my graphics driver
• encoding with x264 rather than sending the script to VirtualDub

The livelock always occurs at the same point. The render never completes. The error message repeats every ten seconds. Has anyone experienced this problem with ColourLikeFBF()?

At first I thought it was because I was rendering to an external hard drive, but when I tried an internal one I received the same error message, as well as the following one.

Dub/IO-Video error: Unknown (80004005)

I checked the output, and it breaks off exactly where ColourLikeFBF kicks in.  I have a good computer with 16GB of RAM. There is nothing else in the script that might be causing the problem because I am using only Trim(), DeleteFrame(), DuplicateFrame() and a few colorspace conversions -- all simple operations.  Moreover, I have tried rendering only the section that uses ColourLikeFBF and experienced the same thing.

I would appreciate any help because this is driving me mad.

Frink is playing on +1/-1, not implying that you're a sock, ww12345.  At least that's how I read it.

NeverarGreat said:So is this how the collaboration aspect of projects such as Despecialized work? Someone sends the settings, another person uses these as a base for more scene specific work?

Yes.  An Avisynth script that applied your color-correction settings to the BD would be an invaluable resource.  It would also be good to have a script that undid the 2011 changes by splicing material from the German HDTV broadcasts into the BD.  When combined with your settings, the result would be a color-corrected 2004 SE – not a bad start to any project.

Your work looks fantastic, NeverarGreat.  It's shame that there's no way to transfer all your settings to Avisynth.

Andrea, I would find the best setting for the whole film, apply it, fall back on ColourLikeFBF() or RGBMatch (even though I know you don't like it much) for those scenes with noticeable artifacts, and just accept that they do not achieve results that are quite as good as one would like.  Some of the differences between your settings are so subtle that it is doubtful that anyone would notice in motion, so a few scenes in which the color correction is not quite perfect would not detract significantly from the overall experience. 

Anything else would take up too much time.  The results would never be absolutely perfect, even if you did take years.

For the extra scenes, I would rather have a mono downmix of the English DTS-HD MA than the Italian mono.  As far as I'm concerned, it's better to have the actors sound older than not sound like themselves.  If there is a remaster, however, I hope it's the US theatrical because that's my preferred cut of the film.