hevc-aq "production-ready"?

[tormento]

Wouldn’t be just easier to feed aq with significative bit binary? I.e. 010 would be much easier to remember than mentally convert bin to dec every time.

[rwill]

Wouldn’t be just easier to feed aq with significative bit binary? I.e. 010 would be much easier to remember than mentally convert bin to dec every time.

For the mentally challenged, the Windows Calculator should be able to convert binary to decimal.

[jpsdr]

Wouldn’t be just easier to feed aq with significative bit binary? I.e. 010 would be much easier to remember than mentally convert bin to dec every time.
No, it was easier for me to deal with a number instead of a string, both for the parameter interface and for parameter analysis.

[Boulder]

Also in this case, I'd say that you either use --aq-auto 2, 6 or 10. Make a note of those somewhere and you'll never need to do binary math (at least in this context) again.

[Guest]

Been doing a little bit of "testing" :-

x265 [INFO]: HEVC encoder version 3.6+8+50-e89bec48b [Mod by JPSDR using mod by Patman]
x265 [INFO]: build info [Windows][MSVC 1928][64 bit] 10bit

or

x265 [INFO]: HEVC encoder version 3.6+8+50-e89bec48b [Mod by JPSDR using mod by Patman]
x265 [INFO]: build info [Windows][GCC 13.1.0][64 bit] 10bit


--auto-aq 0 (default x265)
x265 [INFO]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1


--auto-aq 1
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto / 1.0(1.0) / 32 / 1


--auto-aq 2
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-hyst / 1.0(1.0) / 32 / 1


--auto-aq 3 (same as #2)
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-hyst / 1.0(1.0) / 32 / 1


--auto-aq 4
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-hdr / 1.0(1.0) / 32 / 1


--auto-aq 5 (same as #4)
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-hdr / 1.0(1.0) / 32 / 1


--auto-aq 6
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-hyst-hdr / 1.0(1.0) / 32 / 1


--auto-aq 7 (same as #6)
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-hyst-hdr / 1.0(1.0) / 32 / 1


--auto-aq 8
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-aq5 / 1.0(1.0) / 32 / 1


--auto-aq 9 (same as #8)
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-aq5 / 1.0(1.0) / 32 / 1


--auto-aq 10
x265 [INFO]: AQ: mode / str(edg) / qg-size / cu-tree : auto-hyst-aq5 / 1.0(1.0) / 32 / 1

=======================================================================================

x265 [INFO]: HEVC encoder version 3.6+2+13-9a3dac6e5 [Mod by Patman]
x265 [INFO]: build info [Windows][GCC 13.2.0][64 bit] 10bit

x265 [INFO]: AQ: mode / str / qg-size / cu-tree : auto / 1.0 / 32 / 1

[benwaggoner]

Been doing a little bit of "testing" :-

Any interesting results so far?

[Guest]

Any interesting results so far?

Sorry Ben, I actually haven't done any encodes, I was more interested in what the x265 commands were in reference to the --auto-aq number(s).

ATM I am using Patman's very latest build (posted yesterday)