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: BUCCIANTINI Francesco - ADECCO <francesco.bucciantini.adecco@skytv.it>
Cc: Devin Heitmueller <dheitmueller@ltnglobal.com>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC PATCH 0/5] Properly handle CEA-708 caption data when transcoding
Date: Sat, 18 Mar 2023 19:16:46 -0400
Message-ID: <CAHGibzH=gJQpfm3dJONi4Jeq6nZP=689-PoKqt=erK4MWBw7Hg@mail.gmail.com> (raw)
In-Reply-To: <b5c7dc2a-4750-4336-9e88-0463d16fcf87@email.android.com>

On Fri, Mar 17, 2023 at 7:23 PM BUCCIANTINI Francesco - ADECCO
<francesco.bucciantini.adecco@skytv.it> wrote:
>
> This is indeed very welcome.
> Being able to re-encode from 25i to 50p while preserving subtitles has been something I've been trying to do for a while, so seeing this patch for CEA-708 is definitely a nice thing.
>
> I have a question, though: will something similar be done for OP-47 subtitles too?
> Currently they suffer the same issue when a re-encode changes the frame rate... :(

I don't have any plans to work on OP-47, and I'm not sure if anyone
else does.  While I've done a bit of work with it in the SDI domain,
I'm not super familiar with how it's treated by ffmpeg, or whether a
similar approach is appropriate for dealing with it.  I can say that
the FIFO here is highly specific to the CEA-708 standard, as we have
to disassemble and reassemble the payloads to meet the specification
(i.e. not applicable to OP-47).

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:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 20:09 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
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 [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='CAHGibzH=gJQpfm3dJONi4Jeq6nZP=689-PoKqt=erK4MWBw7Hg@mail.gmail.com' \
    --to=devin.heitmueller@ltnglobal.com \
    --cc=dheitmueller@ltnglobal.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=francesco.bucciantini.adecco@skytv.it \
    /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