Re: [FFmpeg-devel] [PATCH 12/18] avcodec/vvcdec: inter, wait reference with a diffrent resolution
ne CHECK_SAMPLES(d) (frame->pps->r->pps_pic_##d##_in_luma_samples
> == ref->pps->r->pps_pic_##d##_in_luma_samples)
> +static int check_candidate_ref(const VVCFrame *frame, const VVCRefPic
> *refp)
> +{
> +const VVCFrame *ref = refp->ref;
> +
> +if (refp->is_scaled) {
> +const int max = FFMAX(8, frame->sps->min_cb_size_y);
> +return frame->ref_width * 2 >= ref->ref_width &&
> +frame->ref_height * 2 >= ref->ref_height &&
> +frame->ref_width <= ref->ref_width * 8 &&
> +frame->ref_height <= ref->ref_height * 8 &&
> +CHECK_MAX(width) && CHECK_MAX(height);
> +}
> +return CHECK_SAMPLES(width) && CHECK_SAMPLES(height);
> +}
> +
> +#define RPR_SCALE(f) (((ref->f << 14) + (fc->ref->f >> 1)) /
> fc->ref->f)
> /* add a reference with the given poc to the list and mark it as used
> in DPB */
> static int add_candidate_ref(VVCContext *s, VVCFrameContext *fc,
> RefPicList *list,
> int poc, int ref_flag, uint8_t use_msb)
> @@ -372,6 +399,18 @@ static int add_candidate_ref(VVCContext *s,
> VVCFrameContext *fc, RefPicList *lis
> refp->poc = poc;
> refp->ref = ref;
> refp->is_lt = ref_flag & VVC_FRAME_FLAG_LONG_REF;
> +refp->is_scaled = ref->sps->r->sps_num_subpics_minus1 !=
> fc->ref->sps->r->sps_num_subpics_minus1||
> +memcmp(>scaling_win, >ref->scaling_win,
> sizeof(ref->scaling_win)) ||
> +ref->pps->r->pps_pic_width_in_luma_samples !=
> fc->ref->pps->r->pps_pic_width_in_luma_samples ||
> +ref->pps->r->pps_pic_height_in_luma_samples !=
> fc->ref->pps->r->pps_pic_height_in_luma_samples;
> +
> +if (!check_candidate_ref(fc->ref, refp))
> +return AVERROR_INVALIDDATA;
> +
> +if (refp->is_scaled) {
> +refp->scale[0] = RPR_SCALE(ref_width);
> +refp->scale[1] = RPR_SCALE(ref_height);
> +}
> list->nb_refs++;
>
> mark_ref(ref, ref_flag);
> diff --git a/libavcodec/vvc/thread.c b/libavcodec/vvc/thread.c
> index 2654b40058..8777d380bf 100644
> --- a/libavcodec/vvc/thread.c
> +++ b/libavcodec/vvc/thread.c
> @@ -293,10 +293,14 @@ static void schedule_inter(VVCContext *s,
> VVCFrameContext *fc, const SliceContex
> CTU *ctu = fc->tab.ctus + rs;
> for (int lx = 0; lx < 2; lx++) {
> for (int i = 0; i < sh->r->num_ref_idx_active[lx]; i++) {
> -const int y = ctu->max_y[lx][i];
> -VVCFrame *ref = sc->rpl[lx].refs[i].ref;
> -if (ref && y >= 0)
> +int y = ctu->max_y[lx][i];
> +VVCRefPic *refp = sc->rpl[lx].refs + i;
> +VVCFrame *ref = refp->ref;
> +if (ref && y >= 0) {
> +if (refp->is_scaled)
> +y = y * refp->scale[1] >> 14;
> add_progress_listener(ref, >listener[lx][i], t,
> s, VVC_PROGRESS_PIXEL, y + LUMA_EXTRA_AFTER);
> +}
> }
> }
> }
> --
> 2.34.1
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] 5 year plan & Inovation
Hello, On Wed, 17 Apr 2024, at 17:22, Michael Niedermayer wrote: >> > * ffchat >> > (expand into realtime chat / zoom) this would >> > bring in more users and developers, and we basically have almost >> > >> >> Better leave that for others. >> There's an infinite amount of discord clones already. > > iam not following that genre that much ... > so let me ask > are there any that > * preserve privacy (discord is not secure/private) > * allow audio / video / text chat > * scalable > * need no central server Matrix? Elements? Mattermost? Rocket.chat? Jitsi? -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Anyone using 6.0, 4.1, 3.4 ?
Hi, On Mon, 15 Apr 2024, at 01:55, Michael Niedermayer wrote: > I see nothing using 6.0 and 4.1 on our downstreams page, so i suggest to > move 6.0 to the archieve page after 6.0.2 and 4.1 probably without > new releases Good idea. > About 3.4 > ubuntu 18.04 last updated its FFmpeg 3.4 package 15 November 2023 > sadly "apt changelog" doesnt seem to work with that package so iam not > sure that includes our fixes or only other things > our last 3.4 release was 2023-06-12 Just make one point release of 3.4 and drop that branch. > but i intend to make new 3.4 and 2.8 releases too > The branches can be droped afterwards if noone is left using these. Even if those have people using them, you should drop them now. They are old, and we're not sure they are complete in terms of backports and fixes. If you maintain them, people expect completion, while they are not complete, and it does not incentize people to upgrade. > But as shown above ubuntu is still actively doing things with these > packages so if someone confirms that ubuntu still has interrest in > these (or another distro) then ill try to continue to update these In summary, IMHO: I think you should support less versions. Drop 2.8 and 3.4 (after a point release, if you want). Maintain 4.2, 4.4, 5.1, 6.1 and drop all the rest (4.0, 4.1, 4,.3, 5.0). Almost no other project in the world support that many branches. It's better to have a few very well maintained, than all those. -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] Update the Changelog for 7.0
On Thu, 4 Apr 2024, at 07:30, Vittorio Giovara wrote: > On Thu, Apr 4, 2024 at 1:28 AM Jean-Baptiste Kempf wrote: > >> On Wed, 3 Apr 2024, at 23:18, Jean-Baptiste Kempf wrote: >> > As attached. >> >> Updated version attached (v2). >> > > lgtm with AV1 capitalized Fixed & Attached. -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/From ed92996f6e33c6bffe61df0898655bfe4623dbef Mon Sep 17 00:00:00 2001 From: Jean-Baptiste Kempf Date: Wed, 3 Apr 2024 23:12:54 +0200 Subject: [PATCH] Update the Changelog for 7.0 --- Changelog | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Changelog b/Changelog index fcc9f7cfba..a66c3048f0 100644 --- a/Changelog +++ b/Changelog @@ -21,7 +21,7 @@ version 7.0: - qrencode filter and qrencodesrc source - quirc filter - lavu/eval: introduce randomi() function in expressions -- VVC decoder +- VVC decoder (experimental) - fsync filter - Raw Captions with Time (RCWT) closed caption muxer - ffmpeg CLI -bsf option may now be used for input as well as output @@ -42,6 +42,15 @@ version 7.0: - ffplay with hwaccel decoding support (depends on vulkan renderer via libplacebo) - dnn filter libtorch backend - Android content URIs protocol +- AOMedia Film Grain Synthesis 1 (AFGS1) +- RISC-V optimizations for AAC, FLAC, JPEG-2000,LPC, RV4.0, SVQ, VC1, VP8 and more +- Loongarch optimizations for HEVC decoding +- Important AArch64 optimizations for HEVC +- IAMF support inside MP4/ISOBMFF +- Support for HEIF/AVIF still images and tiled still images +- Dolby Vision profile 10 support in AV1 +- Support for Ambient Viewing Environment metadata in MP4/ISOBMFF +- HDR10 metadata passthrough when encoding with libx264, libx265 and SVT-AV1 version 6.1: -- 2.43.0 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] Update the Changelog for 7.0
On Wed, 3 Apr 2024, at 23:18, Jean-Baptiste Kempf wrote: > As attached. Updated version attached (v2). -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/From 96f2b0ee578901ebcf00795950dd78d8e924643c Mon Sep 17 00:00:00 2001 From: Jean-Baptiste Kempf Date: Wed, 3 Apr 2024 23:12:54 +0200 Subject: [PATCH] Update the Changelog for 7.0 --- Changelog | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Changelog b/Changelog index fcc9f7cfba..bf034e9e70 100644 --- a/Changelog +++ b/Changelog @@ -21,7 +21,7 @@ version 7.0: - qrencode filter and qrencodesrc source - quirc filter - lavu/eval: introduce randomi() function in expressions -- VVC decoder +- VVC decoder (experimental) - fsync filter - Raw Captions with Time (RCWT) closed caption muxer - ffmpeg CLI -bsf option may now be used for input as well as output @@ -42,6 +42,15 @@ version 7.0: - ffplay with hwaccel decoding support (depends on vulkan renderer via libplacebo) - dnn filter libtorch backend - Android content URIs protocol +- AOMedia Film Grain Synthesis 1 (AFGS1) +- RISC-V optimizations for AAC, FLAC, JPEG-2000,LPC, RV4.0, SVQ, VC1, VP8 and more +- Loongarch optimizations for HEVC decoding +- Important AArch64 optimizations for HEVC +- IAMF support inside MP4/ISOBMFF +- Support for HEIF/AVIF still images and tiled still images +- Dolby Vision profile 10 support in av1 +- Support for Ambient Viewing Environment metadata in MP4/ISOBMFF +- HDR10 metadata passthrough when encoding with libx264, libx265 and SVT-AV1 version 6.1: -- 2.43.0 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] 7.0 release
Hello, On Thu, 4 Apr 2024, at 00:57, Michael Niedermayer wrote: > I will try to make the 7.0 release from the release branch in the next 48h > (with some luck but easy possible it will get delayed) Please consider pulling in the Changelog modifications I suggested on the mailing list and on IRC, since this is pretty trivial. jbk -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] [PATCH] Update the Changelog for 7.0
As attached. -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/From bc5a37d34d9a634388e425d894aa1219a32d8394 Mon Sep 17 00:00:00 2001 From: Jean-Baptiste Kempf Date: Wed, 3 Apr 2024 23:12:54 +0200 Subject: [PATCH] Update the Changelog for 7.0 --- Changelog | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Changelog b/Changelog index fcc9f7cfba..499a4a37de 100644 --- a/Changelog +++ b/Changelog @@ -21,7 +21,7 @@ version 7.0: - qrencode filter and qrencodesrc source - quirc filter - lavu/eval: introduce randomi() function in expressions -- VVC decoder +- VVC decoder (experimental) - fsync filter - Raw Captions with Time (RCWT) closed caption muxer - ffmpeg CLI -bsf option may now be used for input as well as output @@ -42,6 +42,15 @@ version 7.0: - ffplay with hwaccel decoding support (depends on vulkan renderer via libplacebo) - dnn filter libtorch backend - Android content URIs protocol +- AOMedia Film Grain Synthesis 1 (AFGS1) +- RISC-V optimizations for AAC, FLAC, JPEG-2000,LPC, RV4.0, SVQ, VC1, VP8 and more +- Loongarch optimizations for HEVC decoding +- More ARM optimizations for HEVC +- IAMF support inside MP4/ISOBMFF +- Support for HEIF/AVIF still images and tiled still images +- DV profile 10 support in av1 +- Support for Ambient Viewing Environment metadata in MP4/ISOBMFF +- Display metadata support in libx265, libx264 and libaom encoders version 6.1: -- 2.43.0 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 00/21] aarch64: hevc: Add missing hevc_pel NEON functions
On Mon, 25 Mar 2024, at 22:56, J. Dekker wrote: >> On Mon, 25 Mar 2024, Martin Storsjö wrote: >> >>> Since some time, we have pretty complete AArch64 NEON coverage >>> for the hevc decoder. >>> >>> However, some of these functions require the I8MM instruction set >>> extension, and many of them (but not all) lack a plain NEON >>> version. >>> >>> This patchset fills in a regular NEON version of all functions >>> where we have an I8MM function. >>> >>> For context; the I8MM instruction set extension is a mandatory >>> part of armv8.6-a. E.g. Apple M2, AWS Graviton 3 have it, >>> but Apple M1 and Ampere Altra don't. >>> >>> This patchset takes decoding of a 1080p HEVC clip from 402 >>> fps to 649 fps on an Apple M1. >>> >>> Patch #2 also fixes a subtle bug in the existing implementation; >>> two functions relied on the contents on the stack, below the >>> stack pointer, being untouched within a function. If a signal >>> gets delivered, those parts of the stack could be clobbered. >> >> I know this is a bit short notice for a patchset of this size - but, would >> people be OK with merging this patchset before the impending 7.0 branch >> (which is made within the next 24h)? >> >> The patches pass all my tricky build configurations, they give a very >> non-negligible speedup on many common CPUs, and patch #2 fixes a real bug in >> the existing impleemntations. (A bug fix patch can of course be backported >> after the branch too, but performance optimizations aren't generally >> relevant for backporting.) >> >> // Martin > > Yes, please. I will tomorrow morning if you didn’t already push. +1 -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] 7.0 blocking issues
Hello, On Mon, 25 Mar 2024, at 01:03, Michael Niedermayer wrote: > Should i wait till all issues marked as blocking 7.0 on trac are fixed > before branching ? I think you should branch now. And get things fixed in the 7.0 branch. -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] Changelog: Add Support PacketTypeMetadata of PacketType in enhanced flv
On Mon, 18 Mar 2024, at 11:01, Steven Liu via ffmpeg-devel wrote: > Changelog | 1 + > 1 file changed, 1 insertion(+) Obviously LGTM. jbk -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] avcodec/mips/aaccoder_mips: Remove MIPS-specific aaccoder
On Fri, 15 Mar 2024, at 02:20, Andreas Rheinhardt wrote: > ff_aac_coder_init_mips() modifies a static const structure of > function pointers. This will crash if the binary uses relro > and is a data race in any case. > > Furthermore it points to a maintainability issue: The > AACCoefficientsEncoder structures have been constified > in commit fd9212f2edfe9b107c3c08ba2df5fd2cba5ab9e3, > a Libav commit merged in 318778de9ebec276cb9dfc65509231ca56590d13. > Libav did not have the MIPS-specific AAC code and so this was > fine for them; yet FFmpeg had them, but this was not recognized. LGTM. -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v6] libavfi/dnn: add LibTorch as one of DNN backend
On Fri, 15 Mar 2024, at 05:42, wenbin.chen-at-intel@ffmpeg.org wrote: > From: Wenbin Chen > > PyTorch is an open source machine learning framework that accelerates > the path from research prototyping to production deployment. Official > website: https://pytorch.org/. We call the C++ library of PyTorch as > LibTorch, the same below. LGTM. Please apply. -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] FFmpeg 7.0 blocking issues
n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote: > On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote: >> Hi all >> >> As it was a little difficult for me to not loose track of what is >> blocking a release. I suggest that for all release blocking issues >> open a ticket and set Blocking to 7.0 >> that way this: >> https://trac.ffmpeg.org/query?blocking=~7.0 >> >> or for the ones not closed: >> https://trac.ffmpeg.org/query?status=new=open=reopened=~7.0 >> >> will list all blocking issues >> >> Ive added one, for testing that, i intend to add more if i see something >> >> What is blocking? (IMHO) >> * regressions (unless its non possible to fix before release) >> * crashes >> * security issues >> * data loss >> * privacy issues >> * anything the commuity agrees should be in the release > > We still have 3 blocking issues on trac > > do people want me to wait or ignore them and branch ? I think you can branch soon. However, those 3 bugs are quite important, tbh. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [FFmpeg-cvslog] libavformat/dvdvideo: add DVD-Video demuxer, powered by libdvdread and libdvdnav
On Sun, 3 Mar 2024, at 05:28, Marth64 wrote: > I did take caution here, > ffmpeg must be built with all of the following flags: ./configure > --enable-demuxer=dvdvideo --enable-libdvdread --enable-libdvdnav > --enable-gpl > > This is also called out in the docs: >> FFmpeg must be built with GPL library support available as well as the > configure switches --enable-libdvdnav and --enable-libdvdread. Rocks. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [FFmpeg-cvslog] libavformat/dvdvideo: add DVD-Video demuxer, powered by libdvdread and libdvdnav
Hello,
This is missing an "enabled gpl" in the configure.
BR,
On Sat, 2 Mar 2024, at 09:08, Marth64 wrote:
> ffmpeg | branch: master | Marth64 | Sun Feb 18
> 22:01:44 2024 -0600| [a1304272c3a0ef7c3d77c702dd466b3f11bf300f] |
> committer: Anton Khirnov
>
> libavformat/dvdvideo: add DVD-Video demuxer, powered by libdvdread and
> libdvdnav
>
> Signed-off-by: Marth64
> Signed-off-by: Anton Khirnov
>
>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=a1304272c3a0ef7c3d77c702dd466b3f11bf300f
> ---
>
> Changelog |1 +
> configure |8 +
> doc/demuxers.texi | 130 +
> libavformat/Makefile |1 +
> libavformat/allformats.c |1 +
> libavformat/dvdvideodec.c | 1411
> +
> 6 files changed, 1552 insertions(+)
>
> diff --git a/Changelog b/Changelog
> index c65ef492be..fedad5782c 100644
> --- a/Changelog
> +++ b/Changelog
> @@ -29,6 +29,7 @@ version :
>build environment if it lacks C17 support
> - Change the default bitrate control method from VBR to CQP for QSV encoders.
> - removed deprecated ffmpeg CLI options -psnr and -map_channel
> +- DVD-Video demuxer, powered by libdvdnav and libdvdread
>
> version 6.1:
> - libaribcaption decoder
> diff --git a/configure b/configure
> index b5b233e852..db7dc89755 100755
> --- a/configure
> +++ b/configure
> @@ -227,6 +227,8 @@ External library support:
>--enable-libdavs2enable AVS2 decoding via libdavs2 [no]
>--enable-libdc1394 enable IIDC-1394 grabbing using libdc1394
> and libraw1394 [no]
> + --enable-libdvdnav enable libdvdnav, needed for DVD demuxing
> [no]
> + --enable-libdvdread enable libdvdread, needed for DVD demuxing
> [no]
>--enable-libfdk-aac enable AAC de/encoding via libfdk-aac [no]
>--enable-libfliteenable flite (voice synthesis) support via
> libflite [no]
>--enable-libfontconfig enable libfontconfig, useful for drawtext
> filter [no]
> @@ -1806,6 +1808,8 @@ EXTERNAL_LIBRARY_GPL_LIST="
> frei0r
> libcdio
> libdavs2
> +libdvdnav
> +libdvdread
> librubberband
> libvidstab
> libx264
> @@ -3526,6 +3530,8 @@ dts_demuxer_select="dca_parser"
> dtshd_demuxer_select="dca_parser"
> dv_demuxer_select="dvprofile"
> dv_muxer_select="dvprofile"
> +dvdvideo_demuxer_select="mpegps_demuxer"
> +dvdvideo_demuxer_deps="libdvdnav libdvdread"
> dxa_demuxer_select="riffdec"
> eac3_demuxer_select="ac3_parser"
> evc_demuxer_select="evc_frame_merge_bsf evc_parser"
> @@ -6775,6 +6781,8 @@ enabled libdav1d && require_pkg_config
> libdav1d "dav1d >= 0.5.0" "dav1d
> enabled libdavs2 && require_pkg_config libdavs2 "davs2 >=
> 1.6.0" davs2.h davs2_decoder_open
> enabled libdc1394 && require_pkg_config libdc1394 libdc1394-2
> dc1394/dc1394.h dc1394_new
> enabled libdrm&& check_pkg_config libdrm libdrm xf86drm.h
> drmGetVersion
> +enabled libdvdnav && require_pkg_config libdvdnav "dvdnav >=
> 6.1.1" dvdnav/dvdnav.h dvdnav_open2
> +enabled libdvdread&& require_pkg_config libdvdread "dvdread >=
> 6.1.2" dvdread/dvd_reader.h DVDOpen2 -ldvdread
> enabled libfdk_aac&& { check_pkg_config libfdk_aac fdk-aac
> "fdk-aac/aacenc_lib.h" aacEncOpen ||
> { require libfdk_aac
> fdk-aac/aacenc_lib.h aacEncOpen -lfdk-aac &&
> warn "using libfdk without
> pkg-config"; } }
> diff --git a/doc/demuxers.texi b/doc/demuxers.texi
> index e4c5b560a6..062ea2ea42 100644
> --- a/doc/demuxers.texi
> +++ b/doc/demuxers.texi
> @@ -285,6 +285,136 @@ This demuxer accepts the following option:
>
> @end table
>
> +@section dvdvideo
> +
> +DVD-Video demuxer, powered by libdvdnav and libdvdread.
> +
> +Can directly ingest DVD titles, specifically sequential PGCs,
> +into a conversion pipeline. Menus and seeking are not supported at
> this time.
> +
> +Block devices (DVD drives), ISO files, and directory structures are
> accepted.
> +Activate with @code{-f dvdvideo} in front of one of these inputs.
> +
> +Underlying playback is handled by libdvdnav, and structure parsing by
> libdvdread.
> +FFmpeg must be built with GPL library support available as well as the
> +configure switches @code{--enable-libdvdnav} and
> @code{--enable-libdvdread}.
> +
> +You will need to provide either the desired "title number" or exact
> PGC/PG coordinates.
> +Many open-source DVD players and tools can aid in providing this
> information.
> +If not specified, the demuxer will default to title 1 which works for
> many discs.
> +However, due to the flexibility of the format, it is recommended to
> check manually.
> +There are many discs that are authored strangely or with invalid
> headers.
> +
> +If the input is a real DVD drive, please note that there are some
> drives which may
> +silently fail on reading bad sectors from the disc,
Re: [FFmpeg-devel] [PATCH 2/2] avcodec: remove sonic lossy/lossless audio
On Wed, 28 Feb 2024, at 18:55, James Almer wrote: > On 2/28/2024 10:31 AM, J. Dekker wrote: >> >> Michael Niedermayer writes: >> >>> [[PGP Signed Part:Undecided]] >>> On Wed, Feb 28, 2024 at 01:56:10PM +0100, J. Dekker wrote: >>>> This was an experimental/research codec of which ffmpeg is the only >>>> encoder and decoder, >>> >>> >>>> development has stalled >>> >>> Thats not true, there was private dicussion making sonic the most >>> advanced audio codec in FFmpeg a few months ago. >>> Iam not saying that will happen, i am just saying there was a >>> discussion about it. And that iam in principle interrested in >>> working on this. Its possible i will not have enough time ... >>> >> >> The last commit which actually changed the codec was >> 6026a5ad4f135476c7a1f51f8cfa7f4cc2ca0283 by you in 2013 which is over 10 >> years ago. For an experimental codec I think it's pretty safe to say >> that development has stalled. >> >> Keeping the codec around based on 'what if?'s doesn't seem >> reasonable. Besides, if you do make sonic the most advanced audio codec >> in FFmpeg there's nothing which says you couldn't re-add it at a later >> date when it's being actively developed again. > > Does it hurt keeping it around? If it can at some point be developed > again, then removing the codec id to re-add it later will be a bit dirty. > > IMO, just disable both modules by default during configure, or tag the > encoder as experimental to prevent new streams to be created unless > explicitly requested knowing that it's an unfinished format. +1 -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v3] libavfi/dnn: add LibTorch as one of DNN backend
odel = (THModel *)model->model;
> +THContext *ctx = _model->ctx;
> +TaskItem *task;
> +THRequestItem *request;
> +int ret = 0;
> +
> +ret = ff_check_exec_params(ctx, DNN_TH, model->func_type,
> exec_params);
> +if (ret != 0) {
> +av_log(ctx, AV_LOG_ERROR, "exec parameter checking fail.\n");
> +return ret;
> +}
> +
> +task = (TaskItem *)av_malloc(sizeof(TaskItem));
> +if (!task) {
> +av_log(ctx, AV_LOG_ERROR, "unable to alloc memory for task
> item.\n");
> +return AVERROR(ENOMEM);
> +}
> +
> +ret = ff_dnn_fill_task(task, exec_params, th_model, 0, 1);
> +if (ret != 0) {
> +av_freep();
> +av_log(ctx, AV_LOG_ERROR, "unable to fill task.\n");
> +return ret;
> +}
> +
> +ret = ff_queue_push_back(th_model->task_queue, task);
> +if (ret < 0) {
> +av_freep();
> +av_log(ctx, AV_LOG_ERROR, "unable to push back task_queue.\n");
> +return ret;
> +}
> +
> +ret = extract_lltask_from_task(task, th_model->lltask_queue);
> +if (ret != 0) {
> +av_log(ctx, AV_LOG_ERROR, "unable to extract last level task
> from task.\n");
> +return ret;
> +}
> +
> +request = (THRequestItem
> *)ff_safe_queue_pop_front(th_model->request_queue);
> +if (!request) {
> +av_log(ctx, AV_LOG_ERROR, "unable to get infer request.\n");
> +return AVERROR(EINVAL);
> +}
> +
> +return execute_model_th(request, th_model->lltask_queue);
> +}
> +
> +static DNNAsyncStatusType dnn_get_result_th(const DNNModel *model,
> AVFrame **in, AVFrame **out)
> +{
> +THModel *th_model = (THModel *)model->model;
> +return ff_dnn_get_result_common(th_model->task_queue, in, out);
> +}
> +
> +static int dnn_flush_th(const DNNModel *model)
> +{
> +THModel *th_model = (THModel *)model->model;
> +THRequestItem *request;
> +
> +if (ff_queue_size(th_model->lltask_queue) == 0)
> +// no pending task need to flush
> +return 0;
> +
> +request = (THRequestItem
> *)ff_safe_queue_pop_front(th_model->request_queue);
> +if (!request) {
> +av_log(_model->ctx, AV_LOG_ERROR, "unable to get infer
> request.\n");
> +return AVERROR(EINVAL);
> +}
> +
> +return execute_model_th(request, th_model->lltask_queue);
> +}
> +
> +extern const DNNModule ff_dnn_backend_torch = {
> +.load_model = dnn_load_model_th,
> +.execute_model = dnn_execute_model_th,
> +.get_result = dnn_get_result_th,
> +.flush = dnn_flush_th,
> +.free_model = dnn_free_model_th,
> +};
> diff --git a/libavfilter/dnn/dnn_interface.c
> b/libavfilter/dnn/dnn_interface.c
> index e843826aa6..b9f71aea53 100644
> --- a/libavfilter/dnn/dnn_interface.c
> +++ b/libavfilter/dnn/dnn_interface.c
> @@ -28,6 +28,7 @@
>
> extern const DNNModule ff_dnn_backend_openvino;
> extern const DNNModule ff_dnn_backend_tf;
> +extern const DNNModule ff_dnn_backend_torch;
>
> const DNNModule *ff_get_dnn_module(DNNBackendType backend_type, void
> *log_ctx)
> {
> @@ -40,6 +41,10 @@ const DNNModule *ff_get_dnn_module(DNNBackendType
> backend_type, void *log_ctx)
> case DNN_OV:
> return _dnn_backend_openvino;
> #endif
> +#if (CONFIG_LIBTORCH == 1)
> +case DNN_TH:
> +return _dnn_backend_torch;
> +#endif
> default:
> av_log(log_ctx, AV_LOG_ERROR,
> "Module backend_type %d is not supported or
> enabled.\n",
> diff --git a/libavfilter/dnn_filter_common.c
> b/libavfilter/dnn_filter_common.c
> index f012d450a2..7d194c9ade 100644
> --- a/libavfilter/dnn_filter_common.c
> +++ b/libavfilter/dnn_filter_common.c
> @@ -53,12 +53,22 @@ static char **separate_output_names(const char
> *expr, const char *val_sep, int *
>
> int ff_dnn_init(DnnContext *ctx, DNNFunctionType func_type,
> AVFilterContext *filter_ctx)
> {
> +DNNBackendType backend = ctx->backend_type;
> +
> if (!ctx->model_filename) {
> av_log(filter_ctx, AV_LOG_ERROR, "model file for network is
> not specified\n");
> return AVERROR(EINVAL);
> }
>
> -if (ctx->backend_type == DNN_TF) {
> +if (backend == DNN_TH) {
> +if (ctx->model_inputname)
> +av_log(filter_ctx, AV_LOG_WARNING, "LibTorch backend do
> not require inputname, "\
> + "inputname will be
> ignored.\n");
> +if (ctx->model_outputnames)
> +av_log(filter_ctx, AV_LOG_WARNING, "LibTorch backend do
> not require outputname(s), "\
> + "all outputname(s) will
> be ignored.\n");
> +ctx->nb_outputs = 1;
> +} else if (backend == DNN_TF) {
> if (!ctx->model_inputname) {
> av_log(filter_ctx, AV_LOG_ERROR, "input name of the model
> network is not specified\n");
> return AVERROR(EINVAL);
> @@ -115,7 +125,8 @@ int ff_dnn_get_input(DnnContext *ctx, DNNData
> *input)
>
> int ff_dnn_get_output(DnnContext *ctx, int input_width, int
> input_height, int *output_width, int *output_height)
> {
> -char * output_name = ctx->model_outputnames ?
> ctx->model_outputnames[0] : NULL;
> +char * output_name = ctx->model_outputnames && ctx->backend_type
> != DNN_TH ?
> + ctx->model_outputnames[0] : NULL;
> return ctx->model->get_output(ctx->model->model,
> ctx->model_inputname, input_width, input_height,
> (const char *)output_name,
> output_width, output_height);
> }
> diff --git a/libavfilter/dnn_interface.h b/libavfilter/dnn_interface.h
> index 852d88baa8..63f492e690 100644
> --- a/libavfilter/dnn_interface.h
> +++ b/libavfilter/dnn_interface.h
> @@ -32,7 +32,7 @@
>
> #define DNN_GENERIC_ERROR FFERRTAG('D','N','N','!')
>
> -typedef enum {DNN_TF = 1, DNN_OV} DNNBackendType;
> +typedef enum {DNN_TF = 1, DNN_OV, DNN_TH} DNNBackendType;
>
> typedef enum {DNN_FLOAT = 1, DNN_UINT8 = 4} DNNDataType;
>
> diff --git a/libavfilter/vf_dnn_processing.c
> b/libavfilter/vf_dnn_processing.c
> index e7d21eef32..fdac31665e 100644
> --- a/libavfilter/vf_dnn_processing.c
> +++ b/libavfilter/vf_dnn_processing.c
> @@ -50,6 +50,9 @@ static const AVOption dnn_processing_options[] = {
> #endif
> #if (CONFIG_LIBOPENVINO == 1)
> { "openvino","openvino backend flag", 0,
> AV_OPT_TYPE_CONST, { .i64 = DNN_OV },0, 0, FLAGS, .unit =
> "backend" },
> +#endif
> +#if (CONFIG_LIBTORCH == 1)
> +{ "torch", "torch backend flag", 0,
> AV_OPT_TYPE_CONST, { .i64 = DNN_TH },0, 0, FLAGS,
> "backend" },
> #endif
> DNN_COMMON_OPTIONS
> { NULL }
> --
> 2.34.1
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] fate rsync switch to git
Yo, On Tue, 20 Feb 2024, at 15:31, Michael Niedermayer wrote: > I did hear (at fosdem?) > about the idea to switch from rsync to git for managing the fate samples > i thought the idea sounds interresting but isnt rsync more efficient ? Yes, that's my idea. The git part is not for others clients to sync, but just to manage the samples. It allows to have versioning of the samples, with the extra ability to have branches and tags matching the ffmpeg branches. It avoids the weird dance "waiting for FATE admin to upload thing", because their would be multiple approvers/committers to that repo. It simplifies the workflow on the admin side, since with a git hook, the server does "git update" in the directory that will be rsync'd by the mirrors. And it does not change their workflow, still using rsync. just my 5c. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v2] libavfi/dnn: add LibTorch as one of DNN backend
Hello,
On Fri, 2 Feb 2024, at 08:26, wenbin.chen-at-intel@ffmpeg.org wrote:
> +static void infer_completion_callback(void *args) {
> +THRequestItem *request = (THRequestItem*)args;
> +LastLevelTaskItem *lltask = request->lltask;
> +TaskItem *task = lltask->task;
> +DNNData outputs = { 0 };
> +THInferRequest *infer_request = request->infer_request;
> +THModel *th_model = (THModel *)task->model;
> +torch::Tensor *output = infer_request->output;
> +
> +c10::IntArrayRef sizes = output->sizes();
> +assert(sizes.size == 5);
Why 5?
> +outputs.order = DCO_RGB;
> +outputs.layout = DL_NCHW;
> +outputs.dims[2] = sizes.at(3);
> +outputs.dims[3] = sizes.at(4);
> +outputs.dt = DNN_FLOAT;
> +outputs.dims[1] = 3;
Why 3?
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17.
Hello, On Thu, 8 Feb 2024, at 01:36, Cosmin Stejerean via ffmpeg-devel wrote: >> There were simply no objections to moving to C11. >> The C17 plan came about later because it has important bugfixes. >> It doesn't really matter as compilers backported the new behaviour to C11 >> (or rather, they consistently had the same behaviour, but now it became a >> standard). >> > > There were no objections to C11, however C17 was brought up and there > were objections that it's likely too soon and I believe JB proposed > holding off for a year on C17 (while adopting C11 immediately), which My recommendation is still this: - move to C11 now - activate C17 on some Fate/CI targets - recommend C17 compilers modes - move to C17 at this mid-year when 7.1 is branched (LTS if we follow our plans) -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] Meeting at FOSDEM
Hello Folks, FOSDEM is upon us, in a few days. It would be a great idea to meet for a FFmpeg discussion, since quite a few of us will be there. So please bring your technical topics with you :) As the OpenMediaRoom is on the Sunday, this time, I would say that we should do it on the Saturday afternoon, at the usual place. See you at FOSDEM, -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space
On Wed, 3 Jan 2024, at 23:21, Marth64 wrote:
> Hi,
> I felt that it was strange in all of documentation, this is the only
> scenario where 0xA0 is used for a space character instead of the ordinary
> space 0x20. It is invisible when viewing in email or many IDE but in my
> editor I was able to see the exact hex character was not a ordinary space
> character.
>
> The string currently is actually as follows under a hex lens:
> (default ~5<0xA0>Mo) and @code{analyzeduration} (default 5,000,000<0xA0>µs
> = 5<0xA0>s).
IMHO, this was correct and should be used everywhere to avoid splitting a
number from its unit in various part of the documentation.
—
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space
Why this change?
On Wed, 3 Jan 2024, at 19:47, Marth64 wrote:
> Signed-off-by: Marth64
> ---
> doc/faq.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/faq.texi b/doc/faq.texi
> index 39f28eef08..5998e0d000 100644
> --- a/doc/faq.texi
> +++ b/doc/faq.texi
> @@ -450,7 +450,7 @@ work with streams that were detected during the
> initial scan; streams that
> are detected later are ignored.
>
> The size of the initial scan is controlled by two options: @code{probesize}
> -(default ~5 Mo) and @code{analyzeduration} (default 5,000,000 µs = 5 s). For
> +(default ~5 Mo) and @code{analyzeduration} (default 5,000,000 µs = 5 s). For
> the subtitle stream to be detected, both values must be large enough.
>
> @section Why was the @command{ffmpeg} @option{-sameq} option removed?
> What to use instead?
> --
> 2.34.1
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v9 13/13] vvcdec: add vvc decoder
On Tue, 2 Jan 2024, at 10:38, Nuo Mi wrote: > On Mon, Jan 1, 2024 at 11:22 PM Lynne wrote: > >> Jan 1, 2024, 16:14 by h.lepp...@gmail.com: >> >> > On Mon, Jan 1, 2024 at 3:54 PM Lynne wrote: >> > >> >> >> >> Jan 1, 2024, 15:16 by nuomi2...@gmail.com: >> >> >> >> > vvc decoder plug-in to avcodec. >> >> > split frames into slices/tiles and send them to vvc_thread for >> further decoding >> >> > reorder and wait for the frame decoding to be done and output the >> frame >> >> > >> >> > Features: >> >> > + Support I, P, B frames >> >> > + Support 8/10/12 bits, chroma 400, 420, 422, and 444 and range >> extension >> >> > + Support VVC new tools like MIP, CCLM, AFFINE, GPM, DMVR, PROF, >> BDOF, LMCS, ALF >> >> > + 295 conformace clips passed >> >> > - Not support RPR, IBC, PALETTE, and other minor features yet >> >> > >> >> >> >> IBC == Intra-block copy? >> >> Palette == palette (screen content) coding? >> >> >> > >> > Yes; Both IBC and PALETTE modes are alternate block coding modes, with >> > these two primarily optimized for screen content. >> > >> >> IBC is more general purpose in AV1 afaik. >> They are rather important these days, is there a chance they could be >> implemented before merging? > > Hi Hendrik, > Thank you for your help. > > Hi Lynne, > A contributor submitted an IBC implementation at > https://github.com/ffvvc/FFmpeg/pull/169, but it still needs time to > finish. > They are delta features. Even today, HEVC decoder does not support IBC and > Palette coding. > We can submit the enhancement after the merge. Yes, the patchset is big enough that it should be merged. The delta features can come later. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v9 00/13] Add vvc decoder
On Tue, 2 Jan 2024, at 11:26, Kieran Kunhya wrote: > On Tue, 2 Jan 2024 at 09:21, Nuo Mi wrote: > >> On Mon, Jan 1, 2024 at 11:50 PM Lynne wrote: >> >> > Jan 1, 2024, 16:26 by jamr...@gmail.com: >> > >> > > On 1/1/2024 12:16 PM, Lynne wrote: >> > > >> > >> Jan 1, 2024, 15:13 by nuomi2...@gmail.com: >> > >> >> > >>> libavcodec/vvc/Makefile | 16 + >> > >>> libavcodec/vvc/vvc_cabac.c | 2478 ++ >> > >>> libavcodec/vvc/vvc_cabac.h | 126 + >> > >>> libavcodec/vvc/vvc_ctu.c | 2491 ++ >> > >>> libavcodec/vvc/vvc_ctu.h | 480 >> > >>> libavcodec/vvc/vvc_data.c| 3486 >> ++ >> > >>> libavcodec/vvc/vvc_data.h| 80 + >> > >>> libavcodec/vvc/vvc_filter.c | 1332 ++ >> > >>> libavcodec/vvc/vvc_filter.h | 71 + >> > >>> libavcodec/vvc/vvc_filter_template.c | 1135 + >> > >>> libavcodec/vvc/vvc_inter.c | 923 +++ >> > >>> libavcodec/vvc/vvc_inter.h | 42 + >> > >>> libavcodec/vvc/vvc_inter_template.c | 1023 >> > >>> libavcodec/vvc/vvc_intra.c | 797 ++ >> > >>> libavcodec/vvc/vvc_intra.h | 49 + >> > >>> libavcodec/vvc/vvc_intra_template.c | 1015 >> > >>> libavcodec/vvc/vvc_itx_1d.c | 708 ++ >> > >>> libavcodec/vvc/vvc_itx_1d.h | 52 + >> > >>> libavcodec/vvc/vvc_mvs.c | 1798 + >> > >>> libavcodec/vvc/vvc_mvs.h | 46 + >> > >>> libavcodec/vvc/vvc_ps.c | 1150 + >> > >>> libavcodec/vvc/vvc_ps.h | 263 ++ >> > >>> libavcodec/vvc/vvc_refs.c| 559 + >> > >>> libavcodec/vvc/vvc_refs.h| 57 + >> > >>> libavcodec/vvc/vvc_thread.c | 828 ++ >> > >>> libavcodec/vvc/vvc_thread.h | 36 + >> > >>> libavcodec/vvc/vvcdec.c | 1017 >> > >>> libavcodec/vvc/vvcdec.h | 226 ++ >> > >>> libavcodec/vvc/vvcdsp.c | 141 ++ >> > >>> libavcodec/vvc/vvcdsp.h | 170 ++ >> > >>> libavcodec/vvc/vvcdsp_template.c | 120 + >> > >>> >> > >> >> > >> We have larger decoders than this, could you just put all files in >> > libavodec/? >> > >> >> > > >> > > Was asked him to do it this way. Ideally, other codecs would follow >> > after it, too. >> > >> Yeah, with over 1600+ files under libavcodec, even GitHub struggles to >> fully list them. >> This is not user-friendly for someone who wants to check the code in the >> browser. Not just the browser. Keep it up :) -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v9 09/13] vvcdec: add LMCS, Deblocking, SAO, and ALF filters
On Tue, 2 Jan 2024, at 10:47, Nuo Mi wrote: > On Mon, Jan 1, 2024 at 11:18 PM Lynne wrote: > >> Jan 1, 2024, 15:15 by nuomi2...@gmail.com: >> >> > Co-authored-by: Xu Mu >> > Co-authored-by: Frank Plowman >> > Co-authored-by: Shaun Loo >> > Co-authored-by: Wu Jianhua >> > --- >> > libavcodec/vvc/Makefile |1 + >> > libavcodec/vvc/vvc_ctu.h |1 + >> > libavcodec/vvc/vvc_filter.c | 1332 ++ >> > libavcodec/vvc/vvc_filter.h | 71 ++ >> > libavcodec/vvc/vvc_filter_template.c | 1135 ++ >> > 5 files changed, 2540 insertions(+) >> > create mode 100644 libavcodec/vvc/vvc_filter.c >> > create mode 100644 libavcodec/vvc/vvc_filter.h >> > create mode 100644 libavcodec/vvc/vvc_filter_template.c >> > >> >> Is there really absolutely nothing you can reuse from the HEVC decoder? >> > LMCS and ALF are new filters. SAO is entirely reusable, and deblock is > partially reusable. > However, all of them require some changes to the HEVC code. > Currently, I prefer not to touch the HEVC code as there is no HEVC > maintainer, and any HEVC code change requires a very long review time. Yes, keep it up like this. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v8 13/13] vvcdec: add vvc decoder
On Sun, 31 Dec 2023, at 12:07, Martin Storsjö wrote: > On Sun, 31 Dec 2023, Nuo Mi wrote: > >> vvc decoder plug-in to avcodec. >> split frames into slices/tiles and send them to vvc_thread for further >> decoding >> reorder and wait for the frame decoding to be done and output the frame >> >> Features: >>+ Support I, P, B frames >>+ Support 8/10/12 bits, chroma 400, 420, 422, and 444 and range extension >>+ Support VVC new tools like MIP, CCLM, AFFINE, GPM, DMVR, PROF, BDOF, >> LMCS, ALF >>+ 295 conformace clips passed >>- Not support RPR, IBC, PALETTE, and other minor features yet >> >> Performance: >>C code FPS on an i7-12700K (x86): >>BQTerrace_1920x1080_60_10_420_22_RA.vvc 93.0 >>Chimera_8bit_1080P_1000_frames.vvc 184.3 >>NovosobornayaSquare_1920x1080.bin 191.3 >>RitualDance_1920x1080_60_10_420_32_LD.266 150.7 >>RitualDance_1920x1080_60_10_420_37_RA.266 170.0 >>Tango2_3840x2160_60_10_420_27_LD.266 33.7 >> >>C code FPS on a M1 Mac Pro (ARM): >>BQTerrace_1920x1080_60_10_420_22_RA.vvc 58.7 >>Chimera_8bit_1080P_1000_frames.vvc 153.3 >>NovosobornayaSquare_1920x1080.bin 150.3 >>RitualDance_1920x1080_60_10_420_32_LD.266 105.0 >>RitualDance_1920x1080_60_10_420_37_RA.266 133.0 >>Tango2_3840x2160_60_10_420_27_LD.26621.7 >> >>Asm optimizations still working in progress. please check >>https://github.com/ffvvc/FFmpeg/wiki#performance-data for the latest >> >> Contributors(based on code merge order): >>Nuo Mi >>Xu Mu >>frankplow >>Shaun Loo > > Minor nitpick: For clarity, I'd prefer if you'd spell out Frank's full > namw here. Also, you should use Co-Authored-By: -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] Bloomberg donation to FFmpeg
Hello folks, The nice folks at Bloomberg, represented by their Open Source Program Office (OSPO) are sending us a $10k grant! This is part of their FOSS Contributor Fund, where FFmpeg was selected by employees! This money will come through OpenCollective and should arrive on the SPI account, soon™® Merry Christmas and happy holidays! -- Jean-Baptiste Kempf - CC +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] MAINTAINERS: remove myself from FFmpeg
On Thu, 7 Dec 2023, at 10:14, Nicolas George wrote: > The community is dead. And you never belonged to it anyway, with your > superior attitude. You calling someone "superior attitude" is amazing. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] MAINTAINERS: remove myself from FFmpeg
On Thu, 7 Dec 2023, at 10:10, Nicolas George wrote: > Jean-Baptiste Kempf (12023-12-07): >> You are delusional. > > Oh, this is absolutely appropriate, especially from somebody who just > got elected to apply the code of conduct. Keep antagonizing more people in the community, it's a great idea. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] MAINTAINERS: remove myself from FFmpeg
On Thu, 7 Dec 2023, at 09:59, Nicolas George wrote: > Jean-Baptiste Kempf (12023-12-07): >> Why? > > Because after twelve years libav has finally managed to take control and > FFmpeg is now essentially dead. You are delusional. libav is dead since a long time. The fact that people are pushing against your patches does not mean they are wrong or an enemy. > Thank you for your contribution in this. You are welcome. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] MAINTAINERS: remove myself from FFmpeg
Why? On Thu, 7 Dec 2023, at 08:29, Paul B Mahol wrote: > Attached. > > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > > Attachments: > * 0001-MAINTAINERS-remove-myself-from-FFmpeg.patch -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] [PATCH] doc: mention that for RISC-V, we prefer .S files
$subject
See attachment.
--
Jean-Baptiste Kempf - President
+33 672 704 734From 13eb5105ff6fe664d4a45da6970875ceb763dfe0 Mon Sep 17 00:00:00 2001
From: Jean-Baptiste Kempf
Date: Tue, 5 Dec 2023 10:56:55 +0100
Subject: [PATCH] doc: mention that for RISC-V, we prefer .S files
---
doc/developer.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index 26dc5b9749..eed0ee4915 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -99,7 +99,7 @@ The specific syntax used for writing assembly is:
NASM on x86;
@item
-GAS on ARM.
+GAS on ARM and RISC-V.
@end itemize
A unit testing framework for assembly called @code{checkasm} lives under
--
2.43.0
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] lavc: remove the QOA decoder
Hi, On Sat, 2 Dec 2023, at 19:55, Paul B Mahol wrote: > Its not hard to add/write test, and even its easy to upload test sample to > server, but last time I did it people complained of too big samples. What is too big a sample? What's the problem with large samples? What is the documented official limit? jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] Repeat vote: GA voters list updates
On Sat, 11 Nov 2023, at 17:58, Nicolas George wrote: > Michael Niedermayer (12023-11-11): >> Lets just consider i receive a mail at niedermayer.cc, i could construct a >> bounce and >> send it back while still voting with the token in it. If i now get a mail at >> gmx.at >> i could vote twice. > > I am confused: you would get the same token in the second mail, you > would not be able to use it twice. Nicolas is very correct here: in some of the test voting, some people got the email twice, and could vote only once. TBH, all e-voting systems work like that AFAIK -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] Repeat vote: GA voters list updates
On Sat, 11 Nov 2023, at 08:22, Thilo Borgmann via ffmpeg-devel wrote > The authorized voters for the repeated vote [2] reads as follows: > > mich...@niedermayer.cc > one...@gmail.com > jamr...@gmail.com > andreas.rheinha...@gmail.com > s...@jkqxz.net > c...@passwd.hu > ceffm...@gmail.com > barryjz...@tencent.com > liuq...@kuaishou.com > lance.lmw...@gmail.com > martin.vign...@gmail.com > ffm...@gyani.pro > a...@tmm1.net > mar...@martin.st > di...@biurrun.de > lizhong1...@gmail.com > d...@lynne.ee > nfx...@googlemail.com > an...@khirnov.net > atomnu...@gmail.com > t...@rothenpieler.org > u...@pkh.me > geo...@nsup.org > yejun@intel.com > linjie...@intel.com > kaustubh.ra...@imgtec.com > stebb...@jetheaddev.com > phil...@overt.org > andriy.gel...@gmail.com > vittorio.giov...@gmail.com > jerome.borsb...@carpalis.nl > derek.buitenh...@gmail.com > pr...@xvid.org > j...@itanimul.li > kjeya...@akamai.com > dalecur...@chromium.org > jee...@gmail.com > t.r...@noa-archive.com > vdi...@akamai.com > zhiliz...@tencent.com > matthieu.bou...@gmail.com > yinshiyou...@loongson.cn > z...@zanevaniperen.com > ruiling.s...@intel.com > kjeya...@akamai.com > hwr...@126.com > modma...@google.com > c...@gmx.com > fooba...@gmail.com > baptiste.coudur...@gmail.com You have been told, now, several times, that a list of email is a collection of Private Information, according to a GDPR and that you are a process of this PI, and therefore liable to the law. However, neither YOU nor the legal owner FFmpeg.org explain how you will retain this information, process it further, OR, as the most important part, remove it from this mailing lists archive, when requested or when the time is over. This is illegal. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA
On Fri, 10 Nov 2023, at 14:16, Michael Niedermayer wrote: >> First, because noone said anything else on that thread to ask for it to be >> public. > >> And then, because people complained after that it was not public, at the >> following meeting. >> So we said that we would do differently the following time. > > Was this a FFmpeg meeting or a (weekly) FFlabs meeting ? An FFmpeg one. > And in that one meeting FFmpeg voting was discussed towards the end of the > meeting. You remember all the contents of all FFmpeg meetings since 2020, including all the calls, the FOSDEM and VDD ones? I don't. I remember someone saying it should be public, I said: "sure, that's a good point" and that's it. If people had asked in the previous thread, that's probably what I would have done. Because I'm normal human being, who understand his limitations. People have asked for people becoming candidates to post publicly on this mailing list, I don't see what the big deal in that. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA
On Thu, 9 Nov 2023, at 23:49, Michael Niedermayer wrote: > On Thu, Nov 09, 2023 at 08:30:15PM +0100, Jean-Baptiste Kempf wrote: >> >> >> On Thu, 9 Nov 2023, at 19:15, Michael Niedermayer wrote: >> > On Thu, Nov 09, 2023 at 07:53:33PM +0200, Rémi Denis-Courmont wrote: >> >> Le torstaina 9. marraskuuta 2023, 19.41.53 EET Michael Niedermayer a >> >> écrit : >> > [...] >> >> If you think some people should be added, as far as I am concerned, you >> >> are of >> >> course welcome to nudge them via private message to friendly remind them >> >> that >> >> they can nominate themselves. >> > >> > so what i will do then is >> > If a developer was in the GA before || are just under the threshold but >> > active || are part of the infra teams and packaging >> > i will leave them in the list to be added (that is also what jb suggested) >> >> Of course, this seems reasonable. >> >> > I will contact them and ask if they want to be in the GA and >> >> You should contact who you want, or think is necessary. >> But they should step forward and say so publicly that they are candidates. > > last time you collected candidates you said something very different > > https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2020-June/265348.html > > "If you are interested in being a candidate, please mail me in private > (aka not on the list). > You can suggest another candidate, but I will validate with them if > they might agree in the end." > > I want to use the exact same process, why you and other people demand > a higher bar ? First, because noone said anything else on that thread to ask for it to be public. And then, because people complained after that it was not public, at the following meeting. So we said that we would do differently the following time. You want everything public, for everything, even for list of voters, and emails, and SPI reimbursements, (for things that are something a clear privacy and GDPR violations). But now, you want to keep private the people who should be external GA members, while, on THIS very thread, people asked for publicity and for candidates to speak up for their candidacy. Also, at that time, I did not bring a list of 20 candidates who are, for the most part, inactive. While asking "trust me, I will get their approval in private, but they will not speak on the mailing list". jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA
On Thu, 9 Nov 2023, at 19:15, Michael Niedermayer wrote: > On Thu, Nov 09, 2023 at 07:53:33PM +0200, Rémi Denis-Courmont wrote: >> Le torstaina 9. marraskuuta 2023, 19.41.53 EET Michael Niedermayer a écrit : > [...] >> If you think some people should be added, as far as I am concerned, you are >> of >> course welcome to nudge them via private message to friendly remind them >> that >> they can nominate themselves. > > so what i will do then is > If a developer was in the GA before || are just under the threshold but > active || are part of the infra teams and packaging > i will leave them in the list to be added (that is also what jb suggested) Of course, this seems reasonable. > I will contact them and ask if they want to be in the GA and You should contact who you want, or think is necessary. But they should step forward and say so publicly that they are candidates. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA
On Thu, 9 Nov 2023, at 18:24, Michael Niedermayer wrote: > theres a list of voters in 2020 and 2023 The list of voters in 2020 comes from the script written by Josh (IIRC?) and run by Thilo (?) IIRC when Thilo installed CIVS. It quite matches the gitlog. The list was reused for the vote, and now the new list was written by Anton with the new script. Whatever the old script was, and how wrong it was, I don't think it would change the result of the re-bootstrapping vote. And now we have a clean list for the extra members of the GA. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA
On Thu, 9 Nov 2023, at 17:21, Michael Niedermayer wrote: > On Thu, Nov 09, 2023 at 01:21:13PM +0100, Anton Khirnov wrote: >> Quoting Michael Niedermayer (2023-11-09 12:55:25) >> > On Thu, Nov 09, 2023 at 10:44:12AM +0100, Anton Khirnov wrote: >> > > As nobody expressed a preference, the vote will start next Monday >> > > (2023-11-13). It should run for a week, and will be followed by TC/CC >> > > elections. >> > > >> > > The only extra GA candidate I see proposed so far is Ronald. If anyone >> > > wants to suggest further people, please do so in this thread ASAP. >> > >> > IMHO the question of the relation of the list of people who could vote >> > in the last GA vote and the people who where in the general assembly >> > in 2020 should be awnsered before further votes. >> > https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-November/316609.html >> >> As far as I can tell, the voter list in the last vote should be the same >> as the GA from 2020, except for the extra members whose voting rights >> expire after 2 years. >> >> Do you dispute that? > > There are at least 3 issues here > > * The first and maybe the biggest, is that our vote superviser can reply to > mails within 20min (like in this thread here) but is not replying to a > simple > question within days where the list of voters comes from he used and how it WTF are you talking about ? WTF are you attacking me on my email response time? > relates to the 2020 GA. It gives one the feeling he has some sort of > difficulty with awnsering that question > you took a guess here and replied, and i appreciate that. But really JB > choose this list and also the one in 2020. Only he can explain where these I choose nothing. I got the list that was provided to me for the first vote, after the script was written. I did not write the script, I did not run the script. Would you stop smearing me? This is absolutely unacceptable. A contrario from you, I am not part of the GA and I don’t have voting rights… > * The 2nd issue is that there are rules how to change the GA over time No they don’t. We discussed and voted a way, and after years it seems it was not clear enough for some people. > Now we are here trying the 3rd variant of applying > only half the rules. So what? The previous way was not clear enough for people, so we vote for a new way. And it was accepted quite largely against the other options. > Not stating upfront what this list is > IMO this is not acceptable for a vote. How so? Do you go to and see the list of all the voters in Austria before doing a vote ? Especially, here, it is to bootstrap a new way of voting. If the vote was close, maybe there could be discussion, but here, this is not the case. And stop smearing me in the mud. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA
On Thu, 9 Nov 2023, at 12:55, Michael Niedermayer wrote: > If the current GA stays as it is, then i propose the following people Most of those people have not been active for years. Adding the people who were part of the GA before; or are just under the threshold, but were active before; or are part of the infra teams and packaging; seem sane to add to the ballot. But the others seem totally inactive in this community, even if they were added to MAINTAINERS file a long time ago. And there are people who don't contribute, because their corporate sponsor is not employing them anymore. Best, -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v9 1/9] libavutil: add hwcontext_d3d12va and AV_PIX_FMT_D3D12
gt; +} while (0)
> +
> +#endif /* AVUTIL_HWCONTEXT_D3D12VA_INTERNAL_H */
> \ No newline at end of file
> diff --git a/libavutil/hwcontext_internal.h
> b/libavutil/hwcontext_internal.h
> index e6266494ac..4df516ee6a 100644
> --- a/libavutil/hwcontext_internal.h
> +++ b/libavutil/hwcontext_internal.h
> @@ -165,6 +165,7 @@ int ff_hwframe_map_replace(AVFrame *dst, const
> AVFrame *src);
>
> extern const HWContextType ff_hwcontext_type_cuda;
> extern const HWContextType ff_hwcontext_type_d3d11va;
> +extern const HWContextType ff_hwcontext_type_d3d12va;
> extern const HWContextType ff_hwcontext_type_drm;
> extern const HWContextType ff_hwcontext_type_dxva2;
> extern const HWContextType ff_hwcontext_type_opencl;
> diff --git a/libavutil/pixdesc.c b/libavutil/pixdesc.c
> index 4e4a63e287..0db4167934 100644
> --- a/libavutil/pixdesc.c
> +++ b/libavutil/pixdesc.c
> @@ -2311,6 +2311,10 @@ static const AVPixFmtDescriptor
> av_pix_fmt_descriptors[AV_PIX_FMT_NB] = {
> .name = "d3d11",
> .flags = AV_PIX_FMT_FLAG_HWACCEL,
> },
> +[AV_PIX_FMT_D3D12] = {
> +.name = "d3d12",
> +.flags = AV_PIX_FMT_FLAG_HWACCEL,
> +},
> [AV_PIX_FMT_GBRPF32BE] = {
> .name = "gbrpf32be",
> .nb_components = 3,
> diff --git a/libavutil/pixfmt.h b/libavutil/pixfmt.h
> index a26c72d56b..58f9ad28bd 100644
> --- a/libavutil/pixfmt.h
> +++ b/libavutil/pixfmt.h
> @@ -429,6 +429,13 @@ enum AVPixelFormat {
> AV_PIX_FMT_GBRAP14BE, ///< planar GBR 4:4:4:4 56bpp, big-endian
> AV_PIX_FMT_GBRAP14LE, ///< planar GBR 4:4:4:4 56bpp, little-endian
>
> +/**
> + * Hardware surfaces for Direct3D 12.
> + *
> + * data[0] points to an AVD3D12VAFrame
> + */
> +AV_PIX_FMT_D3D12,
> +
> AV_PIX_FMT_NB ///< number of pixel formats, DO NOT USE
> THIS if you want to link with shared libav* because the number of
> formats might differ between versions
> };
>
> diff --git a/libavutil/tests/hwdevice.c b/libavutil/tests/hwdevice.c
> index c57586613a..9d7964f9ee 100644
> --- a/libavutil/tests/hwdevice.c
> +++ b/libavutil/tests/hwdevice.c
> @@ -137,6 +137,8 @@ static const struct {
>{ "0", "1", "2" } },
> { AV_HWDEVICE_TYPE_D3D11VA,
>{ "0", "1", "2" } },
> +{ AV_HWDEVICE_TYPE_D3D12VA,
> + { "0", "1", "2" } },
> { AV_HWDEVICE_TYPE_OPENCL,
>{ "0.0", "0.1", "1.0", "1.1" } },
> { AV_HWDEVICE_TYPE_VAAPI,
> diff --git a/libavutil/version.h b/libavutil/version.h
> index 589a42b0fa..c5fa7c3692 100644
> --- a/libavutil/version.h
> +++ b/libavutil/version.h
> @@ -79,7 +79,7 @@
> */
>
> #define LIBAVUTIL_VERSION_MAJOR 58
> -#define LIBAVUTIL_VERSION_MINOR 31
> +#define LIBAVUTIL_VERSION_MINOR 32
> #define LIBAVUTIL_VERSION_MICRO 100
>
> #define LIBAVUTIL_VERSION_INT AV_VERSION_INT(LIBAVUTIL_VERSION_MAJOR, \
> --
> 2.41.0.windows.1
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANN] Poll Results: GA voters list updates
Hello, On Mon, 6 Nov 2023, at 16:56, Alexander Strasser wrote: > Hi all, > hi J-B! > > On 2023-11-06 07:10 +0100, Jean-Baptiste Kempf wrote: >> Yo, >> >> Time is up, results are here: >> https://vote.ffmpeg.org/cgi-bin/civs/results.pl?id=E_029f7195fed7aadf > > Should I have been mailed about this vote? > I'm pretty sure I could vote in 2020. Or am I just missing something? You should have been mailed. Sorry, this is probably my mistake: it seems the list I used did not include the extra members, and I forgot to add some of them. Next time we'll add the members into the script so it can't happen again. I'm very sorry. Hopefully, since the results are so clearly in favor of A, no single vote could change it. However, please add yourself to the extra-members thread, so we don't forget it :) jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] [ANN] Poll Results: GA voters list updates
Yo, Time is up, results are here: https://vote.ffmpeg.org/cgi-bin/civs/results.pl?id=E_029f7195fed7aadf The 1. place goes to A: twice a year (1st Jan & 1st July, 0:00 UTC); as an exception, the list will also be updated immediately after this vote The 2. place goes to: B: before each vote The 3. place goes to: D: keep everyone who had vote rights but add active developers each 1st Jan and 1st July, 0:00 UTC; as an exception, the list will also be updated immediately after this vote The 4. place goes to: C: never (keep the 2020 version) The GA has spoken, so, option A is taken, with a bi-annual update. Patches for the documentation are welcome. Best, -- Jean-Baptiste Kempf - Vice +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 1/1] tools/general_assembly.pl - print names with emails
On Mon, 6 Nov 2023, at 03:06, Cosmin Stejerean via ffmpeg-devel wrote: >> On Nov 5, 2023, at 5:41 AM, Thilo Borgmann via ffmpeg-devel >> wrote: >> The script should output two files then, so that no manual editing is >> required. >> The voting system expects a file with mail addresses one per line and the ML >> then shall be given the very same list but with only the names. > > The editing in this case is fairly straight forward to extract the > emails between the <>, but if we need a convenient "emails only" output > option for the voting system I could also add some switches to the > script to print only names, only emails or name and email for example. That would be helpful, tbh. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming GA vote
Yo, On Fri, 3 Nov 2023, at 18:33, Michael Niedermayer wrote: >> It will take a bit of time, but I'll do it. Aman Andreas Andriy Anton Lynne Baptiste Jun Zhao Lauri Kasanen Carl Marton Dale Derek Diego Gyan foo86 Gautam Ramakrishnan Nicolas hwrenx James Jeeb Jerome Borsboom Josh Kaustubh Raste Karthick Jeyapal Limin Wang Linjie Fu Steven Liu Li Zhong Martin Storsjo Martin Vignali Matthieu Bouron Michael Jacob Trimble wm4 Paul Philip Peter Ruiling Song John Stebbins Mark Thilo Timo Ting Fu Tobias Clément Vishwanath Dixit Vittorio Guo Yejun Shiyou Yin Zane Zhao > and how long will it take you ? Sorry, I got quite sick, like many people who came from Demuxed. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming GA vote
Hey, On Wed, 1 Nov 2023, at 18:19, Michael Niedermayer wrote: > Please provide the list of email addresses OR peoples names who > should have received a mail for voting I don't think listing emails on this mailing list is a good idea, or even legal (GDPR, for example). And the old lists (+ the scripts) only give emails, and not names. So I'll need to remap that manually to have the list of names. It will take a bit of time, but I'll do it. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming GA vote
On Mon, 30 Oct 2023, at 11:33, Thilo Borgmann via ffmpeg-devel wrote: > Am 30.10.23 um 09:18 schrieb Jean-Baptiste Kempf: >> Hello, >> >> On Sun, 29 Oct 2023, at 10:33, Anton Khirnov wrote: >>> vote question (unchanged): >>> How do we update the list of active members of the general assembly? >>> >>> Available answers: >>> * twice a year (1st Jan & 1st July, 0:00 UTC); >>>as an exception, the list will also be updated immediately after this >>>vote >>>(suggested at VDD, added time and the exceptional update clause) >>> * before each vote >>>(suggested at VDD) >>> * never (keep the 2020 version) >>>(suggested at VDD) >>> * keep everyone who had vote rights but add active developers >>>each 1st Jan and 1st July, 0:00 UTC; >>>as an exception, the list will also be updated immediately after this >>>vote >>>(suggested by Michael on the ML, clarified date and time, added the >>>exceptional update clause) >>> >>> If nobody has significant objections, we will go with the above for the >>> actual vote tomorrow. >> >> This has been launched. >> You should be able to vote until Sunday 5th Nov, 23:59 > > Sure you did not just create the vote but started it already as well? > I should be part of the GA but didn't get a mail... I'm quite sure, since some people have already started voting. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [ANNOUNCE] upcoming GA vote
Hello, On Sun, 29 Oct 2023, at 10:33, Anton Khirnov wrote: > vote question (unchanged): > How do we update the list of active members of the general assembly? > > Available answers: > * twice a year (1st Jan & 1st July, 0:00 UTC); > as an exception, the list will also be updated immediately after this > vote > (suggested at VDD, added time and the exceptional update clause) > * before each vote > (suggested at VDD) > * never (keep the 2020 version) > (suggested at VDD) > * keep everyone who had vote rights but add active developers > each 1st Jan and 1st July, 0:00 UTC; > as an exception, the list will also be updated immediately after this > vote > (suggested by Michael on the ML, clarified date and time, added the > exceptional update clause) > > If nobody has significant objections, we will go with the above for the > actual vote tomorrow. This has been launched. You should be able to vote until Sunday 5th Nov, 23:59 -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 2/2] aacdec: correctly skip padding at the start of frames and during seeking
Hello, Does this fix #2325 #9667? jb On Mon, 30 Oct 2023, at 06:10, Lynne wrote: > Presently, our AAC decoder didn't skip any samples, unless the side data > contained skip information. > > This uses the newly added ff_decoder_skip_samples function to skip samples > on two levels: base, and additional. > Base is the inherent decoder delay. Most containers already specify it, > hence it is overwritten in that case. > Additional is any extra samples that have to be skipped, in AAC's case, > it's the delay introduced by SBR. > > Patch attached. > > > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > > Attachments: > * 0002-aacdec-correctly-skip-padding-at-the-start-of-frames.patch -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 19:46, Thilo Borgmann via ffmpeg-devel wrote: > Am 29.10.23 um 18:56 schrieb Jean-Baptiste Kempf: >> On Sun, 29 Oct 2023, at 18:20, Thilo Borgmann via ffmpeg-devel wrote: >>> In this case as well, I think you >>> should have transported your reasoning back to this thread on the ML - >> >> It's actually in this very thread on the ML about the timing and prefering >> 7.0 over 6.1. >> >> I even send a longer email to explain. > > I wonder why you didn't say that one iteration back when I asked you > where to > find it. (Your answer was "at VDD & on IRC", just not to delete too > much history > here.) > > Anyway, in this very thread (and in the Release 6.1 thread started from > Michael > before this thread of Lynne) I can see exactly 3 prior mails from you. Mail are not just from me, but about me. Quoting the mail that supposedly quotes me: "6.1 opportunity is gone. We're too late on the schedule, and noone had time to work on it, so it is wiser to target 7.0 in January" I think it's very clear about "opportunity" and "late on the schedule" and what they mean. You decided then it was not clear and "unsubstantiated", and therefore that my opinion had no value, so I had to expand on it. So, I spoke about it at VDD, several time, on IRC and it refers to me on this very mailing list. And instead of asking me to clarify, you started to say that my opinion had no value, and then attacking me. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 19:31, Nicolas George wrote: > Jean-Baptiste Kempf (12023-10-29): >> We'll have to agree to disagree. > > So you disagree that ffmpeg is not a corporate project where developers > can be forced to have fixed work hours. Interesting. IRC has logs and many people having fixed work hours are on IRC. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 19:12, Nicolas George wrote: > Jean-Baptiste Kempf (12023-10-29): >> Sorry, I can. Being on IRC is necessary, IMHO. > > Completely unacceptable and fortunately not true at all. We'll have to agree to disagree. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 18:20, Thilo Borgmann via ffmpeg-devel wrote: > In this case as well, I think you > should have transported your reasoning back to this thread on the ML - It's actually in this very thread on the ML about the timing and prefering 7.0 over 6.1. I even send a longer email to explain. > cannot blame anyone for not following live discussion like VDD or IRC. Sorry, I can. Being on IRC is necessary, IMHO. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 17:49, James Almer wrote: > On 10/29/2023 1:42 PM, Jean-Baptiste Kempf wrote: >> Hello, >> >> On Sat, 28 Oct 2023, at 18:49, Michael Niedermayer wrote: >>> noone mentioned 5.1.x and 6.0.x to me before >> >> Our last releases from our two major bracnhes, are a 5.1.3 (which is a LTS >> branch) and a 6.0.0. >> >> Both of those have not had backports and releases of all the security >> issues, nor on the major regressions found (if any). >> >> Also, if they had some commits for security reasons, we should have a >> release at least every 90 days (3 months), because this is the standard for >> the security issues reporting (after that time, the security community makes >> them public). >> And seeing the number of fuzzing fixes, this is likely important. >> >> So, yes, I think having a 5.1.4 and 6.0.1 with the security fixes is of the >> utmost importance. >> >>> It was just that jb told me >>> "6.1 opportunity is gone. >>> We're too late on the schedule, and noone had time to work on it, so >>> it is wiser to target 7.0 in January" >> >> Yes, we said we would make a new major version for January (which will slip >> in February, as usual :D). >> So, doing a 6.1.0 now, while 7.0 is not far away, might be a lot of work and >> it might not worth it. >> Notably since at the time of 7.0, there might be not enough new things to >> cut a release. >> >> So I'm not against a release for 6.1 at all, but I believe focusing on minor >> releases for security and on 7.0 with the next major deprecations is more >> important. >> If we can do all of those, and keep more or less the timing for 7.0, please >> be my guest for 6.1. > > Lynne made a list of the things that should (hopefully) make it to 7.0 > for early 2024 (E.g. YUVJ removal, D3D12 hwdec, Vulkan encode, VVC, > IAMF) plus Anton's CLI scheduler work, not to mention it will feature a > major version bump and all the deprecated API removal that brings. So > even with not a lot of things, the few it will get in these few months > will be pretty big and appealing. > > 6.1 doesn't need to be supported for too long, but it's a good release > to have as it will feature a year worth of development while being 6.0 > ABI compatible, for those distros that care. Excellent then. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 17:40, Nicolas George wrote: > Jean-Baptiste Kempf (12023-10-29): >> Because instead of doing the polite and normal thing which would be: > > Politeness or not does not make it a personal attack. Moving goalposts > much? Being not polite to someone is a personal attack. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
Hello, On Sat, 28 Oct 2023, at 18:49, Michael Niedermayer wrote: > noone mentioned 5.1.x and 6.0.x to me before Our last releases from our two major bracnhes, are a 5.1.3 (which is a LTS branch) and a 6.0.0. Both of those have not had backports and releases of all the security issues, nor on the major regressions found (if any). Also, if they had some commits for security reasons, we should have a release at least every 90 days (3 months), because this is the standard for the security issues reporting (after that time, the security community makes them public). And seeing the number of fuzzing fixes, this is likely important. So, yes, I think having a 5.1.4 and 6.0.1 with the security fixes is of the utmost importance. > It was just that jb told me > "6.1 opportunity is gone. > We're too late on the schedule, and noone had time to work on it, so > it is wiser to target 7.0 in January" Yes, we said we would make a new major version for January (which will slip in February, as usual :D). So, doing a 6.1.0 now, while 7.0 is not far away, might be a lot of work and it might not worth it. Notably since at the time of 7.0, there might be not enough new things to cut a release. So I'm not against a release for 6.1 at all, but I believe focusing on minor releases for security and on 7.0 with the next major deprecations is more important. If we can do all of those, and keep more or less the timing for 7.0, please be my guest for 6.1. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 15:17, Nicolas George wrote: > Jean-Baptiste Kempf (12023-10-29): >> > Unsubstantiated opinion, let us ignore it. >> Again, a personal attack, from you. > > YOU are not an OPINION, so, no, this is not a personal attack, Because instead of doing the polite and normal thing which would be: "jb, I did not hear your opinion, can you restate it?" you said "jb, I did not hear his opinion, he should be ignored". -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 16:10, Thilo Borgmann via ffmpeg-devel wrote: > Where? I don't see you saying that in this thread. > If you said so at VDD, that's not many times. Explained three times at VDD and several time on IRC. > Not being at where you say s.th. does not imply anything and is not an > argument. Refusing to attend the developer meetups and also refusing to be on one of the major discussion media and then complaining about not receiving information is a problem in an open source community. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
On Sun, 29 Oct 2023, at 10:30, Nicolas George wrote: > Michael Niedermayer (12023-10-28): >> It was just that jb told me >> "6.1 opportunity is gone. > > Unsubstantiated opinion, let us ignore it. Not like your opinions that are always substantiated... Except I explain many times why the opportunity has passed for 6.1, but you, once again, don't listen, or refuse to be on the means where we discuss. Again, a personal attack, from you. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] AG (GA?) VOTE
On Tue, 10 Oct 2023, at 14:42, Jean-Baptiste Kempf wrote: >> There was no real prior discussion on the mailing list about this. > http://ffmpeg.org/pipermail/ffmpeg-devel/2023-September/314772.html -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] AG (GA?) VOTE
Hello, On Tue, 10 Oct 2023, at 13:56, Michael Niedermayer wrote: > a vote on the General Assembly composition was apparently initiated with > a duration of 6 days, i saw this in my inbox: > "1009 23:49 Jean-Baptiste K (3,4K) Poll: FFmpeg AG members rules" > > There was no real prior discussion on the mailing list about this. https://github.com/videolabs/libspatialaudio > There are 2 choices which are similar > (update the list before each vote and update it twice a year) > And a 3rd option that is probably not what the "opposition" wants I think > (use the 2020 version, never update) Those 3 were mentioned at VDD in the FFmpeg meeting you were in. It was also already discussed at FOSDEM this year and the previous, and people complained that I did not do that vote before. > First its neccessary to give the community a chance to discuss the GA > composition > choices, collect suggestions and then do a vote I think this was done. > Now iam quite unprepared to really suggest something as i also didnt > think about this > much or expect this vote now but at least something like > * keep everyone who had vote rights but add active developers each > jan/july > > Is a more honest choice for the "opposition" than "never update" That's an extra choice, in my opinion, and we could also have it, but it's a bit annoying that you say it now. But it's doable. Best, -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
Yo, On Fri, 22 Sep 2023, at 17:27, Paul B Mahol wrote: >> about it because i did not know anyone else who knows perl and be willing >> to help look into a not entirely trivial (for me) issue in fate server > > Do not lie, [...] Calling people liars is not really fitting our Code of Conduct. It's not the first time I remind this fact. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] VDD 2023, FFmpeg meeting notes, (23-11-2023, 4pm, Dublin)
>> General Assembly, Candidates (J-B will mail a vote): >> - BBB >> - Derek > > Quite interresting that every single developer who probably isnt going > to support > some of the significant changes proposed later disappeared from the > Previous > Candidates What are you talking about? This is just people in the room, who asked to be in the extra bucket, because they don't have the required commit numbers. It does not mean it's the complete list. >> Community Committee, Candidates (J-B will mail a vote): >> - Dave Rice >> - James >> - J-B >> - Thilo >> - Steven >> - BBB > > Iam missing carl on the list As above. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] FFmpeg release 6.1
Hello, On Thu, 21 Sep 2023, at 00:47, Kieran Kunhya wrote: >> >> also iam not sure "experimental" is the right flag for code that has >> possible security issues. People might turn experimental on not realizing >> the security aspect. >> > > We should make this clear in the docs then. +1 -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] trac backups
On Wed, 13 Sep 2023, at 01:33, Michael Niedermayer wrote: >> Who else other than you has access to the infrastructure? > > all the root admins do > but that isnt the problem, even if 100 more people had access > the only way that was noticable it seems was if someone looked I disagree. The infrastructure is un-documented, and the people accessing it are un-documented. This is a big problem. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] Changelog: Add Support hevc, vp9, av1 codec fourcclist in enhanced rtmp protocol
On Tue, 5 Sep 2023, at 03:17, Steven Liu wrote: > Signed-off-by: Steven Liu > --- > Changelog | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Changelog b/Changelog > index 6c2622dc4e..0cfcecfb93 100644 > --- a/Changelog > +++ b/Changelog > @@ -31,6 +31,7 @@ version : > - Support HEVC,VP9,AV1 codec in enhanced flv format > - apsnr and asisdr audio filters > - OSQ demuxer and decoder > +- Support HEVC,VP9,AV1 codec fourcclist in enhanced rtmp protocol Lgtm -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 2/2] doc/developer: Code pushed without patches on ffmpeg-devel must be announced on the ML
On Fri, 25 Aug 2023, at 18:27, Nicolas George wrote: > Jean-Baptiste Kempf (12023-08-25): >> So that means mandatory sending to the mailing list :) > > And change the name to libav? Trolling is not going to get you anywhere. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 2/2] doc/developer: Code pushed without patches on ffmpeg-devel must be announced on the ML
On Fri, 25 Aug 2023, at 17:34, Michael Niedermayer wrote: > On Thu, Aug 24, 2023 at 10:04:16PM +0200, Andreas Rheinhardt wrote: >> Michael Niedermayer: >> > Signed-off-by: Michael Niedermayer >> > --- >> > doc/developer.texi | 9 + >> > 1 file changed, 9 insertions(+) >> > >> > diff --git a/doc/developer.texi b/doc/developer.texi >> > index 383120daaa..1c0091fc74 100644 >> > --- a/doc/developer.texi >> > +++ b/doc/developer.texi >> > @@ -856,6 +856,15 @@ way to get everyone's patches reviewed sooner. >> > Reviews must be constructive and when rejecting a patch the reviewer must >> > explain >> > their reasons and ideally suggest an alternative approach. >> > >> > +If a change is pushed without being sent to ffmpeg-devel, the developer >> > +pushing it must annouce doing so on the ffmpeg-devel mailing list >> > immedeatly. >> > +@example >> > +forgot a semicolon in this patch, pushed a seperate fix >> > +pushed my new autograd engine and stable diffusion filter. Didnt want to >> > +go through the bikeshed if that belongs in FFmpeg, go to the GA if you >> > want >> > +it removed. Otherwise Just tell me what i should improve and ill look >> > into it. >> > +@end example >> >> This encourages pushing patches (even completely new filters) without >> sending them to the ML. > > That was not the intend but if you look at "cvslog" and ffmpeg-devel, you will > notice that there are things being pushed that have not been seen on the > ffmpeg-devel mailing list. So that means mandatory sending to the mailing list :) -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v1] avformat/rtmpproto: support fourCcList property in enhanced rtmp
Hello, On Mon, 21 Aug 2023, at 03:35, Steven Liu wrote: > Jean-Baptiste Kempf 于2023年8月20日周日 16:29写道： >> >> Hello, > Hi >> >> On Sun, 20 Aug 2023, at 06:10, Steven Liu wrote: >> > As the enhanced rtmp Extending NetConnection connect Command section >> > said, the rtmp should add a property named fourCcLive, but there should >> > only one codec can be set for the video stream in rtmp+flv, so user can >> > use the option rtmp_enhanced_flags to set the enhanced rtmp with av1, >> > hevc or vp9. >> >> Technically, the protocol allows any type of FourCC, no? > The protocol should allows any type of FourCC, i saw there have three > codecs in the example["av01", "vp09", "hvc1"]. My question is then why have 0,1,2,3 and not a fourcc then? Or does this question make no sense on the protocol level? -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] VDD conference invitation - Dublin 22-24 Sept 2023
On Sun, 20 Aug 2023, at 15:01, Tomas Härdin wrote: > Will it be possible to attend via Jitsi Meet or similar? For the FFmpeg meeting, of course. For the rest, I dunno yet. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v1] avformat/rtmpproto: support fourCcList property in enhanced rtmp
Hello, On Sun, 20 Aug 2023, at 06:10, Steven Liu wrote: > As the enhanced rtmp Extending NetConnection connect Command section > said, the rtmp should add a property named fourCcLive, but there should > only one codec can be set for the video stream in rtmp+flv, so user can > use the option rtmp_enhanced_flags to set the enhanced rtmp with av1, > hevc or vp9. Technically, the protocol allows any type of FourCC, no? jb ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-devel] VDD conference invitation - Dublin 22-24 Sept 2023
Hello FFfolks, I'm glad to invite you to VDD 2023 in Dublin, at the end of next month. I wish I could have invited you to Iceland, but it proved too difficult to organize over there. I'll do better next year, I promise :) What is it? --- The format of the conference is going to be similar to the previous years: - Friday 22nd, community day in Dublin, where we'll do some activities (will be communicated later) and then drinks on the evening - Saturday 23rd, start of the actual conferences, with talks by members from our communities on very technical subjects, in the morning, until lunch. - Saturday afternoon, technical sessions (VLC and FFmpeg in // probably) in an unconference manner. - Saturday night, a dinner in Dublin. - Sunday morning, lightning talks, for the early people - Sunday morning and afternoon, workshops and technical sessions (x264, dav1d, VLC mobile, placebo...) We will be at Trinity College, in Dublin. Who is welcome to join? --- Everyone that cares about any open source multimedia project, VLC, FFmpeg, x264, dav1d, placebo, mpv, kodi, phonon, x265... is welcome. If you are a GSoC student, you should also come. If you are just a fan and a user, you shall probably come. How do I register? -- You can register here: https://framaforms.org/vdd-2023-1691924544 Registration will close at the end of this month. How do I get reimbursed? -- If you are an active member of one of our open source communities, VideoLAN will cover your costs, meaning Hotels + Flight/Train/Boat to Dublin. If you are part of the VideoLAN non-profit, if you are part of the FFmpeg GA, you are invited. If you have commits on git.ffmpeg.org or code.videolan.org, you are invited. If you are a GSoC student, your costs will be covered too. If you are unsure about if you are eligible, you should mail me... What should I do now? - 1. Register 2. Book your flights. 3. Help us. For your flights, please try and find flights that are not too expensive, if VideoLAN cover your costs. We have no sponsors this year, so be mindful about our costs. (Today flights from Berlin can be found easily at 100-150e, and 200e from Paris. Coming from SF can be found at 800e) How can I help? --- Propose a talk, from 5min to 30min. Help the organisation. Bring smile and join to VDD. Questions? For any question, please mail me :) Thanks and see you soon. jbk Remarks: - this is a technical conference. If you are not a technical person, this will probably bore you. - VideoLAN CoC applies to VDD. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] What is FFmpeg and what should it be
On Thu, 10 Aug 2023, at 14:39, Nicolas George wrote: >> livelihood, and millions for their computer use" in response to NG's >> argument >> that FFmpeg should be turned into a fun experimental research project, and >> that people who wanted to keep FFmpeg what he calls a "serious open-source >> trademark" should just fork. > > Not “turned into”, but restored. FFmpeg *was* a fun experimental > research project, and it was the reason it became so great: developers > then could try things that were not tried elsewhere, they were free to > take risks, to make mistakes and fix them. > > And the, during the second half of 2000s decade, people like you took > more and more place, people who demanded absolute stability and rejected > all risks whatsoever. You mean, like every project that starts small and gets bigger and reaches maturity stage? > But what you refuse to realize is that it is only an opinion, shared by > you and a few “people”, backed by zero actual arguments. The issue here, is that you are in minority about your vision of FFmpeg, as a fun and experimental project. You screaming louder does not change this reality. If you disagree, just get a vote from all people who have commit access, and you will see. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] What is FFmpeg and what should it be
On Wed, 2 Aug 2023, at 16:20, Michael Niedermayer wrote: > There are multiple problems but the real problem is that > How many people discuss an SDR API ? (0) > How many people propose an SDR API ? (0) Did you ask people to do that? > How many people say what they want an SDR API to be able to do ? (0) > Again we had 0 that is ZERO discussions about an SDR API. > where does it start ? a hw enumerate, a soapy device, a void * > representing a SDR data stream from something like soapy Just enough to integrate into AVInputFormat and libavformat + libavdevice. Propose something and you will get more feedback Then, the API will evolve into something better in v2. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] What is FFmpeg and what should it be
On Wed, 2 Aug 2023, at 14:55, Michael Niedermayer wrote: > the code already is in a seperate repository. And is basically isolated > in a single demuxer and single input device. But it's not a library in that repository, like swscale, swresample or similar libraries. If it was, with an API, it would be trivial to add support to this optional library as an FFmpeg module, and noone who complain. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v10 0/6] Support enhanced flv in FFmpeg
Please merge. On Thu, 1 Jun 2023, at 12:29, Jean-Baptiste Kempf wrote: > Hello, > > On Thu, 1 Jun 2023, at 02:02, Steven Liu wrote: >> Neal Gompa 于2023年5月31日周三 13:47写道： >>> >>> On Mon, May 15, 2023 at 10:41 PM Neal Gompa wrote: >>> > >>> > On Mon, May 15, 2023 at 4:32 AM Steven Liu wrote: >>> > > >>> > > Reference file: >>> > > https://github.com/veovera/enhanced-rtmp/blob/main/enhanced-rtmp-v1.pdf >>> > > The Enhanced flv has been supported by OBS, Simple Realtime Server, >>> > > mpegts.js. >>> > > you can publish hevc, av1 or vp9 codec stream to Youtube over rtmp. >>> > > The enhanced flv documentation contributors include >>> > > Jean-Baptiste Kempf (FFmpeg, VideoLAN). >>> > > So this should be support by ffmpeg too. >>> > > >>> > > v8: >>> > > Support vp9 codec according to enhanced flv. >>> > > Support PacketTypeCodedFrames type for hevc in flv. >>> > > v9: >>> > > Add dependency codec object files for flvenc in Makefile. >>> > > Move the hevc,av1,vp9 codec out of FF_COMPLIANCE_UNOFFICIAL. >>> > > >>> > > v10: >>> > > modify first patch comment like the others before commit. >>> > > exheader mode should only happened in video stream this patchset. >>> > > >>> > > Steven Liu (6): >>> > > avformat/flvenc: support mux hevc in enhanced flv >>> > > avformat/flvdec: support demux hevc in enhanced flv >>> > > avformat/flvenc: support mux av1 in enhanced flv >>> > > avformat/flvdec: support demux av1 in enhanced flv >>> > > avformat/flvenc: support mux vp9 in enhanced flv >>> > > avformat/flvdec: support demux vp9 in enhanced flv >>> > > >>> > > libavformat/Makefile | 2 +- >>> > > libavformat/flv.h| 15 + >>> > > libavformat/flvdec.c | 73 +++- >>> > > libavformat/flvenc.c | 58 +++++-- >>> > > 4 files changed, 130 insertions(+), 18 deletions(-) >>> > > >>> > >>> > This version works for me. Thanks for this work! >>> > >>> > Tested-by: Neal Gompa >>> > Reviewed-by: Neal Gompa >>> > >>> >>> Is this patch set going to get pushed to master anytime soon? >> >> Hi Neal, >> >> Waiting for j-b check about the Enhanced-FLV status, i cannot sure if >> this patch can be pushed now. > > I've just re-asked what is the final status of the spec. > > If you cannot wait, use experimental flags. > > jb > -- > Jean-Baptiste Kempf - President > +33 672 704 734 > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [RFC] Release 6.1
Heya, On Thu, 6 Jul 2023, at 18:04, Lynne wrote: > It's been a while since we've had a release, and we've had > a lot of new features in. > We did say we would make releases more often, and I think > it's about time we have a new release. It's a good idea. > Anything anyone wants to have merged or should we branch > off 6.1 in a few days? By experience, it requires a bit more than a few days... :D jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] doc/developer: Make tests a requirement
Hello, On Tue, 4 Jul 2023, at 01:00, Michael Niedermayer wrote: > Suggested-by: Anton > > Signed-off-by: Michael Niedermayer > --- > doc/developer.texi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/doc/developer.texi b/doc/developer.texi > index 0c2f2cd7d1..67f7f78e86 100644 > --- a/doc/developer.texi > +++ b/doc/developer.texi > @@ -806,7 +806,7 @@ improves readability. > > @item > Consider adding a regression test for your code. All new modules > -should be covered by tests. That includes demuxers, muxers, decoders, > encoders > +must be covered by tests. That includes demuxers, muxers, decoders, encoders > filters, bitstream filters, parsers. If its not possible to do that, add > an explanation why to your patchset, its ok to not test if theres a reason. +1 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v6 0/1] avformat: add Software Defined Radio support
On Sun, 2 Jul 2023, at 18:07, Nicolas George wrote: > Jean-Baptiste Kempf (12023-07-02): >> Absolutely not. >> You are the only one who believes that. > > Except for the person who created FFmpeg in the first place. And probably > other people too. Having talked to Fabrice lately, I didn’t get that this was his vision at all. > illustrate the shortsightedness of people who want FFmpeg to be a > Serious OpenSource Project TM, it's called The Goose that Laid the > Golden Eggs, I assume everybody knows how it ends. I think you are dreaming and I completely disagree with you. But that’s not the question here at all. The question is “what does the majority of the developers want? What does the majority of the users want?” Unfortunately, for both questions, I think you are in the minority. But if you want, we can call an AG vote. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v6 0/1] avformat: add Software Defined Radio support
On Sun, 2 Jul 2023, at 11:58, Nicolas George wrote: >> Even if it is disabled by default, git master isn't a playground for >> personal projects. > > Yes it is. Absolutely not. You are the only one who believes that. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v6 0/1] avformat: add Software Defined Radio support
On Fri, 30 Jun 2023, at 16:08, Michael Niedermayer wrote: > Also as said previously, If there is at least a 2nd developer working > on this then we could & should move this to a seperate libraray (libavradio) Why wait for a 2nd dev? -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v2] avformat: add Software Defined Radio support
Hello, On Thu, 29 Jun 2023, at 09:14, Nicolas George wrote: >>The reason why XML parsing shouldn't be >> implemented in FFmpeg isn't just because it is difficult but because: >> >> * it is out of scope > > It is necessary. Says you. This is not an opinion that seems to be the majority. > Precisely. Nothing is “important” in absolute?. Things are only > important with regard to a goal. > > My goal is to have fun, and for that goal, API and ABI stability are not > important. To have fun, I still need the project to exist, so I will > spend time on these issues, that is all. Again YOUR goal. It might not be the majority of the community. We can do an AG vote, if you want. > go fork yourself. This is out of line, IMHO. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 6/6] doc/developer: Require new modules to include tests
On Sun, 18 Jun 2023, at 23:50, Michael Niedermayer wrote: > doc/developer.texi | 5 - > 1 file changed, 4 insertions(+), 1 deletion(-) +1 -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] avcodec: add VMX1 decoder
On Thu, 8 Jun 2023, at 19:39, Paul B Mahol wrote: > Attached. Missing version bumping? -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v10 0/6] Support enhanced flv in FFmpeg
Hello, On Thu, 1 Jun 2023, at 02:02, Steven Liu wrote: > Neal Gompa 于2023年5月31日周三 13:47写道： >> >> On Mon, May 15, 2023 at 10:41 PM Neal Gompa wrote: >> > >> > On Mon, May 15, 2023 at 4:32 AM Steven Liu wrote: >> > > >> > > Reference file: >> > > https://github.com/veovera/enhanced-rtmp/blob/main/enhanced-rtmp-v1.pdf >> > > The Enhanced flv has been supported by OBS, Simple Realtime Server, >> > > mpegts.js. >> > > you can publish hevc, av1 or vp9 codec stream to Youtube over rtmp. >> > > The enhanced flv documentation contributors include >> > > Jean-Baptiste Kempf (FFmpeg, VideoLAN). >> > > So this should be support by ffmpeg too. >> > > >> > > v8: >> > > Support vp9 codec according to enhanced flv. >> > > Support PacketTypeCodedFrames type for hevc in flv. >> > > v9: >> > > Add dependency codec object files for flvenc in Makefile. >> > > Move the hevc,av1,vp9 codec out of FF_COMPLIANCE_UNOFFICIAL. >> > > >> > > v10: >> > > modify first patch comment like the others before commit. >> > > exheader mode should only happened in video stream this patchset. >> > > >> > > Steven Liu (6): >> > > avformat/flvenc: support mux hevc in enhanced flv >> > > avformat/flvdec: support demux hevc in enhanced flv >> > > avformat/flvenc: support mux av1 in enhanced flv >> > > avformat/flvdec: support demux av1 in enhanced flv >> > > avformat/flvenc: support mux vp9 in enhanced flv >> > > avformat/flvdec: support demux vp9 in enhanced flv >> > > >> > > libavformat/Makefile | 2 +- >> > > libavformat/flv.h| 15 + >> > > libavformat/flvdec.c | 73 +++- >> > > libavformat/flvenc.c | 58 +-- >> > > 4 files changed, 130 insertions(+), 18 deletions(-) >> > > >> > >> > This version works for me. Thanks for this work! >> > >> > Tested-by: Neal Gompa >> > Reviewed-by: Neal Gompa >> > >> >> Is this patch set going to get pushed to master anytime soon? > > Hi Neal, > > Waiting for j-b check about the Enhanced-FLV status, i cannot sure if > this patch can be pushed now. I've just re-asked what is the final status of the spec. If you cannot wait, use experimental flags. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v8 3/6] avformat/flvenc: support mux av1 in enhanced flv
On Fri, 12 May 2023, at 05:35, Neal Gompa wrote:
> On Thu, May 11, 2023 at 12:26 PM Jean-Baptiste Kempf
> wrote:
>>
>>
>>
>> On Thu, 11 May 2023, at 18:21, Neal Gompa wrote:
>> > On Wed, May 10, 2023 at 9:40 PM Steven Liu wrote:
>> >>
>> >> Neal Gompa 于2023年5月11日周四 09:31写道：
>> >> >
>> >> > On Wed, May 10, 2023 at 7:13 AM Steven Liu
>> >> > wrote:
>> >> > >
>> >> > > Neal Gompa 于2023年5月10日周三 19:05写道：
>> >> > > >
>> >> > > > On Tue, May 9, 2023 at 6:48 AM Gyan Doshi wrote:
>> >> > > > >
>> >> > > > >
>> >> > > > >
>> >> > > > > On 2023-05-09 04:05 pm, Neal Gompa wrote:
>> >> > > > > > On Tue, May 9, 2023 at 12:14 AM Gyan Doshi
>> >> > > > > > wrote:
>> >> > > > > >>
>> >> > > > > >>
>> >> > > > > >> On 2023-05-09 08:11 am, Neal Gompa wrote:
>> >> > > > > >>> On Mon, May 8, 2023 at 9:55 PM Steven Liu
>> >> > > > > >>> wrote:
>> >> > > > > >>>> Neal Gompa 于2023年5月9日周二 07:08写道：
>> >> > > > > >>>>> On Thu, Apr 13, 2023 at 5:45 AM Steven Liu
>> >> > > > > >>>>> wrote:
>> >> > > > > >>>>>> Signed-off-by: Steven Liu
>> >> > > > > >>>>>> ---
>> >> > > > > >>>>>>libavformat/flvenc.c | 25 -
>> >> > > > > >>>>>>1 file changed, 20 insertions(+), 5 deletions(-)
>> >> > > > > >>>>>>
>> >> > > > > >>>>>> diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
>> >> > > > > >>>>>> index 57a26245ff..7b43ecaefa 100644
>> >> > > > > >>>>>> --- a/libavformat/flvenc.c
>> >> > > > > >>>>>> +++ b/libavformat/flvenc.c
>> >> > > > > >>>>>> @@ -28,6 +28,7 @@
>> >> > > > > >>>>>>#include "libavcodec/mpeg4audio.h"
>> >> > > > > >>>>>>#include "avio.h"
>> >> > > > > >>>>>>#include "avc.h"
>> >> > > > > >>>>>> +#include "av1.h"
>> >> > > > > >>>>>>#include "hevc.h"
>> >> > > > > >>>>>>#include "avformat.h"
>> >> > > > > >>>>>>#include "flv.h"
>> >> > > > > >>>>>> @@ -48,6 +49,7 @@ static const AVCodecTag
>> >> > > > > >>>>>> flv_video_codec_ids[] = {
>> >> > > > > >>>>>>{ AV_CODEC_ID_VP6A, FLV_CODECID_VP6A },
>> >> > > > > >>>>>>{ AV_CODEC_ID_H264, FLV_CODECID_H264 },
>> >> > > > > >>>>>>{ AV_CODEC_ID_HEVC, MKBETAG('h', 'v', 'c', '1')
>> >> > > > > >>>>>> },
>> >> > > > > >>>>>> +{ AV_CODEC_ID_AV1, MKBETAG('a', 'v', '0', '1') },
>> >> > > > > >>>>>>{ AV_CODEC_ID_NONE, 0 }
>> >> > > > > >>>>>>};
>> >> > > > > >>>>>>
>> >> > > > > >>>>>> @@ -494,7 +496,8 @@ static void
>> >> > > > > >>>>>> flv_write_codec_header(AVFormatContext* s,
>> >> > > > > >>>>>> AVCodecParameters* par, i
>> >> > > > > >>>>>>FLVContext *flv = s->priv_data;
>> >> > > > > >>>>>>
>> >> > > > > >>>>>>if (par->codec_id == AV_CODEC_ID_AAC ||
>> >> > > > > >>>>>> par->codec_id == AV_CODEC_ID_H264
>> >> > > > > >>>>>> -|| par->codec_id == AV_CODEC_ID_MPEG4 ||
>> >> > > >
Re: [FFmpeg-devel] [PATCH v8 3/6] avformat/flvenc: support mux av1 in enhanced flv
t; > > > >>>>>> par->codec_id == AV_CODEC_ID_MPEG4 || par->codec_id ==
>> > > > > >>>>>> AV_CODEC_ID_HEVC)
>> > > > > >>>>>> +else if (par->codec_id == AV_CODEC_ID_H264 ||
>> > > > > >>>>>> par->codec_id == AV_CODEC_ID_MPEG4 ||
>> > > > > >>>>>> + par->codec_id == AV_CODEC_ID_HEVC ||
>> > > > > >>>>>> par->codec_id == AV_CODEC_ID_AV1)
>> > > > > >>>>>>flags_size = 5;
>> > > > > >>>>>>else
>> > > > > >>>>>>flags_size = 1;
>> > > > > >>>>>>
>> > > > > >>>>>>if (par->codec_id == AV_CODEC_ID_AAC || par->codec_id
>> > > > > >>>>>> == AV_CODEC_ID_H264
>> > > > > >>>>>> -|| par->codec_id == AV_CODEC_ID_MPEG4 ||
>> > > > > >>>>>> par->codec_id == AV_CODEC_ID_HEVC) {
>> > > > > >>>>>> +|| par->codec_id == AV_CODEC_ID_MPEG4 ||
>> > > > > >>>>>> par->codec_id == AV_CODEC_ID_HEVC
>> > > > > >>>>>> +|| par->codec_id == AV_CODEC_ID_AV1) {
>> > > > > >>>>>>size_t side_size;
>> > > > > >>>>>>uint8_t *side = av_packet_get_side_data(pkt,
>> > > > > >>>>>> AV_PKT_DATA_NEW_EXTRADATA, _size);
>> > > > > >>>>>>if (side && side_size > 0 && (side_size !=
>> > > > > >>>>>> par->extradata_size || memcmp(side, par->extradata,
>> > > > > >>>>>> side_size))) {
>> > > > > >>>>>> @@ -874,7 +885,8 @@ static int
>> > > > > >>>>>> flv_write_packet(AVFormatContext *s, AVPacket *pkt)
>> > > > > >>>>>> "Packets are not in the proper order with
>> > > > > >>>>>> respect to DTS\n");
>> > > > > >>>>>>return AVERROR(EINVAL);
>> > > > > >>>>>>}
>> > > > > >>>>>> -if (par->codec_id == AV_CODEC_ID_H264 || par->codec_id
>> > > > > >>>>>> == AV_CODEC_ID_MPEG4 || par->codec_id == AV_CODEC_ID_HEVC) {
>> > > > > >>>>>> +if (par->codec_id == AV_CODEC_ID_H264 || par->codec_id
>> > > > > >>>>>> == AV_CODEC_ID_MPEG4 ||
>> > > > > >>>>>> +par->codec_id == AV_CODEC_ID_HEVC || par->codec_id
>> > > > > >>>>>> == AV_CODEC_ID_AV1) {
>> > > > > >>>>>>if (pkt->pts == AV_NOPTS_VALUE) {
>> > > > > >>>>>>av_log(s, AV_LOG_ERROR, "Packet is missing
>> > > > > >>>>>> PTS\n");
>> > > > > >>>>>>return AVERROR(EINVAL);
>> > > > > >>>>>> @@ -987,6 +999,9 @@ static int
>> > > > > >>>>>> flv_write_packet(AVFormatContext *s, AVPacket *pkt)
>> > > > > >>>>>>if (par->codec_id == AV_CODEC_ID_HEVC) {
>> > > > > >>>>>>avio_w8(pb, FLV_IS_EX_HEADER |
>> > > > > >>>>>> PacketTypeCodedFramesX); // ExVideoTagHeader mode with
>> > > > > >>>>>> PacketTypeCodedFramesX
>> > > > > >>>>>>avio_write(pb, "hvc1", 4);
>> > > > > >>>>>> +} else if (par->codec_id == AV_CODEC_ID_AV1) {
>> > > > > >>>>>> +avio_w8(pb, FLV_IS_EX_HEADER |
>> > > > > >>>>>> PacketTypeCodedFrames);
>> > > > > >>>>>> +avio_write(pb, "av01", 4);
>> > > > > >>>>>>} else {
>> > > > > >>>>>>avio_w8(pb, flags);
>> > > > > >>>>>>}
>> > > > > >>>>>> --
>> > > > > >>>>>> 2.40.0
>> > > > > >>>>>>
>> > > > > >>>>> I tested this by applying the patches on top of ffmpeg 6.0 and
>> > > > > >>>>> it
>> > > > > >>>>> doesn't seem to work:
>> > > > > >>>>>
>> > > > > >>>>> libavutil 58. 2.100 / 58. 2.100
>> > > > > >>>>> libavcodec 60. 3.100 / 60. 3.100
>> > > > > >>>>> libavformat60. 3.100 / 60. 3.100
>> > > > > >>>>> libavdevice60. 1.100 / 60. 1.100
>> > > > > >>>>> libavfilter 9. 3.100 / 9. 3.100
>> > > > > >>>>> libswscale 7. 1.100 / 7. 1.100
>> > > > > >>>>> libswresample 4. 10.100 / 4. 10.100
>> > > > > >>>>> libpostproc57. 1.100 / 57. 1.100
>> > > > > >>>>> [libdav1d @ 0x55c9ea8cae80] libdav1d 1.1.0
>> > > > > >>>>> Input #0, matroska,webm, from '2023-05-08 18-52-42.mkv':
>> > > > > >>>>> Metadata:
>> > > > > >>>>> ENCODER : Lavf60.3.100
>> > > > > >>>>> Duration: 00:02:00.53, start: 0.00, bitrate: 1155 kb/s
>> > > > > >>>>> Stream #0:0: Video: av1 (Main), yuv420p(tv, bt709),
>> > > > > >>>>> 1280x720, 30
>> > > > > >>>>> fps, 30 tbr, 1k tbn
>> > > > > >>>>> Metadata:
>> > > > > >>>>> DURATION: 00:02:00.53300
>> > > > > >>>>> Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp
>> > > > > >>>>> Metadata:
>> > > > > >>>>> title : Track1
>> > > > > >>>>> DURATION: 00:02:00.53300
>> > > > > >>>>> [flv @ 0x55c9ea936140] Codec av1 is not supported in the
>> > > > > >>>>> official FLV
>> > > > > >>>>> specification,
>> > > > > >>>>> [flv @ 0x55c9ea936140] use vstrict=-1 / -strict -1 to use it
>> > > > > >>>>> anyway.
>> > > > > >>>> Pay attention this warning message.
>> > > > > >>>>
>> > > > > >>>>> [out#0/flv @ 0x55c9ea8cda80] Could not write header (incorrect
>> > > > > >>>>> codec
>> > > > > >>>>> parameters ?): Invalid argument
>> > > > > >>>>> [aost#0:1/copy @ 0x55c9ea97ae00] Error initializing output
>> > > > > >>>>> stream:
>> > > > > >>>>> Stream mapping:
>> > > > > >>>>> Stream #0:0 -> #0:0 (copy)
>> > > > > >>>>> Stream #0:1 -> #0:1 (copy)
>> > > > > >>>>> Last message repeated 1 times
>> > > > > >>> Well, this is my command:
>> > > > > >>>
>> > > > > >>> $ ffmpeg -i "input.mkv" -vcodec copy -acodec copy "output.flv"
>> > > > > >>>
>> > > > > >>> What should I be doing instead?
>> > > > > >> ffmpeg -i "input.mkv" -vcodec copy -acodec copy -strict -1
>> > > > > >> "output.flv"
>> > > > > >>
>> > > > > > That defeats the point of this patch. This patch adds proper
>> > > > > > support
>> > > > > > for AV1 to the FLV code, so it should not need that.
>> > > > >
>> > > > > This patch does not add HEVC or AV1 support to the FLV
>> > > > > *specification*,
>> > > > > hence the guard.
>> > > > >
>> > > >
>> > > > The thing is, this patch series is about implementing support for the
>> > > > enhanced FLV specification.
>> > > No, That documentation is not flv official specification, it just a
>> > > document.
>> >
>> > Frankly, so was the original one. The new specification is being
>> > stewarded by a group that has the current owner of the RTMP spec as a
>> > member (Veriskope).
>> >
>> > RTMP was never IETF or ISO standardized, and neither was FLV. F4V was
>> > derived from MP4/MOV, but that's not what RTMP uses.
>>
>> IIRC, RTMP and FLV official specification is released by Adobe, not
>> veovera, right?
>>
>
> Not anymore. Adobe handed it over to Veriskope, and Veriskope seems to
> have done new work in the Veovera group alongside Adobe, OBS,
> VideoLAN, XSplit, and others.
This is correct. Veriskope manages the Flash Server and therefore, de facto,
the flv spec.
Currently, the issue is that this is not 100% standardized. Until it's
official, it should be behind a flag.
After that, sure.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] lavc/aarch64: new optimization for 8-bit hevc_pel_uni_w_pixels, qpel_uni_w_h, qpel_uni_w_v, qpel_uni_w_hv and qpel_h
Hello, Just 2 questions: - could you split this patch into several (3,4 or 5) - are all those functions checked by chekasm? Thanks, jb On Sun, 30 Apr 2023, at 10:57, myais wrote: > Hi, > This is a patch for the aarch64, which completes the neon versions of > the hevc_pel_uni_w_pixels, qpel_uni_w_h, qpel_uni_w_v, qpel_uni_w_hv > interfaces. > > put_hevc_pel_uni_w_pixels4_8_c: 54.3 > put_hevc_pel_uni_w_pixels4_8_neon: 24.1 > put_hevc_pel_uni_w_pixels6_8_c: 105.3 > put_hevc_pel_uni_w_pixels6_8_neon: 53.1 > put_hevc_pel_uni_w_pixels8_8_c: 176.6 > put_hevc_pel_uni_w_pixels8_8_neon: 63.8 > put_hevc_pel_uni_w_pixels12_8_c: 391.1 > put_hevc_pel_uni_w_pixels12_8_neon: 193.3 > put_hevc_pel_uni_w_pixels16_8_c: 688.1 > put_hevc_pel_uni_w_pixels16_8_neon: 226.1 > put_hevc_pel_uni_w_pixels24_8_c: 1542.3 > put_hevc_pel_uni_w_pixels24_8_neon: 536.8 > put_hevc_pel_uni_w_pixels32_8_c: 2753.1 > put_hevc_pel_uni_w_pixels32_8_neon: 875.8 > put_hevc_pel_uni_w_pixels48_8_c: 6251.1 > put_hevc_pel_uni_w_pixels48_8_neon: 1966.1 > put_hevc_pel_uni_w_pixels64_8_c: 11047.1 > put_hevc_pel_uni_w_pixels64_8_neon: 3449.8 > > put_hevc_qpel_uni_w_h4_8_c: 156.6 > put_hevc_qpel_uni_w_h4_8_neon: 44.6 > put_hevc_qpel_uni_w_h6_8_c: 324.6 > put_hevc_qpel_uni_w_h6_8_neon: 103.1 > put_hevc_qpel_uni_w_h8_8_c: 549.3 > put_hevc_qpel_uni_w_h8_8_neon: 138.6 > put_hevc_qpel_uni_w_h12_8_c: 1240.3 > put_hevc_qpel_uni_w_h12_8_neon: 277.3 > put_hevc_qpel_uni_w_h16_8_c: 2161.8 > put_hevc_qpel_uni_w_h16_8_neon: 394.1 > put_hevc_qpel_uni_w_h24_8_c: 4874.8 > put_hevc_qpel_uni_w_h24_8_neon: 972.6 > put_hevc_qpel_uni_w_h32_8_c: 8517.8 > put_hevc_qpel_uni_w_h32_8_neon: 1517.3 > put_hevc_qpel_uni_w_h48_8_c: 19856.1 > put_hevc_qpel_uni_w_h48_8_neon: 3429.8 > put_hevc_qpel_uni_w_h64_8_c: 35159.3 > put_hevc_qpel_uni_w_h64_8_neon: 6018.1 > > put_hevc_qpel_uni_w_v4_8_c: 180.6 > put_hevc_qpel_uni_w_v4_8_neon: 63.8 > put_hevc_qpel_uni_w_v6_8_c: 318.6 > put_hevc_qpel_uni_w_v6_8_neon: 117.8 > put_hevc_qpel_uni_w_v8_8_c: 547.6 > put_hevc_qpel_uni_w_v8_8_neon: 132.1 > put_hevc_qpel_uni_w_v12_8_c: 1202.8 > put_hevc_qpel_uni_w_v12_8_neon: 350.1 > put_hevc_qpel_uni_w_v16_8_c: 2109.6 > put_hevc_qpel_uni_w_v16_8_neon: 442.1 > put_hevc_qpel_uni_w_v24_8_c: 4748.8 > put_hevc_qpel_uni_w_v24_8_neon: 1287.1 > put_hevc_qpel_uni_w_v32_8_c: 8487.3 > put_hevc_qpel_uni_w_v32_8_neon: 1704.3 > put_hevc_qpel_uni_w_v48_8_c: 18798.8 > put_hevc_qpel_uni_w_v48_8_neon: 3790.8 > put_hevc_qpel_uni_w_v64_8_c: 35614.6 > put_hevc_qpel_uni_w_v64_8_neon: 6725.6 > > > put_hevc_qpel_uni_w_hv4_8_c: 498.8 > put_hevc_qpel_uni_w_hv4_8_neon: 139.3 > put_hevc_qpel_uni_w_hv6_8_c: 874.6 > put_hevc_qpel_uni_w_hv6_8_neon: 295.3 > put_hevc_qpel_uni_w_hv8_8_c: 1372.1 > put_hevc_qpel_uni_w_hv8_8_neon: 387.1 > put_hevc_qpel_uni_w_hv12_8_c: 2721.8 > put_hevc_qpel_uni_w_hv12_8_neon: 804.8 > put_hevc_qpel_uni_w_hv16_8_c: 4503.1 > put_hevc_qpel_uni_w_hv16_8_neon: 1038.1 > put_hevc_qpel_uni_w_hv24_8_c: 9321.8 > put_hevc_qpel_uni_w_hv24_8_neon: 2962.1 > put_hevc_qpel_uni_w_hv32_8_c: 15926.8 > put_hevc_qpel_uni_w_hv32_8_neon: 3858.6 > put_hevc_qpel_uni_w_hv48_8_c: 35051.1 > put_hevc_qpel_uni_w_hv48_8_neon: 9301.1 > put_hevc_qpel_uni_w_hv64_8_c: 61215.3 > put_hevc_qpel_uni_w_hv64_8_neon: 14920.1 > > put_hevc_qpel_uni_h4_8_c: 143.3 > put_hevc_qpel_uni_h4_8_neon: 55.3 > put_hevc_qpel_uni_h6_8_c: 304.6 > put_hevc_qpel_uni_h6_8_neon: 82.3 > put_hevc_qpel_uni_h8_8_c: 557.8 > put_hevc_qpel_uni_h8_8_neon: 99.3 > put_hevc_qpel_uni_h12_8_c: 1228.3 > put_hevc_qpel_uni_h12_8_neon: 251.6 > put_hevc_qpel_uni_h16_8_c: 2210.3 > put_hevc_qpel_uni_h16_8_neon: 324.6 > put_hevc_qpel_uni_h24_8_c: 4859.1 > put_hevc_qpel_uni_h24_8_neon: 962.3 > put_hevc_qpel_uni_h32_8_c: 8728.6 > put_hevc_qpel_uni_h32_8_neon: 1249.6 > put_hevc_qpel_uni_h48_8_c: 20346.3 > put_hevc_qpel_uni_h48_8_neon: 2824.1 > put_hevc_qpel_uni_h64_8_c: 36702.6 > put_hevc_qpel_uni_h64_8_neon: 5012.1 > > > > > Signed-off-by: myais > --- > libavcodec/aarch64/hevcdsp_init_aarch64.c | 96 + > libavcodec/aarch64/hevcdsp_qpel_neon.S| 2223 + > 2 files changed, 2319 insertions(+) > > diff --git a/libavcodec/aarch64/hevcdsp_init_aarch64.c > b/libavcodec/aarch64/hevcdsp_init_aarch64.c > index be1049a2ec..42b8e9169d 100644 > --- a/libavcodec/aarch64/hevcdsp_init_aarch64.c > +++ b/libavcodec/aarch64/hevcdsp_init_aarch64.c > @@ -128,6 +128,91 @@ void ff_hevc_put_hevc_qpel_bi_h16_8_neon(uint8_t > *_dst, ptrdiff_t _dststride, co >ptrdiff_t _srcstride, const > int16_t *src2, int height, intptr_t >mx, intptr_t my, int width); > +#define NEON8_FNPROTO(fn, args, ext) \ > +void ff_hevc_put_hevc_##fn##4_8_neon##ext args; \ > +void ff_hevc_put_hevc_##fn##6_8_neon##ext args; \ > +void ff_hevc_put_hevc_##fn##8_8_neon##ext args; \ > +void ff_hevc_put_hevc_##fn##12_8_neon##ext args; \ > +void ff_hevc_put_hevc_##fn##16_8_neon##ext args; \ > +void
Re: [FFmpeg-devel] [PATCH 5/8] lavu: add a JSON writer API (WIP)
On Mon, 1 May 2023, at 08:57, Leo Izen wrote: > On 4/29/23 14:33, Nicolas George wrote: >> Anton Khirnov (12023-04-29): >>> libavfilter is a C library with a C API. Any structured output from >>> filters should be in the form of a C object, typically a struct. I do >>> not see why are you so in love with strings, they make for terrible >>> APIs. >> >> Yes, strings are a terrible API, but our project is not only a set of >> libraries, it is also a set of command-line tools, and command-line >> tools work with strings and nothing else. >> > > This is a good argument for putting the code in fftools/ and not > libavutil, fwiw. This is also my understanding. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH v2] avformat: add MMTP parser and MMT/TLV demuxer
On Sat, 29 Apr 2023, at 07:44, SuperFashi wrote: > +#define AVERROR_INVALIDDATA (abort(), 0) Why are you aborting? -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] FFmpeg 6.0
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 will be maybe 1 week after the branch point >> once it has branched all important fixes should be backported of course > > What name shall 6.0 bear ? Why don’t you select 3 or 4 names from the list And we do a proper vote on vote.ffmpeg.org? -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 00/72] Implement support for Vulkan multiplane images and video decoding
On Mon, 20 Feb 2023, at 00:50, Neal Gompa wrote: > This is not a reasonable response, especially to someone who is > volunteering their time to develop features for a project. If it > misses 6.0, it sucks. > > My concern though is that major version bumps are supposed to be > ABI/API breaks, if this patchset doesn't land in 6.0, does that mean > it'd have to be pushed off to 7.0 if it makes public API changes? If > that's the case, I'd rather request 6.0 to be delayed to get this to land. Adding an API call does not break the API. Adding an API can, in the large percentage of cases, be done without breaking ABI (Sure, it might means that the structures are not as beautiful as they should be, but...) I don't see the issue here. In general, adding big changes should be done at the beginning of a new cycle, not at the end. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 00/72] Implement support for Vulkan multiplane images and video decoding
On Sun, 19 Feb 2023, at 17:58, Lynne wrote: > Feb 19, 2023, 17:57 by j...@videolan.org: > >> On Sun, 19 Feb 2023, at 17:53, Lynne wrote: >> >>> Otherwise, I'd like for 6.1 to be released no later than April. >>> >> >> Sure, that would be the best solution, instead of rushing code right now. >> >> And prepare proper testing for this, with numerous different workstations >> and laptops. >> > > I have properly tested it, 4 different configurations no less. > My AMD desktop with RADV, my 1080Ti with NVIDIA's beta drivers, > my Intel laptop with ANV, and my Intel laptop's 960M. Not everyone has the same machines, distributions, OSes or even FFmpeg utlization. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 00/72] Implement support for Vulkan multiplane images and video decoding
On Sun, 19 Feb 2023, at 17:53, Lynne wrote: > Otherwise, I'd like for 6.1 to be released no later than April. Sure, that would be the best solution, instead of rushing code right now. And prepare proper testing for this, with numerous different workstations and laptops. Best, -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH 00/72] Implement support for Vulkan multiplane images and video decoding
Hello, On Fri, 17 Feb 2023, at 04:43, Lynne wrote: > This small patchset mostly rewrites Vulkan to enable using multiplane images, This is not small. We're talking about thousands of lines of code; And this changes numerous h264 and hevc headers, and adds callback to the make AVHWAccel. And that is besides the full rewrite of some Vulkan files... This will take a long time to review. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Request for assistance with adding new pixel format (NV12_8L128) in FFmpeg
On Wed, 8 Feb 2023, at 10:47, Le Bao Tin Ha wrote: > Hello, you can found the explanation here: > > https://docs.kernel.org/userspace-api/media/v4l/pixfmt-yuv-planar.html > > "V4L2_PIX_FMT_NV12M_8L128 is similar to V4L2_PIX_FMT_NV12M but stores > pixels in 2D 8x128 tiles, and stores tiles linearly in memory. The > image height must be aligned to a multiple of 128. The layouts of the > luma and chroma planes are identical. > > V4L2_PIX_FMT_NV12_8L128 is similar to V4L2_PIX_FMT_NV12M_8L128 but > stores two planes in one memory." Do we really need those PIX_FMT in FFmpeg public API? -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] Hardware purchase request Apple M2
On Mon, 6 Feb 2023, at 04:17, Thilo Borgmann wrote: > Kieran agreed on hosting this one like he does for the existing M1 > machines. > There are currently two M1 machines running at Kieran's, one of which > runs FATE and the other is basically idle. > > So I propose to > > a) spend funding on buying one new M2 to run FATE at Kieran's and > b) retire the idle M1 machine and have that send to me to replace my > Core i7 mini from 2014. OK. -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-devel] [PATCH] configure: add --disable-he-aac option
On Wed, 1 Feb 2023, at 15:56, Hendrik Leppkes wrote: > On Wed, Feb 1, 2023 at 3:33 PM Kristofer Björkström > wrote: >> >> Make it possible to disable HE and HEv2 support for AAC. To avoid >> patents in HE-AAC. >> > > I don't feel like this adds a good precedence to our codebase. We > generally ignore patents, because every codec is littered with them. > Having options to cherry-pick which patents are enabled and which are > not is not only very ugly, but also impossible to track or make any > guarantees on, so I think we should not even start. I agree here. Maybe AAC-LC and Main are patent-free, but that is a big maybe and that depends heavily on the country. jb -- Jean-Baptiste Kempf - President +33 672 704 734 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
