Create a page to compare transmux outputs
When debugging transmux issues, it can be handy to be able to easily compare the result of the javascript segment parser with the working output from a tool like ffmpeg. Put together a test page to display the hex dump of segment-parser output side-by-side with a working example. Fixed the hex dump utility to produce more than one line of output per tag.
Don't jshint or test the muxing test page
Add rules to exclude the muxing utility page from jshint and qunit.
Use more descriptive variable names
Avoid using one-letter variable names, especially in relatively complex functions.
Remove comment
Get rid of a commented console.assert that had been replaced by a runtime conditional anyways.
Add a real-work ExpGolomb test
Make sure that a reasonable sequence parameter set can be decoded.
Simply emulation byte filtering
The original algorithm was incorrectly including the nal_unit_type in the returned RBSP when there were no emulation bytes to filter. This version is slower because it examines every byte individually but it's simpler to understand. Add a test case for H264 stream parsing that demonstrates the issue.
Display a tag-level overview for the generated FLVs
List the type and size of each tag of the input FLVs on the muxing helper page.
Fix jshint issues
Remove an extra semi-colon and refrence videojs through window.
Handle negative PTS values on the TS segments
Overwrite setNextTimeStamp after the first invocation, capturing the first PTS value. Write all FLV PTS and DTS values as offsets from that.
Clear out tag info when the input file changes
Don't append to the tag info pane. Overwrite the innerHTML whenever one of the files change.
Use the `||` operator to default videojs namespace
Instead of using a conditional, use logical or when determining if videojs.hls should be stubbed out or not.
Merge pull request #27 from videojs/feature/mux-helper

Add a page to help debug the transmuxing process