> This is a different issue, and I'd suggest you create a new thread for > it. My suspicion is that the webm encoder requires seeks, which isn't > possible with HTTP. This is the thread I created to discuss the webm muxer/demuxer for HTTP streams.
I will create a separate thread for the libvorbis issue when audio bitrate is set below 44K. So normally if an ffmpeg muxer doesnt support streaming for example like the MP4 container then the muxer will reject the request to create an ouput container over a network stream, it will log an error indicating this as the issue. However in this case that doesnt happen. The matroska spec on which Webm implements a subset does indicate support for this, see the streaming section here http://www.matroska.org/technical/streaming/index.html. It says set the segment size to "unknow" i.e. all 1s. The webm muxer in ffmpeg does this. Im wondering if theres a bug here or was it decided that Webm would not support this streaming functionality? If Web doesnt support streams maybe we should follow the behaviour of the MP4 muxer in this regard and reject the request if its URL is streamed based from the off. Thanks _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
