Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Devin Heitmueller <devin.heitmueller@ltnglobal.com>
To: Dennis Mungai <dmngaie@gmail.com>
Cc: Devin Heitmueller <dheitmueller@ltnglobal.com>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC PATCH 3/5] yadif: Properly preserve CEA-708 closed captions
Date: Sat, 18 Mar 2023 19:20:12 -0400
Message-ID: <CAHGibzHAK7Ho9rxs4N0dR9eYHrgeCo3QidC8JqvfT9i=CyDvLA@mail.gmail.com> (raw)
In-Reply-To: <CAKKYfmHdjn5ZCXCTzssHScs435Ab5_SYikD7guAwGngApSjz2g@mail.gmail.com>

Hello Dennis,

On Sat, Mar 18, 2023 at 11:48 AM Dennis Mungai <dmngaie@gmail.com> wrote:
> Hello Devin,
>
> How would this be propagated (or replicated) in other deinterlacers, namely Intel's OneVPL based deinterlace_qsv, vpp_qsv and VAAPI's deinterlace_vaapi?

So I was focused mainly on the video filters that I use regularly,
which didn't include the hardware accelerated ones.  That said, if you
look at the patches themselves, they're actually only a few lines of
code that need to be added to the individual filters, so the
maintainers of those filters should have little difficulty reusing the
framework.

I would be quite happy to see other filters reuse the same mechanism,
rather than reinventing the wheel, and I intentionally tried to
minimize the amount of code required by modules to make use of the
framework.

Devin

-- 
Devin Heitmueller, Senior Software Engineer
LTN Global Communications
o: +1 (301) 363-1001
w: https://ltnglobal.com  e: devin.heitmueller@ltnglobal.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-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2023-03-18 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 20:09 [FFmpeg-devel] [RFC PATCH 0/5] Properly handle CEA-708 caption data when transcoding Devin Heitmueller
2023-03-17 20:09 ` [FFmpeg-devel] [RFC PATCH 1/5] ccfifo: Properly handle CEA-708 captions through framerate conversion Devin Heitmueller
2023-03-17 20:09 ` [FFmpeg-devel] [RFC PATCH 2/5] vf_fps: properly preserve CEA-708 captions Devin Heitmueller
2023-03-17 20:09 ` [FFmpeg-devel] [RFC PATCH 3/5] yadif: Properly preserve CEA-708 closed captions Devin Heitmueller
2023-03-18 15:48   ` Dennis Mungai
2023-03-18 23:20     ` Devin Heitmueller [this message]
2023-03-17 20:09 ` [FFmpeg-devel] [RFC PATCH 4/5] tinterlace: " Devin Heitmueller
2023-03-18 17:12   ` Thomas Mundt
2023-03-18 23:22     ` Devin Heitmueller
2023-03-19 16:50       ` Thomas Mundt
2023-03-19 17:33         ` Devin Heitmueller
2023-03-17 20:09 ` [FFmpeg-devel] [RFC PATCH 5/5] vf_ccrepack: Add new filter to repack CEA-708 side data Devin Heitmueller
2023-03-17 23:23 ` [FFmpeg-devel] [RFC PATCH 0/5] Properly handle CEA-708 caption data when transcoding BUCCIANTINI Francesco - ADECCO
2023-03-18 23:16   ` Devin Heitmueller

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='CAHGibzHAK7Ho9rxs4N0dR9eYHrgeCo3QidC8JqvfT9i=CyDvLA@mail.gmail.com' \
    --to=devin.heitmueller@ltnglobal.com \
    --cc=dheitmueller@ltnglobal.com \
    --cc=dmngaie@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