On Wed, Dec 18, 2019 at 4:17 PM Wonkap Jang
wrote:
>
> ts_target_bitrate is in kbps, not bps. This commit clarifies the unit
> and modifies the example to match the description.
> ---
> doc/encoders.texi | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
applied, thanks.
Hi,
On Wed, Dec 18, 2019 at 2:00 PM Wonkap Jang
wrote:
>
> Hi James,
>
> I have updated the libvpx.
> https://chromium-review.googlesource.com/c/webm/libvpx/+/1974899
>
Thanks for posting the patch. Remember top-posting isn't preferred on
this mailing list [1].
[1]
Hi James,
I have updated the libvpx.
https://chromium-review.googlesource.com/c/webm/libvpx/+/1974899
Thank you,
Wonkap
On Wed, Dec 18, 2019 at 1:39 PM James Zern
wrote:
> Hi,
>
> On Wed, Dec 18, 2019 at 1:17 PM Wonkap Jang
> wrote:
> >
> > ts_target_bitrate is in kbps, not bps. This commit
Hi,
On Wed, Dec 18, 2019 at 1:17 PM Wonkap Jang
wrote:
>
> ts_target_bitrate is in kbps, not bps. This commit clarifies the unit
> and modifies the example to match the description.
> ---
> doc/encoders.texi | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
lgtm if you can verify
ts_target_bitrate is in kbps, not bps. This commit clarifies the unit
and modifies the example to match the description.
---
doc/encoders.texi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/encoders.texi b/doc/encoders.texi
index 4ee518a124..a207363650 100644
---
