This patch series adds support of timecode in Matroska files, specs are at:
https://github.com/ietf-wg-cellar/matroska-specification/blob/master/cellar-codec/block_additional_mappings/smpte-st12-1-timecode.md
As ST 12-1 support was already partially implemented, using 32 bits
rather than 64 bits
PR #20551 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20551
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20551.patch
The existing is_luma check is fragile as depending on the order
of channels it can be set or reset
No testcase
Signed-off-by: Michael Niedermaye
PR #20550 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20550
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20550.patch
>From 38d62a1a51a84e220b6dbeaefd961f170d2d5c72 Mon Sep 17 00:00:00 2001
From: Michael Niedermayer
Date: Thu, 18 Sep 2025 17:32:46 +0200
Subject:
Hi Martin
On Tue, Sep 16, 2025 at 10:54:19PM +0300, Martin Storsjö via ffmpeg-devel wrote:
> On Tue, 16 Sep 2025, Michael Niedermayer via ffmpeg-devel wrote:
>
> > On Tue, Sep 16, 2025 at 02:12:20PM +0300, Martin Storsjö via ffmpeg-devel
> > wrote:
> > > On Tue, 16 Sep 2025, Michael Niedermayer
Hi,
I currently work on VVC implementation on Amlogic platform. There we use ffmpeg
to demux the stream.
All other codecs like h264 or h265 do have codec parameters extra data:
https://github.com/xbmc/xbmc/blob/master/xbmc/cores/VideoPlayer/DVDDemuxers/DVDDemuxFFmpeg.cpp#L2377
Is there just no e
mån 2025-09-15 klockan 10:26 -0300 skrev Helmuth Schmitz via ffmpeg-
devel:
> The first UL of the SMPTE 436M descriptor triple in mxfenc.c used
> 0x0a
> instead of 0x09. This caused generated MXF files without "MXF-GC
> Generic
> ANC
> Data Mapping" essence container descriptor.
>
> This patch cor
fre 2025-09-12 klockan 15:09 + skrev Niklas Haas via ffmpeg-devel:
> PR #20504 opened by Niklas Haas (haasn)
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20504
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20504.patch
>
> Marking this as WIP because I think it may be a little
On Thu, 18 Sep 2025, Timo Rothenpieler via ffmpeg-devel wrote:
On 9/17/2025 8:32 PM, Marton Balint via ffmpeg-devel wrote:
On Wed, 17 Sep 2025, Timo Rothenpieler via ffmpeg-devel wrote:
On 9/16/2025 11:12 PM, Balint Marton via ffmpeg-devel wrote:
- I am not sure what would be the c
PR #20549 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20549
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20549.patch
Right now, the private contexts of every decoder supporting
H.274 film grain synthesis (namely H.264, HEVC and VVC)
contain a H274FilmGrainDatabase; s
On 9/18/2025 7:29 AM, 张洪源 via ffmpeg-devel wrote:
Dear FFmpeg Developers and Maintainers,
I hope this email finds you well.
My name is [Your Name], and I am writing to kindly inquire about a patch I
recently submitted as my first contribution to the FFmpeg project. The patch is
titled:
"[P
On Mon, Sep 15, 2025 at 02:57:53PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi
>
> On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via ffmpeg-devel
> wrote:
> > On 15/09/2025 13:09, Michael Niedermayer via ffmpeg-devel wrote:
> [...]
> > > Ideas, Comments ?
> >
> > I do
On September 18, 2025 2:15:22 AM PDT, Nicolas George via ffmpeg-devel
wrote:
> If this web monster does not let you push code in your private fork
> without asking to include it upstream, it is one more reason not to use
> that thing.
It does let you push to your private fork without updating
PR #20548 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20548
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20548.patch
This reverts commits fd55c4b5f72a157fbb128d0ef203e9922b53552b
(for tls_openssl.c) and c74181a04b5f4e650eae662231e56518daef64d4
(for tls_gnutls.c).
It
On 9/18/2025 11:25 AM, Zhao Zhili wrote:
Current situation:
1. A patch depends on new sample in fate-suit will fail CI
Just temporarily manually download it in the workflow, and before the PR
gets merged, have the sample be uploaded to the fate-suite and remove
the manual download.
That's h
On Thu, 18 Sep 2025 01:52:31 -0700 Jacob Lifshay via ffmpeg-devel
wrote:
> On Thu, Sep 18, 2025 at 12:03 AM Nicolas George via ffmpeg-devel
> wrote:
> >
> > Timo Rothenpieler via ffmpeg-devel (HE12025-09-18):
> > > The problem is they can be very frequent. And not only force pushes.
> > > So the
PR #20547 opened by add-uos-ffmpeg
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20547
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20547.patch
Add a separator line to show_filters() function output to maintain
consistent formatting with other show functions like show_codecs,
show_for
Jacob Lifshay via ffmpeg-devel (HE12025-09-18):
> I don't know about you, but whenever I'm developing code, I sometimes
> push new changes multiple times in a day and then only ask for more
> review after I'm done developing whatever thing I'm working on, maybe
> after several days -- pushing code
Current situation:
1. A patch depends on new sample in fate-suit will fail CI
2. New sample needs to upload to fate-suit server manually
Question: Is it possible to hook sample uploading request to forgejo?
A simple idea is:
1. Setup a git repo with git-lfs support for fate-suit.
2. Add new sampl
On 2025-09-16 02:19 pm, Michael Niedermayer via ffmpeg-devel wrote:
Hi all
2 months ago we voted on testing Forgejo vs Gitlab, we picked and tested
Forgejo. And as said in that vote, (and surprisingly, i have not forgotten it)
heres the "after testing" discussion and vote
do we want to keep
> On Sep 17, 2025, at 22:44, Niklas Haas via ffmpeg-devel
> wrote:
>
> On Tue, 16 Sep 2025 10:49:00 +0200 Michael Niedermayer
> wrote:
>> Hi all
>>
>> 2 months ago we voted on testing Forgejo vs Gitlab, we picked and tested
>> Forgejo. And as said in that vote, (and surprisingly, i have no
On Thu, Sep 18, 2025 at 12:03 AM Nicolas George via ffmpeg-devel
wrote:
>
> Timo Rothenpieler via ffmpeg-devel (HE12025-09-18):
> > The problem is they can be very frequent. And not only force pushes.
> > So the current implementation is a compromise between visibility and
> > spam-level.
>
> They
21 matches
Mail list logo
