> On Jul 16, 2024, at 6:04 PM, Zhao Zhili wrote:
>
>
>
>> On Jul 16, 2024, at 23:48, Cosmin Stejerean via ffmpeg-devel
>> wrote:
>>
>>
>>
>>> On Jul 16, 2024, at 4:58 PM, Zhao Zhili wrote:
>>>
>>>
>>>
&
> On Jul 16, 2024, at 8:24 PM, Rémi Denis-Courmont wrote:
>
> Le tiistaina 16. heinäkuuta 2024, 18.48.06 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>> To add another data point, the platform decoders might also be more secure
>> due to sandboxing. I bel
> On Jul 17, 2024, at 5:39 PM, Paul B Mahol wrote:
>
> On Tue, Jul 16, 2024 at 5:56 PM Cosmin Stejerean via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
>>
>>
>>> On Jul 16, 2024, at 4:58 PM, Zhao Zhili wrote:
>>>
>>>
&g
> On Jul 31, 2024, at 5:14 AM, Niklas Haas wrote:
>
> On Sun, 28 Jul 2024 12:25:06 +0200 Niklas Haas wrote:
>> From: Niklas Haas
>>
>> ---
>> libavutil/dovi_meta.h | 28 +++-
>> 1 file changed, 15 insertions(+), 13 deletions(-)
>>
>> diff --git a/libavutil/dovi_meta.h
> On Aug 30, 2024, at 3:15 AM, Niklas Haas wrote:
>
> N/A:
> - ayuv, yuv4, y41p, v308, v210, v410, v408 (headerless)
> - pgmyuv (headerless)
> - prores, prores_aw, prores_ks (?)
> - rawvideo, bitpacked (headerless)
> - vnull, wrapped_avframe (pseudocodecs)
AFAIK while ProRes doesn't have taggi
> On Jan 28, 2024, at 7:54 AM, Kieran Kunhya wrote:
>
> So work like Anton's threading, YUVJ removal etc, that couldn't be funded
> via bounties as they have no direct commercial value but require expertise
> in the codebase.
> Statements of Work and milestones (by definition) are for features.
> On Jan 31, 2024, at 11:07 AM, Michael Niedermayer
> wrote:
>
> On Wed, Jan 31, 2024 at 06:22:41PM +, Kieran Kunhya wrote:
>> On Wed, 31 Jan 2024 at 18:03, Michael Niedermayer
>> wrote:
>>
>>> Hi Jonatas, Remi
>>>
>>> _THIS_ reply shows why i LOVE SPI
>>>
>>> I mean this is transparen
> On Feb 1, 2024, at 9:45 AM, Vittorio Giovara
> wrote:
>
> Since all objections and requests for more time have been ignored, and this
> is happening anyway, can we add a small amendment for the sake of
> transparency and for avoiding any conflict of interest? Whoever was
> involved with the
From: Cosmin Stejerean
This rebases the previous patch series from Damiano Galassi after the
packet side data changes and adds FATE tests for both reading and
writing amve
Cosmin Stejerean (1):
tests/fate/mov: add a test for reading and writing amve box
Damiano Galassi (2):
avcodec: add amb
From: Damiano Galassi
---
fftools/ffprobe.c | 3 +++
libavcodec/avpacket.c | 1 +
libavcodec/decode.c | 1 +
libavcodec/packet.h | 7 +++
4 files changed, 12 insertions(+)
diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
index f33e2471cb..aa1153e709 100644
--- a/fftools/ffprobe.c
From: Damiano Galassi
Co-Authored-By: Cosmin Stejerean
---
libavformat/dump.c | 15 +++
libavformat/isom.h | 3 +++
libavformat/mov.c| 35 +++
libavformat/movenc.c | 30 ++
4 files changed, 83 insertions(+)
diff -
From: Cosmin Stejerean
---
tests/fate/mov.mak| 5 +
tests/ref/fate/mov-read-amve | 8
tests/ref/fate/mov-write-amve | 33 +
3 files changed, 46 insertions(+)
create mode 100644 tests/ref/fate/mov-read-amve
create mode 100644 tests/ref
> On Feb 4, 2024, at 12:45, Anton Khirnov wrote:
>
> Quoting Cosmin Stejerean via ffmpeg-devel (2024-02-04 12:16:53)
>> diff --git a/libavcodec/packet.h b/libavcodec/packet.h
>> index 2c57d262c6..215b1c9970 100644
>> --- a/libavcodec/packet.h
>> +++ b/libavco
> On Feb 4, 2024, at 13:44, James Almer wrote:
>
> On 2/4/2024 8:16 AM, Cosmin Stejerean via ffmpeg-devel wrote:
>> From: Cosmin Stejerean
>>
>> ---
>> tests/fate/mov.mak| 5 +
>> tests/ref/fate/mov-read-amve | 8
From: Cosmin Stejerean
Version 4 resolves feedback from v3 by moving new side data field in
packet.h to the end for ABI compatibility, bumping the minor API
version for lavc, adding APIChanges entry, using -c:v in the FATE
test, cleaning up formatting in avformat/movenc and renaming
rescale_mdcv
From: Damiano Galassi
---
doc/APIchanges| 3 +++
fftools/ffprobe.c | 3 +++
libavcodec/avpacket.c | 1 +
libavcodec/decode.c | 1 +
libavcodec/packet.h | 9 -
libavcodec/version.h | 2 +-
6 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/doc/APIchanges b/do
From: Damiano Galassi
Co-Authored-By: Cosmin Stejerean
---
libavformat/dump.c | 15 +
libavformat/isom.h | 3 +++
libavformat/mov.c| 35 +++
libavformat/movenc.c | 50 ++--
4 files changed, 92 insertions(+)
From: Cosmin Stejerean
---
tests/fate/mov.mak| 5 +
tests/ref/fate/mov-read-amve | 8
tests/ref/fate/mov-write-amve | 33 +
3 files changed, 46 insertions(+)
create mode 100644 tests/ref/fate/mov-read-amve
create mode 100644 tests/ref
From: Cosmin Stejerean
---
.mailmap | 1 +
1 file changed, 1 insertion(+)
diff --git a/.mailmap b/.mailmap
index 7546cf0caf..cbe6b3ff99 100644
--- a/.mailmap
+++ b/.mailmap
@@ -22,3 +22,4 @@ rcombs
+Cosmin Stejerean Cosmin Stejerean via ffmpeg-devel
--
2.42.1
> On Feb 6, 2024, at 10:17 AM, Michael Niedermayer
> wrote:
>
> if "merge to git master" is a requirement then iam not participating
> in this. The risk simply outweights the gain. I wont work for months to
> then be at the mercy of not a single of 2000 subscribers posting some
> "i object" an
> On Feb 7, 2024, at 1:55 AM, Anton Khirnov wrote:
>
> As a compromise, we could start requiring C11 now, and C17 in 7.1.
> Or does anyone still care about compilers without even c11 support?
How about C11 now and C17 in a year with ffmpeg 8?
- Cosmin
_
> On Jan 23, 2024, at 11:22 AM, Michael Niedermayer
> wrote:
>
> What is blocking? (IMHO)
> * regressions (unless its non possible to fix before release)
> * crashes
> * security issues
> * data loss
> * privacy issues
> * anything the commuity agrees should be in the release
Can we get the a
> On Feb 7, 2024, at 11:27 AM, Lynne wrote:
>
>>>
>>> As a compromise, we could start requiring C11 now, and C17 in 7.1.
>>> Or does anyone still care about compilers without even c11 support?
>>>
>>
>> How about C11 now and C17 in a year with ffmpeg 8?
>>
>
> Do you have setups and reason
> On Feb 7, 2024, at 1:48 PM, Lynne wrote:
>
> Feb 7, 2024, 22:11 by ffmpeg-devel@ffmpeg.org:
>
>>
>>
>>> On Feb 7, 2024, at 11:27 AM, Lynne wrote:
>>>
>
> As a compromise, we could start requiring C11 now, and C17 in 7.1.
> Or does anyone still care about compilers without ev
> On Feb 1, 2024, at 11:26 PM, wenbin.chen-at-intel@ffmpeg.org wrote:
>
> From: Wenbin Chen
>
> PyTorch is an open source machine learning framework that accelerates
> the path from research prototyping to production deployment. Official
> websit: https://pytorch.org/. We call the C++ libr
101 - 125 of 125 matches
Mail list logo
