From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavfi: add quirc filter
Date: Thu, 28 Dec 2023 11:24:00 +0100
Message-ID: <2f41d38f04ffa0d3d4eb3c7c5d5e6be5e6715f80.camel@haerdin.se> (raw)
In-Reply-To: <ZYyxJXydCa5h+VMs@mariano>
tor 2023-12-28 klockan 00:20 +0100 skrev Stefano Sabatini:
> 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.
This is the same point I've been making lately. With an appropriate
build system a lot of effort can be saved. It's only really when
existing implementations are too slow or mising features that it might
be necessary to reimplement them.
/Tomas
_______________________________________________
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".
prev parent reply other threads:[~2023-12-28 10:24 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
2024-01-02 21:13 ` Stefano Sabatini
2023-12-28 10:24 ` Tomas Härdin [this message]
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=2f41d38f04ffa0d3d4eb3c7c5d5e6be5e6715f80.camel@haerdin.se \
--to=git@haerdin.se \
--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