[x264-devel] x264 rate control

[James Darnley]

On 2013-01-30 11:25, Jason Garrett-Glaser wrote:
> On this note, to others on the mailing list, thoughts on a patch
> that'd limit --threads auto in the case of frame threads to (bufsize /
> maxrate)*(fps-num / fps-den), so that people don't accidentally do
> this to themselves anymore?

This is the second time it has come up recently (very recently).
Perhaps a warning that this situation may have problems and a second
that x264 is lowering threads to X but allow people to override by
specifying --threads Y.  Similar to what x264cli does with refs and levels.

Pseudo-code:
if (dangerous_situation) {
    print("May cause problems")
    if (threads == AUTO) {
        threads = safe_value
        print("Automatically lowered")
}

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 552 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20130130/ec1991a8/attachment.pgp>