Initial import
Describe scanForNalEnd(), as it's complicated.
Ignore usual stuff
Heap buffer much faster than CompositeByteBuf here

Using a simple heap buffer more than doubles throughput for one test file.
Remove unused imports
Remove dependency on locally hacked jaad

Can come back when and if I work out how to sensibly build and distribute
a version of jaad that exposes more of its internal bitstream parsing state.
Remove dependency on jcodec

Was only using a single util function anyway.
Add missing 'private'
Fix test class name to match name of tested class
Don't loose last unread bytes in the PES packet

In particular, if we rewound two bytes at the end of the last buffer received
(in order to not loose any marker sequence crossing the boundary), these bytes
would always be lost from the final buffer in a PES packet.
Unit test H264 NAL unit parsing
WIP to enable move to 'push' H264 NAL parsing
Oops!  Should have commited this before :(
Jacoco coverage reporting / checking support
Move to push-parse for H264 NAL Unit syntax

Buffering the data and then doing a pull-parse once the entire PES packet was
visible is quite costy becase of all the data we copied around in memory.

The hand-rolled parser state machine in this new model is vastly more complicated
but also makes big reduction in the cost of one of the most expensive code-paths.
Have ValidatingNalUnitConsumer do something
Optimise: don't parse all H264 data all the time

We only switch on H264 parsing periodically to check that our calculated
relationship between PCR values and SEI pic_timing values is still correct.

H264 parsing is a relatively expensive part of the protocol stack, so this
makes a fair difference to the overall cost when chunking higher bitrate
video.
Fix typo in package name
Better test shows more poorly handled edge cases

The test previously relied on Mockito verification, but because
the API under test is complex, the assertions that could be made
where limited.  Now, a hand-crafted mock is used which makes the
test code look better, be less sensitive to irrelevant implementation
changes, and better able to assert that code under test makes proper
use of the mocked API.
Better 'snickersnack' command line interface