Hello, On Sat, 2022-12-24 at 13:36 +0200, Rémi Denis-Courmont wrote: > I don't see why you need an option for this. In parsing the SDP, it > should be self-evident if a given socket needs to be reused for RTCP- > mux or for SDP BUNDLE.
I indeed disregarded the "receiving RTP streams" part, my bad. I should clarify that this patch is only useful for _sending_ bundled RTP streams and muxed RTCP sender reports. I am currently using this patch successfully in a simulcast streaming WebRTC infrastructure, that could not work without it. Only the AV_OPT_FLAG_ENCODING_PARAM should be set in the option's flags, as this is the only case that makes sense and properly works. Analyzing the corresponding SDP options and opening only one socket and demuxing in userspace should be the way to go for reading such streams as you pointed it. Again I must clarify that this use case is not covered, and will set the option's flags accordingly. Thanks for your feedback. -- Camille _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
