Re: [FFmpeg-devel] [PATCH] avutil: [LA] use getauxval to do runtime check.

Shiyou Yin 于2023年2月14日周二 20:26写道： > > Replace cpucfg with getauxval to avoid crash in case of > some processor capabilities are not supportted by kernel used. > --- > libavutil/loongarch/cpu.c | 24 > 1 file changed, 8 insertions(+), 16 deletions(-) > > diff --git

Re: [FFmpeg-devel] Chromium 110 and ffmpeg 5.1.2

On Wed, Feb 22, 2023 at 7:28 PM Hendrik Leppkes wrote: > > On Wed, Feb 22, 2023 at 9:42 PM Drew Abbott wrote: > > > > Hello, > > > > I am trying to build Chromium 110 with ffmpeg version 5.1.2. One of > > the errors I get while building has to do with the API for accessing > > first_dts. It

Re: [FFmpeg-devel] [PATCH v3 1/3] hwcontext_d3d11va: add mutiple supported DXGI formats

> On 2/13/2023 11:45 PM, Tong Wu wrote: > > Add support for VUYX, YUYV422, Y210, XV30, P012, Y212, XV36. > > > > The added formats work with qsv acceleration and will not have impact > > on d3d11va acceleration(-hwaccel d3d11va) since so far these formats > > are still not supported by using

[FFmpeg-devel] [PATCH] dash metadata: Added other supported fields besides title only

Now metadata fields for source, copyright, lang and moreInformationURL are supported too. Evidence for the need of such support: https://docs.rs/dash-mpd/0.6.3/dash_mpd/struct.ProgramInformation.html and

Re: [FFmpeg-devel] Chromium 110 and ffmpeg 5.1.2

On Wed, Feb 22, 2023 at 9:42 PM Drew Abbott wrote: > > Hello, > > I am trying to build Chromium 110 with ffmpeg version 5.1.2. One of > the errors I get while building has to do with the API for accessing > first_dts. It looks like previously it was just a member of AVStream, > but now it can

Re: [FFmpeg-devel] Chromium 110 and ffmpeg 5.1.2

On 22.02.2023 21:41, Drew Abbott wrote: Hello, I am trying to build Chromium 110 with ffmpeg version 5.1.2. One of the errors I get while building has to do with the API for accessing first_dts. It looks like previously it was just a member of AVStream, but now it can only be accessed with

[FFmpeg-devel] Chromium 110 and ffmpeg 5.1.2

Hello, I am trying to build Chromium 110 with ffmpeg version 5.1.2. One of the errors I get while building has to do with the API for accessing first_dts. It looks like previously it was just a member of AVStream, but now it can only be accessed with av_stream_get_first_dts:

Re: [FFmpeg-devel] [PATCH] libavcodec/libfdk-aacenc: Scale VBR mode with FF_QP2LAMBDA

I had noticed fdk is specifically looking for the qscale flag, and otherwise does not do anything with global_quality. I suppose the change is risky for anyone who is setting both global quality and qscale, but with the current code, it seems incorrect to have a conditional based on the scaled

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

> On Wed, Feb 22, 2023 at 6:00 PM Zhao Zhili wrote: > > You missed the point. Use any (streaming) container which supports the codec, e.g., webm. I've already discussed solutions with ivf and h264 byte stream which are the same as webm but even easier in implementation. They are not applicable.

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

> 在 2023年2月23日，01:22，sonntex 写道： > > Are you sure that vp8 and vp9 can be put to mpeg-ts? You missed the point. Use any (streaming) container which supports the codec, e.g., webm. Please don’t top post. > > On Wed, Feb 22, 2023 at 3:25 PM Zhao Zhili wrote: > >>> -Original

Re: [FFmpeg-devel] FFmpeg 6.0

On Tue, Feb 21, 2023 at 04:48:41AM -0800, RADSL wrote: > > On 2/21/2023 4:31 AM, Kieran Kunhya wrote: > > On Tue, 21 Feb 2023, 11:38 Michael Niedermayer, > > wrote: > > > > > On Fri, Feb 10, 2023 at 06:47:03PM +0100, Michael Niedermayer wrote: > > > > Hi all > > > > > > > > i plan to branch

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

Are you sure that vp8 and vp9 can be put to mpeg-ts? On Wed, Feb 22, 2023 at 3:25 PM Zhao Zhili wrote: > > -Original Message- > > From: ffmpeg-devel On Behalf Of > sonntex > > Sent: 2023年2月22日 21:59 > > To: FFmpeg development discussions and patches > > Subject: Re: [FFmpeg-devel] How

Re: [FFmpeg-devel] [PATCH] libavcodec/libfdk-aacenc: Scale VBR mode with FF_QP2LAMBDA

On 22.02.2023 17:46, Gyan Doshi wrote: On 2023-02-22 10:12 pm, Timo Rothenpieler wrote: On 22.02.2023 17:33, Gyan Doshi wrote: From fftools\ffmpeg_mux_init.c 619:    ost->enc_ctx->global_quality = FF_QP2LAMBDA * qscale Regards, Gyan But that's only if you set the old qscale CLI

Re: [FFmpeg-devel] [PATCH] libavcodec/libfdk-aacenc: Scale VBR mode with FF_QP2LAMBDA

On 2023-02-22 10:12 pm, Timo Rothenpieler wrote: On 22.02.2023 17:33, Gyan Doshi wrote: From fftools\ffmpeg_mux_init.c 619:    ost->enc_ctx->global_quality = FF_QP2LAMBDA * qscale Regards, Gyan But that's only if you set the old qscale CLI options. If you set the global_quality option

Re: [FFmpeg-devel] [PATCH] libavcodec/libfdk-aacenc: Scale VBR mode with FF_QP2LAMBDA

On 22.02.2023 17:33, Gyan Doshi wrote: From fftools\ffmpeg_mux_init.c 619:    ost->enc_ctx->global_quality = FF_QP2LAMBDA * qscale Regards, Gyan But that's only if you set the old qscale CLI options. If you set the global_quality option directly, there is no factor applied. By dividing

Re: [FFmpeg-devel] [PATCH] libavcodec/libfdk-aacenc: Scale VBR mode with FF_QP2LAMBDA

On 2023-02-22 09:39 pm, Timo Rothenpieler wrote: On 22.02.2023 03:12, JonHGee wrote: libavcodec/libfdk-aacenc: VBR mode currently does not account for scaling when using -aq options with libfdk, resulting in clamping to vbr mode 5 whenever a value >0 is provided.  Adjusting for the scaling

Re: [FFmpeg-devel] [PATCH v4] avcodec/pngdec: read colorspace info when decoding with AVDISCARD_ALL

On Wed, Feb 22, 2023 at 8:49 AM Leo Izen wrote: > On 2/21/23 20:42, Ronald S. Bultje wrote: > > Hi, > > > > On Tue, Feb 21, 2023 at 5:36 PM Leo Izen > > wrote: > > > > These chunks are lightweight and it's useful information to have when > > running ffmpeg -i

Re: [FFmpeg-devel] [PATCH] libavcodec/libfdk-aacenc: Scale VBR mode with FF_QP2LAMBDA

On 22.02.2023 03:12, JonHGee wrote: libavcodec/libfdk-aacenc: VBR mode currently does not account for scaling when using -aq options with libfdk, resulting in clamping to vbr mode 5 whenever a value >0 is provided. Adjusting for the scaling factor for proper VBR support. ---

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

> -Original Message- > From: ffmpeg-devel On Behalf Of sonntex > Sent: 2023年2月22日 21:59 > To: FFmpeg development discussions and patches > Subject: Re: [FFmpeg-devel] How to implement pcap ffmpeg format? > > So, if I have an rtp stream inside my application and want to save it > somehow

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

So, if I have an rtp stream inside my application and want to save it somehow to a playable media container, I have to wrap this stream to something that could be transferred by pipe to ffmpeg, for instance to ivf or to h264 byte stream. The first format requires deep codec parsing to extract at

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

On Wed, Feb 22, 2023 at 7:54 AM Rémi Denis-Courmont wrote: > I agree with Kieran that this doesn't look like it belongs in FFmpeg or in > any media framework. In fact, Wireshark has some support for extracting media > from RTP, and that seems like the right place for it. > > With that said, you

Re: [FFmpeg-devel] [PATCH v4] avcodec/pngdec: read colorspace info when decoding with AVDISCARD_ALL

On 2/21/23 20:42, Ronald S. Bultje wrote: Hi, On Tue, Feb 21, 2023 at 5:36 PM Leo Izen > wrote: These chunks are lightweight and it's useful information to have when running ffmpeg -i or ffprobe, for example. I disagree conceptually with this. If we want

Re: [FFmpeg-devel] [PATCH 2/3] lavc/assenc: set AV_CODEC_CAP_SINGLE_SUB_RECT

Ridley Combs (12023-02-21): > Fair enough, if we're fine with breaking the existing case further. > Should I simply drop rectangles after a first, or return an error? You have to ask? Between reporting an error and silently corrupting data, the answer is never in doubt. > This is only true for

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

Hi, I agree with Kieran that this doesn't look like it belongs in FFmpeg or in any media framework. In fact, Wireshark has some support for extracting media from RTP, and that seems like the right place for it. With that said, you can't realistically pass RTP packets on the standard input.

Re: [FFmpeg-devel] [PATCH v3 1/3] hwcontext_d3d11va: add mutiple supported DXGI formats

On 2/13/2023 11:45 PM, Tong Wu wrote: Add support for VUYX, YUYV422, Y210, XV30, P012, Y212, XV36. The added formats work with qsv acceleration and will not have impact on d3d11va acceleration(-hwaccel d3d11va) since so far these formats are still not supported by using d3d11va acceleration.

Re: [FFmpeg-devel] [PATCH] src/template_head2: Make "community" a seperate page containing Organisation and Code of Conduct.

Am 08.02.23 um 16:48 schrieb Thilo Borgmann: Forgot to put this in the subject, this patch is for ffmpeg-web, of course. -Thilo Am 08.02.23 um 16:47 schrieb Thilo Borgmann: ---   src/template_head2 | 3 ++-   1 file changed, 2 insertions(+), 1 deletion(-) Pushing soon. -Thilo

Re: [FFmpeg-devel] [PATCH 1/2] doc/dev_community: add the addresses of the committees

Am 08.02.23 um 16:57 schrieb Thilo Borgmann: From: Nicolas George Omitting the .org from the address should be protection enough against spam spiders. Signed-off-by: Nicolas George --- doc/dev_community/community.md | 4 1 file changed, 4 insertions(+) diff --git

Re: [FFmpeg-devel] [PATCH 4/6] avformat/wavdec: s337m support

tis 2023-02-21 klockan 12:30 + skrev Nicolas Gaullier: > > This is why it is better to demand that these things be explicitly > > signalled. At the same time a lot of users expect ffmpeg to Just > > Work, but that is not always possible. Perhaps we should should put > > this in the manual and

Re: [FFmpeg-devel] [PATCH 2/6] avformat/s337m: Consider container bit resolution

tis 2023-02-21 klockan 10:43 + skrev Nicolas Gaullier: > > I haven't worked enough with S377m to really know, but I do know > > it's a mess. Is there a way to differentiate "regular" packed 20- > > bit audio from S377m in wav? > > > > /Tomas > > There is a relevant overview of S337m in this

[FFmpeg-devel] [PATCH] Fix broken build on Android due to broken asm-generic/termbits.h include

Best, Fred Brennan (copypaste.wtf) From e9a889bfbf38bda7855792edd8248f4f4a56af7e Mon Sep 17 00:00:00 2001 From: Fredrick Brennan Date: Tue, 21 Feb 2023 12:58:38 -0500 Subject: [PATCH 1/2] Fix build on Android due to termbits.h collision! Applied to libavcodec/aaccoder.c:

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

It might be interesting. I didn’t find how to pass rtp to ffmpeg stdin. That is why I started thinking about pcap. Could you please show an example? On Wed, 22 Feb 2023 at 08:04, Gijs Peskens wrote: > Wouldn't the simplest solution just be a tiny tool that unwraps the pcap > stuff and just

[FFmpeg-devel] P1204.3 video quality metrics ?

Hi, I would like to know if there is any project about an integration of a 3rd party (opens source) lib to compute P1204.3 score from input video ? -- Regards, Alexandre ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] How to implement pcap ffmpeg format?

Wouldn't the simplest solution just be a tiny tool that unwraps the pcap stuff and just passes the packet data out on stdout? That's assuming ffmpeg allows receiving RTP packets on stdin. On 21-02-2023 23:55, sonntex wrote: New pcap ffmpeg format can have all options rtpdec requires. Anyway,