On 2025-01-16 06:17 am, Danil Iashchenko wrote:
Add Nvidia Cuda and Cuda NPP sections for video filters.
---
doc/filters.texi | 1545 +++---
1 file changed, 778 insertions(+), 767 deletions(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index b9
On 2025-01-26 07:09 pm, Ronald S. Bultje wrote:
Hi,
On Sat, Jan 25, 2025 at 11:06 PM Gyan Doshi wrote:
On 2025-01-26 12:49 am, Marton Balint wrote:
On Sat, 25 Jan 2025, Gyan Doshi wrote:
In f121d95, the outlink framerate was unconditionally unset.
This breaks/bloats outputs from CFR mu
Hi Marth64
On Sat, Jan 25, 2025 at 04:40:00PM -0600, Marth64 wrote:
> Hello Michael,
>
> Complaint acknowledged. In the spirit of moving forward and de-escalating:
>
> Would you be open to a scheduled IRC meeting where we can talk through
> some of the project issues in real time?
> Ideally it i
> If the CC takes a clear action, this whole drama simply stops. Otherwise
> i suspect it will lead to a fork eventually. In the fork case they will leave
> with
> several others. I think thats a much bigger loss
I agree, Anton is gone because of your inflammatory behaviour
(banning, censorship e
On 2025-01-26 11:37 pm, Marth64 wrote:
I am only trying to be a voice of reason.
Please consider if we can have a community IRC meeting or in some other fashion
discuss a framework improvement in a safe space.
I would be happy to put together an agenda.
Will the activity of these meetings b
On Sun, Jan 26, 2025 at 9:24 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> On Sun, Jan 26, 2025 at 07:39:38PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > > I remember such a IRC session before the libav fork.
> > > It is very similar to this here
> > > 4+ people, who simply accuse me of
>
> Or is there any reason to not call it what it is (Dish)? There are Sega or
> Nintendo audio decoders and other examples and a cryptic description like
> "DVB 0502" renders it useless for almost everybody.
>
Agreed.
Kieran
>
___
ffmpeg-devel mailing
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Kieran Kunhya via ffmpeg-devel
> Sent: Sunday, January 26, 2025 11:05 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Kieran Kunhya
> Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg12dec.c: rename
On Sun, 2025-01-26 at 11:10 +0800, Nuo Mi wrote:
> AVCodecContext->sw_pix_fmt is used to hold the software pixel format.
>
> Co-authored-by: Frank Plowman
> ---
> libavcodec/vvc/dec.c | 17 ++---
> libavcodec/vvc/dec.h | 2 --
> 2 files changed, 6 insertions(+), 13 deletions(-)
>
>
I am only trying to be a voice of reason.
Please consider if we can have a community IRC meeting or in some other fashion
discuss a framework improvement in a safe space.
I would be happy to put together an agenda.
___
ffmpeg-devel mailing list
ffmpeg-de
On Thu, Dec 26, 2024 at 07:33:23PM +, Niklas Haas wrote:
> ffmpeg | branch: master | Niklas Haas | Mon Dec 16 14:49:39
> 2024 +0100| [af6d52eec66961f6a502b0f2f390c12226d087cd] | committer: Niklas
> Haas
>
> swscale: use 16-bit intermediate precision for RGB/XYZ conversion
>
> The current l
Hi Kieran
On Sun, Jan 26, 2025 at 07:39:38PM +, Kieran Kunhya via ffmpeg-devel wrote:
> > I remember such a IRC session before the libav fork.
> > It is very similar to this here
> > 4+ people, who simply accuse me of everything (on IRC though)
> > this serves no purpose. There is no common gr
On Sun, Jan 26, 2025 at 8:40 PM Rémi Denis-Courmont wrote:
>
> With my CC hat on,
>
> Le sunnuntaina 26. tammikuuta 2025, 21.39.38 UTC+2 Kieran Kunhya via ffmpeg-
> devel a écrit :
> > With Anton leaving the project because of you, Paul forking and James
> > leaving the CC because of your behaviou
On Sun, Jan 26, 2025 at 8:51 PM Kieran Kunhya wrote:
>
> On Sun, Jan 26, 2025 at 8:40 PM Rémi Denis-Courmont wrote:
> >
> > With my CC hat on,
> >
> > Le sunnuntaina 26. tammikuuta 2025, 21.39.38 UTC+2 Kieran Kunhya via ffmpeg-
> > devel a écrit :
> > > With Anton leaving the project because of y
Hi,
That is what I am imagining when I mean have a meeting, suggesting
that maybe we should try a different communication medium that can be
facilitated more rapidly.
I was thinking an IRC meeting would be more beneficial than email
because email is hard to moderate.
In IRC, there are more easily
> Agreed.
I'm good too, thanks for the input.
___
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".
Hi,
On Sat, Jan 25, 2025 at 11:06 PM Gyan Doshi wrote:
>
>
> On 2025-01-26 12:49 am, Marton Balint wrote:
> >
> >
> > On Sat, 25 Jan 2025, Gyan Doshi wrote:
> >
> >> In f121d95, the outlink framerate was unconditionally unset.
> >> This breaks/bloats outputs from CFR muxers unless the user expli
From: Pierre-Anthony Lemieux
---
libavfilter/vf_psnr.c | 70 +++
tests/fate-run.sh | 36 ++
2 files changed, 94 insertions(+), 12 deletions(-)
diff --git a/libavfilter/vf_psnr.c b/libavfilter/vf_psnr.c
index 4a173c73d9..3f55562cec
From: Pierre-Anthony Lemieux
---
tests/fate/jpeg2000.mak | 130 ++-
tests/ref/fate/jpeg2000dec-ds0_hm_15_b8 | 6 ++
tests/ref/fate/jpeg2000dec-ds0_ht_02_b11 | 6 ++
tests/ref/fate/jpeg2000dec-ds0_ht_02_b12 | 6 ++
tests/ref/fate/jpeg2000dec-ds0_ht_03_b
For h264/hevc, when using the raw demuxer, parse_packet() may parse
multiple frames from a single input packet, depending on the setting of
-raw_packet_size. The first parsed packet is returned from
read_frame_internal(), while the subsequent parsed packets are stored in
the parse queue, and return
This error code is for expected exits, like after listing options for a
device.
---
fftools/ffmpeg_demux.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fftools/ffmpeg_demux.c b/fftools/ffmpeg_demux.c
index 0fd095d8ae..5ff75eed1a 100644
--- a/fftools/ffmpeg_demux.c
+++ b
The ref input may have its frame rate unset, which would then lead to
SIGFPE.
Related to #11428
---
libavfilter/vf_xpsnr.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavfilter/vf_xpsnr.c b/libavfilter/vf_xpsnr.c
index 1b2c2a7c2c..8f86c188c5 100644
--- a/libavfilter/vf
Commit ba4b73c9779c32580f8a3ba08602a5d94e0bcd7c caused a regression in
the usage of avg_frame_rate to detect the frame rate of raw h264/hevc
bitstreams: after the commit, avg_frame_rate is always the value of the
-framerate option (which is set to 25 by default) instead of the actual
frame rate der
In f121d95, the outlink framerate was unconditionally unset.
This breaks/bloats outputs from CFR muxers unless the user explicitly
sets a sane framerate. And the most common invocation for setpts seen in
workflows, our docs and across the web is `PTS-STARTPTS` or others of the
general form `PTS+con
Hi
On Sat, Jan 25, 2025 at 6:56 AM Michael Niedermayer
wrote:
>
> On Sat, Jan 25, 2025 at 02:19:52AM +0100, Michael Niedermayer wrote:
> > Hi
> >
> > On Tue, Jan 21, 2025 at 05:30:05PM +0530, Viraaj Raulgaonkar wrote:
> > > Sample rates up to 2^31 - 1 are considered valid, while greater values
>
On Sun, 26 Jan 2025, 00:31 Soft Works,
wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Marth64
> > Sent: Sunday, January 26, 2025 1:14 AM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg1
Instead of returning an error for invalid sample rates, warn the user
and set sample_rate to INT_MAX. This allows the sample rate to be
decoded in certain cases.
Fixes Trac Ticket #11361.
---
libavformat/riffdec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat
Hi Michael,
> I believe discusion about ffmpeg should be public and on the mailing list
> where everyone can participate
It should be public and people should participate. It can also be
real-time and on IRC.
Clearly this was done in the past.
Literally on the front page of TRAC, there is a secti
Hi Gyan,
> Will the activity of these meetings be recorded and available publicly?
If we have a meeting, I would expect it to be recorded and available
publicly just like here:
https://trac.ffmpeg.org/wiki/FFmeeting/2020-12
Looks like the process was established before :)
_
Hi Marth64
On Sun, Jan 26, 2025 at 11:34:37AM -0600, Marth64 wrote:
> Hi Michael,
>
> > I believe discusion about ffmpeg should be public and on the mailing list
> > where everyone can participate
> It should be public and people should participate. It can also be
> real-time and on IRC.
> Clearl
On Sun, 26 Jan 2025, Gyan Doshi wrote:
On 2025-01-26 07:09 pm, Ronald S. Bultje wrote:
Hi,
On Sat, Jan 25, 2025 at 11:06 PM Gyan Doshi wrote:
On 2025-01-26 12:49 am, Marton Balint wrote:
On Sat, 25 Jan 2025, Gyan Doshi wrote:
In f121d95, the outlink framerate was unconditional
> I remember such a IRC session before the libav fork.
> It is very similar to this here
> 4+ people, who simply accuse me of everything (on IRC though)
> this serves no purpose. There is no common ground here
Hi Michael,
With Anton leaving the project because of you, Paul forking and James
leavi
Signed-off-by: Kacper Michajłow
---
libavformat/vqf.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/libavformat/vqf.c b/libavformat/vqf.c
index 58b1546f53..fbe54739cd 100644
--- a/libavformat/vqf.c
+++ b/libavformat/vqf.c
@@ -66,10 +66,10 @@ static int add_metadata(A
On Sun, 26 Jan 2025, Viraaj Raulgaonkar wrote:
Instead of returning an error for invalid sample rates, warn the user
and set sample_rate to INT_MAX. This allows the sample rate to be
decoded in certain cases.
Fixes Trac Ticket #11361.
---
libavformat/riffdec.c | 4 ++--
1 file changed, 2 inse
Le sunnuntaina 26. tammikuuta 2025, 17.06.28 UTC+2 Michael Niedermayer a écrit
:
> I believe discusion about ffmpeg should be public and on the mailing list
> where everyone can participate
> Also as you say "without interpersonal arguments" I see no reason
> for it not to be on the public mailing
With my CC hat on,
Le sunnuntaina 26. tammikuuta 2025, 21.39.38 UTC+2 Kieran Kunhya via ffmpeg-
devel a écrit :
> With Anton leaving the project because of you, Paul forking and James
> leaving the CC because of your behaviour of banning and censoring,
Kieran, there is a fine line between citing
36 matches
Mail list logo
