From: Dennis Sädtler
Added in macOS 15 "Sequoia".
Signed-off-by: Dennis Sädtler
---
Fixed line-endings, otherwise identical to v1.
libavcodec/videotoolboxenc.c | 12
1 file changed, 12 insertions(+)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index d
On Mon, 16 Dec 2024 at 03:17, Michael Niedermayer
wrote:
> This patch is corrupted by line breaks
>
> please make sure your editor and MUA dont break lines of patches
> or use git send-email
Seems Thunderbird broke it, will resubmit in a bit.
___
ffmpeg
From: Dennis Sädtler
Added in macOS 15 "Sequoia".
Signed-off-by: Dennis Sädtler
---
libavcodec/videotoolboxenc.c | 12
1 file changed, 12 insertions(+)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index da7b291b03..fb2de7b960 100644
--- a/libavcodec/v
On Thu, 12 Dec 2024 at 17:31, Timo Rothenpieler wrote:
>
> On 12/12/2024 17:30, Dennis Sädtler wrote:
> > With the spec now being in "beta" and no more (functional) changes
> > being expected, would you be happy to revisit this patch set and merge
> > it or do you want to wait for it to be declare
the
> same packet, have not been tested at all, since no software can write such
> files.
>
> The set can also be found on GitHub, where ignoring whitespaces makes
> specially the last patch a lot more readable:
> https://github.com/BtbN/FFmpeg/tree/enhanced-flv
>
>
&
On 2024-06-20 15:47, Timo Rothenpieler wrote:
On 20/06/2024 15:46, Martin Storsjö wrote:
On Wed, 19 Jun 2024, Martin Storsjö wrote:
This allows ending up with a normal, non-fragmented file when
the file is finished, while keeping the file readable if writing
is aborted abruptly at any point. (
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, 14 Jun 2024, Gyan Doshi wrote:
On 2024-06-14 02:18 am, Martin Storsjö wrote:
On Thu, 13 Jun 2024, Gyan Doshi wrote:
On 2024-06-13 06:20 pm, Martin St
On 2024-06-13 14:50, Martin Storsjö wrote:
On Wed, 5 Jun 2024, Martin Storsjö wrote:
This allows ending up with a normal, non-fragmented file when
the file is finished, while keeping the file readable if writing
is aborted abruptly at any point. (Normally when writing a
mov/mp4 file, the unfini
On 2024-06-03 09:51, Martin Storsjö wrote:
Finally, I've also had a somewhat cursed thought about having a
second always-hidden ftyp before the initial moov, which would then
allow you to use the same file for progressive download and DASH/HLS
streaming by using range-requests (e.g. via BYTERAN
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
On 2024-05-31 10:53, Martin Storsjö wrote:
This allows ending up with a normal, non-fragmented file when
the file is finished, while keeping the file readable if writing
is aborted abruptly at any point. (Normally when writing a
mov/mp4 file, the unfinished file is completely useless unless it
is
> From: Dennis Sädtler via ffmpeg-devel
I wonder what happened here, did I make a mistake when submitting the
original patch to the ML so the actual commit author name/email got
lost?
Should be the same as the signed-off section based on the repo I
submitted it from:
https://github.com/der
Based on enhanced-rtmp v2 spec published by Veovera:
https://veovera.github.io/enhanced-rtmp/docs/enhanced/enhanced-rtmp-v2
Signed-off-by: Dennis Sädtler
---
libavformat/flvdec.c | 117 +++
1 file changed, 96 insertions(+), 21 deletions(-)
diff --git a/li
Based on enhanced-rtmp v2 spec published by Veovera:
https://veovera.github.io/enhanced-rtmp/docs/enhanced/enhanced-rtmp-v2
This implementation maintains some backwards compatibility by only
writing the track information for track indices > 0. This means that
older FFmpeg versions - and possibly o
14 matches
Mail list logo
