Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Eran Kornblau <eran.kornblau@kaltura.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libx265: support ATSC A/53 captions
Date: Tue, 8 Nov 2022 15:19:34 +0000
Message-ID: <AS8PR04MB89131DB5F6C77B25CE1B4DACF53F9@AS8PR04MB8913.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <fbedf05f-124e-07a2-28d5-a182af42b720@rothenpieler.org>

[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]

> 
> On 08.11.2022 15:25, Eran Kornblau wrote:
> >>
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of 
> >> Timo Rothenpieler
> >> Sent: Tuesday, 8 November 2022 13:33
> >> To: ffmpeg-devel@ffmpeg.org
> >> Subject: Re: [FFmpeg-devel] [PATCH] libx265: support ATSC A/53 
> >> captions
> >>
> >>>
> >>> The attached patch adds rendering of ATSC A/53 captions as HEVC SEI messages.
> >>> The option name/implementation is aligned with the corresponding libx264 feature.
> >>
> >> What frees the sei data on success?
> >>
> > Thanks Timo, good point!
> >
> > I missed the fact that libx264 gets a callback for freeing the SEI payloads (sei_free).
> > It seems libx265 does not have this option, so I added some 'for' loop to free the payloads after the call to encoder_encode.
> >
> > In addition:
> > 1. I added av_memdup on the 'user-data-unregistered' side data so that it won't be freed twice.
> > 2. I added a 'free_picture' function for freeing the x265_picture in case of error.
> > (both changes are aligned with the implementation in libx264.c)
> >
> > Updated patch attached.
> 
> One nit: splitting the first line of free_picture() in two isn't really neccesary and makes the function a bit uglier.
> 
Fixed

> One small problem: libx265 now needs to select atsc_a53 in configure, analog to how libx264 and all the others do.
> Otherwise the file containing the a53 code might not get compiled.
> 
Fixed

> LGTM otherwise
> 
Thanks!

Eran

> > While checking the point you raised, I ran some libx265 transcode with valgrind, and it reported errors unrelated to this patch.
> > Attaching the full output, in case anyone wants to have a look.
> 
> x265 has a bunch of issues related to SEI data.
> See for example https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.ffmpeg.org%2Fticket%2F9666%23comment%3A1&amp;data=05%7C01%7C%7C5cd31da5382f4946e0c508dac198454d%7C0c503748de3f4e2597e26819d53a42b6%7C1%7C0%7C638035156992542567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=9AdmTE%2B4dzHED8KLN0ps2GvvynacXfrWjhVJk4SBWJo%3D&amp;reserved=0
> 
> i.e. if the number of per-frame sei data ever increases past its initial count, it'll just straight up explode.
> _______________________________________________


[-- Attachment #2: 0001-libx265-support-ATSC-A-53-captions.patch --]
[-- Type: application/octet-stream, Size: 7277 bytes --]

[-- Attachment #3: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2022-11-08 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 16:28 Eran Kornblau
2022-10-25  4:23 ` Eran Kornblau
2022-11-01  7:42   ` Eran Kornblau
2022-11-08  6:49     ` Eran Kornblau
2022-11-08 11:33       ` Timo Rothenpieler
2022-11-08 14:25         ` Eran Kornblau
2022-11-08 14:48           ` Timo Rothenpieler
2022-11-08 15:19             ` Eran Kornblau [this message]
2022-11-10 15:29               ` Timo Rothenpieler

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=AS8PR04MB89131DB5F6C77B25CE1B4DACF53F9@AS8PR04MB8913.eurprd04.prod.outlook.com \
    --to=eran.kornblau@kaltura.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