Yo,
Time is up, results are here:
https://vote.ffmpeg.org/cgi-bin/civs/results.pl?id=E_029f7195fed7aadf
The 1. place goes to
A: twice a year (1st Jan & 1st July, 0:00 UTC); as an exception, the list will
also be updated immediately after this vote
The 2. place goes to:
B: before each vote
On Mon, 6 Nov 2023, at 03:06, Cosmin Stejerean via ffmpeg-devel wrote:
>> On Nov 5, 2023, at 5:41 AM, Thilo Borgmann via ffmpeg-devel
>> wrote:
>> The script should output two files then, so that no manual editing is
>> required.
>> The voting system expects a file with mail addresses one per
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Ronald S. Bultje
> Sent: Monday, November 6, 2023 10:48 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v5] avcodec/cbs_vp8: Add support for
> VP8 codec bitstream
>
>
Hi,
On Sun, Nov 5, 2023 at 7:56 PM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
> This commit adds support for VP8 bitstream read methods to the cbs
> codec. This enables the trace_headers bitstream filter to support VP8,
> in addition to AV1, H.264, H.265, and VP9. This can be
> On Nov 5, 2023, at 5:41 AM, Thilo Borgmann via ffmpeg-devel
> wrote:
>
> The script should output two files then, so that no manual editing is
> required.
> The voting system expects a file with mail addresses one per line and the ML
> then shall be given the very same list but with only
This commit adds support for VP8 bitstream read methods to the cbs
codec. This enables the trace_headers bitstream filter to support VP8,
in addition to AV1, H.264, H.265, and VP9. This can be useful for
debugging VP8 stream issues.
The CBS VP8 implements a simple VP8 boolean decoder using
Hi,
On Sun, Nov 5, 2023 at 6:25 PM James Almer wrote:
> On 11/5/2023 4:57 PM, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Sun, Nov 5, 2023 at 4:24 AM Anton Khirnov wrote:
> >
> >> Please suggest candidates in replies to this email, with a short
> >> description of how they contribute to the
On 11/5/2023 4:57 PM, Ronald S. Bultje wrote:
Hi,
On Sun, Nov 5, 2023 at 4:24 AM Anton Khirnov wrote:
Please suggest candidates in replies to this email, with a short
description of how they contribute to the project.
Myself, please. I currently maintain the VP8/VP9 decoders and sometimes
On date Sunday 2023-11-05 13:53:38 +, p...@frankplowman.com wrote:
> From: Frank Plowman
>
> Texinfo 7.0, released in November 2022, changed the names of various
> functions. Compiling docs with Texinfo 7.0 results in warnings and
> improperly formatted documentation. More old names appear
On Sat, Nov 04, 2023 at 11:36:08PM +0100, Jean-Baptiste Kempf wrote:
> Yo,
>
> On Fri, 3 Nov 2023, at 18:33, Michael Niedermayer wrote:
> >> It will take a bit of time, but I'll do it.
>
> Aman
> Andreas
> Andriy
> Anton
> Lynne
> Baptiste
> Jun Zhao
> Lauri Kasanen
> Carl
> Marton
> Dale
>
Hi,
On Sun, Nov 5, 2023 at 4:24 AM Anton Khirnov wrote:
> Please suggest candidates in replies to this email, with a short
> description of how they contribute to the project.
>
Myself, please. I currently maintain the VP8/VP9 decoders and sometimes
review AV1-related work also, although James
On 05/11/2023 14:47, Sebastian Ramacher wrote:
On 2023-11-04 00:00:38 +0100, Michael Niedermayer wrote:
Hi
i intend to do releases from thr release/6.0 and 5.1 branches very soon
if theres something you want backported, please do it now. If you want me
to wait for something, just say so.
I'd
On 2023-11-04 00:00:38 +0100, Michael Niedermayer wrote:
> Hi
>
> i intend to do releases from thr release/6.0 and 5.1 branches very soon
> if theres something you want backported, please do it now. If you want me
> to wait for something, just say so.
I'd appreciate a proper fix for
From: Frank Plowman
Texinfo 7.0, released in November 2022, changed the names of various
functions. Compiling docs with Texinfo 7.0 results in warnings and
improperly formatted documentation. More old names appear to have
been removed in Texinfo 7.1, released October 2023, which causes docs
Am 05.11.23 um 14:41 schrieb Thilo Borgmann via ffmpeg-devel:
Hi,
sorry can't comment on the ML atm as people will wonder why I respond to this
but not to other "more important" mails...
Having sent this private mail to the ML anyways just proves how much I should
not post to the ML in my
Hi,
sorry can't comment on the ML atm as people will wonder why I respond to this
but not to other "more important" mails...
Set aside that I think its complete nonsense not to share the list of mail
addresses directly for any legal consideration - all these mail addresses were
put into a
On Sat, Nov 04, 2023 at 06:58:11PM +0100, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2023-11-02 20:53:46)
> > On Sun, Oct 29, 2023 at 10:33:12AM +0100, Anton Khirnov wrote:
> > > Hi all,
> > > updating the answers according to received comments:
> > >
> > > vote question (unchanged):
> >
Quoting Zhao Zhili (2023-11-03 10:32:07)
> From: Zhao Zhili
>
> Signed-off-by: Zhao Zhili
> ---
> libavdevice/android_camera.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Looks trivially ok
--
Anton Khirnov
___
ffmpeg-devel mailing
Hi all,
as previously discussed, we need to re-elect the members of the
Technical and Community Committees. As a reminder - the Technical
Committee (TC) resolves technical disputes, while the Community
Committee (CC) resolves personal conflicts and code of conduct
violations.
Anyone can become a
Hi all,
once the rule for updating the voter list is established (voting closes
today, please vote if you have not done so yet), we also need to vote in
any additional GA members who do not meet the commit criterium. As per
the rules they are voted in for two years, after which they need to be
On Fri, 27 Oct 2023, David Johansen wrote:
On Fri, Oct 27, 2023 at 4:58 AM wrote:
On 27 Oct 2023, at 5:59, Dave Johansen wrote:
> @item second_level_segment_index
> Makes it possible to use segment indexes as %%d in hls_segment_filename
expression
> besides date/time values when
21 matches
Mail list logo
