Would it be difficult to make dcpomatic2_verify report timecodes (or frame numbers) of all frames which exceed max bitrate? Or at least a count of them, and the bitrate/size of the worst violation?

For my purposes, consuming the output of dcpomatic2_verify programmatically, logging the size of every single frame (and component) would be ideal. Though that would be way too verbose for most users.

Perhaps this could be behind a CLI flag so it's not output by default.

This is a "nice to have" rather than essential, but we do see DCPs with these problems fairly regularly, and it's useful to have something concrete to report to the DCP provider, rather than just "it fails". It's not uncommon to receive a response along the lines of "this DCP screened fine at SXSW, there's nothing wrong with it", and solid evidence of a problem helps to convince people they do actually need to do something.