Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: Alex Agranovsky <alex@sighthound.com>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] h264 PPS processing oddity
Date: Sun, 15 May 2022 18:26:43 +0200
Message-ID: <DB6PR0101MB221456C901B9398755D6AB828FCC9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <8460c498-eaae-aa78-f1df-1ac897fea59e@sighthound.com>

Alex Agranovsky:
> Hello,
> 
> 
> I've been chasing the problem with VideoToolbox failures to decode on
> iOS and Apple Silicone described in https://trac.ffmpeg.org/ticket/9713
> 
> As I've mentioned in the ticket, the problem seems to boil down to the
> last byte of PPS "disappearing" by the time we initialize VideoToolbox
> decoder. For some reason, Apple doesn't seem to mind on Intel, but fails
> on iOS/M1.
> 
> At this point I find myself in the area where I'm not 100% familiar with
> the code -- can't be sure whether the last byte of PPS isn't extracted
> and stored by design, or is it a bug.
> 
> Any chance I could get some assistance looking at this? I'm BCC'ing a
> couple of people who recently contributed to the relevant modules; hope
> it's not too much of an imposition.
> 
> Thanks in advance!
> 
> - Alex
> 

This patchset:
http://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/296244.html (in
particular 6/6) look like they are intended to fix the issue you reported.

- Andreas
_______________________________________________
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-15 16:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <8460c498-eaae-aa78-f1df-1ac897fea59e@sighthound.com>]

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=DB6PR0101MB221456C901B9398755D6AB828FCC9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
    --to=andreas.rheinhardt@outlook.com \
    --cc=alex@sighthound.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