The ClearView Command Line Interface only works
with the Broadcast I/O module; thus, it allows
the capture of video content from -- file, SDI, HD-SDI, Component, Composite,
and S-Video. Regardless of the input, the video is converted, based on user
choice, to fully uncompressed 4:2:2 Y’CbCr or RGBA. Any inputted video
sequence, regardless of dimensions, can be cropped or matted to fit into the
selected output raster.

Analysis begins on any two video sequences which
share the same resolution and color space. The goal is to calculate the video
quality without human intervention – termed objective analysis. ClearView
calculates the pixel differences between the video sequences and displays them
as A-B with threshold and add-back. Add-back shows where pixels are greater
than the threshold. Without Add-back shows the actual value of the pixel
differences. The Pixel Value tool shows the Y’CbCr or RGB values at the pixel
location for each video sequence.

ClearView applies various objective metrics to
each frame of the video sequences, generates graphs, applies thresholds and
logs the results.

Output rates are independent from input rates;
so any video sequence can be outputted at rates in excess of 120Hz. The user
has control over shuttle rates, jog, color look-up tables, zoom/pan, and field
display. The video sequences are previewed within the ClearView Interface and
sent to HD-SDI, SDI, Component, S-Video, and Composite. Normally, the video
sequences are shown on the same display, but each video sequence can be
outputted via a separate HD-SDI/SDI link. Video Sequence or a portion of the
video sequence can also be exported as uncompressed BMP, RAW or AVI files.

CVServer resides on the machine running the ClearView
software. It converts the CV commands to appropriate messages to start
ClearView. CVServer must be activated before you can run a CV command. It is
preferred to place CVServer in C:\Program Files\VideoClarity\ClearView since
the path is already set.

When running CVServer from the command line there needs
to be a port number and timeout. CVServer communicates through port 7. The command line should look like
“cvserver<space>7<space>5”.

CV is the command line processor. It communicates via
sockets to CVServer. It reads the Config file to find out where the ClearView
machine sits on the network. A list of CV commands is in the table of contents
above. Each command is detailed below.

It is preferred to place CV in C:\Program
Files\VideoClarity\ClearView.

The system
path is a list of folders, separated by a semicolon, which identifies the
folders that the system should search when looking for files that are called
from the Run dialog box, command line, or other processes. Normal program
installation changes this path to include the program's installation path. To manually
change the system path, perform these steps:

Source material for a reference sequence can be either
imported from file or captured from ClearView’s SDI Input. The “Reference Sequence” will be output as
uncompressed SDI video to the DUT (Device Under Test) video input.

Output Source Video Sequence from ClearView HD/SD-SDI
to DUT

ClearView can be told to start playing at
anytime. If the DUT has a known
startup delay, ClearView can first pause on frame 0 for x number of seconds
before starting to play the sequence.
This ensures that the captured result contains frame 0 of the
reference sequence. Alternatively,
measurements can be set to start at frame X instead of frame 0.

Device Under Test processes video and outputs uncompressed
video

This is most likely a video encoder, video processor,
or video decoder/STB. ClearView
outputs uncompressed video to the DUT, and accepts uncompressed video input
or compressed/uncompressed files.

Output from DUT is captured by ClearView to a new
sequence (GoldResult)

ClearView can simultaneously playout and record up to
1080i (or more precisely anything that requires single-link SDI). If you
exceed the single link requirements, then ClearView can play or record.

Perform Auto Alignment. Create safe inpoint/output for testing

After ClearView has recorded from the DUT, place the
original sequence in Viewport B and the newly recorded sequence in Viewport
A. Advance to the 2nd frame (or beyond) of the original sequence
and run automatic temporal then spatial alignment. In addition, you can run
normalization to equalize the brightness/hue between the videos.

Visually Inspect GoldResult. Run Metrics to define testing thresholds

Run objective metrics on the original and recorded
sequences and apply a threshold creating a pass/fail condition.
Alternatively, you can simply view the results and make your own subjective
analysis.

The Video Clarity Clear View Command Line Interface
allows the user to control any ClearView machine, which can be seen (open
socket call). The general command structure is as follows: CV CommandName
CommandArguments. The command is echo-ed back to the console timestamped, and
the results of the command are displayed (timestamped) on the next line.

Notes: If
<iFirst> AND <iLast> are omitted then the current frame set for
first and last will be returned for the corresponding viewport, if <iFirst>
AND <iLast> are used the first/last frame used for the corresponding
viewport will be changed

Input: cSequenceName Any sequence name that conforms to
Clear View sequence
naming
rules
iFirst First frame to
be exported
iLast Last
frame to be exported cDestFile Full path and name of
file to be createdOutput: Received:
Success
Received: Failure

Notes: There
are two different syntaxes for Import.
The syntax for playlists and logs does not have any more parameters than
the location of the file. The syntax for
files includes where to load the file as well as first/last frame to import.
Path must be from root, i.e. C:\My Clips\Image.avi not \Image.avi
If the source path or sequence name has spaces they need to be enclosed by
double quotes

If the first and last frame
parameter are omitted all frames will be imported
The first frame must be less than or equal to the last frame.

Description: Autoalign aligns the sequence mapped to Viewport A to Viewport B,
auto-align uses the currently selected frame in Viewport B for alignment

Syntax: autoalign
bMaxamizeAlignedLength bIntelligent

Input: bMaxamizeAlignedLength OPTIONAL
- 0
– Off

1 – On

bIntelligent OPTIONAL
- 0
– Off

1 – On

Output: Received: Success
Received: Failure

Example: cv autoalign

Notes: bMaxamizeAlignedLength
is an option that will allow the sequenced to become the longest possible. If the you had the same sequence in viewport
A that was in B and set the first frame in B to 10 and you aligned without this
option you would get two sequences that ran from frame 10 to the end. If you check this option Clearview would
first align them to 10 and then determine that there can be 10 more frames
added to the beginning of each sequence and they would be frame 0 to the end.

Notes: If
one omits the first AND last frame, the previous set first/last frame will be
used
-1 in place of the first frame will set the first frame
to 0
-1 in place of the last frame will se the last frame to
the last frame in the sequence
If the sequence name has spaces the
sequence name needs to be enclosed by double
quotes

Notes: If
one omits the first AND last frame, the previous set first/last frame will be
used
-1 in place of the first frame will set the first frame
to 0
-1 in place of the last frame will se the last frame to
the last frame in the sequence
If the sequence name has spaces the
sequence name needs to be enclosed by double
quotes

When
doing a dual record you must run videoInput twice, first setting logical input
0 then logical input 1

The logical input should always be 0, except
when doing a dual input. It is important to note that the logical input
is not the same as the SDI input. Go to the broadcast tab, if you are
inout mode there is only Input 1 shown (logical input 0). If you go to
dual input you have Input 1 (logical input 0) as well s Input 2 (logical input
1). When doing a dual input you will need to run cv videoinput broadcast twice,
once configuring logical input 0 and a second time configuring logical input
1.

Notes: If
the sequence name has spaces the sequence name needs to be enclosed by double
quotes
There are two record commands the first one listed as well as the first example
is an example if doing a single input.
The second one listed and second example is if doing a dual input.

Notes: bLimitNumerator
limits the numerator in the PSNR metric.
When off the numerator is from 0 -255 for all three components. If
turned on, the numerator is limited to 16 – 235 for Luma and 16 – 240 for
Chroma. These are 8 bit numbers, for 10
bit the ranges are a multiple of 4.

eViewDistan
– is how far the human tester was standing away from the display

cFieldMode – this should be
set to Auto which allows the system to do the right thing. For interlaced video
sequences, the field mode should be field. For progressive video sequences, the
field mode should be frame. You can override this.

cDeinterlace Flag - If you are
calculating interlaced data in frame mode, then you need to choose a de-interlace
method. In general, you should calculate fields in JND field mode.

` cColorModelingFlag - This is
automatically set based on whether we are in HD or SD. This is an override.
iMaxDisplayLuminace - This is the luminance of the viewed display.

cMapLocation – This is where
the map files are stored on the hard disk array. The files are viewed using a
command line program called vpseqw32.exe.

Description: DMOS will perform a DMOS on the currently
loaded sequences

Syntax: dmos
<LogFileName> <bChroma> <dThresholdY> < bSpatialize >
<bNormalize> Input:
LogFileName Path to place the log file and name bChroma OPTIONAL – A threshold in which if
the mos result is above this
number
the frame is considered bad and added to return number

dThresholdY OPTIONAL – A threshold in which if the mos
result is above this
number
the frame is considered bad and added to return number

Notes: One
should start any metric from Stop mode in Clear View
If one omits the threshold value, the number of failed
frames will always be 0
If the log filename has spaces the log file needs to be
enclosed by double quotes

If the log
file does not contain a path, the Clearview.exe path is used

To turn on
Chroma a value must be set for dThresholdChroma (even if it is 10)

Syntax: jnd
<LogFileName> <dThresholdY> <dThresholdChroma>
< bSpatialize > <bNormalize> Input:
LogFileName Path to place the log file and name dThresholdY OPTIONAL – A threshold in which if the jnd
result is above this
number
the frame is considered bad and added to return number

dThresholdChroma

OPTIONAL – A threshold in which
if the jnd result is above this
number
the frame is considered bad and added to return number

Notes: One
should start any metric from Stop mode in Clear View
If one omits the threshold value, the number of failed
frames will always be 0
If the log filename has spaces the log file needs to be
enclosed by double quotes

If the log
file does not contain a path, the Clearview.exe path is used

To turn on
Chroma a value must be set for dThresholdChroma (even if it is 100)

Notes: One
should start any metric from Stop mode in Clear View
If one omits the threshold value, the number of failed
frames will always be 0
If the log filename has spaces the log file needs to be
enclosed by double quotes
Threshold values
must be used if you would like to use NoRef, Spatalize or Normalize

Values

If the log
file does not contain a path, the Clearview exe path is used

Notes: One
should start any metric from Stop mode in Clear View
If one omits the threshold value, the number of failed
frames will always be 0
If the log filename has spaces the log file needs to be
enclosed by double quotes

If the log
file does not contain a path, the Clearview exe path is used

Notes: One
should start any metric from Stop mode in Clear View
If one omits the threshold value, the number of failed
frames will always be 0
If the log filename has spaces the log file needs to be
enclosed by double quotes

If the log
file does not contain a path, the Clearview exe path is used

Fix: Open a second dos window and run
“CVServer 7”, this will open a connection between
CVServer and Clear View witch passes command through port 7 of the
machine. Assure that you run CVServer,
while it is your systems path or from C:\Program Files\Video
Clarity\ClearView\.