Hi all,
Michel Bardiaux wrote:
[...]
>> and I'm receiving the streams
>> from servers on specific ports: eg. 7020 for video (7021 for RTCP) and 7022
>> for audio (7023 for RTCP). So I don't know if FFmpeg is able to listen to a
>> port and build the stream (muxing is currently not a priority).
>
> Yes. You specify the port in the url.
Sorry, no... That would work for raw UDP, but when someone wants to receive
RTP streams, opening an "rtp://..." url is the wrong thing to do.
The correct thing to do is to open the SDP file describing the RTP session.
Sorry if this is off topic on libav-user, but I often receive private emails
from people asking why
ffmpeg -i rtp://...
does not work properly (someone even claims that there is a bug in ffmpeg).
I generally do not answer such emails, but I take this opportunity to clarify
that "ffmpeg -i rtp://..." is almost always the wrong thing to do.
The correct thing is "ffmpeg -i rtsp://..." or "ffmpeg -i file.sdp".
Luca
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
