Never-Never-NEVER open file for reading until you think twice what mode (text/binary) of operation do you need!!
How to compare video metrics
There are specific databases which were subjectively tested. Ans MOS was calculated
for example
http://www.ponomarenko.info/tid2008.htm
you can download database and compare your metric to MOS by Spearman correlation
for example
http://www.ponomarenko.info/tid2008.htm
you can download database and compare your metric to MOS by Spearman correlation
SSIM metric for video
See good explanation is in
Title: Handbook of image and video processing
Title: Handbook of image and video processing
Author(s): Bovik A. (ed.)
Series: Periodical:
Publisher: Elsevier Academic Press
Series: Periodical:
Publisher: Elsevier Academic Press
Year: 2005
Edition: 2ed.
Language: English
Pages: 1429
ISBN: 9780121197926, 0121197921
ISBN: 9780121197926, 0121197921
Replace \n in Microsoft word
To replace new lines in word use "^13" whild-char. "^p" doesn't work :(
Tips for debugging of video processing console
Assume we have Visual Stusio solution for console that makes some video processing.
The console takes two input videos and generates the third video:
1) dataset1 conststs of videos set1_video1.avi and set1_video2.avi
2) dataset2 conststs of videos set2_video1.avi and set2_video2.avi
....
n) ....
It seem rather convenient to distrubute videos between folders. One folder for each dataset. Insise the folder we should give template names to files (e.g. video1.avi and video2.avi)
Therefore now we can set "Command Arguments" in "Project Properties->Configuration properties->Debugging" the same arguments for all cases and configurations,
The thing should vary is "Working directory" in "Properties->Configuration properties->Debugging".
Another usefull thing is setting "Environment". Just write there
PATH=%PATH%;<path to dll>
and you don't need to copy all dependency dll's in every debug folder.
The console takes two input videos and generates the third video:
Console.exe --input1 video1.avi --input2 video2.avi --output result.aviWhile debugging we need to run console on several datasets.
1) dataset1 conststs of videos set1_video1.avi and set1_video2.avi
2) dataset2 conststs of videos set2_video1.avi and set2_video2.avi
....
n) ....
It seem rather convenient to distrubute videos between folders. One folder for each dataset. Insise the folder we should give template names to files (e.g. video1.avi and video2.avi)
Therefore now we can set "Command Arguments" in "Project Properties->Configuration properties->Debugging" the same arguments for all cases and configurations,
The thing should vary is "Working directory" in "Properties->Configuration properties->Debugging".
Another usefull thing is setting "Environment". Just write there
PATH=%PATH%;<path to dll>
and you don't need to copy all dependency dll's in every debug folder.
Bjontegaard metric. Matlab script.
Bjontegaard metric (BD-PSNR) describes the distance between two RD-curved. I is useful to determine how big is the gain between "before" and "after" versions. Or determine what curve is better if they have complex form (for example, intersecting).
I found matlab script, that calculates BD-PSNR, but it was not correct. The limits of integration were wrong. Difference between two curves can be calculated only in the area of thein projections intersection.
Fixed script was verified by data provided the auther of the metric.
Download
fixed matlab script for BD-PSNR calculation
github
original paper (doc)
data for verification (xls)
Original publilcation:
G. Bjontegaard, “Calculation of average PSNR differences between RD-curves (VCEG-M33),” in
VCEG Meeting (ITU-T SG16 Q.6), Austin, Texas, USA, Apr. 2001
Subscribe to:
Posts (Atom)