QUOTE (Dynamic @ Dec 18 2012, 20:05) <{POST_SNAPBACK}>
So those that I've bolded are not close to the bitrate requested. I guess anything below 143 should ideally be mapped to 144 and anything above 300 should be mapped to 300 and possibly throw a warning that the requested bitrate target is out of range and specify the one actually used.
It looks like the new --brV+ function is using the standard -V+ function for values 0-9, and anything outside of the 144-300 range (the range that -V+ is defined for) errors out. Either 32-143 should be mapped to 144, and 301-320 to 300 like Dynamic suggests, or the --brV+ function should be extended to the full range of MPEG-1 bitrates (32-320).