Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Merge QSV decoder SEI patch into master?
Date: Thu, 5 May 2022 22:08:01 +0000
Message-ID: <DM8P223MB036594FC9985F7A1C70E561DBAC29@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAJ1c-E6F=wjY1bvnu0MOwSF5qKv_o32_twxTpLsRTTpzy6KMHQ@mail.gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Vladislav Sorkin
> Sent: Thursday, May 5, 2022 10:48 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] Merge QSV decoder SEI patch into master?
> 
> Would it be possible to merge the following patch into the master
> branch?
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/DM8P223MB03655F44A7B
> F01132BB2959DBA669@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM/
> 
> This patch provides the QSV decoder with SEI message and ATSC A/53
> caption
> capability.
> 
> I understand some time has passed since the patch was originally
> generated
> but I was able to apply it with minimal adjustments and the code works
> as
> desired in regards to captions.
> 
> We'd like to see the QSV decoder become more feature complete.
> 
> If there are any steps necessary to make this happen, please advise.

There's still a pending issue which I'm waiting to get resolved:

https://github.com/Intel-Media-SDK/MediaSDK/issues/2597
(not the OP, start from the bottom)

Second part that needs to be done is some re-ordering to properly
associate SEI data with frames in case B-frames are used.
(as Haihao had pointed out)

It's not forgotten, though.

Regards,
softworkz



_______________________________________________
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-05-05 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 20:47 Vladislav Sorkin
2022-05-05 22:08 ` Soft Works [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=DM8P223MB036594FC9985F7A1C70E561DBAC29@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.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