On Tue, Apr 29, 2014 at 8:19 AM, Luca Barbato <[email protected]> wrote: > On 29/04/14 14:00, [email protected] wrote: >> On Tue, Apr 29, 2014 at 6:47 AM, Luca Barbato <[email protected]> wrote: >>> On 29/04/14 03:48, [email protected] wrote: >>>> I built avconv like this... >>>> ./configure --enable-libx264 --enable-gpl --disable-everything >>>> --enable-protocol=hls --enable-muxer=hls --enable-demuxer=avi >>>> --enable-decoder=pcm_s16le,rawvideo --enable-encoder=libx264,aac >>>> --enable-indev=v4l2,alsa >>>> >>>> Does anyone know which build option I am missing to cause this? I am >>>> trying to make libav smaller for an embedded system. >>> >>> file protocol I'd guess. >> >> No change from adding file protocol except binary is a lot larger. Same >> error. > > Make sure you rebuilt it properly, you are missing the file protocol for > sure (tested locally). > > You might use the pulse capture directly from it btw. > > In doubt
I had reconfigured and built without a make clean. I am rebuilding now with make clean. Machine is much slower than a desktop. I added the error message for the protocol name. I'm built from git master. This is a useful change. Google shows many people having problems with the error message = "Could not write header for output file #0 (incorrect codec parameters ?): Protocol not found" I need to get pulse out of the system and read directly from alsa but I haven't figured out how to do that yet. > > diff --git a/libavformat/avio.c b/libavformat/avio.c > index fe42974..5b05b29 100644 > --- a/libavformat/avio.c > +++ b/libavformat/avio.c > @@ -205,6 +205,7 @@ int ffurl_alloc(URLContext **puc, const char > *filename, int flags, > return url_alloc_for_protocol(puc, up, filename, flags, > int_cb); > } > *puc = NULL; > + av_log(NULL, AV_LOG_ERROR, "Protocol %s not found\n", proto_str); > return AVERROR_PROTOCOL_NOT_FOUND; > } > > _______________________________________________ > libav-tools mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-tools -- Jon Smirl [email protected] _______________________________________________ libav-tools mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-tools
