Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 6/6] lavu/frame: deprecate AVFrame.pkt_{pos, size}
Date: Wed, 15 Mar 2023 00:00:06 +0100
Message-ID: <20230314230006.GC375355@pb2> (raw)
In-Reply-To: <20230311105452.12933-1-anton@khirnov.net>


[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]

On Sat, Mar 11, 2023 at 11:54:52AM +0100, Anton Khirnov wrote:
> These fields are supposed to store information about the packet the
> frame was decoded from, specifically the byte offset it was stored at
> and its size.
> 
> However,
> - the fields are highly ad-hoc - there is no strong reason why
>   specifically those (and not any other) packet properties should have a
>   dedicated field in AVFrame; unlike e.g. the timestamps, there is no
>   fundamental link between coded packet offset/size and decoded frames
> - they only make sense for frames produced by decoding demuxed packets,
>   and even then it is not always the case that the encoded data was
>   stored in the file as a contiguous sequence of bytes (in order for pos
>   to be well-defined)

> - pkt_pos was added without much explanation, apparently to allow
>   passthrough of this information through lavfi in order to handle byte
>   seeking in ffplay. That is now implemented using arbitrary user data
>   passthrough in AVFrame.opaque_ref.

One intended use i remember was that errors are detected after decoding,
be that bitstream, metadata, aspect ratio, yuv type, ...
while the location of the error is in the source file around the packets
position. pkt_pos allows one to patch errors in the source file without
remuxing

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The worst form of inequality is to try to make unequal things equal.
-- Aristotle

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: 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:[~2023-03-14 23:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 11:56 [FFmpeg-devel] [PATCH 1/6] lavc/decode: stop mangling last_pkt_props->opaque Anton Khirnov
2023-03-10 11:56 ` [FFmpeg-devel] [PATCH 2/6] fftools/ffprobe: stop using AVFrame.pkt_{pos, size} Anton Khirnov
2023-03-12 15:04   ` Stefano Sabatini
2023-03-10 11:56 ` [FFmpeg-devel] [PATCH 3/6] fftools/ffplay: drop an unused function argument Anton Khirnov
2023-03-12 15:05   ` Stefano Sabatini
2023-03-10 11:56 ` [FFmpeg-devel] [PATCH 4/6] fftools/ffplay: depend on avfilter Anton Khirnov
2023-03-10 11:56 ` [FFmpeg-devel] [PATCH 5/6] fftools/ffplay: stop using AVFrame.pkt_pos Anton Khirnov
2023-03-13 20:44   ` Marton Balint
2023-03-15 14:18     ` [FFmpeg-devel] [PATCH v2 4/5] " Anton Khirnov
2023-03-10 11:56 ` [FFmpeg-devel] [PATCH 6/6] lavu/frame: deprecate AVFrame.pkt_{pos, size} Anton Khirnov
2023-03-10 12:18   ` James Almer
2023-03-11 10:54     ` [FFmpeg-devel] [PATCH v2 " Anton Khirnov
2023-03-14 23:00       ` Michael Niedermayer [this message]
2023-03-15 15:03         ` Anton Khirnov
2023-03-10 12:11 ` [FFmpeg-devel] [PATCH 1/6] lavc/decode: stop mangling last_pkt_props->opaque Anton Khirnov
2023-03-10 12:39 ` Martin Storsjö
2023-03-11 10:51   ` Anton Khirnov

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=20230314230006.GC375355@pb2 \
    --to=michael@niedermayer.cc \
    --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