Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavfi: add quirc filter
Date: Fri, 29 Dec 2023 12:57:15 +0100
Message-ID: <ZY60G9OX+JDZXyix@mariano> (raw)
In-Reply-To: <4425335c-a8d6-448f-9387-676e593ad3b8@gmail.com>

On date Wednesday 2023-12-27 21:57:19 -0300, James Almer wrote:
> On 12/27/2023 8:20 PM, Stefano Sabatini wrote:
[...]
> > > I really think this should be ported as a native filter. It's not big and
> > > complex like a scaler (sws, zscale) which should not live within
> > > libavfilter.
> > 
> > > Any change can be contributed back to libquirc
> > 
> > This is not realistic, given that a reimplementation would be possibly
> > completely refactored to fit into FFmpeg.
> > 
> > > (A library
> > > that's not going to be abandoned like it happened with libdcadec after it
> > > was merged into lavc,
> > 
> > OTOH, this library is quite outside the scope of the FFmpeg, so it
> > makes sense to keep it as external dependency. This is a quite
> > different use case than a decoder, a QR-decoder library can make sense
> > outside of a multimedia library, for a decoder you would need a
> > complete multimedia library anyway.
> > 
> > I was checking the code, and porting would be a serious effort and
> > comprise several thousands lines of code (against the moderate effort
> > of wrapping it - which is already done), also some of the logic would
> > not really fit into FFmpeg because it is quite specific to this
> > application domain (QR code decoding), so it makes sense for it to
> > live within an external library. Not to mention that this would be
> > a duplication of effort.
> 
> Image analysis is within FFmpeg's scope, which QR code identification and
> decoding would be about.
> 
> > 
> > *Unless* someone is willing to port/reimplement the code, but this
> > should not be a blocker for the wrapper and can be done as a separate
> > step.
> 
> No, i'm not blocking anything. Just stating that ideally this would be a
> native module.

I'm not against this of course, but as I already stated this would
require more effort. It is probably worth it (polynomials and Galois
fields based error correction) as they would be probably reused in
other parts of the code. Ditto for the QR encoder.

But I plan to have this functionality in with the wrappers - this
should also help with an eventual native port of the features.

I plan to push this patch in a few days, unless I see comments.

Thanks for the feedback.
_______________________________________________
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".

  reply	other threads:[~2023-12-29 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 16:20 Stefano Sabatini
2023-12-26 19:08 ` Andreas Rheinhardt
2023-12-27  1:20   ` Stefano Sabatini
2023-12-26 19:21 ` James Almer
2023-12-27  1:19   ` Stefano Sabatini
2023-12-27  1:25 ` Stefano Sabatini
2023-12-27  1:33   ` James Almer
2023-12-27 11:37     ` Stefano Sabatini
2023-12-27 14:49       ` Tomas Härdin
2023-12-27 17:16       ` James Almer
2023-12-27 23:20         ` Stefano Sabatini
2023-12-28  0:57           ` James Almer
2023-12-29 11:57             ` Stefano Sabatini [this message]
2024-01-02 21:13               ` Stefano Sabatini
2023-12-28 10:24           ` Tomas Härdin

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=ZY60G9OX+JDZXyix@mariano \
    --to=stefasab@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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