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

2023-02-21 Thread Xiang, Haihao
On So, 2023-02-19 at 01:57 +, Xiang, Haihao wrote: > On Do, 2023-02-16 at 01:30 +, Xiang, Haihao wrote: > > On Di, 2023-02-14 at 10:45 +0800, Tong Wu wrote: > > > Add support for VUYX, YUYV422, Y210, XV30, P012, Y212, XV36. > > > > > > The added formats work with qsv acceleration and will

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

2023-02-21 Thread JonHGee
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. --- libavcodec/libfdk-aacenc.c | 2 +- 1 file changed, 1

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread RADSL
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 off release/6.0 from master in the next days If theres something blocking and i should wait, please

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

2023-02-21 Thread Ronald S. Bultje
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 to skip "all" decoding, we should also skip metadata for said frames. I

[FFmpeg-devel] [PATCH] Scale libFDK encoder VBR mode with FF_QP2LAMBDA

2023-02-21 Thread JonHGee
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. --- libavcodec/libfdk-aacenc.c | 2 +- 1 file changed, 1 insertion(+), 1

[FFmpeg-devel] [PATCH] Use CONFIG_FFRTMPCRYPT_PROTOCOL for conditional compilation...

2023-02-21 Thread Ziemowit Laski
Use CONFIG_FFRTMPCRYPT_PROTOCOL for conditional compilation and NOT run-time evaluation. If optimizations are disabled and CONFIG_FFRTMPCRYPT_PROTOCOL==0, the compiler may fail to get rid of the conditional blocks. Alas, the blocks themselves contain calls to RTMPE functionality

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

2023-02-21 Thread sonntex
New pcap ffmpeg format can have all options rtpdec requires. Anyway, I don't suggest you implement this feature. I just want to find a good entry point to start coding personally. I need to create a development tool for rtp tracing, and pcap files seem a good idea because I can grab rtp using

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

2023-02-21 Thread Kieran Kunhya
On Tue, 21 Feb 2023, 22:33 sonntex, wrote: > I want to implement something which helps me to play rtp stored in pcap > files. > > tcpdump -i lo udp port 5 -s0 -w - | ffplay -i - > > The specification of pcap files is really simple and I could create a new > ffmpeg format, but don't know how

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

2023-02-21 Thread Leo Izen
These chunks are lightweight and it's useful information to have when running ffmpeg -i or ffprobe, for example. --- libavcodec/pngdec.c | 136 ++- tests/ref/fate/png-icc | 8 +-- tests/ref/fate/png-side-data | 2 +- 3 files changed, 91

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

2023-02-21 Thread sonntex
I want to implement something which helps me to play rtp stored in pcap files. tcpdump -i lo udp port 5 -s0 -w - | ffplay -i - The specification of pcap files is really simple and I could create a new ffmpeg format, but don't know how to process rtp packets extracted from pcap, because it

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread Michael Niedermayer
On Tue, Feb 21, 2023 at 02:20:26PM +0100, Jean-Baptiste Kempf wrote: > > > On Tue, 21 Feb 2023, at 12:38, Michael Niedermayer wrote: > > On Fri, Feb 10, 2023 at 06:47:03PM +0100, Michael Niedermayer wrote: > >> Hi all > >> > >> i plan to branch off release/6.0 from master in the next days > >>

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread Jean-Baptiste Kempf
On Tue, 21 Feb 2023, at 12:38, Michael Niedermayer wrote: > On Fri, Feb 10, 2023 at 06:47:03PM +0100, Michael Niedermayer wrote: >> Hi all >> >> i plan to branch off release/6.0 from master in the next days >> If theres something blocking and i should wait, please reply here >> >> 6.0 release

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread Kieran Kunhya
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 off release/6.0 from master in the next days > > If theres something blocking and i should wait, please reply here > > > > 6.0 release

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread Reto Kromer
Gijs Peskens wrote: >> Here are some previously suggested names: >> Darwin, De broglie, Desitter, Galois, Gauss, Heaviside, >> Jacobi, Maxwell, Mellin, Perelman, Poincaré, Ramanujan, >> Sagan, Viterbi, Voltaire, Von Neumann > >Assuming with Desitter the Dutch mathematician

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

2023-02-21 Thread 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 tell >>spdif/s377m/dolby-e users to RTFM? > >> And another point here

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread Gijs Peskens
On 21-02-2023 12:38, Michael Niedermayer wrote: On Fri, Feb 10, 2023 at 06:47:03PM +0100, Michael Niedermayer wrote: Hi all i plan to branch off release/6.0 from master in the next days If theres something blocking and i should wait, please reply here 6.0 release will be maybe 1 week after

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread Paul B Mahol
On Tue, Feb 21, 2023 at 12:38 PM Michael Niedermayer wrote: > On Fri, Feb 10, 2023 at 06:47:03PM +0100, Michael Niedermayer wrote: > > Hi all > > > > i plan to branch off release/6.0 from master in the next days > > If theres something blocking and i should wait, please reply here > > > > 6.0

Re: [FFmpeg-devel] FFmpeg 6.0

2023-02-21 Thread Michael Niedermayer
On Fri, Feb 10, 2023 at 06:47:03PM +0100, Michael Niedermayer wrote: > Hi all > > i plan to branch off release/6.0 from master in the next days > If theres something blocking and i should wait, please reply here > > 6.0 release will be maybe 1 week after the branch point > once it has branched

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/jpeg2000dec: Move decoder structs to header files.

2023-02-21 Thread Caleb Etemesi
Ping on this On Fri, 6 Jan 2023, 18:46 Tomas Härdin, wrote: > ons 2022-12-28 klockan 23:20 +0300 skrev etemesica...@gmail.com: > > From: caleb > > > > --- > > libavcodec/jpeg2000dec.c | 88 +--- > > libavcodec/jpeg2000dec.h | 121 > >

Re: [FFmpeg-devel] [PATCH 3/6] avformat/s337m: New ff_s337m_probe()

2023-02-21 Thread Nicolas Gaullier
>> ff_s337m_probe is very similar to s337m_probe: what mainly differs is >> the input parameters. >> The one little thing I added is the S337M_PROBE_GUARDBAND_MIN_BYTES. >> Currently it is set to 0, so has no effect (and of course I can remove >> it if someone object). >> There is two things to

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

2023-02-21 Thread 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 dolby paper:

[FFmpeg-devel] [PATCH] avcodec/ac3: Remove unused fields

2023-02-21 Thread Nicolas Gaullier
Signed-off-by: Nicolas Gaullier --- libavcodec/ac3dec.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/libavcodec/ac3dec.h b/libavcodec/ac3dec.h index 138b462abb..adf82b4a98 100644 --- a/libavcodec/ac3dec.h +++ b/libavcodec/ac3dec.h @@ -90,7 +90,6 @@ typedef struct AC3DecodeContext {

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

2023-02-21 Thread Tomas Härdin
fre 2023-02-17 klockan 10:30 + skrev Nicolas Gaullier: > > > +#if CONFIG_S337M_DEMUXER > > > +    {"non_pcm_mode", "Chooses what to do with s337m", > > > OFFSET(non_pcm_mode), AV_OPT_TYPE_INT, {.i64 = 1}, 0, 1, DEC, > > > "non_pcm_mode"}, > > > +    {"copy"    , "Pass s337m through

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

2023-02-21 Thread Tomas Härdin
fre 2023-02-17 klockan 09:44 + skrev Nicolas Gaullier: > > > @@ -56,6 +56,12 @@ static int s337m_get_offset_and_codec(void > > > *avc, > > > avpriv_report_missing_feature(avc, "Data type %#x in > > > SMPTE 337M", data_type & 0x1F); > > > return AVERROR_PATCHWELCOME; > > >

Re: [FFmpeg-devel] [PATCH 3/6] avformat/s337m: New ff_s337m_probe()

2023-02-21 Thread Tomas Härdin
fre 2023-02-17 klockan 10:12 + skrev Nicolas Gaullier: > > The logic here is a bit hairy and I don't have time atm to digest > > it, but is it entirely contained in S337m or would one need to read > > other specs too? > > > > /Tomas > > ff_s337m_probe is very similar to s337m_probe: what

Re: [FFmpeg-devel] Trac votes and priority

2023-02-21 Thread Michael Niedermayer
On Sat, Feb 18, 2023 at 12:18:57AM +0100, Michael Niedermayer wrote: > On Fri, Feb 17, 2023 at 11:29:04PM +0100, Michael Niedermayer wrote: > > Hi > > > > On Fri, Feb 17, 2023 at 12:25:07PM -0600, Brad Isbell wrote: > > > I think that if Trac ticket priority is to be used, it should first be > >

Re: [FFmpeg-devel] trac updating bits

2023-02-21 Thread Michael Niedermayer
On Tue, Feb 21, 2023 at 11:29:22AM +0530, Gyan Doshi wrote: > > > On 2023-02-18 04:58 am, Michael Niedermayer wrote: > > Hi > > > > It appears that a bunch of static files for our trac where missed during > > previous > > updates. I re-deployed them so we should have the latest files now > >

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

2023-02-21 Thread Ridley Combs
> On Feb 21, 2023, at 01:48, Nicolas George wrote: > > rcombs (12023-02-20): >> This already gave garbled output when multiple rects were present, >> so this is simply documenting an existing requirement. >> --- >> libavcodec/assenc.c | 2 ++ >> 1 file changed, 2 insertions(+) > > NAK: the

Re: [FFmpeg-devel] [PATCH 3/3] ffmpeg: respect AV_CODEC_CAP_SINGLE_SUB_RECT

2023-02-21 Thread Ridley Combs
> On Feb 21, 2023, at 01:45, Nicolas George wrote: > > rcombs (12023-02-20): >> Fixes ASS output when multiple rects are present. >> --- >> fftools/ffmpeg.c | 28 ++-- >> 1 file changed, 18 insertions(+), 10 deletions(-) > > Does this not belong to the framework? I

Re: [FFmpeg-devel] [PATCH 1/3] lavc/codec.h: add AV_CODEC_CAP_SINGLE_SUB_RECT

2023-02-21 Thread Ridley Combs
> On Feb 21, 2023, at 01:42, Nicolas George wrote: > > rcombs (12023-02-20): >> --- >> doc/APIchanges | 3 +++ >> libavcodec/codec.h | 5 + >> libavcodec/version.h | 2 +- >> 3 files changed, 9 insertions(+), 1 deletion(-) > > And... No change to the framework to make use of this