On date Tuesday 2023-11-07 00:36:14 +0100, Stefano Sabatini wrote:
> 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
On Mon, Nov 6, 2023 at 6:05 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > Stop twisting people's words and implying things they never said :)
>
> This is not you presenting excuses.
>
Correct, it's you trying to win arguments with aggressive communication
> And thank you for
James Almer:
> Signed-off-by: James Almer
> ---
> libavformat/Makefile | 1 +
> libavformat/avformat.c | 214 --
> libavformat/demux.h| 29
> libavformat/internal.h | 291 +--
> libavformat/stream.c | 243
---
libavformat/hlsenc.c | 32 +++-
1 file changed, 7 insertions(+), 25 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index e1714d4eed..1baefe852f 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -35,6 +35,7 @@
#include
On Mon, Nov 6, 2023 at 4:46 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > Nice try but pointing out your logical fallacies is not being rude, but
> > rather is just showing you how easily your message can be misinterpreted,
>
> You have done nothing of the sort. You have just
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
Vittorio Giovara (12023-11-06):
> I'm not misrepresenting anybody's words,
Me: “I never doubted that Paul's patches do make the bug go away in your
test case.”
You: “you insisted it wasn't there”
This is precisely misrepresenting my words.
So stop lying and present excuses.
--
Nicolas
On Mon, Nov 6, 2023 at 5:49 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > I'm not misrepresenting anybody's words,
>
> Me: “I never doubted that Paul's patches do make the bug go away in your
> test case.”
>
> You: “you insisted it wasn't there”
>
> This is precisely
On Mon, Oct 16, 2023 at 08:43:30AM +1100, Peter Ross wrote:
> Partially fixes ticket #798
>
> Reviewed-by: James Almer
> Reviewed-by: Michael Niedermayer
> Signed-off-by: Peter Ross
+ Paul
will push later tonight. thanks everyone for helping out.
-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760
On date Monday 2023-11-06 18:41:54 +, ffmpeg-devel Mailing List wrote:
> Signed-off-by: Cosmin Stejerean
> ---
> tools/general_assembly.pl | 43 +--
> 1 file changed, 41 insertions(+), 2 deletions(-)
>
> diff --git a/tools/general_assembly.pl
From: Zhao Zhili
Signed-off-by: Zhao Zhili
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index b66c3d09a6..3430e1722b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -268,11 +268,11 @@ Codecs:
Hardware acceleration:
dxva2*
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Ronald S. Bultje
> Sent: Monday, November 6, 2023 8:08 PM
> 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,
Vittorio Giovara (12023-11-06):
> Stop twisting people's words and implying things they never said :)
This is not you presenting excuses.
> And thank you for ignoring my request to stay on topic
There is no topic to stay on: I will review this bug when time permits,
and you do not know anything
---
libavformat/hlsenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 4ef84c05c1..3548299770 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -3090,7 +3090,7 @@ static int hls_init(AVFormatContext *s)
This commit reorganizes the vp8data.[c|h] files, moving all of the
static data to vp8.c and keeping only the extern data in vp8data.[c|h].
It also exports the ff_vp8_token_default_probs variable.
Signed-off-by: Jianhui Dai
---
libavcodec/vp8.c | 602 -
We calculated offsets as pairs, but addressed them in the shader
as single float values, while reading them as ivec2s.
Also removes unused code (was provisionally added if cooperative matrices
could be used, but that turned out to be impossible).
Patch attached.
>From
On Mon, Nov 6, 2023 at 10:20 PM Zhao Zhili wrote:
> From: Zhao Zhili
>
> Signed-off-by: Zhao Zhili
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b66c3d09a6..3430e1722b 100644
> --- a/MAINTAINERS
> +++
Vittorio Giovara (12023-11-06):
> Correct, it's you trying to win arguments with aggressive communication
No. You came into an argument without knowing the first thing about it
and you decided to side with the guy who wants to violate the project's
policy about review. Your behavior in this
Oct 29, 2023, 06:57 by d...@lynne.ee:
> Oct 29, 2023, 05:51 by mich...@niedermayer.cc:
>
>> On Sat, Oct 28, 2023 at 09:23:45PM +0200, Lynne wrote:
>>
>>> Oct 28, 2023, 18:49 by mich...@niedermayer.cc:
>>>
>>> > On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote:
>>> >
>>> >> It's been a while
Please delete:
Comment 14 in ticket 2104
Comment 2 in ticket 5154
User "ballid"
The duplicated search patterns in regex filter did work as expected (-20
points), but the spammer got +20 points from captcha.
I've updated the search patterns.
Michael
By intent, and in practice, the "active contributor" criterium applies
to the person authoring the commits, not the one pushing them into the
repository.
---
doc/community.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/community.texi b/doc/community.texi
index
Cf.:
* http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-October/316054.html
* http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-November/316618.html
---
doc/community.texi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/community.texi b/doc/community.texi
index
Please delete also user "bunnylid". He did not yet write anything, but
he did register with the same IP adress as the other spammer, only a few
minutes earlier.
Michael
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
Quoting Michael Niedermayer (2023-10-27 19:53:08)
> On Fri, Oct 27, 2023 at 02:44:10PM +0200, Michael Koch wrote:
> > Is it possible to make the "Bad Content" page invisible? It would be better
> > if the spammer can't see the filtering rules.
>
> everything is possible but its not a standard
Hi,
Quoting James Almer (2023-10-30 16:23:52)
> Signed-off-by: James Almer
> ---
> No changes since last version. I'm resending this for the IAMF demuxer.
>
> I need opinions or reviews for this. We need to get this right from the start
> and i don't want to push something that will afterwards
Quoting Gyan Doshi (2023-11-06 11:08:02)
>
>
> On 2023-11-06 02:03 pm, Anton Khirnov wrote:
> > By intent, and in practice, the "active contributor" criterium applies
> > to the person authoring the commits, not the one pushing them into the
> > repository.
>
> s/criterium/criterion The former,
Quoting Anton Khirnov (2023-11-06 10:57:45)
> Follows the updated voter list that will be used from today until
> 2024-01-01.
Just realized this wording is too strict, as the list may be extended
with extra members after the next vote. So the final list will be a
superset of the above one.
--
Hi,
On Mon, Nov 6, 2023 at 7:07 AM Ronald S. Bultje wrote:
> On Sun, Nov 5, 2023 at 11:13 PM Dai, Jianhui J <
> jianhui.j.dai-at-intel@ffmpeg.org> wrote:
>
>> > > +static const uint8_t vp8_token_update_probs[4][8][3][11] = {
>> >
>> > It would be nice if these symbols could be re-used from
Hi,
On Sun, Nov 5, 2023 at 11:13 PM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
> > > +static const uint8_t vp8_token_update_probs[4][8][3][11] = {
> >
> > It would be nice if these symbols could be re-used from the existing vp8
> > native decoder, instead of duplicating them?
On 2023-11-06 02:03 pm, Anton Khirnov wrote:
By intent, and in practice, the "active contributor" criterium applies
to the person authoring the commits, not the one pushing them into the
repository.
s/criterium/criterion The former, in English, is related to bicycle
races.
Follows the updated voter list that will be used from today until
2024-01-01.
While generating it, I noticed that Ting Fu has commits with two
different emails, and no .mailmap entry. Please add one, so the script
can count you correctly.
If anyone finds other issues with the below list, please
This patch is obsolete and will be superseded by today's patch for both WHIP
and WHEP.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
This patch series adds support for WHIP and WHEP (WebRTC-HTTP ingestion protocol
and WebRTC-HTTP egress protocol). It supersedes the previous patch series for
WHIP.
The WHIP and WHEP are defined in the following draft RFCs:
- WHIP: https://datatracker.ietf.org/doc/draft-ietf-wish-whip
- WHEP:
Signed-off-by: Michael Riedl
---
configure | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configure b/configure
index 8ab658f7303..187f16b425d 100755
--- a/configure
+++ b/configure
@@ -223,6 +223,7 @@ External library support:
--enable-libcelt enable CELT decoding via libcelt
This is needed for (de)muxers which need to access the Location header as
transmitted when no redirection happend.
Signed-off-by: Michael Riedl
---
libavformat/http.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavformat/http.c b/libavformat/http.c
index c0fe7c36d91..27f9c8e3000
Whitespaces after semicolon breaks some servers
Signed-off-by: Michael Riedl
---
libavformat/sdp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat/sdp.c b/libavformat/sdp.c
index 68889362906..5ab017b1ba5 100644
--- a/libavformat/sdp.c
+++ b/libavformat/sdp.c
Signed-off-by: James Almer
---
libavformat/Makefile | 1 +
libavformat/avformat.c | 214 --
libavformat/demux.h| 29
libavformat/internal.h | 291 +--
libavformat/stream.c | 243 +
On 11/6/2023 8:37 AM, Anton Khirnov wrote:
Hi,
Quoting James Almer (2023-10-30 16:23:52)
Signed-off-by: James Almer
---
No changes since last version. I'm resending this for the IAMF demuxer.
I need opinions or reviews for this. We need to get this right from the start
and i don't want to
Signed-off-by: Michael Riedl
---
libavformat/webrtc.c | 398 +++
libavformat/webrtc.h | 70
2 files changed, 468 insertions(+)
create mode 100644 libavformat/webrtc.c
create mode 100644 libavformat/webrtc.h
diff --git a/libavformat/webrtc.c
Signed-off-by: Michael Riedl
---
configure | 2 +
libavformat/Makefile | 1 +
libavformat/allformats.c | 1 +
libavformat/webrtc_demux.c | 231 +
4 files changed, 235 insertions(+)
create mode 100644 libavformat/webrtc_demux.c
Signed-off-by: Michael Riedl
---
configure| 2 +
libavformat/Makefile | 1 +
libavformat/allformats.c | 1 +
libavformat/webrtc_mux.c | 273 +++
4 files changed, 277 insertions(+)
create mode 100644 libavformat/webrtc_mux.c
diff
On Mon, Nov 6, 2023 at 1:50 PM Nicolas George wrote:
> Paul B Mahol (12023-11-06):
> > Gonna apply soon.
>
> No you are not.
>
While I appreciate the brevity of this email, I think this kind of
communication is non constructive.
If the mailing list is the only and universal voice of the
Vittorio Giovara (12023-11-06):
> Nicolas, have you thought of providing a patch to the bug Paul is
> describing?
Why do you not ask Paul if he have thought of giving me time to have a
chance to do so?
--
Nicolas George
signature.asc
Description: PGP signature
On Sun, Nov 5, 2023 at 5:02 AM Anton Khirnov wrote:
> 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
On Mon, Nov 6, 2023 at 3:07 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > Nicolas, have you thought of providing a patch to the bug Paul is
> > describing?
>
> Why do you not ask Paul if he have thought of giving me time to have a
> chance to do so?
>
You gave no indication you
Vittorio Giovara (12023-11-06):
> You gave no indication you were willing to, and I thought he gave you time
Bullshit. Please do not intervene in a thread when you do not know what
is going on at all. Paul has been repeatedly rude and threatened to push
before review, yet it is towards me you
On 05/11/2023 21:01, Stefano Sabatini wrote:
@@ -159,7 +192,18 @@ sub ffmpeg_begin_file($$$)
my ($title, $description, $encoding, $date, $css_lines,
$doctype, $bodytext, $copying_comment, $after_body_open,
$extra_head, $program_and_version, $program_homepage,
-
On Mon, 6 Nov 2023 at 15:19, Michael Riedl
wrote:
> Whitespaces after semicolon breaks some servers
>
Are you sure this patch doesn't break other servers? SDP is a painfully
fragile format.
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
Impolitely pushing this out of oblivion for review.
The limited capabilities of FFmpeg HDMV_PGS decoder deters the usage of
advanced functionalities in hobbyist and professional applications. E.g !40981
is paramount for in-spec special effects.
I have merged both !40981 and !41826 (this) in the
On Mon, Nov 06, 2023 at 09:25:02AM +0100, Michael Koch wrote:
> Please delete:
> Comment 14 in ticket 2104
> Comment 2 in ticket 5154
> User "ballid"
>
> The duplicated search patterns in regex filter did work as expected (-20
> points), but the spammer got +20 points from captcha.
>
> I've
Hi all,
hi J-B!
On 2023-11-06 07:10 +0100, Jean-Baptiste Kempf wrote:
> Yo,
>
> Time is up, results are here:
> https://vote.ffmpeg.org/cgi-bin/civs/results.pl?id=E_029f7195fed7aadf
Should I have been mailed about this vote?
I'm pretty sure I could vote in 2020. Or am I just missing something?
On Mon, Nov 06, 2023 at 10:03:38AM +0100, Michael Koch wrote:
> Please delete also user "bunnylid". He did not yet write anything, but he
> did register with the same IP adress as the other spammer, only a few
> minutes earlier.
done
[...]
--
Michael GnuPG fingerprint:
On Mon, Nov 06, 2023 at 10:06:10AM +0100, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2023-10-27 19:53:08)
> > On Fri, Oct 27, 2023 at 02:44:10PM +0200, Michael Koch wrote:
> > > Is it possible to make the "Bad Content" page invisible? It would be
> > > better
> > > if the spammer can't
On Mon, Nov 6, 2023 at 10:20 AM Michael Riedl
wrote:
>
> Signed-off-by: Michael Riedl
> ---
> libavformat/webrtc.c | 398 +++
> libavformat/webrtc.h | 70
> 2 files changed, 468 insertions(+)
> create mode 100644 libavformat/webrtc.c
> create
Gonna apply soon.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Le maanantaina 6. marraskuuta 2023, 17.36.18 EET Kieran Kunhya a écrit :
> On Mon, 6 Nov 2023 at 15:19, Michael Riedl
>
> wrote:
> > Whitespaces after semicolon breaks some servers
>
> Are you sure this patch doesn't break other servers? SDP is a painfully
> fragile format.
AFAIK, you're not
On 2023-11-05 07:23 pm, 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 to have
been removed in
On 06.11.2023 16:19, Michael Riedl wrote:
Signed-off-by: Michael Riedl
---
libavformat/webrtc.c | 398 +++
libavformat/webrtc.h | 70
2 files changed, 468 insertions(+)
create mode 100644 libavformat/webrtc.c
create mode 100644
Signed-off-by: Cosmin Stejerean
---
tools/general_assembly.pl | 43 +--
1 file changed, 41 insertions(+), 2 deletions(-)
diff --git a/tools/general_assembly.pl b/tools/general_assembly.pl
index 898a6262ef..8204d89794 100644
--- a/tools/general_assembly.pl
+++
Per http://ffmpeg.org/pipermail/ffmpeg-devel/2023-November/316480.html
a list of emails should not be published as the GA membership. To
facilitate publishing the GA list this updates the GA script with
options to print only names, only emails (for voting) or both.
Changes since v1:
- added
Paul B Mahol (12023-11-06):
> Gonna apply soon.
No you are not.
--
Nicolas George
signature.asc
Description: PGP signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe,
On Mon, Nov 6, 2023 at 3:28 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > You gave no indication you were willing to, and I thought he gave you
> time
>
> Bullshit. Please do not intervene in a thread when you do not know what
> is going on at all. Paul has been repeatedly rude
Vittorio Giovara (12023-11-06):
> world, please make a minimum of effort to keep communication polite
Please realize that politeness resides not only in which words we use,
like “bullshit”, but also in what we say, even if it is with very mild
words. For example:
> while you insisted it wasn't
On Mon, Nov 6, 2023 at 3:50 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > world, please make a minimum of effort to keep communication polite
>
> Please realize that politeness resides not only in which words we use,
> like “bullshit”, but also in what we say, even if it is with
Please provide sample(s) so this can be validated.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject
Vittorio Giovara (12023-11-06):
> Nice try but pointing out your logical fallacies is not being rude, but
> rather is just showing you how easily your message can be misinterpreted,
You have done nothing of the sort. You have just misrepresented my
words, showing that you decided to barge into a
66 matches
Mail list logo
