> On May 18, 2022, at 4:39 AM, Derek Buitenhuis
> wrote:
>
> Some muxers, such as GPAC, create files with only one sidx, but two streams
> muxed into the same fragments pointed to by this sidx.
>
> Prevously, in such a case, when we seeked in such files, we fell back
> to, for example, using
Modified the function av_find_best_stream() such that, when a list of allowed
codecs is supplied in the format context, and when the caller is requesting a
decoder be returned, the function will select the best stream that has a
decoder in the allowed decoders list.
Signed-off-by: Eric Juteau
Some muxers, such as GPAC, create files with only one sidx, but two streams
muxed into the same fragments pointed to by this sidx.
Prevously, in such a case, when we seeked in such files, we fell back
to, for example, using the sidx associated with the video stream, to
seek the audio stream, leavi
On Tue, Apr 19, 2022 at 11:20 AM Bohan Li
wrote:
>
> When target levels are set, this patch checks whether they are
> satisfied by libaom. If not, a warning is shown. Otherwise the output
> levels are also logged.
>
> This patch applies basically the same approach used for libvpx.
>
> Signed-off-b
On Tue, May 17, 2022 at 11:24 AM Vignesh Venkatasubramanian
wrote:
>
> libaom added an usage=allintra mode for doing better with still
> images. Expose that in the ffmpeg's wrapper. This is especially
> useful for encoding still AVIF images.
>
> Signed-off-by: Vignesh Venkatasubramanian
> ---
>
On Mon, May 16, 2022 at 10:40 AM Vignesh Venkatasubramanian
wrote:
>
> Add support for AVIF muxing in the image2 muxer.
>
> Tested with this example:
> ffmpeg -lavfi testsrc=duration=1:size=320x320 -g 1 -flags global_header -c:v
> libaom-av1 -f image2 img-%2d.avif
>
> Signed-off-by: Vignesh Venka
libaom added an usage=allintra mode for doing better with still
images. Expose that in the ffmpeg's wrapper. This is especially
useful for encoding still AVIF images.
Signed-off-by: Vignesh Venkatasubramanian
---
libavcodec/libaomenc.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
This commit moves some of the functionality from avfilter/colorspace
into avutil/csp and exposes it as a public API so it can be used by
libavcodec and/or libavformat.
---
libavfilter/colorspace.c| 94 +-
libavfilter/colorspace.h| 31 ++
libavfilter/ff
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft
> Works
> Sent: Tuesday, May 17, 2022 5:28 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] avutil/wchar_filename,
> file_open: Support long file names on Windo
> -Original Message-
> From: ffmpeg-devel On Behalf Of nil-
> admir...@mailo.com
> Sent: Tuesday, May 17, 2022 5:07 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] avutil/wchar_filename,
> file_open: Support long file names on Windows
>
> > stat wasn't alr
> stat wasn't already defined as win32_stat.
> win32_stat was already defined but not mapped. That's what my change
> does.
There are two defines in os_support.h:
# ifdef stat
# undef stat
# endif
# define stat _stati64
and
DEF_FS_FUNCTION2(stat, _wstati64, _stati64, struct stat*)
which
On 5/17/22 10:09, Andreas Rheinhardt wrote:
Leo Izen:
+#include "csp.h"
+#include "frame.h"
?
+#include "mastering_display_metadata.h"
?
+#include "libavutil/frame.h"
Once again: ?
This includes were all in libavfilter/colorspace, I missed removing them
when I moved it over. I'll rem
Leo Izen:
> This commit moves some of the functionality from avfilter/colorspace
> into avutil/csp and exposes it as a public API so it can be used by
> libavcodec and/or libavformat.
> ---
> libavfilter/colorspace.c| 94 +-
> libavfilter/colorspace.h| 31 ++--
This commit moves some of the functionality from avfilter/colorspace
into avutil/csp and exposes it as a public API so it can be used by
libavcodec and/or libavformat.
---
libavfilter/colorspace.c| 94 +-
libavfilter/colorspace.h| 31 ++
libavfilter/ff
On Mon, May 16, 2022 at 01:05:28PM +0200, Andreas Rheinhardt wrote:
> Michael Niedermayer:
> > Maybe helps coverity
> > Helps: CID1433771
> >
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavcodec/mpeg4videodec.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --
From: softworkz
Unify file access operations by replacing usages of direct calls
to posix fopen() to prepare for long filename support on Windows.
Signed-off-by: softworkz
---
libavcodec/dvdsubdec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/dvdsubdec.c b/li
From: softworkz
Unify file access operations by replacing usages of direct calls
to posix fopen() to prepare for long filename support on Windows.
Signed-off-by: softworkz
---
libavfilter/af_firequalizer.c | 2 +-
libavfilter/vf_deshake.c | 2 +-
libavfilter/vf_psnr.c
Unify file access operations by replacing usages of direct calls to posix
fopen()
v2: Remove changes to fftools for now
v3: Add some additional replacements
v4: Fix and improve commit messages
softworkz (2):
avfilter: use av_fopen_utf8() instead of plain fopen()
avcodec/dvdsubdec: use av_fope
> -Original Message-
> From: Tobias Rapp
> Sent: Tuesday, May 17, 2022 1:56 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>; ffmpegagent
> Cc: Martin Storsjö ; softworkz
>
> Subject: Re: [FFmpeg-devel] [PATCH v3 0/2] use av_fopen_utf8() instead
> of plain fopen()
On Sun, May 15, 2022 at 3:21 PM Jan Ekström wrote:
>
> On Sun, May 15, 2022 at 2:58 PM Gyan Doshi wrote:
> >
> >
> >
> > On 2022-05-15 04:29 pm, Jan Ekström wrote:
> > > On Thu, May 12, 2022 at 11:19 AM Anton Khirnov wrote:
> > >> Quoting Gyan Doshi (2022-05-12 09:01:31)
> > >>> A substitute opt
Hi Philip,
I am currently relying on using ffmpeg with nvcuvid to cross verify my vdpau
patch
I see the clips with me are matching in output for both VDPAU and NVCUVID/NVDEC.
Attached are the script I used to verify and its output.
Was unable to use AV1 VDPAU with MPV hence not able to repro t
On 17/05/2022 02:39, ffmpegagent wrote:
Unify file access operations by replacing usages of direct calls to posix
fopen()
As the cover letter will be gone after commit I think it would be a good
idea to add the reason for the change also in the commit messages directly.
Is this in preparatio
The HEVC decoder can call these functions with smaller widths than the
functions themselves are designed to operate on so we should only check
the relevant output
Signed-off-by: J. Dekker
---
tests/checkasm/hevc_sao.c | 51 ---
1 file changed, 31 insertions(+)
On 28 Apr 2022, at 21:50, Martin Storsjö wrote:
> [...]
> Compared with the previously applied (and reverted) patch, here, you
> previously had "mov x17, #4". I guess that'd mean the function only ever
> produced 8 output rows, while it now uses the real height parameter? Was this
> change a no
The previous instructions do not work, there is no FTP server
running at upload.ffmpeg.org
(which is an alias for streams.videolan.org)
Signed-off-by: Marvin Scholz
---
src/bugreports | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/src/bugreports b/src/bugrep
25 matches
Mail list logo
