revid: MPEG-TS packetisation of MJPEG
Issue #151
resolved
Now that we wish to have the option of video capture using MJPEG, we must have the capacity to packetise into MPEG-TS for correct transmission and storage. It’s proposed that each MJPEG frame be considered an ‘access unit’, and therefore, each MJPEG frame will be stored in its own packetised elementary stream (PES) packet. By the current mechanism (and consistent with other codecs), PES packets will be spread over multiple MPEG-TS packets.
Comments (3)
-
-
reporter Yep, this should transfer over from current functionality.
-
reporter - changed status to resolved
Addressed in PR #257
- Log in to comment
That seems reasonable. Presumably we will also ensure that:
(1) a “clip” (= network data sent by revid) will always start with the first packet for a given access unit and,
(2) clips always include whole frames, i.e., part of a frame will not straddle a clip boundary.