Headers: qcomp=1.0 always?

[Comatose]

So, I just looked at the x264 headers on one of my encodes... and to my surprise I saw qcomp=1.0.

So I go and check my meGUI profile, and yeah, quantizer compression is set to 0.5.
I doubt it's a problem with meGUI, as the commandline it's showing has --qcomp 0.5.

Could it always be writing 1.0 to the headers, regardless of the real value?

[akupenguin]

If your setting of AQ is stronger than your setting of qcomp, then AQ replaces qcomp. (They affect some of the same decisions).

[Comatose]

Ah, I see :3 Thanks!

[LoRd_MuldeR]

According to the manpage:
--qcomp <float> QP curve compression: 0.0 => CBR, 1.0 => CQP

Just to clarify:
When AQ is enabled (at default) there is absolutely no difference between --crf and --qp mode ???

[MasterNobody]

According to the manpage:
--qcomp <float> QP curve compression: 0.0 => CBR, 1.0 => CQP

Just to clarify:
When AQ is enabled (at default) there is absolutely no difference between --crf and --qp mode ???
There is difference because with --qp mode AQ would automatically disabled so this would be really constant QP.

[LoRd_MuldeR]

There is difference because with --qp mode AQ would automatically disabled so this would be really constant QP.

Thanks for the info :)

BTW: Disable AQ when CQP mode is selected - is that done in the CLI/VfW front-end or in the libx264 library itself?

[Dark Shikari]

Thanks for the info :)

BTW: Disable AQ when CQP mode is selected - is that done in the CLI/VfW front-end or in the libx264 library itself?Its done in the parameter validation section of the encoder library.

[LoRd_MuldeR]

Its done in the parameter validation section of the encoder library.

Okay. So it applies to Avidemux as well...