On Sat, 28 Jan 2017, Peter Große wrote:
On Fri, 27 Jan 2017 22:24:35 +0200 (EET)
Martin Storsjö wrote:
Than we have to postpone opening any file handle until the first call to
dash_flush, right?
Which should be possible, but requires some code to be moved. Using a
dyn_buf (patch 10) might als
On Fri, 27 Jan 2017 22:24:35 +0200 (EET)
Martin Storsjö wrote:
> > Than we have to postpone opening any file handle until the first call to
> > dash_flush, right?
> > Which should be possible, but requires some code to be moved. Using a
> > dyn_buf (patch 10) might also help here, so writing to f
On Fri, 27 Jan 2017, Peter Große wrote:
On Fri, 27 Jan 2017 15:21:20 +0200 (EET)
Martin Storsjö wrote:
On Fri, 27 Jan 2017, Peter Große wrote:
Bandwidth information is required in the manifest, but not always
provided by the demuxer. If not available via metadata calculate
bandwith based on
On Fri, 27 Jan 2017 15:21:20 +0200 (EET)
Martin Storsjö wrote:
> On Fri, 27 Jan 2017, Peter Große wrote:
>
> > Bandwidth information is required in the manifest, but not always
> > provided by the demuxer. If not available via metadata calculate
> > bandwith based on the size and duration of the
On Fri, 27 Jan 2017, Peter Große wrote:
Bandwidth information is required in the manifest, but not always
provided by the demuxer. If not available via metadata calculate
bandwith based on the size and duration of the first segment.
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 11 +++
Bandwidth information is required in the manifest, but not always
provided by the demuxer. If not available via metadata calculate
bandwith based on the size and duration of the first segment.
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 11 +++
1 file changed, 11 insertions(+)
