Hi, On Tue, Feb 14, 2012 at 11:34 AM, Camera Man <[email protected]> wrote: > On 02/14/2012 01:56 PM, Ronald S. Bultje wrote: > > In the past, it was possible to use a url like: > > "rstp://user:[email protected]/axis-media/media.amp?udp&buffer_size=1048576". > With latest trunk, it is possible to specify the transport through an option > dictionary ("rtsp_transport" -> "udp"), but I can't figure out how to pass > options like buffer_size, connect, fifo_size etc. > > ./avconv -rtsp_transport udp -i rtsp://... > > -rtsp_transport goes before the -i. Also see ./avconv -h. > > > Ronald, thanks for the answer. > > My question was, however, about parameters that get passed to the underlying > network transport - e.g., for udp, you use to be able to specify the socket > buffer size. My h264 IP camera produces I-frames that are ~220KB, and with > the default 64K socket buffer size, they got corrupted. It ws possible, in > the past, to pass a buffer argument (as in the example I gave above). How > can you do that today, short of recompiling libav with a different #define > RX_BUFFER_SIZE ?
I don't think we have anything called RX_BUFFER_SIZE in our tree, and nothing prevents you from passing ?x=y value pairs that will be transmitted as part of the HTTP or RTSP URI straight to the server. The whole point of the avoptions API switch was that we would leave such URIs intact, to make it easier for you to pass option/value pairs to the server regardless of implementation details in Libav. Ronald _______________________________________________ libav-api mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-api
