[x264-devel] Default value for the --scenecut option causes heavy undesirable flood of I slices in active scenes

[Vladimir Chernyshov]

Ok, the discussion is closed.

I understand the point of B-frames as a form or perceptual  
compression. If 1/3 of the frames in video have a slightly higher  
quality, and 2/3 have slightly lower, the human eye will perceive the  
video as having the slightly higher quality, while the video will have  
a lower bitrate than that of the reference video with constant quality.

regards,
Vladimir

P.S. Sorry, my email client does not show any hint whether the post is  
a top or not.


> And I repeat my point that you still do not understand the purpose of
> B-frames.  The purpose of B-frames is not to raise the quantizer, and
> the purpose of I-frames is not to lower the quantizer.  These are
> ratecontrol choices, which you can adjust as commandline options, and
> have basically nothing to do with the reason why B-frames are useful
> in the first place.
>
> In such a scene as you have described, B-frames are suboptimal:
> period.  No ifs, ands, or buts.  I-frames are relatively optimal,
> because if a frame is nearly entirely I-blocks, there is little point
> to having inter prediction anyways.  I am not going to change encoder
> defaults because clueless people on the mailing list manage to
> convince themselves of falsehoods and then proceed to ignore people
> with enormously more experience in the field than they do and
> completely disregard all responses that don't explicitly agree with
> them.
>
> End of story.  I am not going to waste any more of my time on this
> unless someone starts paying me, or you submit a usable patch that not
> only solves your supposed "problem" but also consistently improves
> PSNR on every single test clip in my repertoire.
>
> Also, stop top-posting, or others will likely proceed to ignore you as well.
>
> Dark Shikari