> On May 21, 2024, at 11:54 AM, Cosmin Stejerean via ffmpeg-devel
> wrote:
>
>
> However I've found a workaround. By setting my git send-email from to just
> "[email protected] <mailto:[email protected]>" rather than "Cosmin Stejerean
> mailto:
On 21.05.24 21:42, Rémi Denis-Courmont wrote:
Le tiistaina 21. toukokuuta 2024, 21.43.44 EEST Thilo Borgmann via ffmpeg-devel
a écrit :
Same as above about that we should and STF would.
Especially since no corporate interest usually pays anyone for these
tasks
Sadly true, but...
(in case
it company.
Same remark as in the previous mail. I'm not sure how you mean that
whole thing. Please elaborate / put in other words.
-Thilo
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To uns
On Tue, 14 May 2024 19:07:59 -0700
Philip Langdale via ffmpeg-devel wrote:
> On Wed, 15 May 2024 01:36:43 +0530
> [email protected] wrote:
>
> > From: llyyr
> >
> > ab77b878f1 attempted to fix the issue of broken packets being sent
> > to the decode
> On May 21, 2024, at 9:19 PM, Andreas Rheinhardt
> wrote:
>
> Cosmin Stejerean via ffmpeg-devel:
>> From: Cosmin Stejerean
>>
>> These two fields are coded together into a single 16 bit integer with upper 8
>> bits for ext_mapping_idc and
LIBAVUTIL_VERSION_MINOR 19
+#define LIBAVUTIL_VERSION_MINOR 20
#define LIBAVUTIL_VERSION_MICRO 100
#define LIBAVUTIL_VERSION_INT AV_VERSION_INT(LIBAVUTIL_VERSION_MAJOR, \
--
2.42.1
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman
atial_resampling_filter_flag);
put_bits(pb, 3, 0); /* reserved_zero_3bits */
--
2.42.1
_______
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".
el_bit_depth_minus8 and ext_mapping_idc
libavcodec/dovi_rpudec.c | 7 ++-
libavcodec/dovi_rpuenc.c | 4 +++-
libavutil/dovi_meta.h| 2 ++
libavutil/version.h | 2 +-
4 files changed, 12 insertions(+), 3 deletions(-)
--
2.42.1
___
ffmpeg-devel mailing
gt; deltas
> > >
> > > base-commit: d263fce2b209e86a5a1e8f1b6aa33430ecc2c187
> > > --
> >
> > Change LGTM.
> > I was debugging the same issue today, and found the same problem
> > with some hwaccels not properly ignoring update_map when
> > segmentation is disabled.
> >
> > Will apply soon if there are no further comments.
> >
>
> Is fine, please apply.
>
Another LGTM. We've been seeing this reported on the mpv side as well.
--phil
___
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 Tue, May 21, 2024 at 9:50 AM Thilo Borgmann via ffmpeg-devel
wrote:
>
> Hi,
>
> [...]
> >>> Tests mostly work for me. There are a few images (that I reported
> >>> earlier) that give:
> >>
> >> thanks for testing!
> >>
> &g
> On May 21, 2024, at 3:19 AM, Niklas Haas wrote:
>
> On Tue, 21 May 2024 04:03:43 + Cosmin Stejerean via ffmpeg-devel
> wrote:
>>
>> diff --git a/libavcodec/libaomenc.c b/libavcodec/libaomenc.c
>> index dec74ebecd..c6104f5522 100644
>> --- a/libavc
_TYPE_BOOL, { .i64 = 1 }, 0, 1,
VE },
{ "x265-params", "set the x265 configuration using a :-separated list of
key=value parameters", OFFSET(x265_opts), AV_OPT_TYPE_DICT, { 0 }, 0, 0, VE },
#if X265_BUILD >= 167
-{ "dolbyvision", "Enable Dolby Vision R
.42.1
___
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".
ext_blocks;
int num_ext_blocks;
+/**
+ * Enable metadata compression in the output. Currently this is
experimental.
+ */
+int enable_compression;
+
/**
* Private fields internal to dovi_rpu.c
*/
--
2.42.1
___
ff
;s->vdr[vdr_rpu_id]->mapping, mapping, sizeof(*mapping));
buffer_size = 12 /* vdr seq info */ + 5 /* CRC32 + terminator */;
buffer_size += num_ext_blocks_v1 * 13;
--
2.42.1
___________
ffmpeg-devel mailing list
[email protected]
https://f
partitions", "Enable 1:4/4:1 partitions",
OFFSET(enable_1to4_partitions), AV_OPT_TYPE_BOOL, {.i64 = -1}, -1, 1, VE},
{ "enable-ab-partitions", "Enable ab shape partitions",
OFFSET(enable_ab_partitions), AV_OPT_TYPE_BOOL, {.i64 = -1}, -1, 1, VE},
--
"auto", NULL, 0, AV_OPT_TYPE_CONST, {.i64 = FF_DOVI_AUTOMATIC}, .flags
= VE, .unit = "dovi" },
+DOVI_ENCODING_OPTS(dovi)
#endif
{ NULL }
};
--
2.42.1
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.or
i" },
+DOVI_ENCODING_OPTS(dovi)
{NULL},
};
--
2.42.1
_______
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 May 23, 2024, at 4:03 AM, Niklas Haas wrote:
>
> On Wed, 22 May 2024 15:50:43 + Cosmin Stejerean via ffmpeg-devel
> wrote:
>> From: Cosmin Stejerean
>>
>> ---
>> libavutil/dovi_meta.h | 2 ++
>> libavutil/version.h | 2 +-
>&
Am 22.05.24 um 14:27 schrieb Rémi Denis-Courmont:
Le 22 mai 2024 00:34:03 GMT+03:00, Thilo Borgmann via ffmpeg-devel
a écrit :
I hope you realize what you argue in favor of.
Yes. It's quoted above.
Are you claiming that *no* review is better than *some* review done in
*public* for a
or such extreme cases like these.
Thanks,
Thnilo
___________
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".
/* update ctts context */
sc->ctts_sample++;
if (sc->ctts_index < sc->ctts_count &&
--
2.45.1.288.g0e0cd299f1-goog
_______
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".
tifies adopting this method for
achieving resilient but compatible recordings in my mind.
~ Dennis
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ff
On 2024-04-29 23:53 +0200, Alexander Strasser via ffmpeg-devel wrote:
> When piping ffmpeg into ffplay both programs write a status line in
> the terminal. That causes flickering and invisibility of one or the
> other status line.
>
> As compromise set ffplay log level to warning
fix wrongly when adding new code.
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".
On 2024-06-02 13:30 +0300, Rémi Denis-Courmont wrote:
> Le sunnuntaina 2. kesäkuuta 2024, 13.04.05 EEST Alexander Strasser via ffmpeg-
> devel a écrit :
> > On 2024-05-29 18:51 +0300, Rémi Denis-Courmont wrote:
> > > Le keskiviikkona 29. toukokuuta 2024, 18.44.13 EEST
On 2024-06-02 21:36, Martin Storsjö wrote:
On Sat, 1 Jun 2024, Dennis Sädtler via ffmpeg-devel wrote:
Should the ftyp atom also be updated to remove brands no longer
required for non-fragmented files?
I'm not sure how important that is in real-world scenarios, so it
might not be worth
some people in Amsterdam
We have a booth on IBC this year which again gets sponsored so no costs for
FFmpeg.
Some details are still unclear which is why it's not yet announced.
@Thomas: Happy you want to attend, I'll keep you updated.
-Thilo
_______
#x27;s
description could explain what it does in a bit more detail.
For OBS I settled on "Hybrid MP4" and calling the process of hiding the
fragments a "soft remux", but the name of the flag should probably be a
bit more technical.
~Dennis
___________
lematic than that.
- Cosmin
___
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 Jun 3, 2024, at 10:36 AM, Rémi Denis-Courmont wrote:
>
> Le 3 juin 2024 19:43:52 GMT+03:00, Cosmin Stejerean via ffmpeg-devel
> a écrit :
>>
>>
>>> On Jun 3, 2024, at 12:55 AM, Rémi Denis-Courmont wrote:
>>>
>>> IBC is probably not
> On Jun 3, 2024, at 11:18 AM, Rémi Denis-Courmont wrote:
>
> Le maanantaina 3. kesäkuuta 2024, 20.48.08 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>>>> What was cost-problematic about NAB? As far as I know it cost ffmpeg $0.
>>>> It would be hard
> On Jun 3, 2024, at 12:26 PM, Rémi Denis-Courmont wrote:
>
> Le maanantaina 3. kesäkuuta 2024, 21.58.48 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>> Not sure why you keep beating this dead horse.
>
> Err, I think that it is obvious why:
>
> 1) The qu
> On Jun 3, 2024, at 3:58 PM, Vittorio Giovara
> wrote:
>
> On Mon, Jun 3, 2024 at 10:57 PM Cosmin Stejerean via ffmpeg-devel <
> [email protected]> wrote:
>
>>
>>
>>> On Jun 3, 2024, at 12:26 PM, Rémi Denis-Courmont
>> wrote:
>&
> On Jun 3, 2024, at 11:53 PM, Vittorio Giovara
> wrote:
>
> On Tue, Jun 4, 2024 at 3:01 AM Cosmin Stejerean via ffmpeg-devel <
> [email protected]> wrote:
>
>>> Reposting my question/comment here since Thilo hasn't had a chance to
>>> re
lly jump in. And if more than 1 person resign, a new
election can be held.
Sounds as a good possibility to me. We should determine our procedure of
choice and put it into the docs.
-Thilo
_______
ffmpeg-devel mailing list
[email protected]
https:/
dotally, the latter has already happened once.
+1, having already tripped on this on my patch to add ext_mapping_idc* fields I
can confirm that it's easy to trip on this, easy to miss unless you carefully
inspect the RPU afterwards, and then hard to spot where the problem is without
having to
tion name quite yet. I'm pondering if we should call it
"hybrid_fragmented" - any opinions, Dennis or Timo?
// Martin
That seems fine to me, but I might be biased considering that's what I
called it :P
~Dennis
___
ffmpeg-dev
r, although the default case is display order.
Why would you want a low latency decode mode with reordering?
I have no idea about hwaccel, but I believe with low latency encoded
video this does work.
Kieran
_______
ffmpeg-devel mailing list
ffmpeg-devel@f
On Fri, Jun 14, 2024 at 1:53 PM Paul B Mahol wrote:
>
>
>
> On Fri, Jun 14, 2024 at 2:41 PM Kieran Kunhya via ffmpeg-devel
> wrote:
>>
>> On Sun, Jun 9, 2024 at 2:39 AM Andreas Rheinhardt
>> wrote:
>> >
>> > The H.264 decoder does not
ously FFmpeg has a different target demographic and can use
something different than OBS, "Hybrid MP4" is just what I came up with
as user-facing name for the feature at the time.
~Dennis
_______
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".
re a patch for this? What
option should I choose?
Best regards,
Stefan
_______
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 2024-06-17 04:08 pm, Martin Storsjö wrote:
On Sat, 15 Jun 2024, Gyan Doshi wrote:
On 2024-06-15 03:54 am, Dennis Sädtler via ffmpeg-devel wrote:
On 2024-06-14 13:23, Gyan Doshi wrote:
On 2024-06-14 04:35 pm, Timo Rothenpieler wrote:
On 14/06/2024 12:44, Martin Storsjö wrote:
On Fri
r/projects/ffmpeg
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/libvpxenc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
lgtm.
___________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-d
ns(+)
Ok. Will push soon.
Thanks,
Thilo
_______
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".
, 78 insertions(+), 9 deletions(-)
create mode 100644 tests/ref/lavf/mov_hybrid_frag
If there are no more comments on this one, I'll go ahead and push it
soon.
+1 from me
Sounds good to me as well.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpe
> On Jun 19, 2024, at 3:21 AM, Niklas Haas wrote:
>
> On Thu, 23 May 2024 19:50:23 + Cosmin Stejerean via ffmpeg-devel
> wrote:
>> From: Cosmin Stejerean
>>
>> not all clients support metadata compression, output when
>> vdr_dm_metadata_changed fa
ewable but shall
be stashed when pushing.
-Thilo
Josef Zlomek (2):
libavcodec/webp: add support for animated WebP
libavformat/webp: add WebP demuxer
Thilo Borgmann via ffmpeg-devel (6):
avcodec/webp: remove unused definitions
avcodec/webp: separate VP8 decoding
avcodec/bsf: Add
From: Thilo Borgmann via ffmpeg-devel
---
libavcodec/webp.c | 50 +--
1 file changed, 44 insertions(+), 6 deletions(-)
diff --git a/libavcodec/webp.c b/libavcodec/webp.c
index af4ebcec27..c52b9732b4 100644
--- a/libavcodec/webp.c
+++ b/libavcodec
From: Thilo Borgmann via ffmpeg-devel
---
libavcodec/webp.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/libavcodec/webp.c b/libavcodec/webp.c
index 7c2a5f0111..af4ebcec27 100644
--- a/libavcodec/webp.c
+++ b/libavcodec/webp.c
@@ -60,8 +60,6 @@
#define VP8X_FLAG_ALPHA
->pkt);
+av_frame_free(&s->frame);
return AVERROR(ENOMEM);
+}
+
+// prepare data pointers for YUVA background
+for (int i = 0; i < 4; i++)
+s->background_data[i] = &s->background_yuva[i];
+// convert transparent black from RGBA to YUVA
+
From: Thilo Borgmann via ffmpeg-devel
---
libavcodec/webp.c | 146 +++---
1 file changed, 72 insertions(+), 74 deletions(-)
diff --git a/libavcodec/webp.c b/libavcodec/webp.c
index 146d5cb393..bacf605ff2 100644
--- a/libavcodec/webp.c
+++ b/libavcodec
From: Thilo Borgmann via ffmpeg-devel
Splits a packet containing a webp animations into
one non-compliant packet per frame of the animation.
Skips RIFF and WEBP chunks for those packets except
for the first. Copyies ICC, EXIF and XMP chunks first
into each of the packets except for the first
From: Thilo Borgmann via ffmpeg-devel
---
libavcodec/webp.c | 42 --
1 file changed, 36 insertions(+), 6 deletions(-)
diff --git a/libavcodec/webp.c b/libavcodec/webp.c
index bacf605ff2..c8be673060 100644
--- a/libavcodec/webp.c
+++ b/libavcodec/webp.c
From: Thilo Borgmann via ffmpeg-devel
---
tests/fate/image.mak | 9
tests/ref/fate/webp-anim | 22
tests/ref/fate/webp-chfmt1 | 23
tests/ref/fate/webp-chfmt2 | 106 +
4 files changed, 160 insertions(+)
create mode 100644
ts/ref/fate/webp-rgb-lossless-palette-predictor
index 92a4ad9810..65537f7ed1 100644
--- a/tests/ref/fate/webp-rgb-lossless-palette-predictor
+++ b/tests/ref/fate/webp-rgb-lossless-palette-predictor
@@ -1,4 +1,4 @@
-#tb 0: 1/25
+#tb 0: 1/10
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 100x30
diff --git a/tests/ref/fate/webp-rgb-lossy-q80
b/tests/ref/fate/webp-rgb-lossy-q80
index f61d75ac13..cd43415b95 100644
--- a/tests/ref/fate/webp-rgb-lossy-q80
+++ b/tests/ref/fate/webp-rgb-lossy-q80
@@ -1,4 +1,4 @@
-#tb 0: 1/25
+#tb 0: 1/10
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 12x8
diff --git a/tests/ref/fate/webp-rgba-lossless
b/tests/ref/fate/webp-rgba-lossless
index bb654ae442..2f763c6c46 100644
--- a/tests/ref/fate/webp-rgba-lossless
+++ b/tests/ref/fate/webp-rgba-lossless
@@ -1,4 +1,4 @@
-#tb 0: 1/25
+#tb 0: 1/10
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 12x8
diff --git a/tests/ref/fate/webp-rgba-lossy-q80
b/tests/ref/fate/webp-rgba-lossy-q80
index d2c2aa3fce..6b114f772e 100644
--- a/tests/ref/fate/webp-rgba-lossy-q80
+++ b/tests/ref/fate/webp-rgba-lossy-q80
@@ -1,4 +1,4 @@
-#tb 0: 1/25
+#tb 0: 1/10
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 12x8
--
2.39.3 (Apple Git-146)
___
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".
VSMap storable type set in a script. It is stored in the key with the same name in dst. Returns 0 on success. */
+int (VS_CC *getVariable)(VSScript *handle, const char *name, VSMap *dst) VS_NOEXCEPT;
+
+/* Sets all keys in the provided VSMap as variables in the script. Returns 0 on success. *
Am 22.06.24 um 08:27 schrieb Stephen Hutchinson:
On 6/21/24 9:37 PM, Stefan Oltmanns via ffmpeg-devel wrote:
The current VapourSynth implementation is rarely used, as it links the
VapourSynth library at build time, making the resulting build unable to
run when VapourSynth is not installed
Am 22.06.24 um 20:23 schrieb Stephen Hutchinson:
On 6/22/24 6:02 AM, Stefan Oltmanns via ffmpeg-devel wrote:
I don't know the extact reason, but VapourSynth is not just a library
like avisynth, but an application that uses Python, meaning a lot of
dependencies.
If we want to be tech
ing_idc is in the upper 8 bits of el_bit_depth_minus8 */
--
2.42.1
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with
support. I found a branch
here: https://github.com/airlied/FFmpeg/tree/vulkan-vp9-decode, but it seems
stale. Are there any plans to bring vulkan vp9 decode onto master?
Best
Daniel
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org
al code that already written. Should I change?
Not here. Keep the move patch as-is.
You can test if ldexp() is equal and if so, add another patch to the
patchset changing the function to utilize ldexp().
-Thilo
_______
ffmpeg-devel mailing list
ffmpeg-de
On Thu, Oct 5, 2023 at 3:40 PM Vignesh Venkat wrote:
>
>
>
> On Thu, Oct 5, 2023 at 10:36 AM Vittorio Giovara
> wrote:
>>
>>
>>
>> On Wed, Oct 4, 2023 at 12:40 PM Vignesh Venkatasubramanian via ffmpeg-devel
>> wrote:
>>>
>>&g
Hi Anton,
On Tue, 2023-10-10 at 12:54 +0200, Anton Khirnov wrote:
>
> Quoting Carotti, Elias via ffmpeg-devel (2023-10-02 19:35:09)
> > diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
> > index 77a9f173b4..4c643c9066 100644
> > --- a/libavcodec/libx264.c
> &
Hello,
I guess this is the right mailing list for mentioning that I uploaded a sample
video with the VideoLAN uploader which is meant for my new ticket #10617 on
ffmpeg. The file is called 01cr.smk.
Regards
___
ffmpeg-devel mailing list
ffmpeg-devel
On Fri, 2023-10-13 at 16:16 +0200, Anton Khirnov wrote:
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you can confirm the sender
> and know the content is safe.
>
>
>
> Quoting Carotti, Elias via ffmpeg-de
err;
+i++;
}
hp->h264pic = (StdVideoDecodeH264PictureInfo) {
--
2.42.0
___
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".
a full rewrite
IMO.
- Cosmin
_______
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".
pical case (while perhaps trying to minimize the instances that hit this
default path and warning loudly when it does).
That said this seems like the kind of change that should be in a 7.0 release
rather than a 6.1 release if a 6.1 is going to happen.
- Cosmin
_______
AV_PROFILE_H264_CONSTRAINED_BASELINE,
> AV_PROFILE_H264_MAIN,
> AV_PROFILE_H264_HIGH,
> AV_PROFILE_UNKNOWN};
_______
ffmpeg-devel mailing l
le appears broken for his
FFmpeg version 6.0... though a proper -preset was sufficient to help out.
-Thilo
_______
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ff
, but it can provide a useful
mechanism to disagree and commit about whether the work should be done at all
and provide the broad strokes (like improve swscale vs write a brand new
library vs integrate some third party one).
- Cosmin
_______
ffmpeg-deve
terested in collaborating with the format? I would be
more than happy to use a github repo for the format description.
Thanks,
-Chema
___________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe,
BR+TFL+TFR+TBL+TBR
hexadecagonal FL+FR+FC+BL+BR+BC+SL+SR+TFL+TFC+TFR+TBL+TBC+TBR+WL+WR
--
2.39.0
_______
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".
than the
mailing list archive. If it has to stay publicly searchable though, is there a
way to add rel="nofollow" to the links when they appear in the trac archive?
That should remove the appeal of this vector for stuffing links in to the trac
archive.
- Cosmin
____
Hi,
I went to Prag for the LinuxDays Prague 23 [1] by Bus and stayed at the
university Dorm/Hotel.
Bus:54,98 EUR
Hotel: 154,08 EUR (converted from CZK by VISA)
=
Total: 209,06 EUR
Thanks,
Thilo
[1] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-October/315777.html
ecode_frame),
.close = webp_decode_close,
-.p.capabilities = AV_CODEC_CAP_DR1 | AV_CODEC_CAP_FRAME_THREADS,
+.p.capabilities = AV_CODEC_CAP_DR1,
.caps_internal = FF_CODEC_CAP_ICC_PROFILES,
};
--
2.37.1 (Apple Git-137.1)
_______
ffmpeg-devel mailin
Am 22.10.23 um 16:30 schrieb Andreas Rheinhardt:
Thilo Borgmann via ffmpeg-devel:
Revealed by the patch to support animated webp, the current
frame threading implementation contains a data race.
No, it doesn't: The current implementation does not call
ff_thread_finish_setup() in vp8.
-Thilo
_______
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".
Am 25.10.23 um 16:23 schrieb Thilo Borgmann via ffmpeg-devel:
Am 25.10.23 um 16:22 schrieb Rémi Denis-Courmont:
Hi,
I am not on the GA, but there are probably people with my locale on the GA.
And it seems that the voting system hits a Perl syntax error if your browser
locale is set to French
cale is set to French.
> _______
> 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".
____
ixing the server side voting software to deal
with different locales.
- Cosmin
_______________
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".
Am 25.10.23 um 19:39 schrieb Rémi Denis-Courmont:
Hi,
Le 25 octobre 2023 18:52:31 GMT+03:00, Thilo Borgmann via ffmpeg-devel
a écrit :
Am 25.10.23 um 16:23 schrieb Thilo Borgmann via ffmpeg-devel:
Am 25.10.23 um 16:22 schrieb Rémi Denis-Courmont:
Hi,
I am not on the GA, but there are
Am 25.10.23 um 21:31 schrieb Thilo Borgmann via ffmpeg-devel:
Am 25.10.23 um 19:39 schrieb Rémi Denis-Courmont:
Hi,
Le 25 octobre 2023 18:52:31 GMT+03:00, Thilo Borgmann via ffmpeg-devel
a écrit :
Am 25.10.23 um 16:23 schrieb Thilo Borgmann via ffmpeg-devel:
Am 25.10.23 um 16:22 schrieb
Am 26.10.23 um 12:57 schrieb Andreas Rheinhardt:
Thilo Borgmann via ffmpeg-devel:
Hi,
Am 24.10.23 um 23:15 schrieb Anton Khirnov:
Hi all,
as discussed at the dev meeting at VDD, we need to have a series of
votes, the first of which concerns defining when is the GA voter list to
be updated
entity that handles the community
funds with absolute objectivity and no intrinsic interest whatsoever. In
contrast to any company, including (my own-ish) FFlabs.
-Thilo
[1]
https://drive.google.com/file/d/1B9VoiT6sjW4vWWsp6ipudLz73QtdBbGi/view?usp=sharing
____
Am 27.10.23 um 03:28 schrieb Kieran Kunhya:
Hi,
On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel <
[email protected]> wrote:
Of course. FFmpeg has a donations account. So the money is already there
and
already used for the reimbursement requests. Whatever we spent
not limited to code bounties.
-Thilo
___________
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".
Am 27.10.23 um 13:30 schrieb Rémi Denis-Courmont:
Hi,
Le 27 octobre 2023 14:10:15 GMT+03:00, Thilo Borgmann via ffmpeg-devel
a écrit :
Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer
a écrit :
This is financial sustainability Plan A (SPI)
ATM SPI has like 150k $, we do not
Am 27.10.23 um 13:24 schrieb Jan Ekström:
On Wed, Oct 25, 2023 at 4:14 PM Thilo Borgmann via ffmpeg-devel
wrote:
Hi,
Am 24.10.23 um 23:15 schrieb Anton Khirnov:
Hi all,
as discussed at the dev meeting at VDD, we need to have a series of
votes, the first of which concerns defining when is
Am 27.10.23 um 15:38 schrieb Kieran Kunhya:
On Fri, 27 Oct 2023 at 03:23, Thilo Borgmann via ffmpeg-devel <
[email protected]> wrote:
Am 27.10.23 um 03:28 schrieb Kieran Kunhya:
Hi,
On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel <
[email protected]>
/
___
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".
mts[0] = hwfc->sw_format;
> -fmts[1] = AV_PIX_FMT_NONE;
> +n = 0;
> +fmts[n++] = hwfc->sw_format;
> +#if CONFIG_CUDA
> + fmts[n++] = AV_PIX_FMT_CUDA;
> +#endif
> +fmts[n++] = AV_PIX_FMT_NONE;
>
> *formats = fmts;
> return 0;
LGTM. Thanks!
rmat(hwfc->device_ctx, dst->format,
> NULL); if (err < 0)
> - return AVERROR(ENOSYS);
> +return err;
> }
>
> err = vaapi_map_frame(hwfc, dst, src, flags);
LGTM.
--phil
___
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".
(vas != VA_STATUS_SUCCESS) {
> av_log(hwfc, AV_LOG_ERROR, "Failed to map image from surface
> " "%#x: %d (%s).\n", surface_id, vas, vaErrorStr(vas));
LGTM. Thanks.
--phil
_______
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".
avif samples.
-Thilo
___
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 Oct 27, 2023, at 5:39 AM, Thilo Borgmann via ffmpeg-devel
> wrote:
>
>> I'll try to post a patch today either inverting their order (which
>> hopefully outputs my community member e-mail), or - since this e-mail
>> is never supposed to apply to a
> On Oct 27, 2023, at 5:39 AM, Thilo Borgmann via ffmpeg-devel
> wrote:
>
>> I'll try to post a patch today either inverting their order (which
>> hopefully outputs my community member e-mail), or - since this e-mail
>> is never supposed to apply to a
FFLabs consultants the "what they work on" can be extracted from
the git log or mailing list patches. Not who is paying for the work or how much
is being paid, but certainly the what can be inferred with a reasonable degree
of accuracy.
- Cosmin
__________
1001 - 1100 of 3425 matches
Mail list logo
