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 2/5] Revert "avcodec/decode: use a packet list to store packet properties"
Date: Mon, 5 Dec 2022 22:26:58 +0100
Message-ID: <20221205212658.GZ3806951@pb2> (raw)
In-Reply-To: <20221204215227.4186-2-jamrial@gmail.com>


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

On Sun, Dec 04, 2022 at 06:52:24PM -0300, James Almer wrote:
> The idea behind last_pkt_props was to store the properties of the last packet
> fed to the decoder. Any sort of queueing required by decoders that consume
> several packets before they start outputting frames should be done by the
> decoders in question. An example of this is in the libdav1d wrapper.
> 
> This is required to maintain its contents during flush, and for the following
> commits that will fix last_pkt_props in frame threading scenarios.
> 
> This revers commit 022a12b306ab2096e6ac9fc9b149828a849d65b2.
> 
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
>  libavcodec/avcodec.c    | 10 ---------
>  libavcodec/decode.c     | 47 ++++++-----------------------------------
>  libavcodec/internal.h   |  1 -
>  tests/ref/fate/flcl1905 |  2 +-
>  4 files changed, 8 insertions(+), 52 deletions(-)

This causes a wrong looking final timestamps
for example with V-codecs/WMVP/Arlington.wmv
./ffmpeg -i Arlington.wmv  -f framecrc -

 0,       4410,       4410,        1,   115200, 0x12ea3f01
 0,       4411,       4411,        1,   115200, 0xb376241c
 1,    8105977,    8105977,    10240,    40960, 0xbbacee03
+1,    8105977,    8105977,     2048,     8192, 0x985d6153
 0,       4412,       4412,        1,   115200, 0xc214049c
 0,       4413,       4413,        1,   115200, 0xcdcddf9c
 0,       4414,       4414,        1,   115200, 0xcbd5c21d
 0,       4415,       4415,        1,   115200, 0xed32b414
-1,    8116217,    8116217,     2048,     8192, 0x985d6153


[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Homeopathy is like voting while filling the ballot out with transparent ink.
Sometimes the outcome one wanted occurs. Rarely its worse than filling out
a ballot properly.

[-- 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:[~2022-12-05 21:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 21:52 [FFmpeg-devel] [PATCH 1/5] avcodec/binkaudio: clear pts when returning more than one frame per input packet James Almer
2022-12-04 21:52 ` [FFmpeg-devel] [PATCH 2/5] Revert "avcodec/decode: use a packet list to store packet properties" James Almer
2022-12-05 21:26   ` Michael Niedermayer [this message]
2022-12-06  0:03     ` [FFmpeg-devel] [PATCH 2/6] avcodec/wmadec: clear pts when returning a frame during flush James Almer
2022-12-06  8:27       ` Paul B Mahol
2022-12-06 11:42         ` James Almer
2022-12-04 21:52 ` [FFmpeg-devel] [PATCH 3/5] avcodec/decode: don't set last_pkt_props->size James Almer
2022-12-04 21:52 ` [FFmpeg-devel] [PATCH 4/5] avcodec/pthread_frame.c: keep the last_pkt_props from worker threads in sync with the user context James Almer
2022-12-04 21:52 ` [FFmpeg-devel] [PATCH 5/5] avcodec/mpeg4videodec: duplicate the last decoded frame when the last coded frame was skipped James Almer
2022-12-06  9:17   ` Andreas Rheinhardt
2022-12-06 11:21     ` James Almer
2022-12-12 11:37   ` James Almer

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=20221205212658.GZ3806951@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