Streaming FFmpeg over TCP
up vote
0
down vote
favorite
I'm experimenting with streaming video using the following basic method, which works fine:
$ ffmpeg -re -i INPUT -f mpegts udp://127.0.0.1:2000
$ ffplay udp://127.0.0.1:2000
However, when replacing udp with tcp (see here), ffmpeg says "connection refused".
[tcp @ 0x7f9ddb408880] Connection to tcp://127.0.0.1:2000 failed: Connection refused
tcp://127.0.0.1:2000: Connection refused
How do I fix this?
(All articles I find on the "connection refused" topic relate to FFserver, which is discontinued.)
Using macOS + FFmpeg 4.0.3
ffmpeg
asked Nov 21 at 21:14
forthrin
1,27121538
add a comment |
up vote
0
down vote
favorite
I'm experimenting with streaming video using the following basic method, which works fine:
$ ffmpeg -re -i INPUT -f mpegts udp://127.0.0.1:2000
$ ffplay udp://127.0.0.1:2000
However, when replacing udp with tcp (see here), ffmpeg says "connection refused".
[tcp @ 0x7f9ddb408880] Connection to tcp://127.0.0.1:2000 failed: Connection refused
tcp://127.0.0.1:2000: Connection refused
How do I fix this?
(All articles I find on the "connection refused" topic relate to FFserver, which is discontinued.)
Using macOS + FFmpeg 4.0.3
ffmpeg
asked Nov 21 at 21:14
forthrin
1,27121538
You’ll have to have something listening at the address and port you want to send the stream to. UDP is connectionless, TCP requires a connection
– Sami Kuhmonen
Nov 21 at 21:54
@SamiKuhmonen: I suspected this. Thanks for pointing this out. I could achieve this by starting the client first, of course. But if not, what are my other options? Can I set up some generic buffering mechanism in nginx that passes the data through to connecting clients on the other side, or do I basically need a streaming server like RTMP?
– forthrin
Nov 21 at 22:09
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm experimenting with streaming video using the following basic method, which works fine:
$ ffmpeg -re -i INPUT -f mpegts udp://127.0.0.1:2000
$ ffplay udp://127.0.0.1:2000
However, when replacing udp with tcp (see here), ffmpeg says "connection refused".
[tcp @ 0x7f9ddb408880] Connection to tcp://127.0.0.1:2000 failed: Connection refused
tcp://127.0.0.1:2000: Connection refused
How do I fix this?
(All articles I find on the "connection refused" topic relate to FFserver, which is discontinued.)
Using macOS + FFmpeg 4.0.3
ffmpeg
asked Nov 21 at 21:14
forthrin
1,27121538
I'm experimenting with streaming video using the following basic method, which works fine:
$ ffmpeg -re -i INPUT -f mpegts udp://127.0.0.1:2000
$ ffplay udp://127.0.0.1:2000
However, when replacing udp with tcp (see here), ffmpeg says "connection refused".
[tcp @ 0x7f9ddb408880] Connection to tcp://127.0.0.1:2000 failed: Connection refused
tcp://127.0.0.1:2000: Connection refused
How do I fix this?
(All articles I find on the "connection refused" topic relate to FFserver, which is discontinued.)
Using macOS + FFmpeg 4.0.3
ffmpeg
ffmpeg
asked Nov 21 at 21:14
forthrin
1,27121538
asked Nov 21 at 21:14
forthrin
1,27121538
asked Nov 21 at 21:14
forthrin
1,27121538
asked Nov 21 at 21:14
forthrin
1,27121538
asked Nov 21 at 21:14
forthrin
1,27121538
1,27121538
You’ll have to have something listening at the address and port you want to send the stream to. UDP is connectionless, TCP requires a connection
– Sami Kuhmonen
Nov 21 at 21:54
@SamiKuhmonen: I suspected this. Thanks for pointing this out. I could achieve this by starting the client first, of course. But if not, what are my other options? Can I set up some generic buffering mechanism in nginx that passes the data through to connecting clients on the other side, or do I basically need a streaming server like RTMP?
– forthrin
Nov 21 at 22:09
add a comment |
You’ll have to have something listening at the address and port you want to send the stream to. UDP is connectionless, TCP requires a connection
– Sami Kuhmonen
Nov 21 at 21:54
@SamiKuhmonen: I suspected this. Thanks for pointing this out. I could achieve this by starting the client first, of course. But if not, what are my other options? Can I set up some generic buffering mechanism in nginx that passes the data through to connecting clients on the other side, or do I basically need a streaming server like RTMP?
– forthrin
Nov 21 at 22:09
You’ll have to have something listening at the address and port you want to send the stream to. UDP is connectionless, TCP requires a connection
– Sami Kuhmonen
Nov 21 at 21:54
You’ll have to have something listening at the address and port you want to send the stream to. UDP is connectionless, TCP requires a connection
– Sami Kuhmonen
Nov 21 at 21:54
@SamiKuhmonen: I suspected this. Thanks for pointing this out. I could achieve this by starting the client first, of course. But if not, what are my other options? Can I set up some generic buffering mechanism in nginx that passes the data through to connecting clients on the other side, or do I basically need a streaming server like RTMP?
– forthrin
Nov 21 at 22:09
@SamiKuhmonen: I suspected this. Thanks for pointing this out. I could achieve this by starting the client first, of course. But if not, what are my other options? Can I set up some generic buffering mechanism in nginx that passes the data through to connecting clients on the other side, or do I basically need a streaming server like RTMP?
– forthrin
Nov 21 at 22:09
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fstackoverflow.com%2fquestions%2f53420557%2fstreaming-ffmpeg-over-tcp%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
You’ll have to have something listening at the address and port you want to send the stream to. UDP is connectionless, TCP requires a connection
– Sami Kuhmonen
Nov 21 at 21:54
@SamiKuhmonen: I suspected this. Thanks for pointing this out. I could achieve this by starting the client first, of course. But if not, what are my other options? Can I set up some generic buffering mechanism in nginx that passes the data through to connecting clients on the other side, or do I basically need a streaming server like RTMP?
– forthrin
Nov 21 at 22:09