HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Settings.txt Part 2 of 3 : Post #2 of 6
Code:
int show Range 0-5
MODES 0 1, and 2 when Decimate == false:
0 Off (Default in MODE 2 only)
1 Show colored block in top left hand of clip when blend detected.
Blue block for 1st blended frame, Red for Second
2 Show blend detection only as in:-
FFF ExBlend a b ?1RPSHOLIMD
FFF shows the frame number
a & b show '-' No Blend, '1' 1st Blend, '2' 2nd Blend
a & b will usually be the same, 'a' is the used detection, which may
have been newly calculated or pre-calculated and stored in a file.
'b' is shown as calculated by the metrics, it is possible
that this is different from a pre-calculated detection.
? is the MODE flag which may be displayed as '¿' (an upside down question
mark) meaning Free running mode 0.
A '?', meaning Mode 1, scan and store mode, where ExBlend creates a precalculated
data file. '!' displayed means Mode 2, Pre-calculated mode, where it will use
data file saved in mode 1.
The '1' flag above, represents the DISP (Display) mode setting and can be
'0', '1', '2', or '3', (the missing mode '4' is not valid unless MODE 2 and Decimate==true
where metrics are different).
'0' represents, disp=0, the original blended clip is returned.
'1' represents, disp=1, ExBlend default returning an identical pair
of unblended frames replacing the blended ones.
'2' represents disp=2, which returns an unblended frame for the first of a blend pair and a
copy of the frame following the blend pair for the second blended frame. This is the SRestore
compatible mode.
'3' Represents disp=3, where the component frames which would be merged together to create the final
recovered frame are returned. In the first blend position, the left component frame is returned and the
right when in blend index 2 postion. You would not in most cases be interested in this.
This setting can be used to view the different return frames using metrics
mode to examine what a frame looks like and the metrics reported for that frame.
The 'R' (RATIO) flag will be displayed hilited at any time the ratio
is not within expected bounds, including during the AUTO PAL detection
period (if it was a 25 FPS clip originally) but will disappear once AUTO
PAL has switched.
The 'P' (PAL) flag indicates that you are in PAL mode. If orange,
then the 'P' flag indicates that the Autopal switch was activated
when the Exblend() argument was set to 'pal = -1' (MODE 0 ONLY, auto detect pal).
The 'F' (FILM) flag indicates Film, if hilited, means that the Autopal switch
was erroneously activated and indicates that you should restart with the argument
set to 'pal=0'. the P and F flags share the same position on screen and
cannot be set simultaneously.
The 'p' (lowercase) flag is shown when 'Auto Detect Pal' is in operation and will
switch to either 'P' or 'F' at frame 1500 where PAL is either detected, or not.
The 'S' (SEQUENCE) flag will display when ExBlend() falls out of
sequence. 1, 2 or HINTED is considered in sequence. 0 is considered out of sequence.
If hilited, means that the current frame is where it went out of sequence.
The 'H' (HINTED) flag indicates that the frame has been hinted.
When Exblend() finds a blended pair, it presets 3 frames on either
side of the blend pair to hinted (NOT-BLENDED), or 4 either side if in
PAL mode.
The 'O' (OVERRIDDEN) flag indicates that the used detection, differs
from the metrics blend detection, this is most likely to happen in static
scenes where false blend detections are overriden by the hints to be
unblended. Will be hi-lited in orange if override not due to hinting.
There is no need to be too concerned about a lot of overrides, the hints
are intended to allow the detector to be quite zealous in its detections.
The 'L' (LOCKED) flag indicates that the (previously EXPERIMENTAL) locking function
has locked onto the sequence dispite a blend detection not being found.
This filter outputs a list of LOCKED frames which can be viewed using DebugView,
or to the logging file.
The I (IGNORED) flag is displayed in the case where the 'merge delta'
exceeds ithresh. The 'I' flag is in Orange if the current frame is
ignored and normal if any frame was ignored (stays on).
Extra 'ignored' info is shown when show=5.
This filter outputs a list of IGNORED frames which can be viewed using DebugView,
or to the logging file.
New in 1.02, writes "New Sequence" and "Lost Sequence" debug messages, can view
in DebugView or in logging file. If you see several "lost sequence", "new sequence"
type messages (in close proximity) in the logs, this is probably down to a false
detection following a lost sequence, this is a prime component for the 'override'
functionality of v1.02.
The 'M' flag denotes a manual override is in effect at the current frame. These
are set using the "override" arg to use the override command file.
The 'D' flag shows if an unblended frame is reconstructed using the DClip (CompUB)
and is hi-lited if adjacent frame also comes from Dclip (CompUB==2).
Show == 2, will also show the colored block in the upper LHS of clip.
3 Show Metrics:-
<--Prev<---><CUR><--><Next->
MD x.xxxx x.xxxx x.xxxx x.xxxx
FD x.xxxx x.xxxx x.xxxx x.xxxx
^ ^
2 1
Right one Hi-lighted for 1st detected blend and Left for 2nd, if blend
pair detected, MD will be smaller than FD and also smaller than the MD
entries on either side. The next frame comes in from the right.
'FD' is Frame Delta (difference) and 'MD' Merge Delta. FD is the delta
between the frames in the clip, when hi-lited it is the difference
between the two frames of the DETECTED blended pair.
MD is the difference between the two copies of the unblended component
frames (that would be merged together to 'iron out' artifacts for the
final recovery frame).
The MD:FD comparison detects that it is a blend (MD should be smaller
than FD), and the MD to MD on either side comparison detects whether
it is in the 1st or 2nd blended pair position. (MD in the hi-lited column
should be smaller than those on either side).
Show == 3, includes show 1 & 2 metrics.
4 Show Blend count and ratio
BlendPairs =w (max=x)
Ratio =y (z%)
Gives a count of detected blend pairs and the ratio of
Unblended to BlendPairs. When you have scanned from start to end of the
clip (without jumping about or going backwards) 'Ratio' should give a
result of 3.xxxx for 24 FPS original and 4.xxxx for 25 FPS original,
meaning 3 good frames and 2 blended for 24 FPS or 4 good and 2 blended
for 25 FPS.
Should only scan forward (Otherwise, BlendPairs & Ratio will
be wrong). Following ratio, the percentage of detected blends is displayed,
based on the current pal mode, this may give a more humanistic idea as to
how well ExBlend() is doing.
Following BlendPairs (max=x) is displayed where x is the maximum number of
blend pairs that could exist in the clip using the current PAL mode, this
will change if AUTO PAL switch is activated. The max value displayed assumes
also that the clip stays in sequence throughout, if it does not, the true
max value could well vary from that shown and the true percentage of blends
found could well be higher or lower than shown, but not by much (small
fraction of a percent, probably).
Also note, ExBlend() may not detect the first or last blends in a clip due
to it needing 3 frames both before and after the current frame to do it's
detections.
Show == 4, includes show 1 to 3 metrics.
5 Shows Lock, Sequence, Overridden and Ignored counts as in:-
[Default when NOT [MODE==2 and Decimate ==true)]
LC=w SC=x OC=y IC=z
In addition, if IC is non-zero, then
IMN[f1]=x.xxxx
IMX[f2]=y.yyyy
Will be displayed where f1 and f2 indicate frame numbers where the minimum
and maximum merge deltas occured that exceeded 'ithresh' and so were
ignored. You might want to investigate these frames with current ithresh
setting and also with ithresh set to 100.0 (ithresh IGNORE switched OFF).
If particularly curious, you might want to set ithresh to 0.0
(Ignore everything), do a complete scan and take a look to see what the blend
with the worst merge delta looks like, if bad, then lower ithresh a little
(tiny weeny bit below y.yyyy). Dont leave ithresh set to 0.0 for the final
scan as this will avoid almost all detections.
New to v1.02, the 'disp' arg allows return of the original blended frames,
or the de-blended frames and so you could say create
a stacked display to show both before and after with metrics, also better than
the above suggested, changing of ithresh.
Seeking to frame zero will reset the statistics. NOTE, if clip Trimmed, then
may not ever go to frame zero, and so frame 0 statistics reset may not work.
(an offhand example of where this might occur [have not checked this] might be
where you script eg "Last.Trim(100,0).Exblend()" so that a new clip never was
produced, ExBlend was invoked on a part of a clip, and so frame zero will not
be encountered within ExBlend)
NoLMN[f]=x.xxxx
L=y.yyyy LMX[f]=z.zzzz
The above is connected to the lockthresh argument of Exblend().
See Lockthresh.
MODE 2, when Decimate==true: (Defaults OFF, for MODE==2, Decimate==true).
show == 0, Off
show > 0, show different metrics.
as In:-
'39 ] Using 48 (* SDDS)'
where '39' is the decimated frame number, 48 is the source clip frame, and '(* SDDS)'
indicates an unblended frame using the source clip for adjacent frames and the DClip
frames for the blended frames.
string ExBfile Default "ExBlend"
ExBlend Project file base name. Used to create any required logging file eg
'ExBlend_1.LOG' when used in MODE==1.
Also used in creating filename of file to store 'mode' 1 Scan and Store data and to also load data file
for mode 2 Pre-calculated mode.
Creates (by default) in local directory where AVS file is located.
In Mode 1, also creates a Decimated Frames command file, by default, 'ExBlend_Decimated.TXT'
for use as a command file giving frame numbers of unblended frames after decimating in MODE==2.
bool ver true or false, Default False
Just shows the version number of ExBlend(), Perhaps other filter writers should
consider whether showing version and copyright stuff serves any positive purpose
(other than ego boosting) when showing metrics. When ver=true, it will show
version info (Also a little ego boosting stuff), without interfering with any
important metrics. ALL args are ignored when 'ver==true'.
bool revip Range false (Off) to true (On), Default false (Off)
Reverses the metrics display as in:-
<--Next<---><CUR><--><Prev->
MD x.xxxx x.xxxx x.xxxx x.xxxx
FD x.xxxx x.xxxx x.xxxx x.xxxx
^ ^
1 2
It may seem more intuitive to have the first blend appear on the left
and the second on the right, but the frames come in from the left.
Last edited by StainlessS; 19th December 2018 at 00:00.
|