How to make ffmpeg stream h264 with PPS and SPS in the RTP stream
I'm trying to use ffmpeg to receive an h264 stream over RTSP and forward that stream as a muliticast rtp stream. I can receive the stream, and output it as a multicast rtp stream using the following command:
ffmpeg -i rtsp://10.255.11.203/ProfileToken_1_1 -vcodec copy -an -f rtp rtp://230.255.10.25:50000
The incoming stream contains SPS PPS and SEI packets. I can't make ffmpeg to output those as well.
I have experimented with the -flags global_header parameter to enable and disable global header, And I have tried adding -bsf h264_mp4toannexb which does not work since the incoming stream is already Annex-B.
ffmpeg video-streaming
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
asked Dec 11 '15 at 9:00
AndréAndré
6613
add a comment |
I'm trying to use ffmpeg to receive an h264 stream over RTSP and forward that stream as a muliticast rtp stream. I can receive the stream, and output it as a multicast rtp stream using the following command:
ffmpeg -i rtsp://10.255.11.203/ProfileToken_1_1 -vcodec copy -an -f rtp rtp://230.255.10.25:50000
The incoming stream contains SPS PPS and SEI packets. I can't make ffmpeg to output those as well.
I have experimented with the -flags global_header parameter to enable and disable global header, And I have tried adding -bsf h264_mp4toannexb which does not work since the incoming stream is already Annex-B.
ffmpeg video-streaming
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
asked Dec 11 '15 at 9:00
AndréAndré
6613
add a comment |
I'm trying to use ffmpeg to receive an h264 stream over RTSP and forward that stream as a muliticast rtp stream. I can receive the stream, and output it as a multicast rtp stream using the following command:
ffmpeg -i rtsp://10.255.11.203/ProfileToken_1_1 -vcodec copy -an -f rtp rtp://230.255.10.25:50000
The incoming stream contains SPS PPS and SEI packets. I can't make ffmpeg to output those as well.
I have experimented with the -flags global_header parameter to enable and disable global header, And I have tried adding -bsf h264_mp4toannexb which does not work since the incoming stream is already Annex-B.
ffmpeg video-streaming
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
asked Dec 11 '15 at 9:00
AndréAndré
6613
I'm trying to use ffmpeg to receive an h264 stream over RTSP and forward that stream as a muliticast rtp stream. I can receive the stream, and output it as a multicast rtp stream using the following command:
ffmpeg -i rtsp://10.255.11.203/ProfileToken_1_1 -vcodec copy -an -f rtp rtp://230.255.10.25:50000
The incoming stream contains SPS PPS and SEI packets. I can't make ffmpeg to output those as well.
I have experimented with the -flags global_header parameter to enable and disable global header, And I have tried adding -bsf h264_mp4toannexb which does not work since the incoming stream is already Annex-B.
ffmpeg video-streaming
ffmpeg video-streaming
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
asked Dec 11 '15 at 9:00
AndréAndré
6613
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
asked Dec 11 '15 at 9:00
AndréAndré
6613
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
edited Dec 14 '15 at 7:33
Mureinik
2,54561625
2,54561625
asked Dec 11 '15 at 9:00
AndréAndré
6613
asked Dec 11 '15 at 9:00
AndréAndré
6613
asked Dec 11 '15 at 9:00
AndréAndré
6613
6613
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Does the incoming stream contain them, or were they just not needed?
If you're receiving the stream via RTSP, you're probably receiving an RTP stream that doesn't have those packets. Your client would have connected via RTCP to get the SDP describing those streams, because PPS and SPS are usually once-per-stream unless you're changing resolutions, framerates, etc.
Run the command you've been running, but in the ffmpeg output you'll see a section like this:
SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 239.100.200.100
t=0 0
a=tool:libavformat 56.40.101
m=video 10000 RTP/AVP 96
b=AS:3027
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1; sprop-parameter-sets=Z2QAM6xyBEB4AiflwEQAAAMABAAAAwDAPGDGEYA=,aOhDssiw; profile-level-id=640033
Everything after the SDP line needs to be saved into a filename.sdp. To connect to the stream, someone would just need to open the file:
ffplay -i filename.sdp
If you put the file on a server, they could open the address:
ffplay -i http://yourhost/filename.sdp
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
The incoming stream does contain the PPS and SPS packets. The receiving decoder does not handle RTSP it will only decode an incoming RTP stream. Hence your answer is not really applicable.
– André
Dec 24 '15 at 9:27
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1011976%2fhow-to-make-ffmpeg-stream-h264-with-pps-and-sps-in-the-rtp-stream%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Does the incoming stream contain them, or were they just not needed?
If you're receiving the stream via RTSP, you're probably receiving an RTP stream that doesn't have those packets. Your client would have connected via RTCP to get the SDP describing those streams, because PPS and SPS are usually once-per-stream unless you're changing resolutions, framerates, etc.
Run the command you've been running, but in the ffmpeg output you'll see a section like this:
SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 239.100.200.100
t=0 0
a=tool:libavformat 56.40.101
m=video 10000 RTP/AVP 96
b=AS:3027
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1; sprop-parameter-sets=Z2QAM6xyBEB4AiflwEQAAAMABAAAAwDAPGDGEYA=,aOhDssiw; profile-level-id=640033
Everything after the SDP line needs to be saved into a filename.sdp. To connect to the stream, someone would just need to open the file:
ffplay -i filename.sdp
If you put the file on a server, they could open the address:
ffplay -i http://yourhost/filename.sdp
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
The incoming stream does contain the PPS and SPS packets. The receiving decoder does not handle RTSP it will only decode an incoming RTP stream. Hence your answer is not really applicable.
– André
Dec 24 '15 at 9:27
add a comment |
Does the incoming stream contain them, or were they just not needed?
If you're receiving the stream via RTSP, you're probably receiving an RTP stream that doesn't have those packets. Your client would have connected via RTCP to get the SDP describing those streams, because PPS and SPS are usually once-per-stream unless you're changing resolutions, framerates, etc.
Run the command you've been running, but in the ffmpeg output you'll see a section like this:
SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 239.100.200.100
t=0 0
a=tool:libavformat 56.40.101
m=video 10000 RTP/AVP 96
b=AS:3027
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1; sprop-parameter-sets=Z2QAM6xyBEB4AiflwEQAAAMABAAAAwDAPGDGEYA=,aOhDssiw; profile-level-id=640033
Everything after the SDP line needs to be saved into a filename.sdp. To connect to the stream, someone would just need to open the file:
ffplay -i filename.sdp
If you put the file on a server, they could open the address:
ffplay -i http://yourhost/filename.sdp
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
The incoming stream does contain the PPS and SPS packets. The receiving decoder does not handle RTSP it will only decode an incoming RTP stream. Hence your answer is not really applicable.
– André
Dec 24 '15 at 9:27
add a comment |
Does the incoming stream contain them, or were they just not needed?
If you're receiving the stream via RTSP, you're probably receiving an RTP stream that doesn't have those packets. Your client would have connected via RTCP to get the SDP describing those streams, because PPS and SPS are usually once-per-stream unless you're changing resolutions, framerates, etc.
Run the command you've been running, but in the ffmpeg output you'll see a section like this:
SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 239.100.200.100
t=0 0
a=tool:libavformat 56.40.101
m=video 10000 RTP/AVP 96
b=AS:3027
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1; sprop-parameter-sets=Z2QAM6xyBEB4AiflwEQAAAMABAAAAwDAPGDGEYA=,aOhDssiw; profile-level-id=640033
Everything after the SDP line needs to be saved into a filename.sdp. To connect to the stream, someone would just need to open the file:
ffplay -i filename.sdp
If you put the file on a server, they could open the address:
ffplay -i http://yourhost/filename.sdp
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
Does the incoming stream contain them, or were they just not needed?
If you're receiving the stream via RTSP, you're probably receiving an RTP stream that doesn't have those packets. Your client would have connected via RTCP to get the SDP describing those streams, because PPS and SPS are usually once-per-stream unless you're changing resolutions, framerates, etc.
Run the command you've been running, but in the ffmpeg output you'll see a section like this:
SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 239.100.200.100
t=0 0
a=tool:libavformat 56.40.101
m=video 10000 RTP/AVP 96
b=AS:3027
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1; sprop-parameter-sets=Z2QAM6xyBEB4AiflwEQAAAMABAAAAwDAPGDGEYA=,aOhDssiw; profile-level-id=640033
Everything after the SDP line needs to be saved into a filename.sdp. To connect to the stream, someone would just need to open the file:
ffplay -i filename.sdp
If you put the file on a server, they could open the address:
ffplay -i http://yourhost/filename.sdp
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
edited Dec 23 '15 at 20:27
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
answered Dec 23 '15 at 20:20
MithrilTuxedoMithrilTuxedo
1464
1464
The incoming stream does contain the PPS and SPS packets. The receiving decoder does not handle RTSP it will only decode an incoming RTP stream. Hence your answer is not really applicable.
– André
Dec 24 '15 at 9:27
add a comment |
The incoming stream does contain the PPS and SPS packets. The receiving decoder does not handle RTSP it will only decode an incoming RTP stream. Hence your answer is not really applicable.
– André
Dec 24 '15 at 9:27
The incoming stream does contain the PPS and SPS packets. The receiving decoder does not handle RTSP it will only decode an incoming RTP stream. Hence your answer is not really applicable.
– André
Dec 24 '15 at 9:27
The incoming stream does contain the PPS and SPS packets. The receiving decoder does not handle RTSP it will only decode an incoming RTP stream. Hence your answer is not really applicable.
– André
Dec 24 '15 at 9:27
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1011976%2fhow-to-make-ffmpeg-stream-h264-with-pps-and-sps-in-the-rtp-stream%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
