What happens when my video exceeds the maximum bitrate of the tier and level?

[YaBoyShredderson]

Im using staxrip to encode using x265, and havent left the tier on auto and high on undefined. Its a 4k60 video, and staxrip automatically chose level 5.0 main tier, but its bitrate came out at 65mbits, using crf 18. How does that work? Should i define a tier and?

[RanmaCanada]

CRF will use as much bitrate as it deems fit. If you want a lower bitrate, you are going to have to tell it so. There were some posts talking about this in the sub.

[benwaggoner]

Originally Posted by YaBoyShredderson

Im using staxrip to encode using x265, and havent left the tier on auto and high on undefined. Its a 4k60 video, and staxrip automatically chose level 5.0 main tier, but its bitrate came out at 65mbits, using crf 18. How does that work? Should i define a tier and?

If you don't specify a level, x265 will default to the lowest level that is compatible with your frame size and fps, and then set --vbv-bufsize and --vbv-maxrate as appropriate (and other parameters).

If your bitrate exceeds main tier, perhaps it will increase it to high tier if you didn't specify that.

If you know what decoders you are targeting, it's better to specify that actual level. And I'd be careful about specifying High Tier for much of anything consumer-oriented. UHD Blu-ray is one exception, as it supports a much higher bitrate than Level 5.1.

[excellentswordfight]

Originally Posted by benwaggoner

If you don't specify a level, x265 will default to the lowest level that is compatible with your frame size and fps, and then set --vbv-bufsize and --vbv-maxrate as appropriate (and other parameters).

Not sure if you have experience with any custom builds, but for me x265 has never set --vbv-bufsize and --vbv-maxrate when level is auto selected, its only set when level is manually specified. It will also default to high tier (if available) when level is specified & tier is not.

Whats a bit odd for TS though that it used level 5 for 2160p60, I didnt think that was valid for level 5. Did you check the encoded file as well TS? Maybe thats just an UI bug in staxrip.

[FranceBB]

Originally Posted by excellentswordfight

Whats a bit odd for TS though that it used level 5 for 2160p60, I didnt think that was valid for level 5. Did you check the encoded file as well TS? Maybe thats just an UI bug in staxrip.

Interesting. Yeah, I think 5.0 is limited to 30fps only and you gotta go to 5.1 for 50fps and 60fps. Does x265 actually allow people to encode it that way? O_O

[excellentswordfight]

Originally Posted by FranceBB

Interesting. Yeah, I think 5.0 is limited to 30fps only and you gotta go to 5.1 for 50fps and 60fps. Does x265 actually allow people to encode it that way? O_O

No, normally it doesnt, encoding fails and exits when using an level that isnt valid for that framesize/rate

[benwaggoner]

Originally Posted by excellentswordfight

No, normally it doesnt, encoding fails and exits when using an level that isnt valid for that framesize/rate

Perhaps an issue with the custom build build being used?

Mainline x265 has always failed or reduced parameters if I asked it to violate profile @ level @ tier restrictions.

[FranceBB]

Originally Posted by excellentswordfight

No, normally it doesnt, encoding fails and exits when using an level that isnt valid for that framesize/rate

Yeah that's what I thought

Originally Posted by benwaggoner

Perhaps an issue with the custom build build being used?

Mainline x265 has always failed or reduced parameters if I asked it to violate profile @ level @ tier restrictions.

Must be a custom_build issue then. I would have been surprised if the mainline x265 actually allowed to encode such a stream eheheheh

[Balling]

Originally Posted by excellentswordfight

No, normally it doesnt, encoding fails and exits when using an level that isnt valid for that framesize/rate

But nvenc does not. LOL. https://trac.ffmpeg.org/ticket/6476#comment:12