Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: always use the same path for setting InputStream.[next_]dts
Date: Thu, 04 May 2023 20:50:20 +0200
Message-ID: <168322622093.3843.8267699107459343430@lain.khirnov.net> (raw)
In-Reply-To: <20230504121258.GD3718108@pb2>

Quoting Michael Niedermayer (2023-05-04 14:12:58)
> On Tue, May 02, 2023 at 09:31:35AM +0000, Anton Khirnov wrote:
> > ffmpeg | branch: master | Anton Khirnov <anton@khirnov.net> | Wed Apr 26 10:51:38 2023 +0200| [129c7bf53fbe2be4f5483ecf6fc036ff9caf05cf] | committer: Anton Khirnov
> > 
> > fftools/ffmpeg: always use the same path for setting InputStream.[next_]dts
> > 
> > Currently those are set in different ways depending on whether the
> > stream is decoded or not, using some values from the decoder if it is.
> > This is wrong, because there may be arbitrary amount of delay between
> > input packets and output frames (depending e.g. on the thread count when
> > frame threading is used).
> > 
> > Always use the path that was previously used only for streamcopy. This
> > should not cause any issues, because these values are now used only for
> > streamcopy and discontinuity handling.
> > 
> > This change will allow to decouple discontinuity processing from
> > decoding and move it to ffmpeg_demux. It also makes the code simpler.
> > 
> > Changes output in fate-cover-art-aiff-id3v2-remux and
> > fate-cover-art-mp3-id3v2-remux, where attached pictures are now written
> > in the correct order. This happens because InputStream.dts is no longer
> > reset to AV_NOPTS_VALUE after decoding, so streamcopy actually sees
> > valid dts values.
> > 
> > > http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=129c7bf53fbe2be4f5483ecf6fc036ff9caf05cf
> > ---
> > 
> >  fftools/ffmpeg.c                          | 34 +++++--------------------------
> >  tests/ref/fate/cover-art-aiff-id3v2-remux | 34 +++++++++++++++----------------
> >  tests/ref/fate/cover-art-mp3-id3v2-remux  | 22 ++++++++++----------
> >  3 files changed, 33 insertions(+), 57 deletions(-)
> 
> Causes assertion failures
> 
> Assertion pkt->duration >= 0 failed at fftools/ffmpeg.c:1502
> Aborted (core dumped)
> 
> ill send you the file privately

Should be fixed by the TAK patchset I just sent.

-- 
Anton Khirnov
_______________________________________________
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-05-04 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230502093136.B998A4107DA@natalya.videolan.org>
2023-05-04 12:12 ` Michael Niedermayer
2023-05-04 18:50   ` Anton Khirnov [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=168322622093.3843.8267699107459343430@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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