Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: "Cosmin Stejerean" <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] [PATCH v3 2/2] avcodec: add external dec libvvdec for H266/VVC
Date: Mon, 20 May 2024 16:24:34 +0000
Message-ID: <0101018f96d1ad54-6ff34d4b-0778-45c9-87de-150010b0a1be-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <1C568FFB-034F-4031-8D64-504BEB687DF0@remlab.net>

On May 18, 2024, at 10:48 PM, Rémi Denis-Courmont <remi@remlab.net> wrote:

Le 18 mai 2024 21:55:04 GMT+03:00, Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org> > a écrit :


On May 18, 2024, at 7:04 AM, Nuo Mi <nuomi2021@gmail.com <mailto:nuomi2021@gmail.com> > wrote:

This happened many years ago. See the discussion here:
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201221060710.12230-6-nuomi2021@gmail.com/#60589 <https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201221060710.12230-6-nuomi2021@gmail.com/#60589> 
Now that we have an internal vvc decoder, we can focus on improving it.
As for the encoder, it is far more complex than the decoder. Reasonable to
wrapper other libraries just like libx264 and libx265...

I'm all for improving the internal decoder, and I agree that the internal decoder should be preferred and be used by default, but it's not clear why that should preclude adding an external decoder as an option.

Adding a disabled-by-default decoder is adding bloat, if there is not a specific known reason why that is needed.

This is especially true for video decoders, where the external decoders typically will have no or worse optimisations for DSP functions, no thread support (or not accessible via libavcodec), 

Is this an actual problem with vvdec? To me it seems like a reasonably optimized decoder with support for threading, etc.

and no integration with hwaccel.

The later point has become a problem even with dav1d...

hwaccel decoding seems somewhat orthogonal


Sometimes bugs are found in the internal decoders

Providing a non-default choice is a poor excuse for a bug. Most users won't know how to do that, 

need better documentation?

and many FFmpeg reverse dependencies don't even allow it.

not sure that designing for the lowest common denominator of reverse dependencies is the best way to do things, but at a minimum one can rebuild ffmpeg with only one decoder enabled to get around this


or some functionality may be missing, and having the option to fallback to an external decoder as a workaround is very useful in practice.

That I can agree, but what do you find missing in the VVC decoder compared to libvvcdec?
_______________________________________________

This I'm not sure, perhaps there is no feature gap? Does the internal VVC decoder supports all features of the Main10 profile?

- Cosmin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2024-05-20 16:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 15:09 [FFmpeg-devel] [PATCH v3 0/2] Add support for H266/VVC encoding Christian Bartnik
2024-05-14 15:09 ` [FFmpeg-devel] [PATCH v3 1/2] avcodec: add external enc libvvenc for H266/VVC Christian Bartnik
2024-05-14 16:49   ` Andreas Rheinhardt
2024-05-16 15:22     ` Christian
2024-05-24 13:03       ` Nuo Mi
2024-05-14 15:09 ` [FFmpeg-devel] [PATCH v3 2/2] avcodec: add external dec libvvdec " Christian Bartnik
2024-05-14 16:28   ` Lynne via ffmpeg-devel
2024-05-17 10:15     ` Christian
     [not found]     ` <66AD9495-91D5-40C7-B3FA-CFA222ED3D7E@cosmin.at>
2024-05-17 17:20       ` Cosmin Stejerean via ffmpeg-devel
2024-05-17 19:14         ` Kieran Kunhya
2024-05-18 14:04         ` Nuo Mi
     [not found]           ` <592133D9-BC0A-4220-B717-66408E9F435B@cosmin.at>
2024-05-18 18:55             ` Cosmin Stejerean via ffmpeg-devel
2024-05-19  5:48               ` Rémi Denis-Courmont
     [not found]                 ` <7C02B7A4-B6C6-477F-A185-0E8D082788B2@cosmin.at>
2024-05-20 16:24                   ` Cosmin Stejerean via ffmpeg-devel [this message]
     [not found]                 ` <8FDC7AD3-E2E8-4E40-9DAE-63C99AE64C49@cosmin.at>
2024-05-20 16:33                   ` Cosmin Stejerean via ffmpeg-devel
2024-05-20 18:03                     ` Rémi Denis-Courmont
     [not found]                       ` <6BF4ADA7-76D0-48C6-9F48-588766A72F85@cosmin.at>
2024-05-20 18:39                         ` Cosmin Stejerean via ffmpeg-devel
2024-05-20 19:01                           ` Rémi Denis-Courmont
     [not found]                             ` <8C6DE791-418E-4464-82E4-9A6D50E4E4D0@cosmin.at>
2024-05-20 19:33                               ` Cosmin Stejerean via ffmpeg-devel
2024-05-20 20:05                                 ` Rémi Denis-Courmont
     [not found]                                   ` <2E0614A4-8D72-4100-BE9C-D91B28F8EDB6@cosmin.at>
2024-05-20 20:38                                     ` Cosmin Stejerean via ffmpeg-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0101018f96d1ad54-6ff34d4b-0778-45c9-87de-150010b0a1be-000000@us-west-2.amazonses.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=cosmin@cosmin.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git