Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COFor my purpose, the video should be either decoded (i.e. full resolution) or decodable at the destination. Muxing (or encapsulating) the **encoded** RTP packets is needed to avoid the transfer of the raw YUV data. I can already encode the video and I know what a container is. Encoded H.264 bitstreams in the RTP packetized form (not the AnnexB form which have 0x001 NALU headers) cannot be decodable at the receiver side without JM. However, with the proper header (or container) most video players are able to decode the bitstream. I changed the question to explain myself better. Please check.
      singulars
    2. COIf I understand correctly, you have h264 non-annex B encapsualted in this special rtp thing that only JM can decode, and you're looking to strip the rtp, and put the h264 inside something else that can easily be demuxed and then decoded. iso-based containers (mp4, frv) are used together with non-annex B regularly but the problem is that with no annex B then the encoder doesn't know the stream parameters (resolution, picture structure, etc.) which are usually in the annex B, Is that extra data in the RTP headers? ffmpeg probably doesn't know what to with them, can you create the data manually?
      singulars
    3. COYes, that is my problem. Ffmpeg generally get the parameters from the headers of given data. Even assuming there is no header of RTP packets, ffmpeg can easily take those from input parameters. Alas, I need that ffmpeg command because I couldn't find it on the web. I didn't understand the part of your question "...,can you create the data manually?" If the question is whether I know the resolution, structure etc., I can supply these information to ffmpeg. If the question is creating the **encoded** bitstream data manually, I clearly can't. :)
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload