How VHQ(s) works?

[rkingbo]

I mean how they affect the quality of I,P,BF? (Some say VHQ does not apply to BF,really?)

Thanks in advance...

[Koepi]

welcome to the board, rkingbo.

You might want to read the FAQ and the XviD guide where your question get answered. Usually it's our forum philosophy to use the search and at least read those guides/FAQs, and you agreed on doing that while signing for this board. No strike for you now, but please keep to the rules next time.

VHQ is in short:
0 - normal ME
1 - rate/distortion (RD) optimized macroblock mode decision
2 - additional narrow range motion estimation
3 - additional middle range motion estimation
4 - additional wide range motion estimation.

(If you keep your mouse over the VHQ-box for a while without moving, a popup will appear where exactly that is mentioned as well.)

VHQ isn't done for bframes (yet). Anyhow, the higher the VHQ level, the better the quality of the resulting p-frame.

Koepi

[rkingbo]

Thanks for your speedy reply.

(Further discussion in PM)

[virus]

Originally posted by Koepi
(If you keep your mouse over the VHQ-box for a while without moving, a popup will appear where exactly that is mentioned as well.)
not exactly ;)
"VHQ enables an additional search process to increase quality (much slower)". Would be nice to have your description added to the tooltip though.

BTW no offense intended, but I'm a bit tired when you devs keep answering "read the tooltip" when, as a matter of fact, some tooltips are still missing... just like the classic question: what is the allowed range for BVOP sensitivity? Read the tooltip, n00b! Too bad the tooltip has never been there... and this has been reported many times by so many different users ;)
again, no offense intended, I've read the thread on how to accept a gift properly, I agree that one should read the FAQ/use Search first and so on. Still, I'm a bit tired ;)

cheers :)
virus

[Soulhunter]

Originally posted by virus
Just like the classic question: what is the allowed range for BVOP sensitivity? Read the tooltip, n00b! Too bad the tooltip has never been there... and this has been reported many times by so many different users ;)Dont know what you complain about... :D

http://img7.imageshack.us/img7/3953/snap39.png


Bye

[virus]

@Soulhunter: :D :D :D

[sysKin]

LOL :D :D

Now, a mistery: the tooltip is there, and (for bvop sensitivity) says
Change the amount of b-frames in this zone. Recommended values are between -20 (almost no b-vops) and 30 (many b-vops).\nThe hardcoded maximum in profile/level will never be exceeded

The only explaination why it's not shown might be "The master bugadder added it". AKA me.

Radek

[virus]

you ask, I answer :D

I've just had a look at the RC4 sources.
Here's what I've found in \vfw\src\resource.rc

row 576: IDC_ZONE_CHROMAOPT don't match the actual string name on row 931 (IDC_CHROMA_OPT)

row 578: IDC_ZONE_BVOPTHRESHOLD_S for the ltext object
row 579: IDC_ZONE_BVOPTHRESHOLD for the edittext box
the string is named IDC_ZONE_BVOPTHRESHOLD_S (row 963-4), maybe ltext objects cannot have a tooltip? I can't remember. For sure there's an error on the edittext box.

...isn't that open source thing great? ;)

hope this helps :)
virus

[Koepi]

I got a PM from rkbingo, and i think the relpy of mine belongs into public so it is once more clarified what VHQ does:

[...]
I don't understand how you come to think it has anything to do with standard deviation, controlled i-frame degradation or anything like that.

As i wrote in my reply, it's a simple block-mode-decision in first place (yes, that is rate-distortion optimized "inter-, intra- or skipped-block" for every Macroblock of an image). After that, a further motion estimation step with different ranges (small, medium, wide) is done to further minimize bits needed.
[...]

sysKin, I hope I don't offend you when I write it's "simple" - people tend to fear complicated things, so I just wrote that, of course it's quite some mathematics behind that :)

Regards
Koepi

[rkingbo]

Originally posted by Koepi
I got a PM from rkbingo, and i think the relpy of mine belongs into public so it is once more clarified what VHQ does:

[...]
I don't understand how you come to think it has anything to do with standard deviation, controlled i-frame degradation or anything like that.

As i wrote in my reply, it's a simple block-mode-decision in first place (yes, that is rate-distortion optimized "inter-, intra- or skipped-block" for every Macroblock of an image). After that, a further motion estimation step with different ranges (small, medium, wide) is done to further minimize bits needed.
[...]

sysKin, I hope I don't offend you when I write it's "simple" - people tend to fear complicated things, so I just wrote that, of course it's quite some mathematics behind that :)

Regards
Koepi

Well, that was not my thought, I just pass the message and prove to the person who came up with that idea. Now, everything is clear(at least much clear) thank you.

[rkingbo]

Sorry, one more question:

Why VHQ is not currently available for B Frame?

[lordadmira]

Can't u describe VHQ as the radius within which the codec will look to see if the block moved to? What I haven't been able to find anywhere is algorithmic descriptions of all these various settings. Everything basically just says "good", "gooder", "goodest", and sometimes "most goodest". ;)

[lordadmira]

I found this old thread discussing VHQ.

http://forum.Doom9.org/showthread.php?s=&threadid=45746

It seems VHQ has something to do with the motion vector mode.