From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [POC][PATCHSET] Add qrencodesrc source Date: Sat, 2 Dec 2023 20:27:05 +0100 Message-ID: <ZWuFCTJfCh9Ygmz+@mariano> (raw) In-Reply-To: <52546995f54f65aa42abc7990fe19ab3786dd322.camel@haerdin.se> On date Friday 2023-12-01 16:08:23 +0100, Tomas Härdin wrote: > tor 2023-11-30 klockan 15:39 +0000 skrev Cosmin Stejerean via ffmpeg- > devel: > > > > > On Nov 30, 2023, at 03:07, Tomas Härdin <git@haerdin.se> wrote: > > > > > > tor 2023-11-30 klockan 01:49 +0100 skrev Stefano Sabatini: > > > > This is meant to introduce functionality to handle QR codes. > > > > > > Why? > > > > > > > The why seems to be answered below the section you quoted in the > > original email > > > > > QR codes are robust to lossy coding, therefore it should be > > > possible to use them to compare a generated video with a reference > > > one (in case > > they cannot be compared frame-by-frame). > > Is the intent to generate per-frame QR codes? I guess that has some > merit. [...] Yes, this was the main use case (if you see the patches I'm reusing the same expansion mechanism we have in drawtext, for example we can specify "%{n}" to encode the picture number). Then I plan to extend it with a filter overlaying on the input frame, and with a decoder (thinking to use again an external library - quirc - assuming there are no objections in that direction). > Otherwise it seems pointless if it's just for generating a > single QR code which could just as well be done with an external > program and then overlaying the resulting image. But in general, having integrated QR encoding it's more than overlaying a single static QR code, you might want to encode some specific frame metadata or change/disable the QR to encode through a filter command, so it would be IMO good to have it for many different use cases. _______________________________________________ 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-02 19:27 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 0:49 Stefano Sabatini 2023-11-30 0:49 ` [FFmpeg-devel] [PATCH 1/2] lavfi: introduce textutils Stefano Sabatini 2023-12-03 15:05 ` Stefano Sabatini 2023-12-09 18:12 ` Stefano Sabatini 2023-12-16 15:35 ` Stefano Sabatini 2024-01-03 12:58 ` Timo Rothenpieler 2024-01-03 15:50 ` Stefano Sabatini 2023-12-06 20:20 ` Nicolas George 2023-11-30 0:49 ` [FFmpeg-devel] [PATCH 2/2] lavfi: add qrencodesrc source Stefano Sabatini 2023-12-09 18:13 ` Stefano Sabatini 2023-12-11 20:59 ` Kyle Swanson 2023-12-11 23:34 ` Stefano Sabatini 2023-12-17 18:00 ` Stefano Sabatini 2023-12-24 17:43 ` Stefano Sabatini 2024-01-02 21:09 ` Stefano Sabatini 2023-11-30 11:07 ` [FFmpeg-devel] [POC][PATCHSET] Add " Tomas Härdin 2023-11-30 11:21 ` Paul B Mahol 2023-12-02 19:19 ` Stefano Sabatini 2023-11-30 11:54 ` Nicolas George [not found] ` <D4F91B2F-6380-48AA-8883-315FA76CA828@cosmin.at> 2023-11-30 15:39 ` Cosmin Stejerean via ffmpeg-devel 2023-12-01 15:08 ` Tomas Härdin 2023-12-02 19:27 ` Stefano Sabatini [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=ZWuFCTJfCh9Ygmz+@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