View Single Post
Old 30th March 2020, 13:49   #27  |  Link
Stereodude
Registered User
 
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
Quote:
Originally Posted by poisondeathray View Post
Interesting. You'd think higher precision @ 10bit operations would produce slightly better results
Yes, it seems counter intuitive.

Quote:
Matrix only applies to YUV<=>RGB transforms , so it's not applicable here. That I'm sure of for the internal functions. (I'm questioning my understanding of how avsresize works.)
There is talk about full vs. limited range in the matrix selection section, hence I thought it might have some impact, but apparently it's only used if going between RGB and YUV.

Quote:
VQMT scales the U,V planes to Y plane size, that might introduce some errors. I tried unchecking that option , but it would crash. It might be a pro version feature. Anyways it's the trends that are important
I found the same thing. Insta-crash.

Quote:
FWIW this is ffmpeg PSNR , and the abs. min value is higher , and the U,V averages are higher than VQMT - maybe some of the difference is from the VQMT UV scaling, not sure. Often there are slightly different calcs too between programs
PSNR y:65.979368 u:64.950274 v:66.120163 average:65.812176 min:59.375502 max:88.556475
I did the comparison in ffmpeg and got this: PSNR y:65.974546 u:57.684810 v:51.288692 average:57.718014 min:53.666230 max:88.556475

I also found that you want to make sure the two sources are exactly the same length or ffmpeg will give you erroneous numbers where as VQMT just uses the length of the shorter source for the comparison.
Stereodude is offline   Reply With Quote