Fix h.264 frame/keyframe identification in the player.

If a NAL unit that determines a frame start appears as the last NAL
unit in the packet, then the frame start is not identified until the
start of the next packet.  If this new packet has its own NAL unit
that determines a frame start, and that NAL unit is not at the end of
the packet, then only one frame start would be counted rather than
two.  This is fixed by returning the total number of frame starts,
rather than a bool.

In theory, the same problem could exist in the recorder, but it
appears that the packets in the original recording may have some
trailing NAL units that are stripped by the ffmpeg libraries when
assembling the packet for the player, causing the situation not to
occur.
(cherry picked from commit 86c22ed3d5c522bcecb88ecacd58104fc0dd6d8d)
Bump binary version after cherry picking 86c22ed3d5c522bcecb88ecacd58104fc0dd6d8d
MythArchive: update the encoding profiles to work with the current mythffmpeg

Refs #11299.

Signed-off-by: Stuart Auchterlonie <stuarta@squashedfrog.net>

(cherry picked from 5a0e83a20e8f75612b86fb56039b7803a11afd1b)
MythArchive: update mythburn.py to work with the updated encoding profiles

Refs #11299.

Signed-off-by: Stuart Auchterlonie <stuarta@squashedfrog.net>

(cherry picked from a784b93f1d1c6edbc0b47ac578def5d3275171a8)
MythArchive: update mythburn.py to work with the new mpeg2video codec name

Refs #11299.

Signed-off-by: Stuart Auchterlonie <stuarta@squashedfrog.net>

(cherry picked from 13c3035d1fed13a37c42d872b1f8dafb2e6f556f)
Make comparisons consistent

Refs #11299
Add AAC and AAC_LATM tages to mythtranscode info output

Pull request: https://github.com/MythTV/mythtv/pull/33
Merge remote-tracking branch 'glidos/fixes/0.26' into fixes/0.26

Refs #11380 and e78e59c6b2d71631e18027b9b9c84212744472bf

Signed-off-by: Stuart Auchterlonie <stuarta@squashedfrog.net>
fix issue #10222: mythcommflag segfaulting

The problem in issue #10222 is that it is adding the CODEC_FLAG2_FAST flag.  This causes unsafe functions to be used, causing a segfault. The proper way to fix this would probably be to figure out how to test for the "experimental speedups" flag, however I don't know the codebase well enough for this.

I tested how this would affect the speed of mythcommflag on one of my recordings.  The results:

Before removing flag:
real 2m13.123s
user 2m16.713s
sys 0m3.502s

After removing flag:
real 2m13.021s
user 2m15.446s
sys 0m3.758s

Signed-off-by: Stuart Auchterlonie <stuarta@squashedfrog.net>
(cherry-picked from 0026dda883ef50ab7f2fda7f2d2218bc56f094a7)