![]() |
Link #1 |
x264 Developer
Join Date: Feb 2008
|
x264: Adaptive Quantization and You!
There's been quite a lot of improvements to x264 lately, mostly speed-oriented. Indeed, performance has gotten 10-20% faster in just the past 3 weeks, depending on what settings you use. The latest builds can be found at x264.nl.
But there has recently been one very major change that will certainly affect anime encoding with x264: adaptive quantization. Now in the official x264 and enabled by default, variance-based AQ (VAQ) attempts to improve quality in flatter areas of the image at the cost of more complex areas of the image. Generally, this helps resolve the classic problem x264 has of overflattening and blurring out fine detail in an image. Even in anime, which it wasn't designed for, the result can be pretty beneficial: ![]() On the other hand, especially for those groups that love to release subs at absurdly low bitrates, AQ might not always be beneficial, since the only way to get acceptable quality at stupidly low bitrates is to just accept the blurring of fine details. tl;dr: if you're one of those people who loves to make 40MB x264 rips of animes, you might want to try turning AQ off and seeing if its better or not to your eyes. As a general warning, AQ redistributes bits between frames, so some scenes will lose bits and others gain bits as AQ sees fit. |
![]() |
![]() |
![]() |
Link #2 |
Part 8
![]() |
Or if it's sort-of breaking stuff, you can reduce the strength with --aq-strength. My tests with low-detail low-bitrate anime have basically shown there's very little difference either way. Obviously it produces magic & stars at high bitrates though :-)
Last edited by checkers; 2008-03-31 at 05:08. |
![]() |
![]() |
![]() |
Link #4 | |
x264 Developer
Join Date: Feb 2008
|
Quote:
Overall I think VAQ is probably better than Haali's, even for anime. |
|
![]() |
![]() |
![]() |
Link #6 |
x264 Developer
Join Date: Feb 2008
|
CRF values with very different AQ values are not comparable in terms of quality. Remember, CRF X with Y settings is not necessarily exactly the same quality as CRF X with Z settings, especially if Y and Z are very very different. That is not the purpose of CRF.
|
![]() |
![]() |
![]() |
Link #7 |
Member
Join Date: Aug 2008
|
How would I go about evaluating its use? I compared a few before/after frames and all I noticed was a slight image degradation but flat areas (provided I understand what those are correctly. I used backgrounds of a cloudy sky, a wooden table and a marbled floor) looked pretty much the same. Pixel may have been shuffled around a little bit but it didn't seem like an improvement to me. The raws could have been too smooth or maybe x264 is just so awesome that there is no detail lost to begin with
![]() Last edited by guest0815; 2008-12-25 at 02:04. |
![]() |
![]() |
![]() |
Link #8 |
Real-life Lolicon
Join Date: Jun 2008
|
The easiest way to compare would be to compare PSNR and SSIM values (which means getting rid of the --no-psnr and --no-ssim flags). Of course, this isn't the best way (which would be using your eyes), but it is simple and generally effective, as long as Psy optimizations are not being compared.
|
![]() |
![]() |
![]() |
Link #9 | ||
x264 Developer
Join Date: Feb 2008
|
Quote:
Quote:
|
||
![]() |
![]() |
![]() |
|
|