On Mon, Feb 23, 2015 at 10:28:29PM -0600, Cary Tetrick wrote: > > > > please ping this thread when this happens > > > > about the patch itself > > > > IIUC a user using old rtmpdump with new ffmpeg would loose the > > rtmp_buffer_size option. > > Would it make sense to support the old setsockopt() code for this > > case ? > > > > [...] > > > > > > > That's a really good point. So the only real question then is whether to > keep it the way it is, or to submit another patch to support the other two > options (which are not as important IMO) in the same manner as Brian's > patch.
thats simply a question of if someone wants to implement and maintain it > Either way, it would eliminate the dependency on rtmpdump. > What do you think? > > Thanks, > Cary > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No snowflake in an avalanche ever feels responsible. -- Voltaire
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
