mit in a bit.
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
need sponsorship, please check with
> FFmpeg's treasurer (who is not me).
Sounds cool!
Did you ask for a both?
If you did it would be best to add an entry in the conferences page:
https://trac.ffmpeg.org/wiki/Conferences
Greetings,
Alexander
_________
t ideas.
Some suggestions to get started follow in no particular order:
* objpool_fifo
* reusable_obj_fifo
* refstruct_fifo
Best regards,
Alexander
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
s is a keyframe and b) a sequence header is present. A keyframe with no
sequence header (which an encoder might decide to emit) or a sequence header in
a non-keyframe like you're describing will not result in the N bit being set.
Hopefully that clarifies things.
Best,
Tristan
_____
was to remove the .alt files after at least all fate clients
have been updated to zlib implementations that don't need it anymore.
Alexander
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffm
o you see a bias in
> the CCs decissions ? (as a whole not based on what i write here)
> And if so what do you plan to do about it ?
But your opinions in this thread are not biased and are factual?
Reporting this thread to CC.
Kieran
_______
ffmpeg-devel m
ng
to happen but is not capable of acting on the vote.
Regards,
Kieran Kunhya
-- Forwarded message -
From:
Date: Thu, 19 Dec 2024, 08:55
Subject: Your message to ffmpeg-devel awaits moderator approval
To:
Your mail to 'ffmpeg-devel' with the subject
Re: [FFmpeg-d
Hello,
This person asked for coverity access:
https://x.com/acentauri92/status/1867186643704099105
I don't know if they should have access.
Kieran
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-
t relative to 29.97 video.
I'm not really sure how an atomic clock is relevant.
Kieran
>
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
On Thu, 12 Dec 2024, 13:07 Nicolas Gaullier,
wrote:
> >De : ffmpeg-devel de la part de Anton
> Khirnov
> >Envoyé : jeudi 12 décembre 2024 09:36
> >
> >I am not intimately familiar with these formats and their mutual
> >relationship, so these problems you refe
t; regression fix or anything like that, but the change adds value for being
> able to use checkasm to benchmark compiler performance.
LGTM.
Tested on aarch64 .
Total run times match.
Output had only additional lines which all were for functions ending in `_c`
Alexander
__
On 2024-12-14 11:09 +0100, Anton Khirnov wrote:
> Quoting Alexander Strasser via ffmpeg-devel (2024-12-01 21:13:56)
> > This is a fixed up version of the series I sent before.
> >
> > This worked for me on Ubuntu 20.04 but probably will break
> > with older zlib version
On Fri, 13 Dec 2024, 02:46 Michael Niedermayer,
wrote:
> Hi
>
> On Fri, Dec 13, 2024 at 01:40:43AM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Thu, 12 Dec 2024, 13:07 Nicolas Gaullier, >
> > wrote:
> >
> > > >De : ffmpeg-devel de la
On Fri, 13 Dec 2024, 10:00 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Where is the second sample rate stored in wav?
>
> Nowhere, obviously. I am surprised somebody who has been in the project
> for more than 12 years still does not know how it
On Fri, 13 Dec 2024, 10:14 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Then the conclusion in your example is wrong.
>
> No it is not. Either you misunderstood what I explained — I am guessing
> you only read it superficially, you did not actuall
On Fri, 13 Dec 2024, 09:31 Nicolas George, wrote:
> Kieran Kunhya via ffmpeg-devel (12024-12-13):
> > Does FFmpeg even support a new sample rate per AVFrame?
>
> Generate a 48000 Hz MP3.
> Generate a 32000 Hz MP3.
> Concatenate them.
> Convert the result to wave.
>
On Thursday, December 12th, 2024 at 4:18 AM, Chris Hodges
wrote:
> Hi Tristan,
>
> thanks for taking the time reviewing.
>
> On 12/6/24 18:39, Tristan Matthews via ffmpeg-devel wrote:
>
> > Hi (also apologies if my client mangles the inline version of the patch,
>
On Fri, 13 Dec 2024, 13:41 Niklas Haas, wrote:
> On Fri, 13 Dec 2024 01:37:34 + Kieran Kunhya via ffmpeg-devel <
> [email protected]> wrote:
> > On Fri, 13 Dec 2024, 00:39 Michael Niedermayer,
> > wrote:
> >
> > > Hi
> > >
> &g
can discuss the changes and it gives me more time to look into the
> issue below.
>
> On 12/11/24 23:53, Tristan Matthews via ffmpeg-devel wrote:
>
> > Aside from my minor comments on the patch, one thing that came up in terms
> > of testing is that while the packetization seems
"Sets the maximum number of reference frames. This only has an
effect when the value is less than the maximum allowed by the
profile/level.", \
OFFSET(max_ref_frames), AV_OPT_TYPE_INT, { .i64 = 0 }, 0,
INT_MAX, VE },
--
2.39.1.windows.1
If they are internally mapping to +2 and +4, I am not
sure it's a good idea that FFmpeg features are added to work around
someone's firewall limitation.
Kieran
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
it not happened?
You can't complain it the CC fails to act when it has voted for something
to happen but is not capable of acting on the vote.
Regards,
Kieran Kunhya
>
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/
else {
> deblock_topleft = (sl->mb_x > 0);
> --
> 2.43.0
Hi Lingyi,
Thank you for your patch. Would it be possible to create a FATE test for this?
https://trac.ffmpeg.org/wiki/FATE/AddingATest
Regards,
Kieran Kunhya
_______
ffmpeg
On Thu, 19 Dec 2024, 20:30 compn, wrote:
> On Thu, 19 Dec 2024 20:15:10 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > Some Animals are More Equal Than Others.
> >
> > Kieran
>
> and now a CC candidate calling devs animals ?
>
This is one of th
On Thu, 19 Dec 2024, 20:38 compn, wrote:
> On Thu, 19 Dec 2024 20:35:43 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > On Thu, 19 Dec 2024, 20:30 compn, wrote:
> >
> > > On Thu, 19 Dec 2024 20:15:10 +0000, Kieran Kunhya via ffmpeg-devel
> > > wro
On Thu, Dec 19, 2024 at 7:25 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> First before replying, id like to say, that i hope we can resolve this and
> in the future work together in a mutually more friendly way.
>
> On Wed, Dec 18, 2024 at 10:18:20PM -0500, Kieran Ku
to happen with the queued emails.
The decentralized/freedom aspects of email are a strong part about
what makes email good.
Thank you Kieran for complaining about this by opening this thread!
Alexander
>
> reading the mails stuck in the moderation queue and clearing the
> moderation
On Thu, Dec 19, 2024 at 7:52 PM Michael Niedermayer
wrote:
>
> Hi compn
>
> On Thu, Dec 19, 2024 at 06:16:03AM -1000, compn wrote:
> > On Thu, 19 Dec 2024 08:58:14 +, Kieran Kunhya via ffmpeg-devel
> > wrote:
> >
> > > Hello,
> > >
> &g
better long-term solution here isn't to just
> > improve the way libavfilter auto-inserts conversion filters, such that it
> > could
> > automatically insert a paletteuse filter when downstream requires PAL8.
>
> PAL8 is tricky, encoders may benefit from similarities in p
On Thu, Dec 19, 2024 at 9:11 PM compn wrote:
>
> On Thu, 19 Dec 2024 20:40:55 +, Kieran Kunhya via ffmpeg-devel
> wrote:
>
> > Please can you confirm you will be resigning your moderator status in light
> > of the election censorship you have undertaken while at t
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
der
> +
> +fate-clear-results:
> + @rm -f tests/data/fate/*.rep
> +
> coverage.info: TAG = LCOV
> coverage.info:
> $(M)lcov -q -d $(CURDIR) -b $(patsubst src%,./,$(SRC_LINK)) --capture |
> \
> --
_______
ffmpeg-devel
Hi (also apologies if my client mangles the inline version of the patch, it's
the first time I've tried to review an attached patch with it)...
On Monday, December 2nd, 2024 at 9:57 AM, Chris Hodges
wrote:
> Hi,
>
> On 11/25/24 18:47, Tristan Matthews via ffmpeg-devel wr
int p_to_gpb;
+// The number of L0/L1 references supported by the driver.
+int ref_l0;
+int ref_l1;
+
// Whether the driver supports ROI at all.
int roi_allowed;
--
2.47.1
___
ffmpeg-devel
text {
int end_of_stream;
int p_to_gpb;
+// The number of L0/L1 references supported by the driver.
+int ref_l0;
+int ref_l1;
+
// Whether the driver supports ROI at all.
int roi_allowed;
--
2.47.1
__
pkg_cflags=$($pkg_config --cflags $pkg_config_flags $pkg)
> pkg_incdir=$($pkg_config --variable=includedir $pkg_config_flags $pkg)
> pkg_incflags=$($pkg_config --cflags-only-I $pkg_config_flags $pkg)
> --
___
ffmpeg-devel mailing list
ffmpeg-d
intolerant where anyone with the slightest bit of observance can see the
problem is you (and your surrogates).
Merry Christmas!
Kieran
>
_______________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubsc
his into a
more readable and potentially stronger form.
Best regards,
Alexander
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
> > 2.41.0
>
> Looks ok - I've managed to reproduce this now.
>
> I'll apply this, and backport it to the 7.1 branch.
Thanks Martin!
FTR: I could also reproduce and confirm the fix locally.
Alexander
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
On 2025-01-10 10:40 -0300, James Almer wrote:
> On 1/10/2025 10:05 AM, James Almer wrote:
> > On 1/7/2025 6:50 PM, Alexander Strasser via ffmpeg-devel wrote:
> > > On 2025-01-07 10:55 -0300, James Almer wrote:
> > > > Should reduce memory usage as w
them and partially tested locally.
Nice clean ups. Thank you!
Best regards,
Alexander
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ.
or(input) || !feof(input))
+if (ferror(input) || !feof(input)) {
+fclose(input);
return -1;
+ }
fclose(input);
--
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
> -const int a = FFABS(v);
> +const unsigned a = is_signed ? FFABS(v) : v;
> const int e = av_log2(a);
> put_rac(c, state + 0, 0);
> if (e <= 9) {
> --
LGTM but s/sambols/symbols/ in the Subject/Git-short-message I suspect.
Alexander
_
(and should be non-controversial to push at this point)
Thanks,
Alexander
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
{v18.4s, v19.4s}, [x0], #32
+stp q18, q19, [x0], #32
b.ne1b
ret
endfunc
--
2.45.2
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe
Removed two redundant pointer arithmetic operations and split load
section into two smaller ones.
Speedup compared to C increased from 4.50 to 5.80.
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> +av_log(ctx, AV_LOG_ERROR, "Failed init OpenVINO executable
> network or inference request\n");
> return ret;
> }
> }
> --
LGTM, will push it soon'ish if Guo doesn't beat me to it.
Thanks,
Alexander
______
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
On Wed, Jan 22, 2025 at 3:33 PM Michael Niedermayer
wrote:
>
> On Mon, Jan 20, 2025 at 06:46:46AM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > >
> > > > The data arrives on multiple sockets, leading to all sorts
> > > > of opportunities
for new contributors?
Running two systems concurrently is a recipe for disaster and makes a
difficult process essentially impossible.
Kieran
>
___________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To u
On Wed, Jan 22, 2025 at 4:37 PM Michael Niedermayer
wrote:
>
> Hi
>
> On Mon, Jan 20, 2025 at 03:00:17PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
>
> > Error recovery protocols are complicated -
>
> everything is complicated
>
>
> > this
On Wed, Jan 22, 2025 at 4:53 PM Romain Beauxis wrote:
>
> Le mer. 22 janv. 2025 à 10:29, Kieran Kunhya via ffmpeg-devel
> a écrit :
> >
> > On Wed, Jan 22, 2025 at 3:33 PM Michael Niedermayer
> > wrote:
> > >
> > > On Mon, Jan 20, 2025 at 06:
separator Character that separates items in the given lists.
+ *
+ * @returns 0 if no match was found, otherwise 1.
*/
int av_match_list(const char *name, const char *list, char separator);
--
___
ffmpeg-devel mailing list
[email protected]
https
e
dozens of other FFmpeg developers in the room.
Regards,
Kieran Kunhya
___________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
llenging the validity of an election is rather in vogue these days.
Regards,
Kieran Kunhya
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-re
On Tue, 21 Jan 2025, 18:57 James Almer, wrote:
> On 1/21/2025 3:13 PM, Kieran Kunhya via ffmpeg-devel wrote:
> > On Tue, Jan 21, 2025 at 5:42 PM Michael Niedermayer
> > wrote:
> >>
> >> Hi
> >>
> >> As people likely know i belive it
On Wed, Jan 22, 2025 at 4:37 PM Michael Niedermayer
wrote:
>
> Hi
>
> On Mon, Jan 20, 2025 at 03:00:17PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
>
> > Error recovery protocols are complicated -
>
> everything is complicated
>
>
> > this
> Can you please stop this "my way or no way"
The irony is not lost on me of this sentence (from the person banning
people, censoring people, creating paranoid theories about the GA).
Kieran
_______
ffmpeg-devel mailing list
ffmpeg-devel@ffm
but what stops an attacker from
faking the extension?
Kieran
>
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
he FEC
> matrix within with the current packet belongs to.
> * Beside that, the decoder keeps a maximum number of packets and FEC
> packets.
I don't see any evidence of wraparound handling unless I miss
something. An FEC matrix can span a wraparound.
Kieran
______
endif
+fcvtzs v3.4s, v3.4s
+st1 {v3.4s}, [x0], #16
+b.ne\signed\()b
+ret
+.endr
+endfunc
--
2.45.2
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
. You say heuristics are not needed and then just claim an issue
that obviously needs heuristics is "out of scope".
Kieran
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe,
On 2025-01-22 23:19 +0100, [email protected] wrote:
>
> On 22 Jan 2025, at 22:59, Alexander Strasser via ffmpeg-devel wrote:
>
> > Since av_match_list was added in commit 0d92b0d5f445d4f2 , this
> > function changed its semantics shortly after, especially with
> &
> 2.25.1
> >
>
> Ping
Seems like your mail client/editor does it (automatically?) to avoid
overly long lines, which might be fine for email texts but isn't in
patches.
Hope you can find the setting for easier contribution in the future.
Another approach for single patches o
On Sun, Jan 19, 2025 at 10:57:57PM +0200, Martin Storsjö wrote:
> On Sun, 19 Jan 2025, Krzysztof Pyrkosz via ffmpeg-devel wrote:
>
> > Removed a branch, unrolled loop. Speed increase bumped from 3.95 to 5.60.
>
> On what core is that? Please quote the actual output incl
);
--
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
On Thu, 23 Jan 2025, 00:11 Michael Niedermayer,
wrote:
> Hi Kieran
>
> On Wed, Jan 22, 2025 at 10:47:52PM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Wed, 22 Jan 2025, 20:36 Michael Niedermayer,
> > wrote:
> >
> > > This blocks disallowed extensi
ss there we add a field with
> individual size greater than end_padding, hence intmax_t.
Sorry, couldn't really follow the problem and this solution idea yet.
Just think we shouldn't use intmax_t as I think it wasn't a good idea
to have it in the C standard at all.
Is it es
tput
> recovery point SEI with useless fields, which makes user who want to use
> intra refresh
> encoding must specify -flags output_corrupt for decoding. That is, without
> recovery point
> SEI, user should have prior knowledge on encoding configuration before
> decoding.
>
y delays between the two links. You
can't just "buffer N packets".
Another edge case.
Kieran
>
_______________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or
with stimulated network issues and found it to be
> > > > able to restore most packets event at 10 or 20% packet drops.
> > > >
> > > > I have also tested it with a bad local broadband.
> > > >
> > > > We plan on testing it more with a conc
19:12, Vitaly Buka via ffmpeg-devel wrote:
> > UBSAN by default is just prints a mesage and
> > moves on. This hides a few UBs in fate-suite.
> >
> > Signed-off-by: Vitaly Buka
> > ---
> > configure | 4 ++--
> > libavcodec/aacen
On Tue, Dec 24, 2024 at 9:34 AM Lingyi Kong wrote:
>
> add fate test case
>
> Signed-off-by: Lingyi Kong
For whatever reason PATCHv4 is in neither of my email boxes, one of
which is subscribed to ffmpeg-devel, the other of which is not
subscribed but I still receive the emails.
to get
STF money for work the community does not want because it's already been
done?
It's funny how all roads appear to end up going to "Michael does what he
wants".
Kieran
>
_______
ffmpeg-devel mailing list
[email protected]
On Fri, Jan 17, 2025 at 3:12 PM James Almer wrote:
> On 1/17/2025 7:53 PM, Vitaly Buka via ffmpeg-devel wrote:
> > My confusion here is that it looks like ffmpeg developers care about UB,
> I
> > see from time to time large cleanups, but there are a bunch of unfixed
>
On Mon, Jan 20, 2025 at 2:51 PM Nicolas George wrote:
>
> Kieran Kunhya via ffmpeg-devel (12025-01-17):
> > I am the author of the only known functional OSS implementation of FEC.
>
> Seen from here, your rejection of this proposal looks a teeny tiny
> little bit like trying
, censorship etc) and the CC should have dealt with it.
Kieran
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
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
> &g
>
> 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
>
____
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
> > lea
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 :
> > &
have no opinions about the rest of the text.
Kieran
>
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
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 > [email protected]>
> > Subj
ng and James
leaving the CC because of your behaviour of banning and censoring,
have you ever considered the problem might be you?
Regards,
Kieran Kunhya
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To
significantly, the initial
benchmark values can be used.
Krzysztof
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
On Mon, Jan 27, 2025 at 7:03 PM Soft Works wrote:
>
> > From: ffmpeg-devel On Behalf Of
> > Kieran Kunhya via ffmpeg-devel
> > Sent: Monday, January 27, 2025 10:40 AM
> > > While this is a very valid concern for some kinds of frame side
> > data, it
> >
1203, "shuffle_bytes_1203");
+report("shuffle_bytes_1203");
+
+check_shuffle_bytes(shuffle_bytes_2130, "shuffle_bytes_2130");
+report("shuffle_bytes_2130");
+
check_uyvy_to_422p();
report("uyvytoyuv422");
--
2.45.2
___
>
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
Hello,
Would it be possible to merge this patch?
Thanks,
Vitaly
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with
t to CC?
>
Hi Remi,
Are you not aware than when Michael does something inflammatory like that
it's a "joke", but any criticism of his behaviour is an "attack"? Just
wanted to be sure you understood the correct terminology used on this ML.
Regards,
Kieran Kunhya
>
lob/master/src/lib_ccx/es_userdata.c#L275
Kieran
>
___________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
transparency about infrastructure, but Michael
refuses to publish.
The community doesn't want arbitrary censorship, but Michael and his
surrogates do.
etc.
Just ask ChatGPT to rewrite Vittorio's email.
Kieran
___
ffmpeg-devel mailing l
cess is and you've turned it into "yet another Michael wall of
text" that has nothing to do with the topic but instead yet another
incoherent airing of your current grievances and the usual defence of
your buddies.
It's clear the contribution method is outdated and difficult t
where you are in control as usual. Your recent
behaviour of condoning censorship during an election and blocking of
contributors on spurious grounds shows that.
Read Tom's quote again and practice what you preach.
Regards,
Kieran Kunhya
>
_______
t;&1 || awk -F: '$$2 != 0 {
print "fate-" $$1 }' tests/data/fate/*.rep
+
+fate-clear-reports:
+ @rm -f tests/data/fate/*.rep
+
coverage.info: TAG = LCOV
coverage.info:
$(M)lcov -q -d $(CURDIR) -b $(patsubst src%,./,$(SRC_LINK)) --capture |
\
```
default:
> -add_metadata(s, chunk_tag, len, header_size);
> +ret = add_metadata(s, chunk_tag, len, header_size);
> +if (ret < 0)
> + return ret;
> break;
> }
>
> --
LGTM regarding my review comments.
Alexand
POV they
can be variable, from the POV of the single expression
evaluation they are constant :)
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
It's Christmas day, give it a rest.
Kieran
On Wed, Dec 25, 2024 at 1:31 PM Michael Niedermayer
wrote:
>
> Hi Community, Community Commitee, Moderators
>
> The message: lists.ffmpeg.org pipermail ffmpeg-devel/2024-December/337868.html
> Is unacceptable. We had alot of messag
On 2024-12-21 19:29 -0500, J Shiff wrote:
> On Sat, Dec 21, 2024 at 5:44 PM Alexander Strasser via ffmpeg-devel
> wrote:
> >
> > On 2024-12-16 16:19 -0500, Joe Schiffler wrote:
> > > Since $pkg_version includes spaces, builds can fail in some MSYS
> > > envir
2001 - 2100 of 3579 matches
Mail list logo
