Yes, it's something I have added to the latest version. If you force a specific level (such as 4.1 in your example), the maximum bitrate allowed for that level is now specified automatically in the command line (with the --vbv-maxrate argument). For level 4.1 (and profile high, the default), the maximum bitrate is 62500 kbps. Since the average bitrate specified by the user must be smaller than the maximum, BD3D2MK3D verifies if it is correct, and if it's not the case, it changes it to an acceptable value (90% of the maximum bitrate).
But if you have specified 9k, (I guess you mean 9000 kbps, right?) then your bitrate is largely below the limit, and BD3D2MK3D should not have displayed that warning. Obviously, there is something wrong. I will have a look. Thanks for the bug report.
|