>then change the resolution (vertical and/or horizontal) until they align perfectly (for example, 1924x1080, or 1916x1072 etc) - try also 1pixel variation, using YV24
Use aspectRatio params instead. And angle params for rotation (range -1 to 1 for beginning) . Aspect ratio is width divided to height.
If your over!ay resolution is 1920x800 then both aspectRatio params are equal to 2.4 by default. Set range instead of fixed default value: aspectRatio1=2.3 and aspectRatio2=2.5. Extend range if necessary. After testing leave minimal appropriate range.

>But, when the alignment is good, the plugin does wonders, working usually in more than 99% of the frames!
In all my hybrids 100% frames are overlaid. With manual correction using editor of course. Pan&scan episodes needs higher attention.
I've made hybrid of matrix using BD and open matte remastered Hdtv/web. All frames could be processed. Open matte includes some unremastered scenes with different AR. But it is possible to match color of them to BD. I have statFile but it for old versions of plugin in different format.

Using this amazing plugin, and slowly knowing how to let it work perfectly, almost always.

The following hints are from my experience, related to AAP-AR, and led to great results.

• try to "define" as much as possible the lower quality source - noise reduction, sharpening etc. - to be closer to the higher quality one; an ATV recording would probably create a lot more problems than a DTV one, let alone a DVD 1:1, which probably is the best SD source you can get (when available)
  
• as said before, first scale the lower quality source to be spatially aligned with the higher quality source BEFORE feed it to the script; yes, of course is it possible to set aspectRatio range, but I think it would be more time consuming for the script to guess the right AR instead of feed it with the "right" one - unless there are many variations and/or different angles.
  
• beware that sometimes, there are shots which need a different scaling - for example, the CCTV shots in Resident Evil are compressed horizontally, and must be streched to get the proper AR
  
• luma is much more important than chroma - even one single step in contrast and/or brightness could make the difference, in some particular instances, between a wobbling and a perfect alignment; so, if you note that a particular shot change frame aspect between a frame and another, modify contrast and/or brightness (and/or gamma) until it would be rock solid stable
  

Again, thanks to random.next for this wonderful plugin! and forgive my "do-not-follow-the-instructions-given" way of using it!

I want to emphasize the fact that a tiny variation in brightness and/or contrast could lead to misalignment even in the middle of a shot; don't think chroma difference would count here; a tiny correction, like brightness +/-1 or contrast +/-1 could make the difference here.

I can say that almost all (or all?) of the times the plugin is fooled, is in frames that are almost, or totally, of the same color, like white frames after an explosion, or fade in/out.

So, I give it a vote of 99/100 - the only quite important missing thing (to me, at least) to be perfect is a setting for a custom border color; I hope the author, the great avisynth guru random.next, would add it in a future release...

Having an issue with AutoOverlay (as it is now called).

Runs fine for probably 99% of the movie, but sometimes it breaks out, like here:
    (click to see large image)

The very same scene is fixed just a few frames later, but these I just can't get right.

Here's my code:

There's lots of random frames across the movie that break out like this. Most seem to have something in common, namely that they all tend to have big flat areas or are rather dark. It's still kinda ridiculous imo, because these frames were almost perfectly aligned to begin with (both same resolution too). The color is a bit off, as the master is different, but there's no way to make a blanket change from one to the other, as it varies per scene.

I'd try the maxX variables and stuff like that, but in some sparse scenes a bigger change is actually necessary, so I'm hesitant about that.

Edit: Tried out minY and maxY. Doesn't work, although it minimally improves the result. Plus, when I set these parameters, suddenly the tool ignores the crop mode and starts cropping despite mode=3.

Edit 2: Maybe the problem here is that the brightness is different, as spoRv pointed out in his own post. Thus the sky in one image is roughly as bright as the woods in the other image, leading to an error. But looking at the image, this is a ridiculous error. I suggest therefore that some other measure than average Diff be offered, where individual details have more weight over big flat areas when calculating the Diff. That would probably solve the issue here.

Edit 3: Applying Levels to the clip that fed into OverlayEngine() with gamma adjustment helped in this particular case. Thx spoRv

Try also backwardFrames=8 and forwardFrames=8, it should help, I think...

Thanks spoRv. Sadly that is not an option, because in this case the sources are not stabilized to each other, so I had to define the backwards frames as 0 explicitly, as advised by the author of the plugin. Though I wonder if I need to put forwardFrames to 0 as well to get optimum results.

(2018-02-18, 06:22 AM)TomArrow Wrote: in this case the sources are not stabilized to each other

Please explain better.

(2018-02-18, 03:53 AM)TomArrow Wrote: Here's my code:

Code:

config=OverlayConfig(subpixel=2,minOverlayArea=80,minSourceArea=80,scaleBase=1.1,minSampleArea=200,requiredSampleArea=500,acceptableDiff=10)
OverlayEngine(srcdehalo2.ConvertToY8(), src2.ConvertToY8(), configs=config,editor=false,maxDiff=10,backwardFrames=0,forwardFrames=0)
OverlayRender(srcdehalo2.ConvertToYV24(), src2.ConvertToYV24(), debug=true, noise=0,\
upsize="Spline64Resize", mode=3, gradient=10,coloradjust=2,width=1920,height=1080,opacity=0.5) 
ConvertToRGB24()

scaleBase=1.1 Such value produces a very long sequence of downsized sample images. Default is good in most cases. In all that I had.
minSampleArea=200,requiredSampleArea=500 - too small values. To understand - resize your clips to the such area (width*height) and see that all details are lost.
acceptableDiff=10 - this parameter is used by plugin only if you have a sequence of OverlayConfigs: OverlayConfig(...) + OverlayConfig(...). With one config it takes no effect.
With backwardFrames=0 other prediction params such as maxDiff, forwardFrames take no effect.

To prevent misaligment try OverlayConfig params as follows:
minSampleArea=2000,requiredSampleArea=5000, correction=2, branches=3, downsize="Spline36Resize", upsize="Spline36Resize"
With correct minSourceArea, minOverlayArea, aspecRatios and angles of course. If you have unstablized different transfers then they have different in-frame aspect ratio in most cases. Check it in difference mode.

(2018-02-18, 06:39 AM)spoRv Wrote:

(2018-02-18, 06:22 AM)TomArrow Wrote: in this case the sources are not stabilized to each other

Please explain better.

Means that the masters are slightly different and you can't reuse alignment frame-to-frame, because each master has different micro-movement from frame to frame, probably due to the way it's been stabilized (or not stabilized) or simply due to a different transfer where the film wobbled slightly differently. Make sense?

(2018-02-18, 06:05 PM)TomArrow Wrote: Means that the masters are slightly different and you can't reuse alignment frame-to-frame, because each master has different micro-movement from frame to frame, probably due to the way it's been stabilized (or not stabilized) or simply due to a different transfer where the film wobbled slightly differently. Make sense?

Makes sense.

Do you want to make an AAP-AR version, or just use both to improve overall quality?