0001-libavformat-dashenc.c-add-support-to-change-mpd-upda.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
I have trouble with mailman email system .
My company email client can reply email . but looks mailman can not read out
text content . and it will add a warning picture automatically .
And third part email client such as outlook , though it works with text
content without warning pitcture. but
0001-libavformat-dashenc.c-add-support-to-change-mpd-upda.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
Hello Mr. Moritz
I update docs . and here is the latest patch .
Ps: when I test doc file , muxers.texi
It show some warning by
root@saber:/ffmpeg# makeinfo --html --no-split -o muext.html doc/muxers.texi
doc/muxers.texi:1948: @ref reference to nonexistent node `concat'
Hello Mr. Moritz
I update docs . and here is the latest patch .
Ps: when I test doc file , muxers.texi
It show some warning by
root@saber:/ffmpeg# makeinfo --html --no-split -o muext.html doc/muxers.texi
doc/muxers.texi:1948: @ref reference to nonexistent node `concat'
On Thu, Jun 04, 2020 at 10:35:32 +0800, Siyuan Huang wrote:
> Hello Mr. Moritz
Please use your mailer's reply function to reply to e-mail messages to
the list, so that the email threading in maintained.
> I have try finding recently doc update for dashenc.c , but I found no
> related commit .
>
Hello Mr. Moritz
I have try finding recently doc update for dashenc.c , but I found no
related commit .
For example in f63407a9863a0168cddfafebb6b8a4ba85716bbe commit , it add some
options , but no doc update in that commit .
Can you show which document should I update ?
I Only find
Hello Mr. Michael
Update by your opinions
0001-libavformat-dashenc.c-add-support-to-change-mpd-upda.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To
On Mon, Jun 01, 2020 at 18:21:40 +0800, Siyuan Huang wrote:
> { "max_playback_rate", "Set desired maximum playback rate",
> OFFSET(max_playback_rate), AV_OPT_TYPE_RATIONAL, { .dbl = 1.0 }, 0.5, 1.5, E
> },
> +{"update_period", "Set the mpd update interval", OFFSET(update_period),
>
On Mon, Jun 01, 2020 at 06:21:40PM +0800, Siyuan Huang wrote:
> Hello Mr.James
>
>
>
> For this , in dash if . there are tcs whose segment type is SegmentTemplate
> ,and minimumUpdatePeriod is not 50 .
>
> (eg: https://livesim.dashif.org/livesim/mup_30/testpic_2s/Manifest.mpd)
>
> Cause
Hello Mr.James
For this , in dash if . there are tcs whose segment type is SegmentTemplate
,and minimumUpdatePeriod is not 50 .
(eg: https://livesim.dashif.org/livesim/mup_30/testpic_2s/Manifest.mpd)
Cause there is no rules in dash spec says , in template cases , the live
miniupdateperiod
On 5/29/2020 4:18 AM, Siyuan Huang wrote:
> according iso 23009-1 , in live cases , mpd refresh period should be
> changeable
>
> and default 500 seconds is too long , in normal live cases , it should be
> 2~5 seconds
It's set to 500 when timeline isn't used (for example, template only),
in
according iso 23009-1 , in live cases , mpd refresh period should be
changeable
and default 500 seconds is too long , in normal live cases , it should be
2~5 seconds
Signed-off-by: SiyuanHuang
---
libavformat/dashenc.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
mode change
13 matches
Mail list logo
