Quoting Martin Storsjö (2017-01-27 14:13:11) > On Fri, 27 Jan 2017, Peter Große wrote: > > > From: Peter Große <[email protected]> > > > > Bandwidth information is required in the manifest, but not always provided > > by the demuxer. > > So enable hinting the stream bandwidth via a metadata field, supports same > > values as codec bitrate setting. > > > > Example: -metadata:s:v:0 bitrate=3500k > > > > Signed-off-by: Peter Große <[email protected]> > > --- > > libavformat/dashenc.c | 12 ++++++++++++ > > 1 file changed, 12 insertions(+) > > This is kinda abusing the metadata mechanism, which is mostly intended to > be used for user-visible metadata like author/title and such. > > I'd like to ask for Anton's opinion on this (although I'm pretty sure > we've discussed it before).
If we did, I don't remember the conclusion :) Anyway, I agree that this is a misuse of metadata. There are at least two methods for passing the stream bitrate to the muxer -- the AVCodecParameters.bit_rate field and the AV_PKT_DATA_CPB_PROPERTIES side data. IIUC, the problem you're trying to solve is that avconv does not set the bit_rate field in certain situations. If that's the case, that should be fixed in avconv. We should not design our muxer behaviour around limitations of one specific caller. If you describe more fully what's the situation where bit_rate is not set properly, I might have some more specific ideas for handling this. -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
